Changes to ARIN Online - Routing Security Dashboard - RPKI & IRR integration (was: Fwd: [arin-announce] New Features Added to ARIN Online)

Wed Aug 9 22:19:11 UTC 2023

NANOGers -

As alluded to by Mark Kosters in his message below, we are placing on hold the functionality for the automatic
creation of corresponding new route objects for RPKI validated ROAs that lack such.  This is being done out of
an abundance of caution in order to allow us to conduct a community consultation in the near future to confirm
with the operational community the desired functionality in this area.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers

On Aug 9, 2023, at 2:42 PM, Mark Kosters <markk at arin.net> wrote:

Responses inline starting with "MK:"

On 8/9/23, 10:21 AM, "NANOG on behalf of Jay Borkenhagen" <nanog-bounces+markk=arin.net at nanog.org <mailto:arin.net at nanog.org> on behalf of jayb at braeburn.org <mailto:jayb at braeburn.org>> wrote:

I agree that in ARIN's RPKI-->IRR synthesis, the set of route[6]
objects created should not depend on the maxlength used. In Mark's
phrasing, "just have least-specific."

MK: I think it was Job that brought it up as a recommendation and glad to hear you agree with him.

Ideally, discussion about details such as this should have occurred on
some ARIN technical mailing list in the months leading up to ARIN
deploying this change to production.

MK: I agree that we have some improvements to make here on issues that directly impact the operations community. In fact, we will be placing the automatic creation of new route objects on hold. We are in the process of issuing a community consultation that is being formulated to solicit feedback on several technical aspects of this change. We hope to hear from you and others when this consultation is announced (it will conducted on the arin-consult mailing list - https://lists.arin.net/mailman/listinfo/arin-consult).

Thanks,
Mark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20230809/5bc73e27/attachment.html>