ARIN Consultation and Suggestion Process Report

Nate Davis

Open Suggestion and Consultation 2012.11: DNSSEC Improvements• Enhance ARIN Online to accept TTLs

when editing DS records• Enable submission of bulk DS RR

records including TTLs• Parse bulk DS RR records and load

into ARIN Online2

Open Suggestion and Consultation 2012.11: DNSSEC IMPROVEMENTS – Implementation Estimates, only for TTLs• Cost estimate – underway, though we note: – Extensive rework to database structure– Extensive changes to Zone Generation– Moderate changes to Whois– Application and Rest Changes

3

Suggestions Just Received2012.17: Changes to Documentation Requirements for ASN Requests • ARIN should accept any valid evidence

of a unique routing policy and/or multi-homed connectivity as proof of the need for an autonomous system number, per policy. It is ridiculous for ARIN to insist on copies of signed agreements as the only form of acceptable evidence.

4

Suggestions Just Received2012.18: Improve Request Submission Options• ARIN should not phase out the

hostmaster@arin.net channel for additional communication about requests. Ideally, restoring that as a channel for request submission should be restored.

• ARIN needs to provide much better tools for consultants to use to work with their customers on ARIN resource requests. The need for these better tools is a direct result of the conversion to ARIN on-line.

5

Suggestions Just Received2012.19: Make Company Name Optional for Billing Form• In the billing form on ARIN On-Line,

Company name should be an optional field for the person paying the bill. Currently it is mandatory and requires 3-150 characters.

• It is nonsensical in the case where an individual may be paying an ARIN invoice.

6

Questions?

7