Stellar Technologies leverages BGP Standard Communities to provide granular control of internal and external traffic engineering. This document describes the BGP Communities implemented in AS14525. The information contained herein should be considered authoritative for this purpose.
Many of the below community definitions make use of 4-digit origin identifiers (IDs). These IDs are used to identify routes with common properties, such as geographic location or connectivity at a particular IXP.
|Group Code||Description||Visible to Peers|
|Global - used to identify any and all routes that transit AS14525||✅|
|Location identifier for routes within a region, where ||✅|
|Location identifier for routes within a country, where ||✅|
|Location identifier for routes within a regional area, where ||✅|
|Location identifier for routes within a particular Point of Presence (POP), where ||✅|
|AS14525 Originated - All||✅|
|AS14525 Originated - Regional Aggregate, where ||✅|
|AS14525 Originated - Aggregate||✅|
|AS14525 Originated - Specific Prefix||✅|
|All customer routes||✅|
|All direct peer routes||❌|
|All IXP routes||❌|
|All transit routes||❌|
|All routes with a specific global transit provider, where ||❌|
Peer Origin IDs
|Internet Exchange||DRFortress: DRF-IX|
The following communities are used to influence routing decisions within AS14525. Many routing control communities are accepted from customer peers. However, only specific routing control communities are accepted from transit, or direct peers. These are indicated in the table below. Routing control communities are never exported to external peers of AS14525.
|✅||Community will be accepted and applied for valid customer prefixes.|
|🔵||Community will be accepted for routes originating from the peer's AS. Community logic will not apply to the peer's customer or peer routes.|
|🔴||Community will not be accepted.|
|Set LOCAL_PREF to 150 |
Default for transit
|Set LOCAL_PREF to 200||🔴||🔵||🔴|
|Set LOCAL_PREF to 250 |
Default for peers
|Set LOCAL_PREF to 300||✅||🔴||🔴|
|Set LOCAL_PREF to 350 |
Default for customers
|Set LOCAL_PREF to 400||✅||🔴||🔴|
Next Hop Modification
|Blackhole traffic to any IPv4 /32 or IPv6 /128 route||✅||🔵||🔵|
AS Path Prepend
|Don't export to non-customer peers with ID ||✅||🔴||🔴|
|Export only to non-customer peer with ID ||✅||🔴||🔴|
While the blackhole community
14525:999 is accepted from transit peers, it is only accepted on routes with an AS_PATH length of 1 (direct routes).
Changes and Version Control
Where notice of an impending change is deemed necessary, Stellar Technologies will make every attempt to notify affected customers or peers if it is determined that any impact will occur.
Stellar Technologies Inc accepts no liability whatsoever for damages or losses suffered by third parties as a result of their reliance on the information contained herein. By making use of any of information contained herein, the user acknowledges and agrees to these conditions.