mice-announce

Download

mice-announce@lists.micemn.net

May 2023

1 participants
2 discussions

Re: IRR Mandatory at MICE / New Route Servers
by Richard Laager June 7, 2023

June 7, 2023

This is the current cutover plan: Phase 1: On Tuesday, May 23, starting around 10:00 AM US/Central, we will upgrade route server 1. It will enforce the IRR as-set requirement for transit ASes, but will NOT enforce the IRR prefix requirement. Since route server 2 will still exist, even the as-set requirement is only a soft requirement. Phase 2: On Wednesday, May 31, starting around 10:00 AM US/Central, we will upgrade route server 2. It will be fully enforcing. At that point, the as-set requirement will be a hard requirement. The prefix IRR requirement will still be a soft requirement, as route server 1 will still not be enforcing. Phase 3: Tentatively, on Wednesday, June 7, starting around 10:00 AM US/Central, we will configure route server 1 to be fully enforcing. At that point, all IRR requirements will hard requirements. This date is subject to change based on what we see filtered. *We ask that you do /not/ take down your route server BGP sessions for these changes, as that will make it harder for us to know if things are working. If you are going to do so (e.g. because your organization's policies require it), then please let me know so I can expect your session to be down.* -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 6

Re: IRR Mandatory at MICE / New Route Servers
by Richard Laager May 11, 2023

May 11, 2023

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* > > * You MUST have an as-set object listing your AS and your downstream > ASes (if any). > o You MUST either list that as-set in PeeringDB or email the > name of your as-set to me (off-list to rlaager(a)wiktel.com please). > * A route/route6 object MUST exist for each prefix you announce to > the route servers (whether originated by you or transited through > you) and it must list an Origin AS that is in your as-set. > > *When* > > * *If you are a transit AS (i.e. have ASes behind you) and don't > have an /as-set/ object, fix this **/now/**.* Without an as-set > object, your downstream ASes announcements will be blocked > (filtered) immediately when the /first/ new route server is cut > in. (Granted, they will still work through the second route server > until it is upgraded.) Figure you have 1-2 weeks at most. > * Enforcement of the route/route6 objects (for both transit and > non-transit ASes) will come later, but not a lot later. So please, > start on this now. > > *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=… <https://lists.iphouse.net/cgi-bin/wa?A2=ind2305&L=MICE-DISCUSS&T=0&F=&S=&P=…> -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 0