2018.15: Add "Routing" and "DNS" Points of Contact
Author: Bill Woodcock
Submitted On: 30 July 2018
Add “Routing” and “DNS” points of contact.
There are currently a number of different types of Point of Contact, including Administrative, Technical, Abuse, and others. I suggest that we add two more types of optional POC: one for routing contacts (such as would be responsible for IRR and RPKI implementation) and one for DNS contacts (such as would be responsible for updating in-addr DNSSEC DS records and in-addr DNS nameserver delegations).Support the RRDP protocol (RFC8182) for RPKI publication, just like the RIPE NCC and APNIC already do.
Value to Community: This will allow ARIN resource recipients to optionally delegate authority for specific technical tasks (updating IRR, RPKI, DS, and NS records in ARIN’s databases, for example) to the appropriate people within their organization, without exposing all functions to all POCs. It will also allow network operators to use the more specific whois POC records to directly contact the appropriate people responsible for these functions within counterpart networks.
Timeframe: Not specified
Status: Open Updated: 10 August 2018
10 August 2018
Thank you for your suggestion, numbered 2018.15 upon confirmed receipt, requesting ARIN add two new Point of Contact types—Routing and DNS.
This suggestion is well timed with the start of ARIN’s new Internet Routing Registry (IRR) development. We agree with your suggestion to include a new “Routing” point of contact type and have also received suggestions from customers over recent years through customer service interactions that we also add a “DNS” point of contact type. These new additions will be included in our IRR-related development work that runs this year through the first quarters of 2019.
Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented.