<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Pesonally, I believe we have a terminology problem more than anything else.<div class=""><br class=""></div><div class="">At this time, we should no longer be even considering “2-byte” ASNs.</div><div class=""><br class=""></div><div class="">There are two classes of 4-byte ASNs. The idea of 2-byte ASNs should be considered anachronistic.</div><div class=""><br class=""></div><div class="">The classes of 4-byte ASNs are those that are ≤65535 and those that are ≥65536.</div><div class=""><br class=""></div><div class="">The former class can be used as a 2-byte ASN in the rare case of a technological limitation (obsolete routing equipment or equipment with inadequate support for extended communities).</div><div class=""><br class=""></div><div class="">The latter class cannot be used as a 2-byte ASN in such cases.</div><div class=""><br class=""></div><div class="">In all cases, continuing to talk about 2-byte ASNs IMHO contributes to the misperception that the internet has not yet moved on.</div><div class=""><br class=""></div><div class="">I believe that current policy is sufficient. I would prefer that operational practice actually revert to what is in policy and that we no longer treat 4-byte ASNs ≤65535 as being in any way special.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 8, 2016, at 09:06 , Andrew Dul <<a href="mailto:andrew.dul@quark.net" class="">andrew.dul@quark.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
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 class="">
<br class="">
Thanks,<br class="">
Andrew<br class="">
<br class="">
<div class="moz-cite-prefix">On 4/7/2016 12:24 PM, Scott Leibrand
wrote:<br class="">
</div>
<blockquote cite="mid:CAGkMwz7pEovs=t3+LMTmkAzZ7zivf0PQ5uLHqkHhfC43A_ZAiQ@mail.gmail.com" type="cite" class="">
<div dir="ltr" class="">Thanks, John.
<div class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">-Scott</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Thu, Apr 7, 2016 at 11:44 AM, John
Curran <span dir="ltr" class=""><<a moz-do-not-send="true" href="mailto:jcurran@arin.net" target="_blank" class="">jcurran@arin.net</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Folks -<br class="">
<br class="">
Please forgive this omnibus email of information, but we've
had sufficient individual<br class="">
questions for 2-byte ASN data that it simply made more sense
to provide one full<br class="">
summary rather than reply to each question individually...<br class="">
<br class="">
ARIN continues to have classic, 2-byte, AS numbers in
inventory. Over the last few<br class="">
years, we have received small blocks of them in our new
delegations from the IANA,<br class="">
obtained them from customer returns of AS numbers, or
through revocations of AS<br class="">
numbers due to non-payment of registration fees.<br class="">
<br class="">
Our last AS block delegation from IANA was on 29 April
2015. We received 99 2-byte<br class="">
ASNs and 925 4-byte ASNs at that time, and do not expect to
receive any additional<br class="">
2-byte ASNs from the IANA in future delegations. The 2-byte
ASNs received from the<br class="">
IANA in 2015 were added to the inventory and placed on
hold. The reason that the<br class="">
2-byte ASNs were put on hold is that was not responsible to
issue from the dwindling<br class="">
quantity of these resources to parties that did not
specifically request such while we<br class="">
were still receiving AS number requests specifically asking
for 2-byte AS numbers.<br class="">
<br class="">
As of today, we currently have the following 2-byte ASNs in
ARIN inventory:<br class="">
<br class="">
387 2-byte AS numbers on hold (most were routed at
some point)<br class="">
535 2-byte AS numbers revoked<br class="">
133 2-byte AS numbers returned<br class="">
<br class="">
= 1,055 2-byte AS numbers returned/revoked/held (Total)<br class="">
<br class="">
Customers requesting ASNs receive a 4-byte ASN by default.
If a request comes in<br class="">
that specifically requests a 2-byte ASN, we inform the
customer that we have noted<br class="">
their special request and that we will accommodate it at the
issuance phase of the<br class="">
ticket process if we have 2-byte ASN available at that time.<br class="">
<br class="">
Rate of issuance for 2-byte ASNs per month -<br class="">
<br class="">
1/2015: 68<br class="">
2/2015: 77<br class="">
3/2015: 74<br class="">
4/2015: 60<br class="">
5/2015: 7<br class="">
6/2015: 12<br class="">
7/2015: 16<br class="">
8/2015: 4<br class="">
9/2015: 7<br class="">
10/2015: 11<br class="">
11/2015: 7<br class="">
12/2015: 11<br class="">
1/2016: 5<br class="">
2/2016: 6<br class="">
3/2016: 13<br class="">
<br class="">
A waiting list will only be applicable after depletion of
the present 2-byte ASN inventory,<br class="">
hence the following general run-out estimates are provided
for consideration:<br class="">
<br class="">
- If we release all of the 2-byte ASNs from hold and
issue ASNs strictly from smallest<br class="">
to largest, i.e. the practice prior to May 2015, it is
likely that the current inventory of<br class="">
2-byte ASN’s would last somewhere between 6 to 12
months.<br class="">
<br class="">
- If we continue the current approach (wherein 4-byte
ASNs are issued by default and<br class="">
2-byte ASNs are only issued upon special request), the
current inventory of 2-byte<br class="">
ASNs would appear to last for many years (5+ years at
present rate).<br class="">
<br class="">
I hope the above information helps in your policy
development efforts!<br class="">
<br class="">
Thank you,<br class="">
/John<br class="">
<br class="">
John Curran<br class="">
President and CEO<br class="">
American Registry for Internet Numbers (ARIN)<br class="">
<br class="">
_______________________________________________<br class="">
PPML<br class="">
You are receiving this message because you are subscribed to<br class="">
the ARIN Public Policy Mailing List (<a moz-do-not-send="true" href="mailto:ARIN-PPML@arin.net" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
<a moz-do-not-send="true" href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">
Please contact <a moz-do-not-send="true" href="mailto:info@arin.net" class="">info@arin.net</a> if you
experience any issues.</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">PPML<br class="">You are receiving this message because you are subscribed to<br class="">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">Please contact info@arin.net if you experience any issues.</div></blockquote></div><br class=""></div></body></html>