From info at arin.net Wed Jan 7 17:20:43 2009 From: info at arin.net (Member Services) Date: Wed, 07 Jan 2009 17:20:43 -0500 Subject: ARIN Policy Development Process Message-ID: <49652ABB.9060703@arin.net> On 3 December 2008 the ARIN Board of Trustees adopted the ARIN Policy Development Process (PDP), available at: http://www.arin.net/policy/pdp.html The new PDP is effective today, 7 January 2009. All open proposals have been transitioned to the new PDP. The following two proposals are still in last call. After last call the ARIN Advisory Council (AC) will conduct their last call review: 2007-14: Resource Review Process 2008-6: Emergency Transfer Policy for IPv4 Addresses The following two proposals were presented at the last ARIN Public Policy Meeting and the AC elected to continue to work on them. They are on the AC?s docket: 2008-3: Community Networks IPv6 Allocation 2008-7: Whois Integrity Policy Proposal The following two proposals are in the first stage of the policy development process. They will be reviewed by ARIN staff for clarity and understanding, and a report of that review will be provided to the AC: Policy Proposal: IPv4 Recovery Fund Policy Proposal: Depleted IPv4 reserves All of these proposals can be found at the Proposal Archive at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu Jan 8 16:01:38 2009 From: info at arin.net (Member Services) Date: Thu, 08 Jan 2009 16:01:38 -0500 Subject: Board adopts 2008-5: Dedicated IPv4 block to facilitate IPv6 Deployment Message-ID: <496669B2.7030107@arin.net> On 5 January 2009 the ARIN Board of Trustees adopted the following policy proposal: 2008-5: Dedicated IPv4 block to facilitate IPv6 Deployment 2008-5 will be implemented no later than 31 May 2009. The policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2008_5.html Regards, Member Services Department American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2008-5 Dedicated IPv4 block to facilitate IPv6 deployment Policy statement: When ARIN receives its last /8 IPv4 allocation from IANA, a contiguous /10 IPv4 block will be set aside and dedicated to facilitate IPv6 deployment. Allocations and assignments from this block must be justified by immediate IPv6 deployment requirements. Examples of such needs include: IPv4 addresses for key dual stack DNS servers, and NAT-PT or NAT464 translators. ARIN staff will use their discretion when evaluating justifications. This block will be subject to a minimum size allocation of /28 and a maximum size allocation of /24. ARIN should use sparse allocation when possible within that /10 block. In order to receive an allocation or assignment under this policy: 1. the applicant may not have received resources under this policy in the preceding six months; 2. previous allocations/assignments under this policy must continue to meet the justification requirements of this policy; 3. previous allocations/assignments under this policy must meet the utilization requirements of end user assignments; 4. the applicant must demonstrate that no other allocations or assignments will meet this need; 5. on subsequent allocation under this policy, ARIN staff may require applicants to renumber out of previously allocated / assigned space under this policy in order to minimize non-contiguous allocations. Rationale for reserving IPv4 space: This policy provides predictability on how the end game of IPv4 is going to be played after IANA completion. It will facilitate IPv6 deployment by ensuring that some small chunks of IPv4 space will remain available for a long time to ease the co-existence of IPv4 & IPv6. Rationale for reserving a contiguous /10 This is a balance between setting aside too much space and not having enough to facilitate IPv6 deployment for many years. Out of the last /8, that would leave the equivalent of 3 /10 to ARIN either for business as usual or for other policies in the spirit of this one. A /10 represents 4,194,304 IP addresses, If all of them were to be used in NAT-PT or NAT464 type devices with a consolidation factor of 100 users behind each IP address, that would represent about 400 million users. Most networks today filter IPv4 announcements more specific than /24. This policy creates allocations & assignment prefixes as long as /28. Allocating out of a contiguous block will mitigate the impact of this policy on filter lists. Rationale for minimum size allocation of /28 This minimum size allocation will put a cap at 250k additional entries in the global IPv4 routing table. Rationale for maximum size allocation of /24 and for the 6 month delay between allocations This maximum allocation size coupled with the requirement of a 6 months delay between allocations will prevent hoarding and make sure this pool will last several years. Rationale for forced renumbering for further allocation The minimum allocation size of /28 may create a huge increase in the IPv4 routing table size. Forcing renumbering for subsequent allocations under this policy will somehow limit the growth of the routing table size by enabling the announcement of aggregated space. It is expected that the savings in routing table entries will outweigh the pain of forced renumbering. However, renumbering is never an easy task, so it should only be considered as last resort. it is expected that sparse allocation techniques will prevent the need of force renumbering for a fairly long time. Note: This policy proposal hints that the /10 should come out of the last /8 received by ARIN from IANA. However, it does not say so explicitly, leaving the final decision up to the ARIN staff. Timetable for implementation: As soon as ARIN gets its last /8 allocation from IANA. From info at arin.net Thu Jan 8 16:02:37 2009 From: info at arin.net (Member Services) Date: Thu, 08 Jan 2009 16:02:37 -0500 Subject: Policy Proposal: IPv4 Recovery Fund - Revised Message-ID: <496669ED.8040903@arin.net> Policy Proposal IPv4 Recovery Fund This proposal is in the first stage of the ARIN Policy Development Process. The proposal originator submitted a revised version of the proposal. ARIN staff will perform the Clarity and Understanding step of the Policy Development Process. Staff does not evaluate the proposal itself at this time, their only aim is to make sure that they understand the proposal and believe that the community will as well. Staff will report the results of this step to the ARIN Advisory Council (AC) within 10 days. The AC will review this 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. The decision will be announced to the PPML. In the meantime, the AC invites everyone to comment on this 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: http://www.arin.net/policy/pdp.html Mailing list subscription information can be found at: http://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal Name: IPv4 Recovery Fund Proposal originator: Leo Bicknell Proposal Version: 4.0 Date: 1/8/2009 Proposal type: New Policy term: Permanent Policy statement: (Create new section in section 4, represented by "4.X".) 4.X IPv4 Recovery Fund 4.X.1 Implementation Timing Upon receiving a valid request for a block larger than ARIN can satisfy from its existing free pool, or, by obtaining additional space from IANA, ARIN shall begin offering financial incentives for returned IP blocks according to this policy. 4.X.2 Recovery of IPv4 Space ARIN believes that organizations should voluntarily return unused and/or unneeded IP resources to the community. However, upon implementation of this policy, ARIN will offer financial incentives for the return of IPv4 resources to ARIN relinquishment of any future claims to those resources. ARIN will continue to accept voluntary returns. 4.X.3 Allocation of Recovered Space Once approved for IPv4 space ARIN will ask the requester to specify a bid of how much they are willing to pay for reclamation of address space. ARIN will use this bid in determining what incentives to offer for return of space. The requester may make a higher bid at any time, which is treated as a brand new bid replacing their old bid. If ARIN recovers space and offers it to requester at or below the specified bid within 60 days of the time the bid was made then the bid shall be binding on requester at the price ARIN offers the space. 4.X.4 Address Block Management ARIN may not offer a partial fill, that is provide a block smaller than the one for which the requester was approved. ARIN may split recovered blocks into multiple smaller blocks at the staff's discretion using the following principals: - It is unlikely a request will be made for the address block size involved in the next 60 days. - The block is divided into as few parts as practical. - There are enough bids to allow the entire block to be allocated. 4.X.5 Transparency ARIN staff shall make public the current and historical prices of asks, bids, and executed transactions in a manor that facilitates the bidding process. ARIN staff must regularly report on the amount of address space obtained and distributed via this mechanism, number of blocks subdivided, as well as aggregate financial numbers. 4.X.6 Cost Recovery ARIN shall manage the address space recovery program with a goal of cost recovery. ARIN may: - Use ARIN funds to reclaim blocks when there is no specific demand; if such reclamation is deemed in the best interest of the community and there is a significant likelyhood of future demand. - Use a portion of the funds collected under this program to pay for the implementation of this program. Rationale: Many have recognized that in order for unused or poorly used IPv4 resources to be returned to the free pool that financial compensation will be required. This is particularly the case in poorly used assets where the current holder may have to expend time and money to renumber in order to free the blocks. This proposal sets up a fund administered by ARIN to encourage the return of space. Effectively ARIN will offer financial incentives to return unused or poorly used IPv4 resources and place them back into the IPv4 free pool. The intention is for this activity to be revenue neutral to ARIN. To achieve that goal those requesting IPv4 resources will be requested to bid on a one-time payment to the recovery fund to cover the cost of the resources they have received. The proposal is intentionally vague on the exact implementation details to staff because: - Transactions with those returning space and obtaining space may occur in any order. - The bidding process may need to evolve over time, and may not be as simple as highest bidder wins. It may include aspects such as a dutch auction style format (all winners pay the lowest winning price), or may include other factors such as which size blocks ARIN has free in an effort to limit deaggregation. - ARIN will have to develop contracts and procedures around this activity that are better suited for staff and legal than the policy process. Compared to other "transfer proposals", this proposal has the following benefits: - Maintains that IP addresses are not property. - Maintains the concept that unused addresses should be returned to the free pool. - Maintains need based addressing. - Removes the need for those with excess resources to find those without resources. There is no need for any sort of listing service, eBay, etc. - All transactions are two party transactions with ARIN as one of the parties. The potential for multi-party legal disputes is reduced. - ARIN can absorb spikes in supply or demand, creating more level prices over time. - ARIN can provide transparency across all transactions in this system. - Reduces confusion to new entrants over where they should go to receive address space. Change Log: - Changed "monetary" to "financial" to allow for the possibility of ARIN offering things other than direct payment (like fee credits). Credit: Robert Bonomi. - Updated numbering so there were not two 4.10.2's. Also changed to using a place holder for section. Credit: Robert Bonomi - Changed the cost recovery language to be more clear and provide some additional flexibility. - Clarified 4.10.2 about future claims. Credit: Ted Mittelstaedt - Split 10.X.3 into 10.X.3 and 10.X.3 with better titles. - Left the exact algorithm to staff. Removed examples as a result. Timetable for implementation: Staff should begin developing procedures and updated templates immediately. Policy would not go into effect until the criteria listed occurs. From info at arin.net Mon Jan 12 09:15:00 2009 From: info at arin.net (Member Services) Date: Mon, 12 Jan 2009 09:15:00 -0500 Subject: Policy Development Process - Submit policy proposals at any time Message-ID: <496B5064.8050002@arin.net> In the past ARIN staff posted reminders of the deadline for submitting policy proposals. The new Policy Development Process (PDP), published last week, does not contain such a deadline. The current PDP is designed to bring forth clear, technically sound and useful policy. Since good ideas can happen at any time, policy proposals may be submitted at any time. Despite there being no deadline, the new PDP does have several time requirements: ? Policy originators need time to think about and write policy proposals, ? ARIN staff needs time to conduct the Clarity and Understanding review, ? The AC needs time to make a decision and create draft policy, ? ARIN staff and legal counsel must be given time to perform staff assessments, ? And, draft policies must be posted to PPML at least 35 days prior to an ARIN meeting to be considered for that meeting?s agenda. If you are considering submitting a policy proposal, the sooner you submit it the better the chances are of it being acted upon in the first half of 2009. The Policy Development Process and Policy Proposal Template are available at: http://www.arin.net/policy/pdp.html Policy proposals and draft policies under discussion are available at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue Jan 13 14:15:53 2009 From: info at arin.net (Member Services) Date: Tue, 13 Jan 2009 14:15:53 -0500 Subject: Policy Proposal (Global): Allocation of IPv4 Blocks to Regional Internet Registries Message-ID: <496CE869.7010902@arin.net> ARIN received the following global policy proposal. In accordance with the ARIN Policy Development Process, the proposal is being posted to the ARIN Public Policy Mailing List (PPML). This proposal is in the first stage of the ARIN Policy Development Process. ARIN staff will perform the Clarity and Understanding step. Staff does not evaluate the proposal itself at this time, their only aim is to make sure that they understand the proposal and believe that the community will as well. Staff will report the results of this step to the ARIN Advisory Council (AC) within 10 days. The AC will review this 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. The decision will be announced to the PPML. In the meantime, the AC invites everyone to comment on this 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: http://www.arin.net/policy/pdp.html Mailing list subscription information can be found at: http://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal Name: Allocation of IPv4 Blocks to Regional Internet Registries Proposal Originator: This proposal was developed by a team consisting of persons from each of the 5 RIRs. Adiel A. Akplogan" AfriNIC Raul Echeberria LACNIC MAEMURA Akinori APNIC Axel Pawlik RIPE NCC Ray Plzak ARIN Oscar A. Robles-Garay" LACNIC Nigel Titley RIPE NCC Paul Wilson APNIC Proposal Version: 1.0 Date: 13 January 2009 Proposal type: New Policy term: Permanent Policy statement: This document describes the policy governing the allocation of IPv4 address space from the IANA to the Regional Internet Registries (RIRs). This document does not stipulate performance requirements in the provision of services by IANA to an RIR in accordance with this policy. Such requirements should be specified by appropriate agreements among the RIRs and ICANN. This policy is to be implemented in two phases. A. Phase I: Recovery of IPv4 Address Space Upon ratification of this policy by the ICANN Board of Directors the IANA shall establish a mechanism to receive IPv4 address space which is returned to it by the RIRs, and hold that address space in a 'recovered IPv4 pool'. Each RIR through their respective chosen policies and strategies may recover IPv4 address space which is under their administration. Each RIR shall at quarterly intervals return any such recovered address space to the IANA in aggregated blocks of /24 or larger, for inclusion in the recovered IPv4 pool. During Phase I, no allocations will be made from the recovered IPv4 pool. B. Phase II: Allocation of Recovered IPv4 address space by the IANA Upon ratification of this policy by the ICANN Board of Directors and a declaration by the IANA that its existing free pool of unallocated IPv4 addresses space is depleted; Global Addressing Policy ASO-001-2 (adopted by ICANN Board 8 April 2005) is rescinded. IANA will then commence to allocate the IPv4 address space from the recovered IPv4 pool. 1. Allocation of IPv4 Address Space a. For the purposes of this policy, an 'IPv4 allocation period' is defined as a 6-month period following 1 March or 1 September in each year. b. At the beginning of each IPv4 allocation period, the IANA will determine the 'IPv4 allocation unit' for that period, as 1/10 of its IPv4 address pool, rounded down to the next CIDR (power-of-2) boundary. c. In each allocation period, each RIR may issue one IPv4 request to the IANA. Providing that the RIR satisfies the allocation criteria described in paragraph B.2, the IANA will allocate a single allocation unit, composed of the smallest possible number of blocks available in its IPv4 address pool. 2. IPv4 Address Space Allocation Criteria A RIR is eligible to receive additional IPv4 address space from the IANA when the total of its IPv4 address holdings is less than 50% of the current IPv4 allocation unit, and providing that it has not already received an IPv4 allocation from the IANA during the current IPv4 allocation period. 3. Initial Allocation of IPv4 Address Space Each new RIR shall, at the moment of recognition, be allocated one (1) allocation unit by the IANA. If an allocation unit is not available, then the IANA will issue this block as soon as one is available. This allocation will be made regardless of the newly formed RIR's projected utilization figures and shall be independent of the IPv4 address space that may have been transferred to the new RIR by the already existing RIRs as part of the formal transition process. 4. Reporting a. All returned space is to be recorded in an IANA-published log of IPv4 address space transactions, with each log entry detailing the returned address block, the date of the return, and the returning RIR. b. All allocated space is also to be recorded in this IANA-published log of IPv4 address space transactions, with each log entry detailing the address blocks, the date of the allocation and the recipient RIR. c. The IANA will maintain a public registry of the current disposition of all IPv4 address space, detailing all reservations and current allocations and current IANA-held address space that is unallocated. d) The IANA may make public announcements of IPv4 address block transactions that occur under this policy. The IANA will make appropriate modifications to the "Internet Protocol V4 Address Space" page of the IANA website and may make announcements to its own appropriate announcement lists. The IANA announcements will be limited to which address ranges, the time of allocation and to which Registry they have been allocated. Rationale: With the depletion of the IANA free pool of IPv4 address space, the current policy regarding the allocation of IPv4 address space to the RIRs will become moot. The RIRs may, according to their individual policies and procedures, recover IPv4 address space. This policy provides a mechanism for the RIRs to retro allocate the recovered IPv4 address space to the IANA and provides the IANA the policy by which it can allocate it back to the RIRs on a needs basis. This policy creates a new global pool of IPv4 address space that can be allocated where it is needed on a global basis without a transfer of address space between the RIRs. Timetable for implementation: This policy is to be implemented immediately upon ratification by the ICANN Board of Directors according to the global policy process described in the ASO MoU. From info at arin.net Fri Jan 23 11:15:25 2009 From: info at arin.net (Member Services) Date: Fri, 23 Jan 2009 11:15:25 -0500 Subject: [arin-ppml] Policy Proposal (Global): Allocation of IPv4 Blocks to Regional Internet Registries In-Reply-To: <496CE869.7010902@arin.net> References: <496CE869.7010902@arin.net> Message-ID: <4979ED1D.9050403@arin.net> The shepherds from the ARIN Advisory Council for this proposal are Scott Leibrand and Marla Azinger. Regards, Member Services American Registry for Internet Numbers (ARIN) Member Services wrote: > ARIN received the following global policy proposal. In accordance with > the ARIN Policy Development Process, the proposal is being posted to the > ARIN Public Policy Mailing List (PPML). > > This proposal is in the first stage of the ARIN Policy Development > Process. ARIN staff will perform the Clarity and Understanding step. > Staff does not evaluate the proposal itself at this time, their only aim > is to make sure that they understand the proposal and believe that the > community will as well. Staff will report the results of this step to > the ARIN Advisory Council (AC) within 10 days. > > The AC will review this 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. The decision will be announced to the PPML. > > In the meantime, the AC invites everyone to comment on this 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: > http://www.arin.net/policy/pdp.html > > Mailing list subscription information can be found at: > http://www.arin.net/mailing_lists/ > > Regards, > > Member Services > American Registry for Internet Numbers (ARIN) > > > ## * ## > > > Policy Proposal Name: Allocation of IPv4 Blocks to Regional Internet > Registries > > Proposal Originator: > > This proposal was developed by a team consisting of persons from each of > the 5 RIRs. > > Adiel A. Akplogan" AfriNIC > > Raul Echeberria LACNIC > > MAEMURA Akinori APNIC > > Axel Pawlik RIPE NCC > > Ray Plzak ARIN > > Oscar A. Robles-Garay" LACNIC > > Nigel Titley RIPE NCC > > Paul Wilson APNIC > > Proposal Version: 1.0 > > Date: 13 January 2009 > > Proposal type: New > > Policy term: Permanent > > Policy statement: > > This document describes the policy governing the allocation of IPv4 > address space from the IANA to the Regional Internet Registries (RIRs). > This document does not stipulate performance requirements in the > provision of services by IANA to an RIR in accordance with this policy. > Such requirements should be specified by appropriate agreements among > the RIRs and ICANN. > > This policy is to be implemented in two phases. > > A. Phase I: Recovery of IPv4 Address Space > > Upon ratification of this policy by the ICANN Board of Directors the > IANA shall establish a mechanism to receive IPv4 address space which is > returned to it by the RIRs, and hold that address space in a 'recovered > IPv4 pool'. > > Each RIR through their respective chosen policies and strategies may > recover IPv4 address space which is under their administration. Each RIR > shall at quarterly intervals return any such recovered address space to > the IANA in aggregated blocks of /24 or larger, for inclusion in the > recovered IPv4 pool. > > During Phase I, no allocations will be made from the recovered IPv4 pool. > > B. Phase II: Allocation of Recovered IPv4 address space by the IANA > > Upon ratification of this policy by the ICANN Board of Directors and a > declaration by the IANA that its existing free pool of unallocated IPv4 > addresses space is depleted; Global Addressing Policy ASO-001-2 (adopted > by ICANN Board 8 April 2005) is rescinded. IANA will then commence to > allocate the IPv4 address space from the recovered IPv4 pool. > > 1. Allocation of IPv4 Address Space > > a. For the purposes of this policy, an 'IPv4 allocation period' is > defined as a 6-month period following 1 March or 1 September in each year. > > b. At the beginning of each IPv4 allocation period, the IANA will > determine the 'IPv4 allocation unit' for that period, as 1/10 of its > IPv4 address pool, rounded down to the next CIDR (power-of-2) boundary. > > c. In each allocation period, each RIR may issue one IPv4 request to the > IANA. Providing that the RIR satisfies the allocation criteria > described in paragraph B.2, the IANA will allocate a single allocation > unit, composed of the smallest possible number of blocks available in > its IPv4 address pool. > > 2. IPv4 Address Space Allocation Criteria > > A RIR is eligible to receive additional IPv4 address space from the IANA > when the total of its IPv4 address holdings is less than 50% of the > current IPv4 allocation unit, and providing that it has not already > received an IPv4 allocation from the IANA during the current IPv4 > allocation period. > > 3. Initial Allocation of IPv4 Address Space > > Each new RIR shall, at the moment of recognition, be allocated one (1) > allocation unit by the IANA. If an allocation unit is not available, > then the IANA will issue this block as soon as one is available. This > allocation will be made regardless of the newly formed RIR's projected > utilization figures and shall be independent of the IPv4 address space > that may have been transferred to the new RIR by the already existing > RIRs as part of the formal transition process. > > 4. Reporting > > a. All returned space is to be recorded in an IANA-published log of IPv4 > address space transactions, with each log entry detailing the returned > address block, the date of the return, and the returning RIR. > > b. All allocated space is also to be recorded in this IANA-published log > of IPv4 address space transactions, with each log entry detailing the > address blocks, the date of the allocation and the recipient RIR. > > c. The IANA will maintain a public registry of the current disposition > of all IPv4 address space, detailing all reservations and current > allocations and current IANA-held address space that is unallocated. > > d) The IANA may make public announcements of IPv4 address block transactions > that occur under this policy. The IANA will make appropriate > modifications to the "Internet Protocol V4 Address Space" page of the > IANA website and may make announcements to its own appropriate > announcement lists. The IANA announcements will be limited to which > address ranges, the time of allocation and to which Registry they have > been allocated. > > Rationale: > > With the depletion of the IANA free pool of IPv4 address space, the > current policy regarding the allocation of IPv4 address space to the > RIRs will become moot. The RIRs may, according to their individual > policies and procedures, recover IPv4 address space. This policy > provides a mechanism for the RIRs to retro allocate the recovered IPv4 > address space to the IANA and provides the IANA the policy by which it > can allocate it back to the RIRs on a needs basis. This policy creates a > new global pool of IPv4 address space that can be allocated where it is > needed on a global basis without a transfer of address space between the > RIRs. > > > Timetable for implementation: > > This policy is to be implemented immediately upon ratification by the > ICANN Board of Directors according to the global policy process > described in the ASO MoU. > > > _______________________________________________ > 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. > > From info at arin.net Wed Jan 28 11:12:16 2009 From: info at arin.net (Member Services) Date: Wed, 28 Jan 2009 11:12:16 -0500 Subject: Advisory Council Draft Policy and Proposal Decisions Message-ID: <498083E0.9020202@arin.net> Advisory Council Draft Policy and Proposal Decisions On 24 January 2009 the ARIN Advisory Council (AC), acting under the provisions of the ARIN Policy Development Process, recommended that the ARIN Board of Trustees adopt: Draft Policy 2007-14: Resource Review Process http://www.arin.net/policy/proposals/2007_14.html In addition, the AC, acting under the provisions of the ARIN Policy Development Process, recommended that the ARIN Board of Trustees adopt a revised version of 2008-6: Draft Policy 2008-6: Emergency Transfer Policy for IPv4 Addresses http://www.arin.net/policy/proposals/2008_6.html The next step for the above two proposals is a review by the ARIN Board of Trustees. The AC reviewed the following three proposals and accepted them onto the AC's docket for development and evaluation: Policy Proposal: IPv4 Recovery Fund Policy Proposal: Depleted IPv4 reserves Policy Proposal: Allocation of IPv4 Blocks to Regional Internet Registries Proposal texts are available at: http://www.arin.net/policy/proposals/proposal_archive.html The ARIN Policy Development Process can be found at: http://www.arin.net/policy/pdp.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Jan 30 17:46:52 2009 From: info at arin.net (Member Services) Date: Fri, 30 Jan 2009 17:46:52 -0500 Subject: Policy Proposal (Global): Allocation of IPv4 Blocks to Regional Internet Registries - Revised Message-ID: <4983835C.1030109@arin.net> Policy Proposal (Global) Allocation of IPv4 Blocks to Regional Internet Registries The proposal originator submitted a revised version of the proposal. The proposal will be forwarded to the ARIN Advisory Council for their consideration. The proposal is on the AC's docket for development and evaluation. The ARIN Policy Development Process can be found at: http://www.arin.net/policy/pdp.html Mailing list subscription information can be found at: http://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal Name: Allocation of IPv4 Blocks to Regional Internet Registries Proposal Originator: This proposal was developed by a team consisting of persons from each of the 5 RIRs. Adiel A. Akplogan AfriNIC Raul Echeberria LACNIC Geoff Huston APNIC MAEMURA Akinori APNIC Axel Pawlik RIPE NCC Ray Plzak ARIN Oscar A. Robles-Garay" LACNIC Nigel Titley RIPE NCC Paul Wilson APNIC Proposal Version: 2.0 Date: 30 January 2009 Proposal type: New Global Policy term: Permanent Policy statement: This document describes the policy governing the allocation of IPv4 address space from the IANA to the Regional Internet Registries (RIRs). This document does not stipulate performance requirements in the provision of services by IANA to an RIR in accordance with this policy. Such requirements should be specified by appropriate agreements among the RIRs and ICANN. This policy is to be implemented in two phases. A. Phase I: Recovery of IPv4 Address Space Upon ratification of this policy by the ICANN Board of Directors the IANA shall establish a mechanism to receive IPv4 address space which is returned to it by the RIRs, and hold that address space in a 'recovered IPv4 pool'. Each RIR through their respective chosen policies and strategies may recover IPv4 address space which is under their administration. Each RIR shall at quarterly intervals return any such recovered address space to the IANA in aggregated blocks of /24 or larger, for inclusion in the recovered IPv4 pool. During Phase I, no allocations will be made from the recovered IPv4 pool. B. Phase II: Allocation of Recovered IPv4 address space by the IANA Upon ratification of this policy by the ICANN Board of Directors and a declaration by the IANA that its existing free pool of unallocated IPv4 address space is depleted; Global Addressing Policy ASO-001-2 (adopted by ICANN Board 8 April 2005) is rescinded. IANA will then commence to allocate the IPv4 address space from the recovered IPv4 pool. 1. The following definitions apply to this policy: a. Recovered Address Space. Recovered address space is that address space that is returned to an RIR as a result of any activity that seeks to reclaim unused address space or is voluntarily returned to the RIR or is reclaimed by the RIR as a result of legal action or abuse determination. Recovered address space does not include that address space that is reclaimed because of non-payment of contractual fees whose reclamation date is less than 1 year at the time of the report. b. IPv4 Address Holdings. IPv4 address holdings are all unallocated IPv4 address space held by an RIR to include recovered address space not yet returned less that address space that is committed in accordance with the RIR's reservation policy and practices. 2. Allocation of IPv4 Address Space a. For the purposes of this policy, an 'IPv4 allocation period' is defined as a 6-month period following 1 March or 1 September in each year. b. At the beginning of each IPv4 allocation period, the IANA will determine the 'IPv4 allocation unit' for that period, as 1/10 of its IPv4 address pool, rounded down to the next CIDR (power-of-2) boundary. c. In each allocation period, each RIR may issue one IPv4 request to the IANA. Providing that the RIR satisfies the allocation criteria described in paragraph B.2, the IANA will allocate a single allocation unit, composed of the smallest possible number of blocks available in its IPv4 address pool. 3. IPv4 Address Space Allocation Criteria A RIR is eligible to receive additional IPv4 address space from the IANA when the total of its IPv4 address holdings is less than 50% of the current IPv4 allocation unit, and providing that it has not already received an IPv4 allocation from the IANA during the current IPv4 allocation period. 4. Initial Allocation of IPv4 Address Space Each new RIR shall, at the moment of recognition, be allocated one (1) allocation unit by the IANA. If an allocation unit is not available, then the IANA will issue this block as soon as one is available. This allocation will be made regardless of the newly formed RIR's projected utilization figures and shall be independent of the IPv4 address space that may have been transferred to the new RIR by the already existing RIRs as part of the formal transition process. 5. Reporting a. All returned space is to be recorded in an IANA-published log of IPv4 address space transactions, with each log entry detailing the returned address block, the date of the return, and the returning RIR. b. All allocated space is also to be recorded in this IANA-published log of IPv4 address space transactions, with each log entry detailing the address blocks, the date of the allocation and the recipient RIR. c. The IANA will maintain a public registry of the current disposition of all IPv4 address space, detailing all reservations and current allocations and current IANA-held address space that is unallocated. d) The IANA may make public announcements of IPv4 address block transactions that occur under this policy. The IANA will make appropriate modifications to the "Internet Protocol V4 Address Space" page of the IANA website and may make announcements to its own appropriate announcement lists. The IANA announcements will be limited to which address ranges, the time of allocation and to which Registry they have been allocated. Rationale: This version is the result of clarification questions and comments submitted to the authors by the ARIN staff in accordance with the ARIN Policy Development Process (PDP). Specifically this revision does the following: a. Inserts a new paragraph 1 in Section B and renumbers the subsequent paragraphs. The new paragraph 1 contains the definitions that were crafted in response to several comments by the ARIN staff. b. Corrects a typo noted in the stem paragraph of Section B. Timetable for implementation: This policy is to be implemented immediately upon ratification by the ICANN Board of Directors according to the global policy process described in the ASO MoU.