On 2023-05-09 05:19, Richard Laager wrote:

MICE will soon be deploying new route servers which will require IRR (Internet Routing Registry) records, as is a best practice at IXPs.

What

When

Where

If you are not sure where to create IRR records, use ARIN (assuming you are in the ARIN region).

How (with ARIN)

  1. Login to ARIN Online. (Go to arin.net and click Login in the top right.)
  2. On the left side, expand "Routing Security" and click "IRR".
  3. Click "as-set" at the top.
  4. Click "Create an Object".
  5. Fill in the fields:
    The "AS Set Name" is what you will list in PeeringDB (or email to me).
    "Description" is unparsed, but they suggest the location and have a button to "Copy the Address from My Org ID".
    "Members" is where you list your ASN and downstream ASes (if any).
  6. Click "Review". Once ready, click "Submit".
  7. Click "route/route6" at the top.
  8. Click "Create an Object".
  9. Fill in the fields:
    "Prefix" is the prefix, e.g. 192.0.2.0/24.
    "Origin" is your ASN.
  10. Click "Review". Once ready, click "Submit".
  11. Repeat to create additional route objects until all of your announcements are covered. Don't forget IPv6!

Examples

Here is my as-set: https://www.radb.net/query?keywords=AS-WIKTEL

Here is one example route: https://www.radb.net/query?keywords=69.89.192.0%2F20

(I created the AS33362 one. The AS19905 one is because another AS can originate this route for DDoS scrubbing reasons.)


For more discussion, see the thread on MICE-DISCUSS: https://lists.iphouse.net/cgi-bin/wa?A2=ind2305&L=MICE-DISCUSS&T=0&F=&S=&P=2710

--
Richard


To unsubscribe from the MICE-ANNOUNCE list, click the following link:
&*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);