From info at arin.net Fri Nov 21 12:26:09 2008 From: info at arin.net (Member Services) Date: Fri, 21 Nov 2008 12:26:09 -0500 Subject: [arin-ppml] 8.4 Emergency Transfer Policy for IPv4 Addresses - Continued [Policy Proposal 2008-6] In-Reply-To: References: Message-ID: <4926EF31.3090003@arin.net> Policy Proposal 2008-6 Emergency Transfer Policy for IPv4 Addresses This proposal has been revised. It is open for discussion on this mailing list. The current policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2008_6.html Regards, Member Services American Registry for Internet Numbers (ARIN) Bill Darte wrote: > Hello, > > As the author of 2008-6 Emergency Transfer Policy for IPv4 Addresses, I > would like everyone to be aware of the most recent language changes that > are the result of ARIN XXII Los Angeles public policy meeting comments > and subsequent Advisory Council discussions. > > The AC believes that the substance of the proposal remains true to that > which was presented at ARIN XXII and which received substantial support. > > Please take this opportunity to review and comment on this proposal, > especially voicing your support or objection. > > Thank you for your involvement in the ARIN policy proposal process. > > Bill Darte > ARIN Advisory Council > > > > > **************************** > 8.4 Emergency Transfer Policy for IPv4 Addresses > > For a period of 3 years from policy implementation, ARIN-region number > resources may be released, in whole or in part, to ARIN or another > organization, by the authorized holder of the resource. > > Number resources may only be received under RSA, with demonstrated need, > in the exact amount which they are able to justify under ARIN > resource-allocation policies. > > Rationale: > > In order for ARIN to fulfill its mission and to facilitate a continuing > supply of IPv4 address resources to its service community when ARIN > resources are no longer adequate, and to preserve the integrity of > documentation and ARIN services for those resources, this policy may be > implemented. Its intent is to preserve the current tradition of > need-based allocation/assignments for those still needing IPv4 resources > during a transition period as the industry adopts IPv6. This policy is > not intended to create a 'market' for such transfers and does not > introduce or condone the monetization of address resources or a view of > addresses as property. It does recognize that organizations making > available unused or no longer needed address resources may incur certain > costs that might be compensated by those acquiring the resources. This > policy is intended to be transient and light-weight and does not > encourage a sustained or continuing role for IPv4, but rather helps to > mitigate a transitional crisis that may emerge while the industry adopts > IPv6 in accordance with the recommendation of ARIN's Board of Trustees. > > Timetable for implementation: > > This policy, once ratified by the ARIN Board of Trustees, would be > implemented when either the free-pool of IANA addresses is exhausted or > IPv4 address resources in the ARIN Region reach a threshold of scarcity > recognized by the ARIN Board of Trustees as requiring this policy > implementation. > _______________________________________________ > 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 Fri Nov 21 15:12:16 2008 From: info at arin.net (Member Services) Date: Fri, 21 Nov 2008 15:12:16 -0500 Subject: Policy Proposal: IPv4 Recovery Fund Message-ID: <49271620.8090106@arin.net> ARIN received the following policy proposal. In accordance with the ARIN Internet Resource Policy Evaluation Process, the proposal is being posted to the ARIN Public Policy Mailing List (PPML) and being placed on ARIN's website. The ARIN Advisory Council (AC) will review this proposal at their next regularly scheduled meeting. The AC will assign shepherds in the near future. ARIN will provide the names of the shepherds to the community via 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 Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.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 Author: Leo Bicknell Proposal Version: 1 Submission Date: 21 November 2008 Proposal type: New Policy term: Permanent Policy statement: (Create new section in section 4, which would be 4.10 based on the current NRPM): 4.10 IPv4 Recovery Fund 4.10.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 monetary incentives for returned IP blocks according to this policy. 4.10.2 Recovery of IPv4 Space ARIN still believes that organizations should voluntarily return unused and/or unneeded IP resources to the community. However, upon implementation of this policy, ARIN will offer monetary incentives for the return of IPv4 resources to ARIN. 4.10.2 Distribution of Recovered Space Once approved for IPv4 space ARIN will ask the requester to specify an amount they are willing to pay for a block or the specified size. ARIN will use this bid in determining what incentives ARIN may offer for return of space. If ARIN recovers space and offers it to requester at or below the specified price, the bid shall be binding on requester. If space becomes available from ARIN at a higher cost, ARIN shall still offer the space to the requester(s) in the order of approval of the requests, but, requester shall have the right to refuse any offer at a price higher than bid. ARIN shall match bidders first on best prefix length, but, in no case shall ARIN provide a partial-fill offer. 4.10.3 Transparency ARIN staff shall make public the current and historical prices of asks, bids, and executed transactions. ARIN staff must regularly report on the amount of address space obtained and distributed via this mechanism. 4.10.4 Cost Recovery It is anticipated that ARIN may need to provide some seed money to obtain space before it can be given out. The money raised through successful bids will fund the purchase of additional blocks to supply any ongoing demand. While there may be a surplus of money or of IPv4 resources at any one time, asking prices should be managed in such a way as to be revenue neutral to ARIN. Rationale: Many have recognized that in order for unused or poorly used IPv4 resources to be returned to the free pool that monetary 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 monetary 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. To illustrate the intent of section 4.10.2, let's say that ARIN has the following requests in the following order: 1. a /22 for XYZ Corp. ($300) 2. a /15 for BIll's Bait and Hosting Megacorp. ($2500) 3. a /19 for John's Host Hideaway ($2000) 4. a /21 for Piner Klerpin's New Net ($800) Example 1: ARIN receives a /18 from someone, but, pays an incentive of $2200 for that /18. ARIN would offer a /19 to John's Host Hideaway for $1100 ARIN would then satisfy Piner Klerpin's request for $225 ARIN would then satisfy XYZ Corp's request for $112.50 ARIN would still have a /20, /21, and /22 for future requests. Example 2: ARIN receives a /19 from someone, but, pays an incentive of $2500 ARIN would offer the /19 to John's Host Hideaway for $2500. If John's turned down the $2500 price, they would remain in the queue, but, ARIN would subsequently satisfy request 4 at 625 and offer a /21 to requester 4 for 312.50. Finally an example of what happens with several requests for the same size: 1. a /20 for DEF Corp. ($1800) 2. a /20 for Frank's Swizzler ($1500) 3. a /20 for Jim's Compushop ($2100) ARIN manages to obtain a /19 from someone, but, pays $4200 for it. ARIN would first offer a /20 to DEF for $2100. ARIN would also offer a /20 to Frank's for $2100. If either of them refused, Jim's would receive their /20 for $2100. 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 Nov 24 12:09:34 2008 From: info at arin.net (Member Services) Date: Mon, 24 Nov 2008 12:09:34 -0500 Subject: [arin-ppml] Policy Proposal: IPv4 Recovery Fund In-Reply-To: <49271620.8090106@arin.net> References: <49271620.8090106@arin.net> Message-ID: <492ADFCE.4070101@arin.net> > The AC will assign shepherds in the near > future. ARIN will provide the names of the shepherds to the community > via the PPML. AC shepherds are Cathy Aronson and Bill Darte. Regards, Member Services American Registry for Internet Numbers (ARIN) Member Services wrote: > ARIN received the following policy proposal. In accordance with the ARIN > Internet Resource Policy Evaluation Process, the proposal is being > posted to the ARIN Public Policy Mailing List (PPML) and being placed on > ARIN's website. > > The ARIN Advisory Council (AC) will review this proposal at their next > regularly scheduled meeting. The AC will assign shepherds in the near > future. ARIN will provide the names of the shepherds to the community > via 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 Internet Resource Policy Evaluation Process can be found at: > http://www.arin.net/policy/irpep.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 > > Author: Leo Bicknell > > Proposal Version: 1 > > Submission Date: 21 November 2008 > > Proposal type: New > > Policy term: Permanent > > Policy statement: > > (Create new section in section 4, which would be 4.10 based on the > current NRPM): > > 4.10 IPv4 Recovery Fund > > 4.10.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 monetary > incentives for returned IP blocks according to this policy. > > 4.10.2 Recovery of IPv4 Space > > ARIN still believes that organizations should voluntarily > return unused and/or unneeded IP resources to the community. > However, upon implementation of this policy, ARIN will offer > monetary incentives for the return of IPv4 resources to ARIN. > > 4.10.2 Distribution of Recovered Space > > Once approved for IPv4 space ARIN will ask the requester to > specify an amount they are willing to pay for a block or the > specified size. > > ARIN will use this bid in determining what incentives ARIN > may offer for return of space. If ARIN recovers space and > offers it to requester at or below the specified price, the > bid shall be binding on requester. > > If space becomes available from ARIN at a higher cost, ARIN > shall still offer the space to the requester(s) in the order > of approval of the requests, but, requester shall have the > right to refuse any offer at a price higher than bid. > > ARIN shall match bidders first on best prefix length, but, > in no case shall ARIN provide a partial-fill offer. > > 4.10.3 Transparency > > ARIN staff shall make public the current and historical > prices of asks, bids, and executed transactions. ARIN staff > must regularly report on the amount of address space obtained > and distributed via this mechanism. > > 4.10.4 Cost Recovery > > It is anticipated that ARIN may need to provide some seed > money to obtain space before it can be given out. The money > raised through successful bids will fund the purchase of > additional blocks to supply any ongoing demand. While there > may be a surplus of money or of IPv4 resources at any one > time, asking prices should be managed in such a way as to > be revenue neutral to ARIN. > > Rationale: > > Many have recognized that in order for unused or poorly used IPv4 > resources to be returned to the free pool that monetary 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 monetary 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. > > To illustrate the intent of section 4.10.2, let's say that ARIN has > the following requests in the following order: > > 1. a /22 for XYZ Corp. ($300) > 2. a /15 for BIll's Bait and Hosting Megacorp. ($2500) > 3. a /19 for John's Host Hideaway ($2000) > 4. a /21 for Piner Klerpin's New Net ($800) > > Example 1: > ARIN receives a /18 from someone, but, pays an incentive of > $2200 for that /18. > > ARIN would offer a /19 to John's Host Hideaway for $1100 > ARIN would then satisfy Piner Klerpin's request for $225 > ARIN would then satisfy XYZ Corp's request for $112.50 > ARIN would still have a /20, /21, and /22 for future requests. > > > Example 2: > ARIN receives a /19 from someone, but, pays an incentive of $2500 > ARIN would offer the /19 to John's Host Hideaway for $2500. > If John's turned down the $2500 price, they would remain in > the queue, but, ARIN would subsequently satisfy request 4 > at 625 and offer a /21 to requester 4 for 312.50. > > Finally an example of what happens with several requests > for the same size: > > 1. a /20 for DEF Corp. ($1800) > 2. a /20 for Frank's Swizzler ($1500) > 3. a /20 for Jim's Compushop ($2100) > > ARIN manages to obtain a /19 from someone, but, pays $4200 > for it. > > ARIN would first offer a /20 to DEF for $2100. > ARIN would also offer a /20 to Frank's for $2100. > If either of them refused, Jim's would receive their /20 for $2100. > > Timetable for implementation: > > Staff should begin developing procedures and updated templates > immediately. Policy would not go into effect until the criteria > listed occurs. > > > > _______________________________________________ > 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 Tue Nov 25 14:27:43 2008 From: info at arin.net (Member Services) Date: Tue, 25 Nov 2008 14:27:43 -0500 Subject: =?windows-1252?Q?Policy_Proposal_2007-14=3A_Resource_Rev?= =?windows-1252?Q?iew_Process_=96_Revised_and_posted_to_las?= =?windows-1252?Q?t_call?= Message-ID: <492C51AF.4090008@arin.net> Policy Proposal 2007-14 Resource Review Process Following the ARIN XXII meeting the ARIN Advisory Council (AC) determined that this proposal needed to be revised. The author has revised the proposal to version 3.3A. On 20 November 2008 the AC, acting under the provisions of the ARIN Internet Resource Policy Evaluation Process, determined that the community supports this proposal and moved it to an extended last call. A list of updates to this proposal is provided following the proposal text. Feedback is encouraged during this last call period. All comments should be provided to the Public Policy Mailing List. This last call will expire at 23:59 EST, 14 January 2009. The policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2007_14.html The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-14 Resource Review Process Author: Owen DeLong, Stephen Sprunk Proposal Version: 3.3A Date: 17 October 2008 Proposal type: modify Policy term: permanent Policy statement: Add the following to the NRPM: Resource Review 1. ARIN may review the current usage of any resources maintained in the ARIN database. The organization shall cooperate with any request from ARIN for reasonable related documentation. 2. ARIN may conduct such reviews: a. when any new resource is requested, b. whenever ARIN has reason to believe that the resources were originally obtained fraudulently or in contravention of existing policy, or c. at any other time without having to establish cause unless a full review has been completed in the preceding 24 months. 3. At the conclusion of a review in which ARIN has solicited information from the resource holder, ARIN shall communicate to the resource holder that the review has been concluded and what, if any, further actions are required. 4. Organizations found by ARIN to be materially out of compliance with current ARIN policy shall be requested or required to return resources as needed to bring them into (or reasonably close to) compliance. a. The degree to which an organization may remain out of compliance shall be based on the reasonable judgment of the ARIN staff and shall balance all facts known, including the organization?s utilization rate, available address pool, and other factors as appropriate so as to avoid forcing returns which will result in near-term additional requests or unnecessary route de-aggregation. b. To the extent possible, entire blocks should be returned. Partial address blocks shall be returned in such a way that the portion retained will comprise a single aggregate block. 5. If the organization does not voluntarily return resources as requested, ARIN may revoke any resources issued by ARIN as required to bring the organization into overall compliance. ARIN shall follow the same guidelines for revocation that are required for voluntary return in the previous paragraph. 6. Except in cases of fraud, or violations of policy, an organization shall be given a minimum of six months to effect a return. ARIN shall negotiate a longer term with the organization if ARIN believes the organization is working in good faith to substantially restore compliance and has a valid need for additional time to renumber out of the affected blocks. 7. In case of a return under sections 4-6, ARIN shall continue to provide services for the resource(s) while their return or revocation is pending, except any maintenance fees assessed during that period shall be calculated as if the return or revocation was complete. 8. This policy does not create any additional authority for ARIN to revoke legacy address space. However, the utilization of legacy resources shall be considered during a review to assess overall compliance. 9. In considering compliance with policies which allow a timeframe (such as a requirement to assign some number of prefixes within 5 years), failure to comply cannot be measured until after the timeframe specified in the applicable policy has elapsed. Blocks subject to such a policy shall be assumed in compliance with that policy until such time as the specified time since issuance has elapsed. Delete NRPM sections 4.1.2, 4.1.3, 4.1.4 Remove the sentence "In extreme cases, existing allocations may be affected." from NRPM section 4.2.3.1. Rationale: Under current policy and existing RSAs, ARIN has an unlimited authority to audit or review a resource holder's utilization for compliance at any time and no requirement to communicate the results of any such review to the resource holder. This policy attempts to balance the needs of the community and the potential for abuse of process by ARIN in a way that better clarifies the purpose, scope, and capabilities of ARIN and codifies some appropriate protections for resource holders while still preserving the ability for ARIN to address cases of fraud and abuse on an expedited basis. The intended nature of the review is to be no more invasive than what usually happens when an organization applies for additional resources. Additionally, paragraph 2c prevents ARIN from doing excessive without-cause reviews. The authors believe that this update addresses the majority of the feedback received from the community to date and addresses most of the concerns expressed. ##### The current version is available at: http://www.arin.net/policy/proposals/2007_14.html Previous versions, including 3.0 can be viewed at: http://www.arin.net/policy/archive/2007_14_orig.html This version incorporates the following changes vs. what was published in the ARIN XXII meeting discussion guide: H 1. Proposal Version 3.0 updated to 3.3A H 2. Date 14 August updated to 17 October 2008 P 3. Paragraph 1 -- covered by an ARIN RSA updated to maintained in the ARIN database L 4. Paragraph 1b -- fraudulently updated to fraudulently or in contravention of existing policy P 5. Paragraph 1c -- unless a prior review updated to unless a full review LS 6. Paragraph 3 Generic updated to Specific statement about staff communication requirements. L 7. Paragraph 4 substantially out of compliance updated to materially out of compliance L 8. Paragraph 4a extent to which updated to degree to which L 9. Paragraph 6 intentional violations updated to violations of policy L 10. Paragraph 7 Rephrased to convey intent in manner acceptable to legal (primarily made specific as to return clauses applicable) L 11. Paragraph 8 Rephrased for compliance with legal. H 12 Paragraph 9 Comma (,) added after first phrase. Changes tagged with an H are simple housekeeping. Changes tagged with a P are the result of public comments. Changes tagged with an L are made at the request of ARIN Legal Counsel. Changes tagged with an S are made at the request of ARIN Staff. The version in the meeting discussion guide was Version 3.0 from August 14, 2008 and was archived on October 6, 2008. There were several interim versions on PPML and in the policy archive. They were not discussed at the meeting, although all of the changes in them were discussed during ARIN XXII. From info at arin.net Tue Nov 25 14:28:49 2008 From: info at arin.net (Member Services) Date: Tue, 25 Nov 2008 14:28:49 -0500 Subject: =?windows-1252?Q?Policy_Proposal_2008-5=3A_Dedicated_IPv?= =?windows-1252?Q?4_block_to_facilitate_IPv6_deployment_=96_?= =?windows-1252?Q?Revised_and_reposted_to_last_call?= Message-ID: <492C51F1.1030200@arin.net> Policy Proposal 2008-5 Dedicated IPv4 block to facilitate IPv6 deployment On 20 November 2008 the ARIN Advisory Council (AC), acting under the provisions of the ARIN Internet Resource Policy Evaluation Process, decided to repost 2008-5 to last call with a minor revision. The AC removed the following text: ?6. recipient organizations must be members in good standing of ARIN.? The AC explained that this revision was made in response to the ARIN staff assessment and public discussion. The criterion was removed because it would unintentionally exclude resource holders who are not ARIN members, and because current ARIN practice already does not allow the issuance of resources to any recipient with a balance due. Feedback is encouraged during this last call period. All comments should be provided to the Public Policy Mailing List. This last call will expire at 23:59 EST, 15 December 2008. The policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2008_5.html The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2008-5 Dedicated IPv4 block to facilitate IPv6 deployment Author: Alain Durand Date: 25 November 2008 Proposal type: New Policy term: Permanent 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 Tue Nov 25 14:30:06 2008 From: info at arin.net (Member Services) Date: Tue, 25 Nov 2008 14:30:06 -0500 Subject: Policy Proposal 2008-7: Whois Integrity Policy Proposal - To be merged with other proposals Message-ID: <492C523E.7070208@arin.net> Policy Proposal 2008-7 Whois Integrity Policy Proposal On 20 November 2008 the ARIN Advisory Council (AC), acting under the provisions of the ARIN Internet Resource Policy Evaluation Process, decided to accept and merge the following policy proposals: Policy Proposal: Whois Authentication Alternatives Policy Proposal: Whois POC e-mail cleanup Policy Proposal: Annual WHOIS POC Validation These proposals will be merged into Policy Proposal 2008-7: Whois Integrity Policy Proposal. The AC shepherds for the proposal are Marla Azinger and Heather Schiller. A policy proposal that results from the work on combining these proposals will be posted to the Public Policy Mailing List for community discussion. The four proposals to be merged are available at: http://www.arin.net/policy/proposals/2008_7.html http://lists.arin.net/pipermail/arin-ppml/2008-August/011435.html http://lists.arin.net/pipermail/arin-ppml/2008-September/012099.html http://lists.arin.net/pipermail/arin-ppml/2008-October/012337.html The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html Regards, Member Services American Registry for Internet Numbers (ARIN)