AS1299 BGP Communities

Telia Carrier's Internet Services on AS1299, offers a range of BGP Community options to help control the scope and route preference of traffic.

IP Transit customers can use predefined communities to prepend or deny announcements to specific Telia Carrier peers. Communities are checked at AS1299 exit points, starting with the most specific (i.e. per- peer communities checked before regional communities).

Allowable values for the regional & peer prepend are 0, 1, 2 & 3, denoting the number of prepends to be applied. Telia Carrier’s community support also allows customers to set multiple community actions. For example, simultaneously setting a regional prepend of 1x and a peer- specific prepend of 2x. A prepend of zero is also possible.

PLEASE NOTE: Prepend and Do Not Announce community actions are not available for Content Connect customers.

Telia Carrier offers origin BGP communities to all IP Transit customers as a standard service feature. Origin communities indicate if a prefix was learned from a customer or a peer, and the region in which it was learned.

Customers can request to have the Origin + feature enabled on their services. This provides City level Origin Communities.

Numbering Structure

Community numbering uses the following structure:

• 1299:xyzzz
• Where: 

• x is BGP Neighbour type; 2 for Peers or 3 for Customers
• y is Region; 0 for Europe, 5 for North America or 7 for Asia
• zzz is City; see below

Currently available Customer Origin + Communities are listed below:

The remote blackhole community allows IP Transit customers to tag announced prefixes with a community (see below) that will trigger Telia Carrier to automatically discard (null-route) traffic destined for the tagged prefix as soon as it enters our network. IPv4 and IPv6 prefixes can be tagged up to a /32 or /128, respectively.

While not enabled by default, this capability can be requested when ordering a new service or via a change order for existing services.

For security purposes, customers must use per-prefix BGP filters and register and maintain their prefixes and route objects in the applicable Internet Routing Registry database.

Customers also have the option to change the default local preference setting within AS1299 from 200 (customers) to either 150 (Peerings) or 50 (Backup). 

AS1299 Accepts and Honours the BGP Graceful Shutdown community; 65535:0 - compliant with IETF RFC8326. The purpose of this is to reduce the amount of traffic lost when BGP sessions are to be shut down, for example, during planned work. When announced by a customer, AS1299 will set local-preference to 20, which will ensure the use of alternative paths, if they exist. During Planned Works, AS1299 will always signal this community to customers and peers, allowing them to also re-route within their network.