Hi Ron, On Tue, Jul 27, 2021 at 01:15:36AM -0700, Ronald F. Guilmette wrote: > ...
We have one route object remaining that references an undelegated ASN. The Member has requested some additional time to review this matter before they take action. There are three route objects remaining that reference private ASNs. These objects have been created by a Member for testing purposes, and they have advised us that they will remove these objects once they finish their testing. We are working on a notification system that will alert the APNIC Helpdesk team when such route objects are created, so that we can promptly follow them up with our Members. There is also a new policy proposal around restricting the creation of ROA objects that reference private, reserved, or unallocated ASN. https://www.apnic.net/community/policy/proposals/prop-138/ Since the route management interface in MyAPNIC permits our Members to create both route objects and ROAs with arbitrary ASNs, we will seek clarification from the author if this proposal should be extended to include route(6) objects as well. -Tom _______________________________________________ apnic-talk mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/apnic-talk
