Supported by the GlobalNOC at Indiana University

BGP Communities



Internet2 R&E/AS11537 BGP Communities

Updated for NGI on September 2021.

Internet2 External Traffic Influencing Communities

 

International, NREN, and FEDNET peers may set these communities to change the local-preference Internet2 will set on a route:

  • Default - local-pref 500
  • 11537:40 - Low (local-pref 460)
  • 11537:160 - High (local-pref 560)

Internet2 Participants/Connectors may set these communities to change the local-preference Internet2 will set on a route:

  • Default - local-pref 600
  • 11537:140 - Low (local-pref 540)
  • 11537:260 - High (local-pref 620)

 

Internet2 Peers may send the following communities:

  • 11537:2002 - Block prefix to commercial R&E peers.

Internet2 International (ITN) peers may send the below communities for path prepending:

  • 65001:65000 - prepend x1
  • 65002:65000 - prepend x2 
  • 65003:65000 - prepend x3 

 

The following community combination of <CODE>:<ASN> allows you to block or prepend prefixes sent to individual international (ITN) peers.  This is in the process of being deployed, once a peer has had the necessary configuration added, their ASN will be added here.

  • Codes:
    • 65000     - prefixes will not be sent to ITN peer’s ASN
    • 65001     - prefixes will be prepended 1 time to ITN peer’s ASN
    • 65002     - prefixes will be prepended 2 times to ITN peer’s ASN
    • 65003     - prefixes will be prepended 3 time2 to ITN peer’s ASN
    • 65012     - prefixes will only be sent to ITN peer's ASN
  • ITN Peer ASN:
    • 2603     - NORDUnet
    • 20965     - GEANT

 

 

Internet2 Internal Traffic Influencing Communities

 

Internet2-connected Gigapops and connectors with heterogeneous participants (i.e. not all are universities) may need to use these communities to help them pass prefixes appropriately to their participants.  For example, connectors can pass all prefixes on to their university participants, but should not pass commercial or US Fednet prefixes to their commercial or Fednet participants. 

  • 11537:888 - Block to external (Internet2 uses this community to mark prefixes that will not be reannounced to external peers).
  • 11537:902 - non-I2 R&E sites sponsored for connection by members.
  • 11537:910 - sponsored educational groups (Primary state networks).
  • 11537:950 - Internet2 Participants.
  • 11537:2000 - Commercial research - Lab participant.
  • 11537:2001 - Special Commercial prefix used for V6 or multicast.
  • 11537:2500 - Block advertisement to international.
  • 11537:2501 - International.
  • 11537:3000 - FEDNET (US Federal Peer Network).
  • 11537:3500 - Connector Only (Internet2 uses this to mark prefixes sent to connectors but not peers).
  • 11537:4000 - RHCPP (Rural Health Network Groups).
  • 11537:6001 - LHCOne Connectors.
  • 11537:6002 - LHCOne Peers
  • 11537:911 - Remote Triggered Black Hole (RTBH).  Traffic to prefixes tagged for RTBH will be discarded.
  • 65535:666 - Remote Triggered Black Hole (RTBH).  Traffic to prefixes tagged for RTBH will be discarded.

NET+ BGP Communities

While most of Internet2's settlement-free peering with commercial networks is done using I2PX/AS11164, for historical reasons there are still several commercial networks that are part of Internet2's NET+ Cloud program that are peering with Internet2's Research & Education network/AS11537.  Internet2 plans to consolidate all commercial peers into AS11164 during 2024.

Internet2 has implemented a set of BGP communities that, along with your own local BGP import policy, will allow you to control your traffic path to/from the Internet2 NET+ peer networks. All of these communities are specific to individual peer networks and do not affect routing to/from the other peer networks.

  • 11537:5000 - Internet2 NET+ Services.
  • 11537:5002 - Cloud.
  • 11537:5003 - SIP
  • 11537:5004 - Amazon
  • 11537:5007 - Code42
  • 11537:5013 - ServiceNow
  • 11537:5015 - DropBox
  • 11537:5016 - Oracle
  • 11537:5017 - Zoom
  • 11537:5500 - Block to NET+ (Internet2 uses this to mark prefixes that will not be sent to NET+ peers).

