Arvig BGP Routing Policy

This document will cover the BGP policies implemented by Arvig. It describes customer requirements and recommendations, communities customers can utilize and routing policies used.

IRR (Routing Registry)
Arvig recommends that all BGP customers register each route they plan to advertise with an IRR. RADB and ARIN are suitable IRRs. You may prefer to use ARIN if you have direct allocations. Arvig currently uses RADB, which allows Arvig to proxy for customers. However, do not rely on it, as this may change in the future. Make sure your ARIN allocation has the proper OriginAS attribute set to your ASN.

Resources

Note: Please make sure all of your Route Objects (ROs) are registered under your ASN.

RPKI
Resource Public Key Infrastructure (RPKI) is an opt-in service at ARIN that provides security for internet routing. RPKI allows IP address holders to specify which Autonomous Systems (ASes) are authorized to originate their IP address prefixes.

Resources

Arvig is working towards utilizing RPKI for route validation, just as a number of Tier 1 providers have already completed. Arvig currently has ROAs created for all prefixes that are direct allocations to Arvig. Customers with their own direct allocations from ARIN are not currently required to create ROAs for their prefixes. Although not required today, in the future Arvig will be filtering out all bad routes that do not match an announced ROA.

IPv4 Routing Policies
Customers can choose to receive a full internet routing table, default only or both. If a customer requires a full internet table, they need to make sure their router has the capability to support it.

Inbound
Arvig will accept only prefixes with a length of /24 or shorter. Arvig will allow host /32 prefixes for RTBH, as long as the community 16904:666 is set. Arvig will explicitly restrict prefixes registered to the customer.

Outbound
Arvig will announce prefixes with a length of /24 or shorter to our peers. All Arvig announcements will be registered in an IRR, and be included under the as-set AS-ARVIG.

IPv6 Routing Policies
Customers can choose to receive a full internet routing table, default only or both. If a customer requires a full internet table, they need to make sure their router has the capability to support it.

Inbound
Arvig will accept /48 and shorter prefixes from our peers. Arvig will allow host /128 prefixes for RTBH, as long as the community 16904:666 is set. Arvig will explicitly restrict prefixes registered to the customer.

Outbound
Arvig will announce /48 and shorter prefixes to our peers. All Arvig announcements will be registered in an IRR, and be included under the as-set AS-ARVIG.

Bogon Filtering
Arvig will not accept BOGON prefix announcements from eBGP peers. Arvig will also not accept announcements that include BOGON ASNs.

BFD
Arvig will support BFD for neighbor configurations upon request.

Route Dampening
Arvig does not use BGP route dampening.

MEDs
Arvig will accept meds from its customers.

Blackhole Service
Customers may announce IPv4 and IPv6 host prefixes tagged with the BGP community. 16904:666. Traffic destined to a host route tagged with this community will be dropped once it reaches our network. By default, peers are configured to allow for blackhole functionality.

Graceful BGP Shutdown
To reduce the amount of traffic lost when BGP sessions are about to be shut down deliberately, e.g., for planned maintenance, the Global IP Network supports receiving and honoring the Graceful Shutdown BGP community 65535:0 (also known as “GRACEFUL_SHUTDOWN”) on all EBGP sessions.

Customer Community Controls
All Arvig communities used are removed prior to advertising prefixes to all peers. Customers are allowed to prepend their own AS. Studies have shown prepending more than 2 times does not provide any additional benefit.

NANOG N80 AS Prepending reference links

Customers may choose to change local preference for their routes.

BGP 1

Customers may choose to prepend to all Arvig eBGP peers.

BGP 2

Customers wanting to alter route announcements to selected peers.

BGP 3

Customers wanting to alter route announcements to all peers in selected POPs.

BGP 4

*Arvig reserves the right to modify this policy without prior notice.