<div dir="ltr"><div class="gmail_default" style="font-size:small"><div class="gmail_default" style="font-size:small">I believe the
current practice is sufficient for now. If a sudden run on 2-byte ASN's
occurs this issue should be resurrected at that time. <br></div><br clear="all"><div><div class="gmail_signature">--<br>Brian<div class="gmail_default" style="font-size:small;display:inline"> E Jones</div></div></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">--<br>Brian</div></div>
<br><div class="gmail_quote">On Fri, Apr 8, 2016 at 12:06 PM, Andrew Dul <span dir="ltr"><<a href="mailto:andrew.dul@quark.net" target="_blank">andrew.dul@quark.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Do other members of the ARIN community believe that the current
policy and operational practice is sufficient for now, or are there
policy changes needed at this time?<br>
<br>
Thanks,<br>
Andrew<br>
<br>
<div>On 4/7/2016 12:24 PM, Scott Leibrand
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Thanks, John.
<div><br>
</div>
<div>It sounds to me like ARIN is already doing the right thing
(saving 2-byte ASNs for people who specifically want them),
and that is sufficient for the time being. It does not appear
that additional restrictions on who may request a 2-byte ASN
are necessary at this time. If at some point 5+ years down
the road the rate of 2-byte ASN demand starts to exceed the
recovered supply and the 2-byte ASN inventory is depleted, we
can consider a waiting list and/or technical requirements for
requesting a 2-byte ASN at that time.</div>
<div><br>
</div>
<div>Is there any other reason we need to consider taking action
sooner? Was there something else I'm missing that prompted
ARIN staff to start the consultation process around a 2-byte
ASN waiting list?</div>
<div><br>
</div>
<div>-Scott</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Apr 7, 2016 at 11:44 AM, John
Curran <span dir="ltr"><<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks -<br>
<br>
Please forgive this omnibus email of information, but we've
had sufficient individual<br>
questions for 2-byte ASN data that it simply made more sense
to provide one full<br>
summary rather than reply to each question individually...<br>
<br>
ARIN continues to have classic, 2-byte, AS numbers in
inventory. Over the last few<br>
years, we have received small blocks of them in our new
delegations from the IANA,<br>
obtained them from customer returns of AS numbers, or
through revocations of AS<br>
numbers due to non-payment of registration fees.<br>
<br>
Our last AS block delegation from IANA was on 29 April
2015. We received 99 2-byte<br>
ASNs and 925 4-byte ASNs at that time, and do not expect to
receive any additional<br>
2-byte ASNs from the IANA in future delegations. The 2-byte
ASNs received from the<br>
IANA in 2015 were added to the inventory and placed on
hold. The reason that the<br>
2-byte ASNs were put on hold is that was not responsible to
issue from the dwindling<br>
quantity of these resources to parties that did not
specifically request such while we<br>
were still receiving AS number requests specifically asking
for 2-byte AS numbers.<br>
<br>
As of today, we currently have the following 2-byte ASNs in
ARIN inventory:<br>
<br>
387 2-byte AS numbers on hold (most were routed at
some point)<br>
535 2-byte AS numbers revoked<br>
133 2-byte AS numbers returned<br>
<br>
= 1,055 2-byte AS numbers returned/revoked/held (Total)<br>
<br>
Customers requesting ASNs receive a 4-byte ASN by default.
If a request comes in<br>
that specifically requests a 2-byte ASN, we inform the
customer that we have noted<br>
their special request and that we will accommodate it at the
issuance phase of the<br>
ticket process if we have 2-byte ASN available at that time.<br>
<br>
Rate of issuance for 2-byte ASNs per month -<br>
<br>
1/2015: 68<br>
2/2015: 77<br>
3/2015: 74<br>
4/2015: 60<br>
5/2015: 7<br>
6/2015: 12<br>
7/2015: 16<br>
8/2015: 4<br>
9/2015: 7<br>
10/2015: 11<br>
11/2015: 7<br>
12/2015: 11<br>
1/2016: 5<br>
2/2016: 6<br>
3/2016: 13<br>
<br>
A waiting list will only be applicable after depletion of
the present 2-byte ASN inventory,<br>
hence the following general run-out estimates are provided
for consideration:<br>
<br>
- If we release all of the 2-byte ASNs from hold and
issue ASNs strictly from smallest<br>
to largest, i.e. the practice prior to May 2015, it is
likely that the current inventory of<br>
2-byte ASN’s would last somewhere between 6 to 12
months.<br>
<br>
- If we continue the current approach (wherein 4-byte
ASNs are issued by default and<br>
2-byte ASNs are only issued upon special request), the
current inventory of 2-byte<br>
ASNs would appear to last for many years (5+ years at
present rate).<br>
<br>
I hope the above information helps in your policy
development efforts!<br>
<br>
Thank you,<br>
/John<br>
<br>
John Curran<br>
President and CEO<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank"></a><a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you
experience any issues.</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br></blockquote></div><br></div>