<div dir="ltr">There are valid technical reasons, pertaining to communities, why ISP networks with multihomed downstream BGP customers would be better served by ASNs that can be represented by a two-byte number, with the other two bytes all zeros. Those technical reasons do not apply, AFAIK, to edge networks, only to transit providers with BGP-speaking customers who want to use communities to control route announcements.<div><br></div><div>-Scott</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 30, 2016 at 5:13 PM, David Huberman <span dir="ltr"><<a href="mailto:David_Huberman@outlook.com" target="_blank">David_Huberman@outlook.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Apologies, but I have this data analysis done, and I dont want to lose it. I can resend when the consultation officially opens.<br>
<br>
<br>
I just did a quick data analysis of the DFZ found on one of my routers.<br>
<br>
There are 601,729 unique routes originating from and transiting through 53,511 ASNs.<br>
<br>
71,170 routes (11.8%) originate from or propagate through a 4-byte ASN.<br>
There are 10,244 (19.1%) unique 4-byte ASNs in my copy of the table.<br>
<br>
Given this data, I'm unclear why the registry should be treating 4-byte ASNs as anything but a single contiguous pool, as policy currently states.<br>
<br>
________________________________________<br>
From: <a href="mailto:arin-suggestions-bounces@arin.net">arin-suggestions-bounces@arin.net</a> <<a href="mailto:arin-suggestions-bounces@arin.net">arin-suggestions-bounces@arin.net</a>> on behalf of ARIN <<a href="mailto:info@arin.net">info@arin.net</a>><br>
Sent: Wednesday, March 30, 2016 4:28 PM<br>
To: <a href="mailto:arin-suggestions@arin.net">arin-suggestions@arin.net</a><br>
Subject: [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs<br>
<div><div class="h5"><br>
We received the following suggestion on 18 March:<br>
<br>
Suggestion Details:<br>
<br>
Description: Waiting list for 2 Byte ASNs<br>
<br>
Value to Community: One member said to me:<br>
<br>
Ticket from ARIN "We have noted your request for a 2-byte ASN. ARIN is<br>
out of 2-byte ASN's in its inventory. We get them returned voluntarily<br>
from time to time. If we have one at the time of issuance, we will issue<br>
it to your organization. If we do not have a 2-byte in inventory at that<br>
time, your organization will receive the standard 4-byte ASN. "<br>
<br>
Member comment "if they are really out - a waitinglist would be nice...."<br>
<br>
On 30 March, we sent the following response to the submitter:<br>
<br>
Thank you for your suggestion numbered 2016.04 - Waiting List for 2 Byte<br>
ASNs.<br>
<br>
Background<br>
<br>
The NRPM included instructions in the past for ARIN staff to remove any<br>
distinction between 2-byte and 4-byte in the issuance of AS numbers.<br>
This particular policy language has since been retired in the NRPM.<br>
<br>
Staff has followed policy regarding issuance of AS numbers, but has<br>
often had lower numbered, classic 2-byte, AS numbers available over<br>
time. We would either receive them in our new delegations from the IANA,<br>
obtain them from customer returns of AS numbers, or through revocations<br>
of AS numbers due to non-payment of registration fees. Although ARIN<br>
expects to no longer receive AS numbers from the IANA inside the classic<br>
2-byte range, we do expect to continue reclaiming them through returns<br>
and revocations going forward.<br>
<br>
Some AS number requests today continue to specifically ask for an AS<br>
number from the classic 2-byte range. In those situations we relay to<br>
the customer that we have noted their special request and that we will<br>
accommodate it at the issuance phase of the ticket process if one is<br>
available at the time.<br>
<br>
The Suggestion<br>
<br>
We understand your suggestion is to establish a waiting list for AS<br>
numbers from the classic 2-byte range for those customers who<br>
specifically request one when ARIN does not have them available. This<br>
waiting list would be similar to the IPv4 waiting list for unmet<br>
requests, but managed separately for AS numbers. Organizations would be<br>
placed on this AS number waiting list, and when one became available<br>
through reclamation at ARIN, it would be slated for the organization<br>
first on the waiting list.<br>
<br>
Staff Action<br>
<br>
ARIN staff can create a waiting list for 2-byte AS numbers if there is<br>
favor from the community to establish one. ARIN staff will open a<br>
consultation on the topic to gather feedback and take appropriate action<br>
based on information received through that process.<br>
<br>
Thank you for participating in the ARIN Consultation and Suggestion<br>
Process. We will leave this suggestion open until a consultation has<br>
been completed on this topic and an implementation plan has been<br>
established.<br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
_______________________________________________<br>
arin-suggestions mailing list<br>
<a href="mailto:arin-suggestions@arin.net">arin-suggestions@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-suggestions" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/arin-suggestions</a><br>
</div></div>_______________________________________________<br>
ARIN-Consult<br>
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br>
List (<a href="mailto:ARIN-consult@arin.net">ARIN-consult@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br>
Help Desk at <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br></div>