NANOGers -
ARIN would like to remind the community about the ongoing consultation on Resource Public Key Infrastructure/BGP intelligence. This consultation is slated to close on Thursday, 29 February. Please be sure to submit your comments to the arin-consult mailing list before then.
Read the full text of the consultation at: ACSP Consultation 2024.1: Consultation on RPKI/BGP Intelligence - American Registry for Internet Numbers
As of 14 February 2024, we have received very few comments from the community regarding this consultation. We believe adding this feature would benefit many ARIN customers, and we are seeking input from our community for any additional information or capabilities that should be included in this proposed functionality development.
If you have feedback you’d like to share with ARIN, please provide it to the arin-consult mailing list via arin-consult@arin.net. You may subscribe to this mailing list at ARIN-consult Info Page. ARIN will use the feedback provided to determine how we move forward with improvements to our routing security services.
Thank you in advance for your participation in this community consultation.
Thanks!
/John
John Curran
President and CEO
American Registry for Internet Numbers (ARIN)
john,
Read the full text of the consultation at:
ACSP Consultation 2024.1: Consultation on RPKI/BGP Intelligence - American Registry for Internet Numbers
please explain the need for bureaucrazy to do what RPKI CAs have been
doing since dirt was invented.
randy
Randy -
I’d tend to agree with you, but ARIN already once attempted to rollout such functionality –
alas, with overly ambitious scope that not only provided increased visibility after potentially
affected routes but functionality that also created default linkage to matching IRR objects –
and thus created a real potential for subtle operational impacts at the time of the rollout.
<https://mailman.nanog.org/pipermail/nanog/2023-August/222790.html>
Rather than have a repeat of that fiasco, we’re now moving ahead with changes that have
any potential for causing routing changes in a more deliberate and consultative manner.
Thanks!
/John
John Curran
President and CEO
American Registry for Internet Numbers
john:
I’d tend to agree with you, but ARIN already once attempted to rollout
such functionality – alas, with overly ambitious scope that not only
provided increased visibility after potentially affected routes but
functionality that also created default linkage to matching IRR
objects
whoops! i still code around another RIR doing that. vendors have a
long history of thinking they know best what operators should do. some
RIRs seem to have such hubris.
ok, i can see opening up discussion to reduce foot shooting risks.
sorry for skepticism.
randy