Routing policy

This page describes the policy implemented at the borders of AS37721 to control the import and export of routing information with other autonomous systems.

The information provided may be altered and updated at any time. Though our processes cover updates to documentation, there is no guarantee that it is always up-to-date. In case of doubt, transit customers should contact our NOC noc@vts.bf and peers should contact peering@vts.bf.

A list of communities used by AS37721 and their meaning can be found under bgp communities page on this website.

AS37721's main as-set is AS-VTS-SET (AFRINIC and RADB).

Finding Information

VTS maintains up to date information in multiple publicly available data sources, including:

If any of the information you find on this page does not contain what you are looking for or if the information within this page appears to be inaccurate, please email peering@vts.bf.

Peering Relationships

The topological relationship of AS37721 to the external peers of AS37721 may be generally categorised into:

  • Customers
  • Peers
  • Transits

These terms are used herein to describe the topological relationship between AS37721 and an adjacent network, and do not necessarily imply the existence of a particular commercial relationship.

AS37721 may have multiple distinct relationships with a given AS at different points of interconnection. Thus, polices described here as applying to particular types of interconnection relationship should be construed as applying only to those interconnections or peerings of that type, rather than to all adjacencies with a given AS.

Import and Export Policies

Some policies are implemented uniformly across all adjacencies, whilst others will vary according to the topological relationship between AS37721 and the adjacent networks.

These policies follow IETF BCP 194 (RFC 7454, BGP Operations and Security) and the filtering action of MANRS (Mutually Agreed Norms for Routing Security).

Autonomous Systems

  • 37721

BGP Protocol

AS37721 will exchange routing information for Internet networks with external peers using Border Gateway Protocol version 4 only.

Bogon Address Space

  • AS37721 will not accept routing information for, and will not deliver IP packets addressed to or from, “Bogon” address space, including RFC1918, RFC2544, RFC3927, RFC5737, RFC6598 and RFC6890
  • IPv6 address space outside the global unicast range 2000::/3, and the 6bone, documentation, Teredo and 6to4 ranges
  • IX (Exchange) LAN ranges VTS connects to

Bogon and reserved ASNs

AS37721 will not accept routing information that contain Bogon ASNs in the BGP path (private and reserved ASN numbers as defined by RFC7607, RFC6793, RFC5398, RFC6996, RFC7300)

Prefix Length

AS37721 will accept routing information for IP prefixes conforming to minimum and maximum prefix-lengths as follows:

Address Family Min Length Max Length
IPv4 8 bits 24 bits
IPv6 16 bits 48 bits

These limits apply to routes from peers, CDN and PNI partners and IX route servers (RFC 7454, Section 6.1.3). Routes from transit providers are accepted up to /24 (IPv4) and /48 (IPv6). Routes from customers are filtered by the customer’s prefix list (see Prefix Filter). AS37721 announces to peers and transit providers only IPv4 prefixes up to /24 and IPv6 prefixes up to /48.

AS Path Length

AS37721 does not accept routes whose AS_PATH contains more than 50 AS numbers, prepends included. This applies to every eBGP neighbor.

Import BGP Filtering

Prefix Filter

Customers: AS37721 filters the routes of each customer with a prefix list built from RPSL data in the distributed IRR system. The customer’s as-set (or its ASN) is resolved recursively to a list of member ASNs, and the route and route6 objects whose origin is one of these ASNs make up the list. The lists are refreshed every day at about 06:15 UTC and installed on our routers at about 06:45 UTC. A list that comes back empty, loses more than half of its prefixes or grows past a size limit is held for review, and the previous list stays in place. Customers without usable IRR data are filtered with a static prefix list maintained by VTS. Prefixes received from customers are accepted only if they are in the customer’s prefix list, and are subject to the other conditions described in this document, including RPKI origin validation and the AS_PATH checks.

Peers: AS37721 does not apply IRR prefix lists to peers. Routes received from peers, CDN and PNI partners and IX route servers are accepted subject to the other conditions described in this document: bogon and martian prefixes, prefixes outside the lengths above, the IX LAN ranges VTS connects to, routes with bogon ASNs or an AS_PATH longer than 50 ASNs, routes whose first AS is not the peer’s own (route servers excepted) and route leaks (see AS_PATH Filters) are rejected; RPKI-invalid routes are rejected (Route Origin Validation, RFC 6811); and maximum-prefix limits apply.

