[ARIN-Suggestions] Response to Suggestion 2012.17 - CHANGES TO DOCUMENTATION REQUIREMENTS FOR ASN REQUESTS

[ARIN]

ARIN has issued its initial response to ACSP Suggestion 2012.17. The 
suggestion and response text are provided below. This suggestion remains 
is now closed and is available at:

https://www.arin.net/participate/acsp/suggestions/2012-17.html

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)

****
Suggestion: *

ARIN should accept any valid evidence of a unique routing policy and/or 
multihomed 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.

As an example, ARIN can independently corroborate that route-views shows 
a prefix or collection of prefixes terminating at or being routed via 
the stated transit providers in the case where an organization is moving 
from static-routed connectivity to BGP-based multi-homing.

*Response:*

ARIN has received your suggestion entitled "Changes to Documentation 
Requirements for ASN Requests" and assigned it the number 2012.17.

We would like to first take the time to clarify our existing procedures 
so that you have a better understanding of what is required since there 
seems to be some misconceptions. For example, your suggestion to 
"independently corroborate that route-views shows a prefix or collection 
of prefixes terminating at or being routed via the stated transit 
providers " is already standard practice at ARIN.

ARIN accepts a pretty broad range of things to verify connectivity. We 
will accept a reassignment from an ISP to the requester, or an ISP 
routing a block that's assigned/reassigned to the requester, or a copy 
of their signed connectivity agreement, or a recent/bill invoice showing 
the connectivity.

It should be noted that when an organization is requesting an additional 
AS number, we need to verify not just connectivity, but that a second AS 
number is justified. We typically can't verify that with a reassignment 
from an ISP or based on routing of IP addresses since those don't tell 
us the location(s) at which the customer has connectivity, and 
non-connected multi-homed networks at geographically different sites are 
very often the requester's justification for an additional AS number. 
Obtaining a copy of a signed connectivity agreement for the new location 
or a recent bill/invoice showing connectivity at the new location may be 
the only way to verify a second AS number is justified.

So in closing, we would like to state that ARIN already accepts multiple 
verification methods for connectivity during an ASN request, including 
the one you used as an example. If you have any additional feedback or 
ideas for new verification methods, we would be happy to review them.

Thank you for taking the time to participate in the ARIN Consultation 
and Suggestion Process. Suggestion 2012.17 is closed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-suggestions/attachments/20121113/02881969/attachment.html>