<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="">Actually, the community thing is largely a red herring in lieu of “convenience”.<div class=""><br class=""></div><div class="">There are perfectly valid ways to address the community functionality desired using 4-byte ASNs.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 30, 2016, at 17:17 , Scott Leibrand <<a href="mailto:scottleibrand@gmail.com" class="">scottleibrand@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">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 class=""><br class=""></div><div class="">-Scott</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Mar 30, 2016 at 5:13 PM, David Huberman <span dir="ltr" class=""><<a href="mailto:David_Huberman@outlook.com" target="_blank" class="">David_Huberman@outlook.com</a>></span> wrote:<br class=""><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 class="">
<br class="">
<br class="">
I just did a quick data analysis of the DFZ found on one of my routers.<br class="">
<br class="">
There are 601,729 unique routes originating from and transiting through 53,511 ASNs.<br class="">
<br class="">
71,170 routes (11.8%) originate from or propagate through a 4-byte ASN.<br class="">
There are 10,244 (19.1%) unique 4-byte ASNs in my copy of the table.<br class="">
<br class="">
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 class="">
<br class="">
________________________________________<br class="">
From: <a href="mailto:arin-suggestions-bounces@arin.net" class="">arin-suggestions-bounces@arin.net</a> <<a href="mailto:arin-suggestions-bounces@arin.net" class="">arin-suggestions-bounces@arin.net</a>> on behalf of ARIN <<a href="mailto:info@arin.net" class="">info@arin.net</a>><br class="">
Sent: Wednesday, March 30, 2016 4:28 PM<br class="">
To: <a href="mailto:arin-suggestions@arin.net" class="">arin-suggestions@arin.net</a><br class="">
Subject: [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs<br class="">
<div class=""><div class="h5"><br class="">
We received the following suggestion on 18 March:<br class="">
<br class="">
Suggestion Details:<br class="">
<br class="">
Description: Waiting list for 2 Byte ASNs<br class="">
<br class="">
Value to Community: One member said to me:<br class="">
<br class="">
Ticket from ARIN "We have noted your request for a 2-byte ASN. ARIN is<br class="">
out of 2-byte ASN's in its inventory. We get them returned voluntarily<br class="">
from time to time. If we have one at the time of issuance, we will issue<br class="">
it to your organization. If we do not have a 2-byte in inventory at that<br class="">
time, your organization will receive the standard 4-byte ASN. "<br class="">
<br class="">
Member comment "if they are really out - a waitinglist would be nice...."<br class="">
<br class="">
On 30 March, we sent the following response to the submitter:<br class="">
<br class="">
Thank you for your suggestion numbered 2016.04 - Waiting List for 2 Byte<br class="">
ASNs.<br class="">
<br class="">
Background<br class="">
<br class="">
The NRPM included instructions in the past for ARIN staff to remove any<br class="">
distinction between 2-byte and 4-byte in the issuance of AS numbers.<br class="">
This particular policy language has since been retired in the NRPM.<br class="">
<br class="">
Staff has followed policy regarding issuance of AS numbers, but has<br class="">
often had lower numbered, classic 2-byte, AS numbers available over<br class="">
time. We would either receive them in our new delegations from the IANA,<br class="">
obtain them from customer returns of AS numbers, or through revocations<br class="">
of AS numbers due to non-payment of registration fees. Although ARIN<br class="">
expects to no longer receive AS numbers from the IANA inside the classic<br class="">
2-byte range, we do expect to continue reclaiming them through returns<br class="">
and revocations going forward.<br class="">
<br class="">
Some AS number requests today continue to specifically ask for an AS<br class="">
number from the classic 2-byte range. In those situations we relay to<br class="">
the customer that we have noted their special request and that we will<br class="">
accommodate it at the issuance phase of the ticket process if one is<br class="">
available at the time.<br class="">
<br class="">
The Suggestion<br class="">
<br class="">
We understand your suggestion is to establish a waiting list for AS<br class="">
numbers from the classic 2-byte range for those customers who<br class="">
specifically request one when ARIN does not have them available. This<br class="">
waiting list would be similar to the IPv4 waiting list for unmet<br class="">
requests, but managed separately for AS numbers. Organizations would be<br class="">
placed on this AS number waiting list, and when one became available<br class="">
through reclamation at ARIN, it would be slated for the organization<br class="">
first on the waiting list.<br class="">
<br class="">
Staff Action<br class="">
<br class="">
ARIN staff can create a waiting list for 2-byte AS numbers if there is<br class="">
favor from the community to establish one. ARIN staff will open a<br class="">
consultation on the topic to gather feedback and take appropriate action<br class="">
based on information received through that process.<br class="">
<br class="">
Thank you for participating in the ARIN Consultation and Suggestion<br class="">
Process. We will leave this suggestion open until a consultation has<br class="">
been completed on this topic and an implementation plan has been<br class="">
established.<br class="">
<br class="">
Regards,<br class="">
<br class="">
Communications and Member Services<br class="">
American Registry for Internet Numbers (ARIN)<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
arin-suggestions mailing list<br class="">
<a href="mailto:arin-suggestions@arin.net" class="">arin-suggestions@arin.net</a><br class="">
<a href="http://lists.arin.net/mailman/listinfo/arin-suggestions" rel="noreferrer" target="_blank" class="">http://lists.arin.net/mailman/listinfo/arin-suggestions</a><br class="">
</div></div>_______________________________________________<br class="">
ARIN-Consult<br class="">
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br class="">
List (<a href="mailto:ARIN-consult@arin.net" class="">ARIN-consult@arin.net</a>).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" rel="noreferrer" target="_blank" class="">http://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br class="">
Help Desk at <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.<br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">ARIN-Consult<br class="">You are receiving this message because you are subscribed to the ARIN Consult Mailing<br class="">List (<a href="mailto:ARIN-consult@arin.net" class="">ARIN-consult@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="http://lists.arin.net/mailman/listinfo/arin-consult" class="">http://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br class="">Help Desk at <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.</div></blockquote></div><br class=""></div></body></html>