Stellar

BGP Communities

AS14525 BGP Communities
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.

Well-Known Communities

AS14525 supports some well-known BGP communities for routing and export control.
CommunityDescription
65535:1NO_EXPORT Don't export outside AS14525 (RFC1997)
65535:2NO_ADVERTISE Don't export to any other peer, internal or external (RFC1997)
65535:666BLACKHOLE Blackhole traffic to any IPv4 /32 or IPv6 /128 route (RFC7999)

AS14525 Communities

Originated Route Types

Routes to destinations inside AS14525.
CommunityDescription
14525:1Originated Any
14525:2Global Aggregate
14525:3Regional Aggregate
14525:4Metro Aggregate
14525:5POP Aggregate
14525:6Specific Prefix

External Route Types

Routes to destinations outside AS14525.
CommunitiyDescription
14525:1*Customer Route
14525:2*Private Peer Route
14525:3*Public Peer/IX Route
14525:4*Transit Route
In external route type communities, x corresponds to an arbitrary internal identifier. For the purposes of regular expression filtering, one should use a pattern such as ^14525:1[0-9]$ if the intent is to filter all customer routes.

Security Signaling

RPKI

Stellar drops RPKI Invalid announcements at all external peering points. After dropping RPKI Invalids, AS14525 attaches the following communities to each prefix relative to its RPKI state:
CommunityDescription
14525:600RPKI Valid
14525:601RPKI Unknown

Remotely Triggered Black Hole Filtering

Customers and peers may signal to AS14525 to automatically blackhole any host prefix (IPv4 /32 or IPv6 /128) in their allowed address space.Upon import, routes with a blackhole community are propagated to other AS14525 routers, and all traffic to the host is discarded globally. Routes with a blackhole community also have the no-export community appended, so they are never exported from AS14525.
CommunityDescription
14525:666Blackhole traffic to any host route. Equivalent to well-known BLACKHOLE community.
Blackhole CommunityWhile blackhole communities are accepted from transit peers, they are only accepted on routes with an AS_PATH length of 1 (directly originated).

Origin Identifiers

CommunityDescription
14525:0Any route that has ingressed or egressed AS14525
14525:1xxxxRoutes from Region xxx
14525:2xxxRoutes from Country xxx
14525:30xxRoutes from Metro xxx
14525:4xxxRoutes from Point of Presence (POP) xxx
14525:9xxxRoutes from a specific Peer xxx

Region IDs

Region ID numbers map to UN M.49 identifiers.

Country IDs

Country ID numbers map to ISO 3166-1 country identifiers.

Metro IDs

Metros are groups of Points of Presence (POPs) that are geographically and performantly close to one or more groups of customers.
NameID
US West01
US Hawaii02
US Central03
US East04

POP IDs

Each Point of Presence is assigned a unique identifier for the purposes of identification and routing control.
NameIDLocationFacilityRegionCountryRegion
phx01001Phoenix, AZEdgeConneX ECDPHX01US WestUSNorth America
hnl01003Honolulu, HIDRFortressUS HawaiiUSNorth America
gvl01004Greenville, SCDC BLOX GSPUS EastUSNorth America

Peer IDs

ASN(s)NameTypeID
2914NTT America, Inc.Transit001
6939Hurricane ElectricTranist002
1299Arelion/Telia CarrierTranist003
3257GTT CommunicationsLegacy004
7843, 20115, 20001SpectrumPrivate Peer005
701VerizonLegacy006
40300DRFortress: DRFConnectLegacy007
40300DRFortress: DRF-IXIX Route Server008
13335CloudflarePrivate Peer009
22773Cox CommunicationsPrivate Peer010
6248448 IXIX Route Server011
34553PacketFrameCustomer012
24115Equinix ChicagoLegacy013
3356Lumen TechnologiesTransit014
33713Chicago Internet ExchangeLegacy015
36149Hawaiian TelcomPrivate Peer016
8075MicrosoftPrivate Peer017
19035Hawaii Internet ExchangePrivate Peer018
19233Xiber Hawaii (fka Hawaii Dialogix Telecom)Private Peer019
Community ExportAll Origin ID communities are exported to transit, direct, IXP, and customer peers.

