[arin-ppml] Policy Proposal: Extend 16 bit ASN Assignments

Scott Leibrand scottleibrand at gmail.com
Thu May 7 16:19:36 EDT 2009


I disagree.  We are still waiting to get a release of the code train we 
use on the Cisco 7600 platform that supports 32-bit ASNs.  It sounds 
like they're finally getting close, but I think a further extension 
probably would be helpful.

We'll have a much better view of what's required by the fall meeting, 
when this is up for discussion.  Since that will be our last chance to 
change policy before the current 1 Jan 2010 deadline, I definitely think 
this needs to be on the agenda.

-Scott

Owen DeLong wrote:
> NIT:  The revised text of 5.1 (or at least specific amendments to it) 
> should be
> stated as part of the Policy statement. The rationale section is not a 
> binding
> part of the policy.
>
> Substance: This policy simply isn't needed. Current software for most
> routers supports 32 bit ASNs. There's been ample warning for providers
> and other organizations to update their management systems, scripts,
> etc. If they haven't done it by now, they are only going to do it in 
> response
> to the change actually happening.  Putting it off further does not really
> benefit the community.
>
> I am opposed to this policy as written.
>
>> ## * ##
>>
>>
>> Policy Proposal Name: Extend 16 bit ASN Assignments
>>
>> Proposal Originator: Marla Azinger
>>
>> Proposal Version: 1
>>
>> Submission Date: 6 May 2009
>>
>> Proposal type: Modify
>>
>> Policy term: Permanent
>>
>> Policy statement: This proposal is to modify section 5.1 in the NRPM to
>> extend the 16-bit ASN assignment timeframe for one more year further
>> than the current text. The expiration requiring removal of section 5.1
>> is also being removed.
>>
>> Rationale:
>>
>> Currently users of 32-bit ASN’s are encountering technical issues that
>> they can’t immediately overcome and therefore require 16-bit ASN’s to
>> operate. As a result in the ARIN region to date, 204 of the 216 32-bit
>> ASN’s that have been assigned have been returned and exchanged for a 16
>> bit ASN. On 1 JAN 2010 ARIN policy declares zero distinction between
>> 32-bit and 16-bit ASN’s. This proposal is to change the date on the
>> third line of NRPM 5.1 and extend the timeframe for 16 bit ASN’s to be
>> assigned. If these changes are made then ARIN RIR ASN policy will read
>> clearly and remove any misconceptions of 16-bit cutoff post run out and
>> enable technology to catch up to the ASN bit change. The expiration date
>> that requires removal of section 5.1 after zero distinction occurs is to
>> be removed. Instead section 5.1 will be left in place in the NRPM for
>> value added historical purposes.
>>
>> The revision of 5.1 would read as follows:
>>
>> 5.1 16-bit and 32-bit AS Numbers
>>
>> • Commencing 1 January 2007, ARIN will process applications that
>> specifically request 32-bit only AS Numbers and assign such AS numbers
>> as requested by the applicant. In the absence of any specific request
>> for a 32-bit only AS Number, a 16-bit only AS Number will be assigned.
>>
>> • Commencing 1 January 2009, ARIN will process applications that
>> specifically request 16-bit only AS Numbers and assign such AS Numbers
>> as requested by the applicant. In the absence of any specific request
>> for a 16-bit only AS Number, a 32-bit only AS Number will be assigned.
>>
>> • Commencing 1 January 2011, ARIN will cease to make any distinction
>> between 16-bit only AS Numbers and 32-bit only AS Numbers, and will
>> operate AS number assignments from an undifferentiated 32-bit AS Number
>> pool.
>>
>> Terminology
>>
>> • "16-bit only AS Numbers" refers to AS numbers in the range 0 - 65535
>>
>> • "32-bit only AS Numbers" refers to AS Numbers in the range 65,536 -
>> 4,294,967,295
>>
>> • "32-bit AS Numbers" refers to AS Numbers in the range 0 - 
>> 4,294,967,295
>>
>> Timetable for implementation: Immediate
>>
>>
>> _______________________________________________
>> PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.



More information about the ARIN-PPML mailing list