Supported by the GlobalNOC at Indiana University

BGP Communities

This document describes the BGP Communities used by the Indiana Gigapop. This includes communities that the Gigapop tags simply to add meta-data to BGP prefixes and communities that Gigapop members can set to influence routing behavior at the Gigapop.

BGP Communities the Indiana Gigapop sets:

19782:1001 Tagged to all Indiana Gigapop Member prefixes that receive R&E (ie connectivity to Internet2 and other Gigapop members) connectivity.
19782:1002 Tagged to all Indiana Gigapop Member ipv4 prefixes that receive Commodity Internet connectivity.
19782:1003 Tagged to all Indiana Gigapop Member ipv4 prefixes that receive Settlement-Free Commodity Internet connectivity.
19782:1006 Tagged to all Indiana Gigapop Member ipv6 prefixes that receive R&E (ie connectivity to Internet2 and other Gigapop members) connectivity.
19782:2001 Tagged to all prefixes received from Commodity Internet providers (currently Sprint and Timewarner)
19782:2002 Tagged to all prefixes received from Settlement-Free Peer Networks (currently IQuest, Wintek, and Internet2's Peering Service)
19782:2003 Tagged to all prefixes received from R&E network (currently Internet2 and MREN)
19782:2004 Tagged to all ipv6 prefixes received from R&E network (currently Internet2, BTAA and MREN)

BGP Communities that Gigapop Members can set:

19782:911 Blackhole, GigaPOP will discard traffic toward this prefix. Only members who “own” this prefix may set the 911 community for it.

Local-preference modification (member default is 400, R&E Peer default is 300, Settlement-Free Peers 275, Commodity Peer default is 250 and Commodity Transit default is 200):

19782:150 Causes the Gigapop to add 50 to the default BGP Local-Preference applied to Member prefixes.
19782:50 Causes the Gigapop to subtract 50 from the default BGP Local-Preference applied to Member prefixes
19782:600 Causes the Gigapop to set BGP Local-Prefernece to 600
19782:500 Causes the Gigapop to set BGP Local-Prefernece to 500
19782:200 Causes the Gigapop to set BGP Local-Prefernece to 200

Export modification: default behavior is to send all learned GigaPOP prefixes to all BGP peers. The following communities are available per-prefix to allow members and peers to modify the default behavior (XXXXX=remote ASN. i.e. 65100:87 to block prefix to IU):

65000:XXXX Do not send this prefix to R&E Peer network.
65000:65000 Do not send this prefix to any R&E Peer network.
65001-65003:XXXX GigaPOP should prepend one-three ASs to R&E Peer network.
65100:XXXX Do not send this prefix to GigaPOP member.
65100:65100 Do not send this prefix to any GigaPOP member.
65101-65103:XXXX GigaPOP should prepend one-three ASs to GigaPOP member.
65400:XXXX Do not send this prefix to GigaPOP transit.
65400:65400 Do not send this prefix to any GigaPOP transit.
65401-65403:XXXX GigaPOP should prepend one-three ASs to GigaPOP transit.

Note: The Gigapop may need to change the BGP Communities it tags to prefixes in the future. If this is necessary, we will provide sufficient notification so that any routing policy members may have based on these communities can be updated.

Your request has been completed.