New BGP customer turn up instructions (for customers of AS11796 and AS26652):

At this time, due to differing requirements from different upstream providers we are requiring both an LOA and up-to-date IRR entries for all customers using BGP. The process for both is outlined below.

IRR Instructions

In order to facilitate good internet hygiene and full reachability through peers we are requiring customers to register prefixes in an IRR. If you have an RADB subscription please update there. If you do not, ARIN offers an excellent free IRR database that can be used if you have ARIN resources.

Note: If you are advertising prefixes provided to you by another ISP you will need to reach out to them to either have them update their IRR to list your ASN as an origin-as, or they may reallocate/reassign the prefix to you via ARIN so you can make updates as detailed below.

Instructions for ARINs IRR can be found at the following links:

https://www.arin.net/resources/manage/irr/

https://www.arin.net/resources/manage/irr/quickstart/

If you do not have any IRR entries currently, the below would be a minimal starting point:

  1. Create a maintainer object (this is done automatically if using ARIN IRR).

  2. If you have a public ASN, creat an “aut-num” object for your ASN (optional, but still recommended).

  3. Create route-object(s) for every prefix you will be announcing.

    3a. If you have your own ASN and will be announcing routes via BGP, use your ASN as the origin-as for each route-object.

    3b. If you have your own prefixes but Airstream will be supplying a private ASN to you, please contact us for the origin-as you should use.

    3c. Many of our peers require exact match between the IRR entries and prefix(es) you are announcing via BGP. If you will be splitting your network(s) into smaller prefixes (e.g. splitting a /23 into two /24’s), then please create IRR entries for each smaller prefix.

  4. If you have downstream BGP customers, consider creating an “as-set” object and provide the name of that “as-set” to us. Otherwise please provide a list of downstream customer ASNs you intend to announce through us.

You can check the IRR status of your announcements at http://irrexplorer.nlnog.net. Please note it can take a long time before it reflects any changes you have made.

LOA Instructions

Some of our upstream providers still require an LOA (Letter Of Authorization) to be sent before they will update their filters. Our provisioning team will send an LOA as part of the initial turn-up, or if you are announcing any new networks or downstream customers not currently in our filters.

Note: If you are advertising prefixes provided to you by another ISP we will need the form returned from them authorizing such use. If you have been delegated prefixes from multiple ISPs we will need an LOA from each for their respective prefixes.

Please fill out the fields with technical contact name(s), along with an email and/or phone number for those contacts.

Please ensure you put your ASN, as well as a list of downstream customer ASNs (if any).

Please ensure you put a list of all IPv4 and IPv6 prefixes that may be announced by you and/or your downstream customers (aggregated, if possible).

Return signed form on your letterhead (or the other ISP(s) delegating prefixes to you, if applicable)

Note: RPKI

Airstream is not currently validating RPKI, although many of our peers do. Creating RPKI ROAs is recommended but not required at this time.

Please note that RPKI will take precedence over IRR entries, and any RPKI “Invalid” entries will be dropped even if IRR validates (for peers validating RPKI). Use caution if creating ROAs.