The following community combination of <CODE>:<ASN> allows you to block or prepend prefixes sent to individual NET+ peers.

  • Codes:
    • 65000:<ASN>     - prefixes will not be sent to NET+ peer with ASN
    • 65001:<ASN>     - prefixes will be prepended 1 time to NET+ peer with ASN
    • 65002:<ASN>     - prefixes will be prepended 2 times to NET+ peer with ASN
    • 65003:<ASN>     - prefixes will be prepended 3 time2 to NET+ peer with ASN
  • NET+ peer ASN’s
    • 16509     - Amazon
    • 62715     - Code42
    • 16839     - ServiceNow
    • 19679     - DropBox
    • 7160       - Oracle
    • 30103     - Zoom

BLENDED VRF (AS396955) Communities:

  • 396955:9000 - Customer Routes

 

 

 

Internet2 Prefix Advertisement Matrix

 Non-International Peers International Peers Connectors  Commercial Participants Internet2 NET+ 
Federal Peer Network  NO NO YES YES YES
Sponsored Participant  YES YES YES YES YES
Sponsored Education Group Participant  YES YES YES YES YES
Network Participant  YES YES YES YES YES
Commercial Participant  YES YES YES NO NO
Connector Only  NO NO YES NO YES
Internet2 Net+  NO NO YES NO NO

YES indicates prefixes from the network class in that row are sent to the network class in that column.



BGP Community Controls for I2PX / AS11164

BGP Community Controls for I2PX Participants:

Updated for NGI, September 2021.

Per-peer traffic engineering communities:

  • 65000:<ASN> Do not advertise at all to the peer ASN
  • 65001:<ASN> Prepend once toward peer ASN
  • 65002:<ASN> Prepend twice toward peer ASN
  • 65003:<ASN> Prepend thrice toward peer ASN
  • 65009:<ASN> Allow advertisement toward peer ASN if otherwise excluded by more general community control such as 11164:52000

Remote Triggered Black Hole (RTBH) communities:

The following communities can be used to blackhole traffic to more specific netblocks (up to IPv4 /32 and IPv6 /128).

  • 65535:666 Rewrite next hop to discard traffic (RFC7999 well-known community)
  • 11164:53666 Rewrite next hop to discard traffic

Set local-pref on I2PX participant routes:

  • 11164:51240 Set local-pref high (240) to indicate a preferred route
  • default local-pref (220)
  • 11164:51200 Set local-pref low (200) to indicate a backup route

These additional communities are available to alter relative preference. Though available, these communities are rarely used and can take substantial care to appreciate the outcome from using them:

  • 11164:51080 Set preference of learned route Below standard local preference value for Settlement Free Peers.
  • 11164:51050 Set preference of learned route Below standard local preference value for any Transit Providers (no Transit Providers exist to-date).

Additionally, these communities can be used to alter the announcement profile of your routes:

  • 11164:52000 Do not export to peers
  • 11164:52001 Prepend once to peers
  • 11164:52002 Prepend twice to peers
  • 11164:52003 Prepend thrice to peers
  • 11164:52400 Do not export to North American peers (all I2PX peers to-date)
  • 11164:52401 Prepend once to North American peers
  • 11164:52402 Prepend twice to North American peers
  • 11164:52403 Prepend thrice to North American peers
  • 11164:52300 Do not export to Extended Peers

Related communities for future use, but which are in-active in the network, at present:

  • 11164:52200 Do not export to transit
  • 11164:52201 Prepend once to transit
  • 11164:52202 Prepend twice to transit
  • 11164:52203 Prepend thrice to transit
  • 11164:52500 Do not export via peer-links in Asia-Pac
  • 11164:52501 Prepend once via peer-links in Asia-Pac
  • 11164:52502 Prepend twice via peer-links in Asia-Pac
  • 11164:52503 Prepend thrice via peer-links in Asia-Pac
  • 11164:52600 Do not export via peer-links in Europe
  • 11164:52601 Prepend once via peer-links in Europe
  • 11164:52602 Prepend twice via peer-links in Europe
  • 11164:52603 Prepend thrice via peer-links in Europe


Please let us know if you have questions, <mailto:noc@net.internet2.edu>



Internet2 Community Controls for DDoS Scrubbing Service

Keywords: communties, ddos

The following BGP communities are available for Subscribers and Tenants of the DDoS scrubbing service. These are extended communities.

Changing local preference:

  • Default - 200
  • target:396450L:140 - Low
  • target:396450L:260 - High

To announce to ZenEdge to unsuppress a prefix under attack:

  • target:393676L:211 or 6.460:211

To announce to Radware to unsuppress a prefix under attack:

  • target:396450L:723 or 6.3234:723



Your request has been completed.