Customers of RASCOM's RASCOM GiGANET network, connected via BGP protocol (IP Transit) are able to manage local preference for their prefixes and propagation of announcing to different uplinks and peerings.
You can apply BGP community attributes listed below (more specific values are more significant) :
|
Management BGP communities for limiting of prefixes' announcement propagation |
||
|
Towards Russia-transit providers |
20764:120x |
|
|
|
Golden Telecom |
20764:121x |
|
|
Comcor |
20764:122x |
|
|
MTS |
20764:123x |
|
|
TTK |
20764:124x |
|
|
Rostelecom |
20764:125x |
|
Towards Tier-1 global transit providers |
20764:130x |
|
|
|
Level3 |
20764:132x |
|
|
Cogent |
20764:133x |
|
Towards peers at Russian PoPs |
20764:140x |
|
|
|
MSK-IX |
20764:141x |
|
|
Vkontakte SPb AS47541 |
20764:143x |
|
|
Vkontakte MSK AS47542 |
20764:115x |
|
|
Mail.Ru |
20764:116x |
|
|
Corbina |
20764:145x |
|
Towards peers at Europe PoPs |
20764:150x |
|
|
|
DE-CIX |
20764:151x |
|
|
Netnod-IX |
20764:152x |
|
|
AMS-IX |
20764:153x |
|
|
FICIX |
20764:154x |
|
|
LINX |
20764:155x |
|
|
PeeringCZ |
20764:156x |
|
|
FCX Paris |
20764:157x |
|
|
Neterra Frankfurt |
20764:163x |
Where 'x' may be one of the next values:
0 - Do not announce
1 - Add one prepend of "20764" into AS-PATH
2 - Add two prepends of "20764" into AS-PATH
4 - Add four prepends of "20764" into AS-PATH
|
Additional management BGP comunities |
||
|
Blackhole Community |
||
|
Traffic drop towards the customer's address (DDoS mitigation) |
20764:6666 |
You should use this community only for /32 specific prefix |
|
Local preference change |
||
|
To change local preference inside Rascom's network |
20764:2030 |
Minimum in the network (for full reserve use only) |
|
20764:2050 |
Less then transit (uplinks) |
|
|
20764:2070 |
Less then peers |
|
|
20764:2090 |
Less then direct customers |
|
Peering partners connected via BGP could not manage their prefixes announcement .
All prefixes announced by RASCOM's routers have these informational communities :
|
Incoming prefixes marking |
||
|
Main marking |
||
|
Classification and type of transit required |
20764:3000 |
International peer or uplink prefix, transit only towards customers. |
|
20764:3002 |
Customer's prefix, full transit |
|
|
20764:3004 |
Customer's prefix, only Russian transit |
|
|
20764:3006 |
Russian peer or uplink prefix, transit only towards customers. |
|
|
20764:3007 |
Uplink's prefix, transit only towards customers. |
|
|
20764:3008 |
Customer's prefix, transit only towards international |
|
|
Additional marking |
||
|
Source of prefix |
20764:3010 |
SPB POP |
|
20764:3011 |
MSK POP |
|
|
20764:3012 |
Stockholm POP |
|
|
20764:3013 |
Frankfurt POP |
|
|
20764:3014 |
Amsterdam POP |
|
|
20764:3015 |
Helsinki POP |
|
|
20764:3016 |
Tver POP |
|
|
20764:3017 |
Bologoe POP |
|
|
20764:3018 |
Klin POP |
|
|
20764:3019 |
Chudovo, Novgorod, Kirishi POPs |
|
|
20764:3101 |
London PoP |
|
|
20764:3102 |
Paris PoP |
|
|
20764:3103 |
Prague PoP |
|
|
20764:3104 |
Riga PoP |
|
|
20764:3105 |
Kiev PoP |
|
|
20764:3106 |
Tbilisi PoP |
|
|
20764:3020 |
Any international source |
|
|
20764:3021 |
Any russian source |
|
|
20764:3022 |
--reserved source-- |
|
|
20764:3024 |
MSK-IX source |
|
|
20764:3025 |
VKontakte source |
|
|
20764:3026 |
Golden Telecom source |
|
|
20764:3027 |
Global Crossing source |
|
|
20764:3028 |
Level3 source |
|
|
20764:3029 |
Cogent source |
|
|
20764:3030 |
Comcor source |
|
|
20764:3031 |
DE-CIX source |
|
|
20764:3032 |
NETNOD-IX source |
|
|
20764:3033 |
AMS-IX source |
|
|
20764:3034 |
FICIX source |
|
|
20764:3035 |
LINX source |
|
|
20764:3037 |
FranceIX source |
|
|
20764:3039 |
TTK source |
|
|
20764:3040 |
Rostelecom source |
|
|
20764:3096 |
Do not announce outside of the region (for future use) |
|