BGP Communities

BGP Informational Communities

i3D.net strips all external BGP communities on the AS49544 border routers. If a customer unilaterally attempts to set i3D.net informational communities on their prefix advertisement to AS49544, these will be stripped as well before the rest of the AS49544 import policy is processed. Informational communities that provide knowledge about where (and how) that route was learned are then added to each prefix. There are always two informational tags on a prefix in the AS49544 backbone, one with full location details and one for the generic continental area. These codes are always in the 49544:CTLLL format:

49544: Standard preamble.
C Continent where the route was learned.
T Type of relationship with BGP neighbor.
LLL Location where the route was learned.

Continental codes:

  1. North America
  2. Europe
  3. Asia-Pacific
  4. Oceania
  5. South America
  6. Africa

Relationship codes:

  1. Internal route originated by AS49544
  2. IP transit customer route
  3. Private peering route
  4. Public peering route
  5. Upstream partial IP transit route
  6. Upstream full IP transit route

Location codes:


Examples:

  • 49544:16106 = route learned from full transit in North America, USA, California.
  • 49544:24031 = route learned from public peering in Europe, The Netherlands.
  • 49544:23000 = route learned from private peering in Europe.
  • 49544:35852 = route learned from partial transit in Asia-Pacific, Hong Kong.
  • 49544:22031 = route learned from IP transit customer in Europe, The Netherlands.
  • 49544:14235 = route learned from public peering in North America, Canada, Ontario.


BGP Well-known Communities

i3D.net is aware of well-known BGP communities as defined by the IETF and has currently implemented the following standardized well-known BGP communities:

  • RFC1997 = 65535:65281 = NO_EXPORT
  • RFC3765 = 65535:65284 = NO_PEER

Please note that 65535:65284 has the same effect as 65500:65000 per the BGP Action Community documentation described later in the document.
 

BGP Blackhole Communities

i3D.net currently provides a blackhole community which takes global effect. You can trigger a blackhole for IPv4 and IPV6 prefixes that you're already permitted to advertise by tagging the route with 49544:666. This works for the whole prefix, all the way down to /32 and /128 size: so please take great care when using this functionality.

 

BGP LocalPref Communities

By default i3D.net customers are imported to BGP with LocalPref 5000. However, i3D.net provides a LocalPref manipulation community that will allow you to control the link over which traffic comes in for active-passive backup purposes. You can set the LocalPref to 4000 by tagging the route with 49544:4000, which is still higher than non-customer routes.

BGP Action Communities

i3D.net provides a set of BGP action communities allowing customers to manipulate routing policy for their prefixes within the backbone. This functionality only works for AS49544 peering and transit BGP neighbors, our transit customers always receive every prefix without 49544 prepends. Please note we already take great care when announcing our prefixes outside the originating continent to prevent hairpinning. BGP action communities are always in the action:target format, using the following syntax:


Action:

  • 65501 = Prepend the AS-path once using AS49544, results in _TARGET_49544_49544_CUSTOMER$
  • 65502 = Prepend the AS-path twice using AS49544, results in _TARGET_49544_49544_49544_CUSTOMER$
  • 65503 = Prepend the AS-path thrice using AS49544, results in _TARGET_49544_49544_49544_49544_CUSTOMER$
  • 65500 = Do not advertise route to target (AKA no-export).


