<HTML><head><META content="text/html; charset=utf-8" http-equiv="Content-Type">
<STYLE><!-- /* Style Definitions */ p.0d196a6b-1a79-4af3-be95-f962d2a57edb, li.0d196a6b-1a79-4af3-be95-f962d2a57edb, div.0d196a6b-1a79-4af3-be95-f962d2a57edb, table.0d196a6b-1a79-4af3-be95-f962d2a57edbTable {margin:0cm; margin-bottom:.0001pt;} div.Section1 {page:Section1;} --></STYLE>
<TITLE>Re: [arin-ppml] Policy Proposal: Extend 16 bit ASN Assignments</TITLE>
</head><BODY>
<P>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi Aaron,<BR>
<BR>
What changes would you propose to the policy? Or do you just see it as totally unnecessary? Thanks.<BR>
<BR>
<BR>
On 5/7/09 4:51 PM, "Aaron Hughes" <<a href="aaronh@bind.com">aaronh@bind.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
I oppose this policy as written.<BR>
<BR>
Looking at ARIN's historical statistics, it appears as though ARIN issues 1,600 to 1,700 ASNs each year.<BR>
<BR>
Looking at IANA's stats:<BR>
35840-36863 Assigned by ARIN 2005-02<BR>
39936-40959 Assigned by ARIN 2006-03-29<BR>
46080-47103 Assigned by ARIN 2008-03-27<BR>
53248-54271 Assigned by ARIN 2009-04-21<BR>
54272-55295 Assigned by ARIN 2009-04-21<BR>
Excluding April 2009, ARIN has only requested 3,072 ASNs since February 2005.<BR>
<BR>
Looking again at ARIN's historical statistics, they have issued 6,550 ASNs from 2005 through 2008, but have only gotten 3,072 ASNs from the IANA.<BR>
<BR>
Where's the difference?<BR>
In San Antonio, Leslie gave a presentation that included information about returned and revoked ASNs. Slide 10 of the presentation indicates 4,357 ASNs have been returned to ARIN since January 2005.<BR>
<BR>
So it looks like ARIN is recycling unused ASNs, prolonging the lifespan of the free 16-bit ASN pool.<BR>
Projecting this forward, at current consumption rates it should take approximately 32 months for ARIN to use up the 2,048 ASNs issued on 2009-04-21 by IANA, which puts us somewhere near December 2012.<BR>
<BR>
ARIN's historical statistics:<BR>
<a href="https://www.arin.net/knowledge/statistics/historical.html">https://www.arin.net/knowledge/statistics/historical.html</a><BR>
IANA's stats:<BR>
<a href="http://www.iana.org/assignments/as-numbers/">http://www.iana.org/assignments/as-numbers/</a><BR>
Presentation foils:<BR>
<a href="https://www.arin.net/participate/meetings/reports/ARIN_XXIII/ppt/wednesday/rsd.ppt">https://www.arin.net/participate/meetings/reports/ARIN_XXIII/ppt/wednesday/rsd.ppt</a><BR>
<BR>
Cheers,<BR>
Aaron<BR>
<BR>
<BR>
On Thu, May 07, 2009 at 01:19:36PM -0700, Scott Leibrand wrote:<BR>
> I disagree. We are still waiting to get a release of the code train we<BR>
> use on the Cisco 7600 platform that supports 32-bit ASNs. It sounds<BR>
> like they're finally getting close, but I think a further extension<BR>
> probably would be helpful.<BR>
><BR>
> We'll have a much better view of what's required by the fall meeting,<BR>
> when this is up for discussion. Since that will be our last chance to<BR>
> change policy before the current 1 Jan 2010 deadline, I definitely think<BR>
> this needs to be on the agenda.<BR>
><BR>
> -Scott<BR>
><BR>
> Owen DeLong wrote:<BR>
> > NIT: The revised text of 5.1 (or at least specific amendments to it)<BR>
> > should be<BR>
> > stated as part of the Policy statement. The rationale section is not a<BR>
> > binding<BR>
> > part of the policy.<BR>
> ><BR>
> > Substance: This policy simply isn't needed. Current software for most<BR>
> > routers supports 32 bit ASNs. There's been ample warning for providers<BR>
> > and other organizations to update their management systems, scripts,<BR>
> > etc. If they haven't done it by now, they are only going to do it in<BR>
> > response<BR>
> > to the change actually happening. Putting it off further does not really<BR>
> > benefit the community.<BR>
> ><BR>
> > I am opposed to this policy as written.<BR>
> ><BR>
> >> ## * ##<BR>
> >><BR>
> >><BR>
> >> Policy Proposal Name: Extend 16 bit ASN Assignments<BR>
> >><BR>
> >> Proposal Originator: Marla Azinger<BR>
> >><BR>
> >> Proposal Version: 1<BR>
> >><BR>
> >> Submission Date: 6 May 2009<BR>
> >><BR>
> >> Proposal type: Modify<BR>
> >><BR>
> >> Policy term: Permanent<BR>
> >><BR>
> >> Policy statement: This proposal is to modify section 5.1 in the NRPM to<BR>
> >> extend the 16-bit ASN assignment timeframe for one more year further<BR>
> >> than the current text. The expiration requiring removal of section 5.1<BR>
> >> is also being removed.<BR>
> >><BR>
> >> Rationale:<BR>
> >><BR>
> >> Currently users of 32-bit ASN?s are encountering technical issues that<BR>
> >> they can?t immediately overcome and therefore require 16-bit ASN?s to<BR>
> >> operate. As a result in the ARIN region to date, 204 of the 216 32-bit<BR>
> >> ASN?s that have been assigned have been returned and exchanged for a 16<BR>
> >> bit ASN. On 1 JAN 2010 ARIN policy declares zero distinction between<BR>
> >> 32-bit and 16-bit ASN?s. This proposal is to change the date on the<BR>
> >> third line of NRPM 5.1 and extend the timeframe for 16 bit ASN?s to be<BR>
> >> assigned. If these changes are made then ARIN RIR ASN policy will read<BR>
> >> clearly and remove any misconceptions of 16-bit cutoff post run out and<BR>
> >> enable technology to catch up to the ASN bit change. The expiration date<BR>
> >> that requires removal of section 5.1 after zero distinction occurs is to<BR>
> >> be removed. Instead section 5.1 will be left in place in the NRPM for<BR>
> >> value added historical purposes.<BR>
> >><BR>
> >> The revision of 5.1 would read as follows:<BR>
> >><BR>
> >> 5.1 16-bit and 32-bit AS Numbers<BR>
> >><BR>
> >> ? Commencing 1 January 2007, ARIN will process applications that<BR>
> >> specifically request 32-bit only AS Numbers and assign such AS numbers<BR>
> >> as requested by the applicant. In the absence of any specific request<BR>
> >> for a 32-bit only AS Number, a 16-bit only AS Number will be assigned.<BR>
> >><BR>
> >> ? Commencing 1 January 2009, ARIN will process applications that<BR>
> >> specifically request 16-bit only AS Numbers and assign such AS Numbers<BR>
> >> as requested by the applicant. In the absence of any specific request<BR>
> >> for a 16-bit only AS Number, a 32-bit only AS Number will be assigned.<BR>
> >><BR>
> >> ? Commencing 1 January 2011, ARIN will cease to make any distinction<BR>
> >> between 16-bit only AS Numbers and 32-bit only AS Numbers, and will<BR>
> >> operate AS number assignments from an undifferentiated 32-bit AS Number<BR>
> >> pool.<BR>
> >><BR>
> >> Terminology<BR>
> >><BR>
> >> ? "16-bit only AS Numbers" refers to AS numbers in the range 0 - 65535<BR>
> >><BR>
> >> ? "32-bit only AS Numbers" refers to AS Numbers in the range 65,536 -<BR>
> >> 4,294,967,295<BR>
> >><BR>
> >> ? "32-bit AS Numbers" refers to AS Numbers in the range 0 -<BR>
> >> 4,294,967,295<BR>
> >><BR>
> >> Timetable for implementation: Immediate<BR>
> >><BR>
> >><BR>
> >> _______________________________________________<BR>
> >> PPML<BR>
> >> You are receiving this message because you are subscribed to<BR>
> >> the ARIN Public Policy Mailing List (<a href="ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<BR>
> >> Unsubscribe or manage your mailing list subscription at:<BR>
> >> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><BR>
> >> Please contact <a href="info@arin.net">info@arin.net</a> if you experience any issues.<BR>
> ><BR>
> > ------------------------------------------------------------------------<BR>
> ><BR>
> > _______________________________________________<BR>
> > PPML<BR>
> > You are receiving this message because you are subscribed to<BR>
> > the ARIN Public Policy Mailing List (<a href="ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<BR>
> > Unsubscribe or manage your mailing list subscription at:<BR>
> > <a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><BR>
> > Please contact <a href="info@arin.net">info@arin.net</a> if you experience any issues.<BR>
> --<BR>
> PPML<BR>
> You are receiving this message because you are subscribed to<BR>
> the ARIN Public Policy Mailing List (<a href="ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<BR>
> Unsubscribe or manage your mailing list subscription at:<BR>
> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><BR>
> Please contact <a href="info@arin.net">info@arin.net</a> if you experience any issues.<BR>
<BR>
--<BR>
<BR>
Aaron Hughes<BR>
<a href="aaronh@bind.com">aaronh@bind.com</a><BR>
(703) 244-0427<BR>
Key fingerprint = AD 67 37 60 7D 73 C5 B7 33 18 3F 36 C3 1C C6 B8<BR>
<a href="http://www.bind.com/">http://www.bind.com/</a><BR>
_______________________________________________<BR>
PPML<BR>
You are receiving this message because you are subscribed to<BR>
the ARIN Public Policy Mailing List (<a href="ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<BR>
Unsubscribe or manage your mailing list subscription at:<BR>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><BR>
Please contact <a href="info@arin.net">info@arin.net</a> if you experience any issues.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
<BR><SPAN LANG="EN-GB" STYLE="FONT-SIZE: 14pt; COLOR: green; FONT-FAMILY: Webdings">P</SPAN> <FONT COLOR="green" FACE="Verdana" SIZE="2">Go Green! Print this email only when necessary. Thank you for helping Time Warner Cable be environmentally responsible.</FONT></P>
<P> </P>
<P></P>
<P><FONT COLOR="green" FACE="Verdana" SIZE="2"> </FONT></P>
<P CLASS="0d196a6b-1a79-4af3-be95-f962d2a57edb"><FONT COLOR="#008000" FACE="Verdana" SIZE="1"></FONT></P>
<P CLASS="0d196a6b-1a79-4af3-be95-f962d2a57edb"></P><pre>This E-mail and any of its attachments may contain Time Warner
Cable proprietary information, which is privileged, confidential,
or subject to copyright belonging to Time Warner Cable. This E-mail
is intended solely for the use of the individual or entity to which
it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents
of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any
copy of this E-mail and any printout.
</pre></BODY></HTML>