From info at arin.net Thu Dec 2 13:43:44 2010 From: info at arin.net (ARIN) Date: Thu, 02 Dec 2010 13:43:44 -0500 Subject: [arin-announce] Important Update Regarding Resource Certification Message-ID: <4CF7E8E0.4030303@arin.net> We previously announced that ARIN intends to provide a production-grade Resource Certification service starting 1 January 2011. As a result of an extensive review in preparation for offering this service, we have determined that additional functionality must be added to the service architecture to mitigate specific security concerns. These features will delay ARIN?s production release until very early in the second quarter of 2011. We apologize for the inconvenience that this may cause ARIN participants; however, we think you will like the result. In the meantime, the ARIN community is encouraged to join ARIN?s Resource Certification pilot as an interim measure. This pilot has been in place since June 2009. For more information concerning Resource Certification and ARIN?s pilot program, visit http://www.arin.net/resources/rpki.html. Regards, Mark Kosters Chief Technical Officer American Registry for Internet Numbers (ARIN) From info at arin.net Thu Dec 2 14:03:32 2010 From: info at arin.net (ARIN) Date: Thu, 02 Dec 2010 14:03:32 -0500 Subject: [arin-announce] [Fwd: Policy Proposal 124: Clarification of Section 4.2.4.4] Message-ID: <4CF7ED84.3090107@arin.net> The following is a new policy proposal that has been posted to the ARIN Public Policy Mailing List for discussion on that list. Reminder: RSS feeds of all posts to the Public Policy Mailing List (PPML) and just postings by ARIN to PPML are available at: https://www.arin.net/participate/mailing_lists/rss.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) -------- Original Message -------- Subject: Policy Proposal 124: Clarification of Section 4.2.4.4 Date: Thu, 02 Dec 2010 14:02:35 -0500 From: ARIN To: arin-ppml at arin.net ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with the Policy Development Process. The ARIN Advisory Council (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. 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. Draft Policies and Proposals under discussion can be found 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 Mailing list subscription information can be found at: https://www.arin.net/mailing_lists/ Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 124: Clarification of Section 4.2.4.4 Proposal Originator: Martin Hannigan and Chris Grundemann Proposal Version: 1.0 Date: 2 December 2010 Proposal type: Modify, complete replacement of 4.2.4.4 Policy term: Permanent Policy statement: 4.2.4.4. Subscriber Members After One Year After an organization has been a subscriber member of ARIN for one year, that organization may choose to request up to a 12 month supply of IP addresses. On the date that ARIN receives its last /8 as a result of the IANA executing section 10.4.2.2 of the NRPM and in accordance with the Global Policy for the Allocation of the Remaining IPv4 Address Space, the length of supply that any organization may request from ARIN from that moment forward will be reduced to three months. Any pending request submitted prior to that moment will continue to be eligible for a twelve month supply of addresses as long as need is established within thirty days of that moment. Rationale: ARIN's pending operational practice is that if an organization has a request in the ARIN hostmaster queue for IPv4 resources when the IANA declares the exhaustion phase (10.4.2.2), their request will be automatically truncated from a twelve month supply to a three month supply since policy in effect at the time of exhaustion will apply. 8.3 and 4.2.4.4 are currently "in effect". Example: If an entity is asking for 4 x /24 for a 12 month period and IANA exhaustion occurs, a requester will receive, if justified, 1 x /24. If an entity is asking for 120 x /24 at the time that exhaustion occurs, they would only receive 30 x /24 if justified. If ARIN determines that this same entity would only qualify for 90 of the 120 x /24 requested, then that entity would only receive 22 x /24. ARIN has the equivalent of almost a /8 in at least one reserve, has recently received 2 /8's, received ~391 x /16's as a result of the distribution of "various registries" from the IANA and is guaranteed to receive at least one additional /8 (aggregate of about 92 million individual IPv4 addresses) as a result of the execution of 10.4.2.2 by the IANA. Considering the size of the supply, it would seem prudent to provide for all members needs in a fair and consistent manner as long as possible in order to support the continued orderly transition of the Internet to IPv6. The ARIN AC should review and determine what action if any should be taken at their next available opportunity, or sooner if they deem warranted. From info at arin.net Fri Dec 3 10:28:53 2010 From: info at arin.net (ARIN) Date: Fri, 03 Dec 2010 10:28:53 -0500 Subject: [arin-announce] [Fwd: Policy Proposal 125: Efficient Utilization of IPv4 Requires Dual-Stack] Message-ID: <4CF90CB5.2070002@arin.net> The following is a new policy proposal that has been posted to the ARIN Public Policy Mailing List for discussion on that list. Reminder: RSS feeds of all posts to the Public Policy Mailing List (PPML) and just postings by ARIN to PPML are available at: https://www.arin.net/participate/mailing_lists/rss.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) -------- Original Message -------- Subject: Policy Proposal 125: Efficient Utilization of IPv4 Requires Dual-Stack Date: Fri, 03 Dec 2010 10:28:18 -0500 From: ARIN To: arin-ppml at arin.net ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with the Policy Development Process. The ARIN Advisory Council (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. 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. Draft Policies and Proposals under discussion can be found 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 Mailing list subscription information can be found at: https://www.arin.net/mailing_lists/ Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 125: Efficient Utilization of IPv4 Requires Dual-Stack Proposal Originator: Chris Grundemann, Martin Hannigan, Jason Schiller Proposal Version: 1 Date: 3 December 2010 Proposal type: modify Policy term: permanent Policy Statement: * Add the following sections to section 4.1: 4.1.2. Efficient Utilization IPv4 addresses are a finite resource and as such are required to be efficiently utilized by resource holders in order to maximize their benefit to the community. 4.1.3. Dual-Stack Dual-stack refers to configuring both an IPv4 and an IPv6 address or network together on the same network infrastructure. All new IPv4 addresses assigned, allocated or transfered to an organization must be deployed on dual-stacked interfaces along with IPv6 addresses. 4.1.4. IPv6 Deployment When addresses are used to provide an Internet facing service, the service must be fully IPv6 accessible (if you deploy an A record, you must also have a AAAA record, and both must answer). * Add the following sentance to the end of sections 4.2.1.6, 4.2.2.1.2, 4.2.2.2.1, 4.2.3.1. and 4.3.4: In accordance with section 4.1.3 and 4.1.4, all new addresses must be deployed on dual-stacked interfaces and all Internet facing services provided by new addresses must be fully IPv6 accessible. * Re-write section 4.2.3.4.1. to: Reassignment information for prior allocations must show that each customer meets the 80% utilization criteria, the dual-stack criteria and must be available via SWIP / RWhois prior to your issuing them additional space. * Add the following section to section 4.2.4: 4.2.4.5. IPv6 Deployment In order to receive additional space ISPs must provide detailed documentation demonstrating that: - for every IPv4 address requested, at least one pre-existing interface is dual stacked, up to 80% of all interfaces and - for every down stream customer site where the new addresses will be deployed, at least one pre-existing down stream customer site is IPv6 enabled, up to 80% of the total customer base. * Add the following to section 4.3.6: 4.3.6.3. IPv6 Deployment In order to receive additional space end-users must provide detailed documentation demonstrating that at least 80% of their existing IPv4 addresses are deployed on dual-stacked interfaces in accordance with section 4.1.3. Rational: In this period of available IPv4 address scarcity and transition to IPv6, IPv4 addresses that are not deployed along with IPv6 are simply not being efficiently utilized. Although we have likely failed to deploy dual-stack in a meaningful way in time to avoid transition problems, we can still choose the correct path for future assignments, allocations and transfers. This proposal has three objectives: -1- Encourage IPv6 deployment prior to and post depletion -2- Enable growth of IPv4 to accelerate IPv6 transition #[only change was to this line]# -3- Improve the utilization of IP addresses It accomplishes these goals by enforcing three basic ideals: -1- ARIN will only make allocations and assignments for networks that have already deployed production IPv6 -2- Any new IPv4 addresses received, must be deployed along side of IPv6 (dual-stacked) -3- Firmly encourages deployment of IPv6 in existing IPv4-only networks The specific requirements to be enforced can be summed up in this way: ~ New addresses must be deployed on dual-stacked interfaces plus one additional pre-existing IPv4-only interface must be dual-stacked per new address, up to 80% of all interfaces. ~ For each down stream customer site where these addresses are deployed, another pre-existing IPv4 only down stream site must also be IPv6 enabled, up to 80% of the total customer base. ~ All end-sites must dual-stack before getting new space. ~ Internet facing services that new IPv4 addresses are used to provide must be fully IPv6 accessible. From info at arin.net Thu Dec 9 11:09:26 2010 From: info at arin.net (ARIN) Date: Thu, 09 Dec 2010 11:09:26 -0500 Subject: [arin-announce] Ron da Silva Appointed to Address Supporting Organization Advisory Council Message-ID: <4D00FF36.5080905@arin.net> On 22 November 2010, the ARIN Board of Trustees voted to appoint Ron da Silva of Time Warner Cable to the Address Supporting Organization Advisory Council for a one-year term beginning 1 January 2011. He will fill the seat being vacated by Marty Hannigan, who begins a three-year term on the ARIN Advisory Council 1 January 2011. Following published procedures for interim appointments, the Board voted by secret ballot, and the person receiving the majority of votes of the active members of the Board became the appointee. Details are available at https://www.arin.net/participate/elections/nronumbercouncil.html#ncinterim. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Dec 15 16:02:52 2010 From: info at arin.net (ARIN) Date: Wed, 15 Dec 2010 16:02:52 -0500 Subject: [arin-announce] Planned Changes to IPv4 Reverse DNS Infrastructure Message-ID: <4D092CFC.2050008@arin.net> ARIN and ICANN are planning changes to the infrastructure which supports the IPv4 Reverse DNS, the part of the DNS which provides the ability to look up an IPv4 address and convert it to a name. With this change the IN-ADDR.ARPA zone will move to new, dedicated nameservers, five operated by the Regional Internet Registries (RIRs) and one operated by ICANN. ARIN has carried out the DNS zone maintenance function for IN-ADDR.ARPA since 1997. This function will transition in February 2011 to ICANN and will be managed concurrently with the central assignment of IPv4 address space to RIRs. Once the IN-ADDR.ARPA zone is being maintained by ICANN it will also be signed using DNS Security Extensions (DNSSEC), providing end-users with the ability to validate answers to reverse DNS queries. For more information and details please see: http://blog.icann.org/2010/12/planned-changes-to-ipv4-reverse-dns-infrastructure/ and http://in-addr-transition.icann.org/. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)