AS37721 maintains the following RPSL dataset which may be used to prefix filter adjacencies with AS37721:

  • as-set : AS-VTS-SET

Please note: The size of as-set should not be used as an indicator of the number of routes that a non-customer peer should expect to receive.

Maximum Prefixes Limits

AS37721 sets limits on the maximum number of prefixes accepted from a given eBGP neighbor. When a reasonable suggested value is published in the PeeringDB, that value will be used. Otherwise, VTS use its discretion to arrive at an appropriate value.

AS_PATH Filters

The first AS in the AS_PATH of every route must be the AS of the neighbor that sent it (RFC 7454, Section 9). This is checked for customers, peers, CDN and PNI partners and transit providers; IX route servers are exempt because they do not add their own AS. Customer routes must also be covered by the customer’s prefix list. To prevent route leaks (RFC 7908), routes from peers whose AS_PATH contains AS37721, the AS of one of our customers or a Tier-1 transit network are rejected.

Export BGP Filtering

Export to Customers

AS37721 will advertise one or more of the following sets of prefixes towards its customer peers:

  1. Full Routes: All routes learned by AS37721 from customer and non-customer peers according to the policies described herein.
  2. Default Route: A single route of last resort, i.e. 0.0.0.0/0 or ::/0, generated locally on the border router upon which the eBGP session with AS37721 is configured.
  3. Partial Routes: In the case of “partial transit” customers, a subset of the full routes, being those imported from non-customer peers within the defined scope of the relevant customer’s service. In all cases, partial transit customers will be advertised all prefixes imported from other customers, regardless of their scope of service.

Export to Non-customers

AS37721 will export towards non-customer peers only routes that are originated in AS37721 or imported from customer peers.

Peers wishing to set a sensible maximum-prefixes limit on sessions with AS37721 should refer to the ‘IPv4 Prefixes’ and ‘IPv6 Prefixes’ field in our record on PeeringDB.

AS37721 will make every attempt to maintain consistent announcements of prefixes towards peers. However, advertisement of prefixes learned from customers may be suppressed at certain peering locations, or towards specific neighbor ASNs, as the result of traffic engineering communities received from customers.

To prevent the inadvertent advertisement of transit between non-customer networks, a BGP community will be appended on import to indicate that a prefix was imported from a customer peer, and only prefixes carrying such community will be exported to non-customer neighbors.

Route Control 

The following BGP attribute handling policies define the expected route selection, for traffic routed to and from AS37721.

Local Preference

AS37721 sets the BGP LOCAL_PREF attribute on import according to the relationship of AS37721 to the adjacent neighbor or the type of route, as per the below table.

Where a range of values is indicated, other factors such as whether a peering cross an IXP or PNI are used to select the eventual value.

  LOCAL_PREF
Transit 90 to 110 (default: 100)
Peer 149 to 310
Customer 400, or 80 to 310 when the customer sets a local-preference community (see BGP Communities)
Locally Originated 450
Blackhole Routes 666
Graceful Shutdown (65535:0) 0

Routes received from any eBGP neighbor with the GRACEFUL_SHUTDOWN community 65535:0 (RFC 8326) get LOCAL_PREF 0, so traffic moves to other paths before a planned shutdown. Neighbors may send it before maintenance.

AS Path

AS37721 will not modify the AS_PATH attribute of any route on import.

Customers of AS37721 may send BGP communities to influence the export of their routes to non-customer peers. Such communities may be used to suppress advertisement, prepend 37721 up to 3 times to selected groups of non-customer peers, or influence the LOCAL_PREF values of their prefixes relative to the AS37721 routing domain.

The above functionality is documented fully in BGP Communities.

MED

AS37721 resets the MULTI_EXIT_DISC (MED) of every route received from customers, peers and transit providers to 0, so MED does not influence path selection inside AS37721.

AS37721 does not derive the MED of the routes it announces from its IGP cost.