<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p class="MsoNormal" style="margin: 6pt 0in; line-height: 18pt;
background: none repeat scroll 0% 0% white;"><span
style="font-family:Helvetica;mso-fareast-font-family:
"Times New Roman";mso-bidi-font-family:"Times New
Roman"">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: </span><span style="font-family: Times;"></span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family: "Times New Roman""></span><span
style="font-family: Helvetica;"><br>
</span></p>
<p class="MsoNormal"
style="margin-top:6.0pt;margin-right:0in;margin-bottom:6.0pt;
margin-left:0in;line-height:18.0pt;background:white"><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman""><a class="moz-txt-link-freetext" href="https://www.arin.net/participate/acsp/suggestions/2012-17.html">https://www.arin.net/participate/acsp/suggestions/2012-17.html</a></span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family: "Times New Roman""><br>
<br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">Regards,</span><span style="font-family:
Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family:"Times New Roman""><br>
<br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">Communications and Member Services</span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family: "Times New Roman""><br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">American Registry for Internet Numbers (ARIN)</span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman"; mso-bidi-font-family:"Times New Roman""><br>
<br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">***</span><span style="font-family:
Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family:"Times New Roman""><o:p></o:p></span><b><span
style="font-family: Helvetica;mso-bidi-font-family:"Times
New Roman";color:black"><br>
Suggestion: </span></b><span
style="font-family:Arial;mso-bidi-font-family:"Times New
Roman";color:black"><o:p></o:p></span></p>
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.<br>
<br>
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.<span style="font-family:
Helvetica;mso-bidi-font-family:"Times New
Roman";color:black"></span><span
style="font-family:Arial;mso-bidi-font-family:"Times New
Roman";color:black"><o:p></o:p></span>
<p class="MsoNormal"
style="margin-top:6.0pt;margin-right:0in;margin-bottom:6.0pt;
margin-left:0in;line-height:18.0pt;background:white"><b><span
style="font-family: Helvetica;mso-bidi-font-family:"Times
New Roman";color:black">Response:</span></b><span
style="font-family:Arial;mso-bidi-font-family:"Times New
Roman";color:black"><o:p></o:p></span></p>
ARIN has received your suggestion entitled "Changes to Documentation
Requirements for ASN Requests" and assigned it the number 2012.17.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Thank you for taking the time to participate in the ARIN
Consultation and Suggestion Process. Suggestion 2012.17 is closed.<span
style="font-family:Helvetica; mso-bidi-font-family:"Times New
Roman";color:black"></span>
</body>
</html>