Legacy Communities

CommunityDescriptionNotes
14525:50xxMetro Aggregate, where xx is equal to the Metro ID.Currently used to control export of routes within a metro area.

Routing Control

The following communities are used to influence routing decisions within AS14525. Routing control communities are never exported to external peers of AS14525.

Local Preference

Levels

Each local preference community maps to a specific level of preference allowed for the peer type.
Peer TypeDefaultLevel 1Level 2Level 3
Transit150
Public Peer200
Private Peer25050150250
Customer35050250350
Peer Local PreferenceTransit peers may use the local preference communities, however they will only be applied to routes with an AS_PATH length of 1 (directly originated). Local preference communities are not accepted from public peers (IX route servers).

Communities

When using a local preference community, the corresponding local preference will be applied based on peer type.
CommunityDescription
14525:10001Set Local Preference to Level 1
14525:10002Set Local Preference to Level 2
14525:10003Set Local Preference to Level 3

AS Path Prepend

Customers and peers may signal AS14525 to automatically prepend 14525 to route announcements. Prepend communities are only accepted from customers, direct peers, and transit peer routes with an AS_PATH length of 1.Prepending OrderPrepending occurs on export from AS14525.
CommunityDescription
14525:11000Prepend 14525 1x to all peers & customers
14525:21000Prepend 14525 2x to all peers & customers
14525:31000Prepend 14525 3x to all peers & customers
14525:11xxxPrepend 14525 1x to all peers with ID xxx
14525:21xxxPrepend 14525 2x to all peers with ID xxx
14525:31xxxPrepend 14525 3x to all peers with ID xxx
14525:12xxxPrepend 14525 1x to all peers in Region xxx
14525:22xxxPrepend 14525 2x to all peers in Region xxx
14525:32xxxPrepend 14525 3x to all peers in Region xxx
14525:13xxxPrepend 14525 1x to all customers in Region xxx
14525:23xxxPrepend 14525 2x to all customers in Region xxx
14525:33xxxPrepend 14525 3x to all customers in Region xxx
14525:14xxxPrepend 14525 1x to all peers in Country xxx
14525:24xxxPrepend 14525 2x to all peers in Country xxx
14525:34xxxPrepend 14525 3x to all peers in Country xxx
14525:15xxxPrepend 14525 1x to all customers in Country xxx
14525:25xxxPrepend 14525 2x to all customers in Country xxx
14525:35xxxPrepend 14525 3x to all customers in Country xxx
14525:16xxxPrepend 14525 1x to all peers in Metro xxx
14525:26xxxPrepend 14525 2x to all peers in Metro xxx
14525:36xxxPrepend 14525 3x to all peers in Metro xxx
14525:17xxxPrepend 14525 1x to all customers in Metro xxx
14525:27xxxPrepend 14525 2x to all customers in Metro xxx
14525:37xxxPrepend 14525 3x to all customers in Metro xxx
14525:18xxxPrepend 14525 1x to all peers in POP xxx
14525:28xxxPrepend 14525 2x to all peers in POP xxx
14525:38xxxPrepend 14525 3x to all peers in POP xxx
14525:19xxxPrepend 14525 1x to all customers in POP xxx
14525:29xxxPrepend 14525 2x to all customers in POP xxx
14525:39xxxPrepend 14525 3x to all customers in POP xxx

Examples

Prepend Prepend 1x to all Customers & Peers
Cisco IOS
!
ip prefix-list prepend1 permit 192.0.2.0/24
!
route-map as14525-out permit 10
  match ip address prefix-list prepend1
  set community 14525:11000
route-map as14525-out permit 20
!
router bgp 64496
  neighbor 198.51.100.1 remote-as 14525
  address-family ipv4 unicast
    neighbor 198.51.100.1 route-map as14525-out out
