[arin-ppml] ARIN 2-Byte ASN inventory and issuance

Owen DeLong owen at delong.com
Mon Apr 11 17:06:36 EDT 2016


> On Apr 11, 2016, at 12:24 , John Curran <jcurran at arin.net> wrote:
> 
>> 
>> On Apr 11, 2016, at 3:18 PM, Owen DeLong <owen at delong.com> wrote:
>> 
>> Pesonally, I believe we have a terminology problem more than anything else.
>> 
>> At this time, we should no longer be even considering “2-byte” ASNs.
>> 
>> There are two classes of 4-byte ASNs. The idea of 2-byte ASNs should be considered anachronistic.
>> 
>> The classes of 4-byte ASNs are those that are ≤65535 and those that are ≥65536.
>> 
>> 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).
>> 
>> The latter class cannot be used as a 2-byte ASN in such cases.
>> 
>> In all cases, continuing to talk about 2-byte ASNs IMHO contributes to the misperception that the internet has not yet moved on.
>> 
>> 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.
> 
> Since parties coming to ARIN are distinguishing between these classes of 4-byte ASNs 
> and come back explicitly asking for one ≤65535, are you suggesting that ARIN not hold
> these lower ones to be able to satisfy such requests?

Yes.

I believe that we, more than any other region, have been lazy in our adoption of current internet technologies to the detriment of the internet at large.

I believe that continuing to facilitate this is not providing a useful service to the internet as a whole.

Owen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20160411/aa06e204/attachment.html>


More information about the ARIN-PPML mailing list