From info at arin.net Thu May 7 06:27:42 2009 From: info at arin.net (Member Services) Date: Thu, 07 May 2009 06:27:42 -0400 Subject: Policy Proposal: Extend 16 bit ASN Assignments Message-ID: <4A02B79E.8060807@arin.net> ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with Policy Development Process. This proposal is in the first stage of the Policy Development Process. ARIN staff will perform the Clarity and Understanding step. Staff does not evaluate the proposal at this time, their goal is to make sure that they understand the proposal and believe the community will as well. Staff will report their results to the ARIN Advisory Council (AC) within 10 days. The AC will review the proposal at their next regularly scheduled meeting (if the period before the next regularly scheduled meeting is less than 10 days, then the period may be extended to the subsequent regularly scheduled meeting). The AC will decide how to utilize the proposal and announce the decision to the PPML. In the meantime, the AC invites everyone to comment on the proposal on the PPML, particularly their support or non-support and the reasoning behind their opinion. Such participation contributes to a thorough vetting and provides important guidance to the AC in their deliberations. The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Mailing list subscription information can be found at:https://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## 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 From info at arin.net Fri May 8 16:32:53 2009 From: info at arin.net (Member Services) Date: Fri, 08 May 2009 16:32:53 -0400 Subject: ARIN XXIII Meeting Report Now Available Message-ID: <4A0496F5.5020801@arin.net> From 26-29 April, the ARIN community took part in the ARIN XXIII Public Policy and Members Meeting, held in San Antonio. The report of that meeting, which includes presentations, summary notes, and transcripts of the entire meeting, is now available on the ARIN website at: http://www.arin.net/participate/meetings/reports/ARIN_XXIII/ Please check back next week when an archive of the meeting's webcast will be available. We thank everyone in the community who participated in person or remotely and those who responded to the surveys. We look forward to seeing you 21-23 October 2009 for ARIN XXIV in Dearborn, Michigan. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 20 10:06:27 2009 From: info at arin.net (Member Services) Date: Wed, 20 May 2009 10:06:27 -0400 Subject: Policy Proposal: IPv4 Example Shortages Message-ID: <4A140E63.6090007@arin.net> ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with Policy Development Process. This proposal is in the first stage of the Policy Development Process. ARIN staff will perform the Clarity and Understanding step. Staff does not evaluate the proposal at this time, their goal is to make sure that they understand the proposal and believe the community will as well. Staff will report their results to the ARIN Advisory Council (AC) within 10 days. The AC will review the proposal at their next regularly scheduled meeting (if the period before the next regularly scheduled meeting is less than 10 days, then the period may be extended to the subsequent regularly scheduled meeting). The AC will decide how to utilize the proposal and announce the decision to the PPML. In the meantime, the AC invites everyone to comment on the proposal on the PPML, particularly their support or non-support and the reasoning behind their opinion. Such participation contributes to a thorough vetting and provides important guidance to the AC in their deliberations. The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Mailing list subscription information can be found at:https://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal Name: IPv4 Example Shortages Proposal Originator:Martin J. Levy Proposal Version: 1.0 Date: 20 May 2009 Proposal type: new Policy term: permanent Policy statement: Add section 4.1.8 to the NRPM to state: 4.1.8 IPv4 Example Shortages Beginning on January 1, 2010, and on the first of each January and July thereafter, for a period of 7 calendar days, ARIN will not process requests from existing IPv4 holders for additional IPv4 space. Rationale: The IANA is expected to issue the last of the available IPv4 address space to RIRs some time in 2011. RIRs are expected to run out approximately one year later. These brief delays should be minimal (no) impact to organizations with existing space wanting more, but, can provide a brief but visible glimpse into the future that awaits after runout. Organizations which fail to plan for these delays will have the option of waiting for ARIN to issue their space, or, can avail themselves of the transfer policy contained in section 8.3 of the NRPM (resulting from policy proposals 2008-6 and 2009-1). The cost of these delays will be minimal compared to what will happen when space simply is no longer available. This policy has no impact on IPv6 assignments or allocations and has no impact on new organizations making their first IPv4 request. Timetable for implementation: 1 January 2010 From info at arin.net Tue May 26 14:26:52 2009 From: info at arin.net (Member Services) Date: Tue, 26 May 2009 14:26:52 -0400 Subject: Advisory Council Meeting Results - May 2009 Message-ID: <4A1C346C.3000509@arin.net> On 21 May 2009 the ARIN Advisory Council (AC) reviewed ?Policy Proposal 87: Extend 16 bit ASN Assignments? and accepted it onto the AC's docket for development and evaluation. In addition, the AC conducted their last call review of ?Draft Policy 2008-7: Identify Invalid WHOIS POC?s?. The AC found support for the draft policy and recommended it to the ARIN Board of Trustees for adoption. Draft Policy and Policy Proposal texts are available at: https://www.arin.net/policy/proposals/index.html The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri May 29 11:11:13 2009 From: info at arin.net (Member Services) Date: Fri, 29 May 2009 11:11:13 -0400 Subject: Policy Proposal: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries Message-ID: <4A1FFB11.9080101@arin.net> ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with Policy Development Process. This proposal is in the first stage of the Policy Development Process. ARIN staff will perform the Clarity and Understanding step. Staff does not evaluate the proposal at this time, their goal is to make sure that they understand the proposal and believe the community will as well. Staff will report their results to the ARIN Advisory Council (AC) within 10 days. The AC will review the proposal at their next regularly scheduled meeting (if the period before the next regularly scheduled meeting is less than 10 days, then the period may be extended to the subsequent regularly scheduled meeting). The AC will decide how to utilize the proposal and announce the decision to the PPML. In the meantime, the AC invites everyone to comment on the proposal on the PPML, particularly their support or non-support and the reasoning behind their opinion. Such participation contributes to a thorough vetting and provides important guidance to the AC in their deliberations. The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Mailing list subscription information can be found at:https://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries Proposal Originator: Stacy Hughes and Andrew de la Haye Proposal Version: 1.0 Date: 29 May 2009 Proposal type: modify Policy term: permanent Policy statement: Modification of NRPM section 10.3 extending the deadline for an undifferentiated ASN pool by 1 year to read: 1. Allocation Principles IANA allocates ASNs to RIRs in blocks of 1024 ASNs. In this document the term "ASN block" refers to a set of 1024 ASNs. Until 31 December 2010, allocations of 16-bit and 32-bit only ASN blocks will be made separately and independent of each other [1]. This means until 31 December 2010, RIRs can receive two separate ASN blocks, one for 16-bit ASNs and one for 32-bit only ASNs from the IANA under this policy. After this date, IANA and the RIRs will cease to make any distinction between 16-bit and 32-bit only ASNs, and will operate ASN allocations from an undifferentiated 32-bit ASN allocation pool. Rationale: a. Arguments supporting the proposal Due to operational issues external to the IANA/RIR policy process, 32-bit only ASNs are not being issued by the RIRs at the anticipated rate. As it stands, RIRs will likely not be able to justify a new block of ASNs from the IANA after 31 December 2009 due to a glut of free 32 bit only ASNs in the RIR?s pool. This leaves available, essential 16-bit ASNs stranded in the IANA free pool. This proposal seeks to remedy the potential problem by extending the deadline for differentiation by one year. With this proposal the policy will be aligned with the actual reality in regards to 32-bit ASN deployment and usage. The subject was raised during RIPE 58 and a presentation was made: http://www.ripe.net/ripe/meetings/ripe-58/content/presentations/asn32-take-up-report.pdf The feedback in this session suggested that a global policy proposal should be developed and should be discussed. b. Arguments opposing the proposal Some may think that extending the previously set timeline can be perceived as some discouragement for the deployment of 32-bit ASNs. One counter argument to this is that RIRs and Internet community have some other mechanisms and activities to raise awareness for 32-bit ASN pool (via public presentations and trainings). These activities will continue while 16-bit ASN blocks are still allocated to RIRs by the IANA as they are available and they are needed. Timetable for implementation: Immediately upon ratification by ICANN Board From info at arin.net Fri May 29 11:14:45 2009 From: info at arin.net (Member Services) Date: Fri, 29 May 2009 11:14:45 -0400 Subject: Policy Proposal: Open Access To IPv6 Message-ID: <4A1FFBE5.20807@arin.net> ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with Policy Development Process. This proposal is in the first stage of the Policy Development Process. ARIN staff will perform the Clarity and Understanding step. Staff does not evaluate the proposal at this time, their goal is to make sure that they understand the proposal and believe the community will as well. Staff will report their results to the ARIN Advisory Council (AC) within 10 days. The AC will review the proposal at their next regularly scheduled meeting (if the period before the next regularly scheduled meeting is less than 10 days, then the period may be extended to the subsequent regularly scheduled meeting). The AC will decide how to utilize the proposal and announce the decision to the PPML. In the meantime, the AC invites everyone to comment on the proposal on the PPML, particularly their support or non-support and the reasoning behind their opinion. Such participation contributes to a thorough vetting and provides important guidance to the AC in their deliberations. The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Mailing list subscription information can be found at:https://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal Name: Open Access To IPv6 Proposal Originator: Stacy Hughes and Cathy Aronson Proposal Version: 1.0 Date: 29 May 2009 Proposal type: modify Policy term: permanent Policy statement: 1) Remove ?by advertising that connectivity through its single aggregated address allocation? from article 3 of section 6.5.1.1 2) Remove article 4 of section 6.5.1.1, ?be an existing, known ISP in the ARIN region or have a plan for making at least 200 end-site assignments to other organizations within 5 years? in its entirety. Rationale: It is acknowledged that these concepts have been put before the community in the past. However, with the wisdom of actual operational experience, the necessity of promoting IPv6 adoption throughout our region, and emerging native v6 only network models, it becomes obvious that these modifications to the NRPM are necessary. Removing the 200 end site requirement enables smaller, but no less important and viable, networks access to IPv6. Removing the ?known ISP? requirement enfranchises new, native v6 businesses that can drive innovation and expansion in the Internet industry, as well as other industries. Removing the requirement for a single aggregate announcement benefits the NRPM itself, as it has been decided by the community that it should not contain routing advice. Timetable for implementation: immediately upon BoT ratification