Target:

  • IP transit providers:
    • 174 = Cogent Communications
    • 2914 = NTT Communications
    • 3549 = Level(3) Communications (formerly known as Global Crossing)
    • 3356 = Level(3) Communications
    • 6453 = TATA Communications
    • 65535 = All transit providers
       
  • Regional peering codes:
    • 65000 = All worldwide peering
    • 65001 = All North American peering
    • 65002 = All European peering
    • 65003 = All Asian-Pacific peering
    • 65004 = All Oceanian peering
    • 65005 = All South American peering
    • 65006 = All African peering
       
  • Internet Exchange codes:
    • 65010 = All peering in the Netherlands
      • 65011 = AMS-IX, Amsterdam
      • 65012 = NL-ix, Rotterdam
      • 65013 = R_iX, Rotterdam
      • 65014 = Asteroid, Amsterdam
    • 65020 = All peering in Germany
      • 65021 = DE-CIX, Frankfurt
      • 65022 = ECIX, Frankfurt
    • 65030 = All peering in the United Kingdom
      • 65031 = LINX LON1, London
      • 65032 = LONAP, London
    • 65040 = All peering in Poland
      • 65041 = PLIX, Warsaw
      • 65042 = TPIX, Warsaw
      • 65043 = EPIX.Katowice, Warsaw
      • 65044 = EPIX.Warszawa-KIX, Warsaw
    • 65050 = All peering in Virginia, USA
      • 65051 = Equinix Ashburn IX, Ashburn VA
      • 65052 = LINX NoVA, Ashburn VA
    • 65060 = All peering in California, USA
      • 65061 = Any2 California, Los Angeles CA
      • 65062 = Equinix Los Angeles IX, Los Angeles CA
      • 65063 = Equinix San Jose IX, Santa Clara CA
      • 65064 = Equinix Palo Alto IX, Santa Clara CA
      • 65065 = SFMIX, Santa Clara CA
    • 65070 = All peering in Australia
      • 65071 = IX Australia NSW, Sydney
      • 65072 = PipeIX NSW, Sydney
      • 65073 = Equinix Sydney IX, Sydney
      • 65074 = MegaIX Sydney, Sydney
      • 65075 = EdgeIX, Sydney
    • 65080 = All peering in Japan
      • 65081 = BBIX Tokyo, Tokyo
      • 65082 = Equinix Tokyo IX, Tokyo
      • 65083 = JPIX Tokyo, Tokyo
    • 65090 = All peering in Brazil
      • 65091 = IX.br São Paulo, Brazil
    • 65100 = All peering in Texas, USA
      • 65101 = Equinix Dallas IX, Dallas TX
      • 65102 = DE-CIX Dallas, Dallas TX
    • 65110 = All peering in South Africa
      • 65111 = NAPAfrica IX Johannesburg, Johannesburg
      • 65112 = angonix, Johannesburg
      • 65113 = JINX, Johannesburg
    • 65120 = All peering in Hong Kong
      • 65121 = HKIX, Hong Kong
      • 65122 = Equinix Hong Kong IX, Hong Kong
      • 65123 = BBIX Hong Kong, Hong Kong
      • 65124 = AMS-IX Hong Kong, Hong Kong
    • 65130 = All peering in the United Arab Emirates
      • 65131 = UAE-IX, Dubai
    • 65140 = All peering in New Jersey, USA
      • 65141 = DE-CIX New York, Newark NJ
    • 65150 = All peering in Illinois, USA
      • 65151 = Equinix Chicago IX, Chicago IL
    • 65160 = All peering in Russia
      • 65161 = MSK-IX, Moscow
      • 65162 = EurasiaPeeringIX, Moscow
      • 65163 = Piter-IX, Moscow
    • 65170 = All peering in Singapore
      • 65171 = Equinix Singapore IX, Singapore
      • 65172 = SGIX, Singapore
      • 65173 = BBIX Singapore, Singapore
    • 65180 = All peering in France
      • 65181 = Equinix Paris IX, Paris
      • 65182 = France-IX Paris, Paris
    • 65190 = All peering in Québec, Canada
      • 65191 = QIX, Montreal
    • 65200 = All peering in Ukraine
      • 65201 = DTEL-IX, Kyiv
      • 65202 = UA-IX, Kyiv
    • 65210 = All peering in Washington, USA
      • 65211 = SIX Seattle, Seattle WA
      • 65212 = Equinix Seattle IX, Seattle WA
    • 65220 = All peering in Spain
      • 65221 = DE-CIX Madrid, Madrid
      • 65222 = Equinix Madrid IX, Madrid
      • 65223 = ESPANIX Madrid Lower-LAN, Madrid

Examples:

  • 65501:3356 = prepend the AS-path for this prefix once towards transit Level(3) Communications.
  • 65500:174 = do not advertise this prefix towards transit Cogent Communications.
  • 65502:65041 = prepend the AS-path for this prefix twice with AS49544 towards peers on PLIX, Warsaw.
  • 65503:65072 = prepend the AS-path for this prefix thrice with AS49544 towards peers on PipeIX NSW, Sydney.