 |
 |
On 2023-05-13 02:02, Richard Laager wrote: > > 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. > This work is about to commence. > 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