!
Juniper JunOS
set policy-options community as14525-prepend1 members 14525:11000
set policy-options prefix-list prepend1 192.0.2.0/24
set policy-options policy-statement as14525-out term prepend1 from prefix-list prepend1
set policy-options policy-statement as14525-out term prepend1 then community add as14525-prepend1
set policy-options policy-statement as14525-out then accept
set protocols bgp group ipv4-as14525 peer-as 14525
set protocols bgp group ipv4-as14525 neighbor 198.51.100.1
set protocols bgp group ipv4-as14525 export as14525-out
Prepend 2x to all Peers in Australia
Cisco IOS
!
ip prefix-list prepend2-australia permit 192.0.2.0/24
!
route-map as14525-out permit 10
  match ip address prefix-list prepend2-australia
  set community 14525:24036
route-map as14525-out permit 20
!
router bgp 64496
  neighbor 198.51.100.1 remote-as 14525
  address-family ipv4 unicast
    neighbor 198.51.100.1 route-map as14525-out out
Juniper JunOS
set policy-options community as14525-prepend2-australia members 14525:24036
set policy-options prefix-list prepend2-australia 192.0.2.0/24
set policy-options policy-statement as14525-out term prepend from prefix-list prepend2-australia
set policy-options policy-statement as14525-out term prepend then community add as14525-prepend2-australia
set policy-options policy-statement as14525-out then accept
set protocols bgp group ipv4-as14525 peer-as 14525
set protocols bgp group ipv4-as14525 neighbor 198.51.100.1
set protocols bgp group ipv4-as14525 export as14525-out
AS PrependingBecause 14525 is automatically prepended to all route announcements, using the above prepend communities yields an AS_PATH of 14525 + N where N is the number of prepends. For example:Given a customer ASN of 64496, and a customer prefix of 192.0.2.0/24, a standard route announcement would look like:
Prefix          AS_PATH
192.0.2.0/24    14525 64496 i
For each available prepend options, the route announcement would look like one of the below examples on export from AS14525:1X PREPEND
Prefix          AS_PATH
192.0.2.0/24    14525 14525 64496 i
2X PREPEND
Prefix          AS_PATH
192.0.2.0/24    14525 14525 14525 64496 i
3X PREPEND
Prefix          AS_PATH
192.0.2.0/24    14525 14525 14525 14525 64496 i

Export Control

No Export

Routes with a No Export community attached are immediately rejected on export, prior to any other policy being applied.
CommunityDescriptionSupport Status
14525:40001Don't export outside of AS14525. Equivalent to well-known NO_EXPORT community.Supported
14525:40002Don't export to any other peer, internal or external. Equivalent to well-known NO_ADVERTISE community.Supported
14525:40003Don't export to peers. Equivalent to well-known NO_EXPORT community, but only applies to peers, not customers.Not yet supported
14525:40004Don't export to customers. Equivalent to well-known NO_EXPORT community, but only applies to customers, not peers.Not yet supported
14525:41xxxDon't export to Peer xxxSupported
14525:42xxxDon't export to peers in Region xxx.Not yet supported
14525:43xxxDon't export to peers in Country xxxNot yet supported
14525:44xxxDon't export to peers in Metro xxxNot yet supported
14525:45xxxDon't export to peers in POP xxx.Not yet supported
14525:46xxxDon't export to customers in Region xxx.Not yet supported
14525:47xxxDon't export to customers in Country xxxNot yet supported
14525:48xxxDon't export to customers in Metro xxx.Not yet supported
14525:49xxxDon't export to customers in POP xxxNot yet supported
Export Only
Routes with an Export Only community attached are immediately rejected on export by any routers where the region, country, metro, or POP does not match the ID specified.
CommunityDescriptionSupport Status
14525:51xxxExport only to Peer xxxSupported
14525:52xxxExport only to peers in Region xxxNot yet supported
14525:53xxxExport only to peers in Country xxxNot yet supported
14525:54xxxExport only to peers in Metro xxxNot yet supported
14525:55xxxExport only to peers in POP xxxNot yet supported
14525:56xxxExport only to customers in Region xxxNot yet supported
14525:57xxxExport only to customers in Country xxxNot yet supported
14525:58xxxExport only to customers in Metro xxxNot yet supported
14525:59xxxExport only to customers in POP xxxNot yet supported

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.