[ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs

Fri Apr 1 15:44:43 EDT 2016

If it happens at all, it should happen through the PDP.

Personally, I think that this is yet another excuse for further delays in 32-bit ASN integration and we shouldn’t be supporting it.

Owen

> On Apr 1, 2016, at 08:59 , Andrew Dul <andrew.dul at quark.net> wrote:
> 
> This suggestion would seem to be about who gets which number resources when, and thus perhaps should be handled by a policy change to the PDP.  Do others feel the same way? 
> 
> I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community.
> 
> Andrew
> 
> On 3/30/2016 5:17 PM, Scott Leibrand wrote:
>> 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.
>> 
>> -Scott
>> 
>> On Wed, Mar 30, 2016 at 5:13 PM, David Huberman <David_Huberman at outlook.com <mailto:David_Huberman at outlook.com>> wrote:
>> Apologies, but I have this data analysis done, and I dont want to lose it.   I can resend when the consultation officially opens.
>> 
>> 
>> I just did a quick data analysis of the DFZ found on one of my routers.
>> 
>> There are 601,729 unique routes originating from and transiting through 53,511 ASNs.
>> 
>> 71,170 routes (11.8%) originate from or propagate through a 4-byte ASN.
>> There are 10,244 (19.1%) unique 4-byte ASNs in my copy of the table.
>> 
>> 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.
>> 
>> ________________________________________
>> From: arin-suggestions-bounces at arin.net <mailto:arin-suggestions-bounces at arin.net> <arin-suggestions-bounces at arin.net <mailto:arin-suggestions-bounces at arin.net>> on behalf of ARIN <info at arin.net <mailto:info at arin.net>>
>> Sent: Wednesday, March 30, 2016 4:28 PM
>> To: arin-suggestions at arin.net <mailto:arin-suggestions at arin.net>
>> Subject: [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for     2 Byte ASNs
>> 
>> We received the following suggestion on 18 March:
>> 
>> Suggestion Details:
>> 
>> Description: Waiting list for 2 Byte ASNs
>> 
>> Value to Community: One member said to me:
>> 
>> Ticket from ARIN "We have noted your request for a 2-byte ASN. ARIN is
>> out of 2-byte ASN's in its inventory. We get them returned voluntarily
>> from time to time. If we have one at the time of issuance, we will issue
>> it to your organization. If we do not have a 2-byte in inventory at that
>> time, your organization will receive the standard 4-byte ASN. "
>> 
>> Member comment "if they are really out - a waitinglist would be nice...."
>> 
>> On 30 March, we sent the following response to the submitter:
>> 
>> Thank you for your suggestion numbered 2016.04 - Waiting List for 2 Byte
>> ASNs.
>> 
>> Background
>> 
>> The NRPM included instructions in the past for ARIN staff to remove any
>> distinction between 2-byte and 4-byte in the issuance of AS numbers.
>> This particular policy language has since been retired in the NRPM.
>> 
>> Staff has followed policy regarding issuance of AS numbers, but has
>> often had lower numbered, classic 2-byte, AS numbers available over
>> time. We would either receive them in our new delegations from the IANA,
>> obtain them from customer returns of AS numbers, or through revocations
>> of AS numbers due to non-payment of registration fees. Although ARIN
>> expects to no longer receive AS numbers from the IANA inside the classic
>> 2-byte range, we do expect to continue reclaiming them through returns
>> and revocations going forward.
>> 
>> Some AS number requests today continue to specifically ask for an AS
>> number from the classic 2-byte range. In those situations we relay to
>> the customer that we have noted their special request and that we will
>> accommodate it at the issuance phase of the ticket process if one is
>> available at the time.
>> 
>> The Suggestion
>> 
>> We understand your suggestion is to establish a waiting list for AS
>> numbers from the classic 2-byte range for those customers who
>> specifically request one when ARIN does not have them available. This
>> waiting list would be similar to the IPv4 waiting list for unmet
>> requests, but managed separately for AS numbers. Organizations would be
>> placed on this AS number waiting list, and when one became available
>> through reclamation at ARIN, it would be slated for the organization
>> first on the waiting list.
>> 
>> Staff Action
>> 
>> ARIN staff can create a waiting list for 2-byte AS numbers if there is
>> favor from the community to establish one. ARIN staff will open a
>> consultation on the topic to gather feedback and take appropriate action
>> based on information received through that process.
>> 
>> Thank you for participating in the ARIN Consultation and Suggestion
>> Process. We will leave this suggestion open until a consultation has
>> been completed on this topic and an implementation plan has been
>> established.
>> 
>> Regards,
>> 
>> Communications and Member Services
>> American Registry for Internet Numbers (ARIN)
>> 
>> 
>> _______________________________________________
>> arin-suggestions mailing list
>> arin-suggestions at arin.net <mailto:arin-suggestions at arin.net>
>> http://lists.arin.net/mailman/listinfo/arin-suggestions <http://lists.arin.net/mailman/listinfo/arin-suggestions>
>> _______________________________________________
>> ARIN-Consult
>> You are receiving this message because you are subscribed to the ARIN Consult Mailing
>> List (ARIN-consult at arin.net <mailto:ARIN-consult at arin.net>).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-consult <http://lists.arin.net/mailman/listinfo/arin-consult> Please contact the ARIN Member Services
>> Help Desk at info at arin.net <mailto:info at arin.net> if you experience any issues.
>> 
>> 
>> 
>> _______________________________________________
>> ARIN-Consult
>> You are receiving this message because you are subscribed to the ARIN Consult Mailing
>> List (ARIN-consult at arin.net <mailto:ARIN-consult at arin.net>).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-consult <http://lists.arin.net/mailman/listinfo/arin-consult> Please contact the ARIN Member Services
>> Help Desk at info at arin.net <mailto:info at arin.net> if you experience any issues.
> 
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services
> Help Desk at info at arin.net if you experience any issues.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20160401/cbcf9017/attachment.html>