From info at arin.net Fri Mar 2 12:02:00 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:02:00 -0500 Subject: Policy Proposal 2007-6: IPv4 PI minimum size change Message-ID: <45E85888.5060807@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of 'IPv4 PI Minimum Size Change' and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-6: IPv4 PI Minimum Size Change. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_6.html All persons in the community are encouraged to discuss Policy Proposal 2007-6 prior to it being presented at the ARIN Public Policy Meeting in San Juan, Puerto Rico, 23-24 April 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-6: IPv4 PI minimum size change Author: David Williamson Proposal Version: 1.0 Submission Date: 2/14/2007 Proposal type: modify Policy term: permanent Policy statement: In section 4.3.2.2 of the NRPM, change all occurrences of "/22" to "/24". (That is, replace the existing 4.3.2.2 with this text: For end-users who demonstrate an intent to announce the requested space in a multihomed fashion, the minimum block of IP address space assigned is a /24. If assignments smaller than a /24 are needed, multihomed end-users should contact their upstream providers. When prefixes are assigned which are longer than /20, they will be from a block reserved for that purpose. Remove references to IPv4 in section 4.4, as they are no longer relevant. Section 4.4 could be moved, at the discretion of the NRPM editors, to somewhere in section 6, for clarity. Rationale: The rationale for moving the allocation "edge" for IPv4 PI space to /24 has three fundamental points: routing slot consumption would be unchanged, it reflects widespread routing practices, and it discourages waste. While experiments indicate that a few ISPs still try to filter at the /22 boundary, I have been repeatedly told that most don't filter anything shorter than a /24. While routing policy and allocation policies don't need to necessarily match, it is not unreasonable to have them in alignment. In addition, by keeping the PI allocation size for multi-homed organizations at /22, organizations seeking PI space that don't meet the requirements may be encouraged to exaggerate their address usage. This is something that should clearly not be encouraged. On the topic of routing slots, I would like to note that any org qualifying under the PI policies in 4.3.2.2 would also qualify for PA space, and would likely have an interest in multi-homing regardless of the usage of PA vs. PI space. In either instance, a routing slot is consumed by a /24. This policy change should therefore have minimal, if any, impact on the size of the global routing table. It merely gives organizations more options at a slightly smaller network size. Remember that for consideration under 4.3.2.2, an organiztion *must* be multi-homed. On a side note, it's tempting to remove the restriction entirely. If an organization only qualifies for a /28 (for example), they could receive an allocation of that size. Market forces would decide if that /28 was worth a routing slot. If the /28 contained my personal website, I suspect it would not be routable. If that /28 contained Microsoft Update, I suspect it would. In the interest of operational sanity and simplicity, I am not making a proposal to remove the restriction. (Note that section 4.1.1 explicitly notes that PI addresses are not guaranteed to be globally routable.) There is fundamental conflict between the urge for aggregation and the desire for conservation. The latter would prefer that organizations not have any excess space, while the former would prefer that fewer networks exist in the DFZ, regardless of wastage. Since the DFZ already permits deaggregation to /24, the conservation urge should be allowed to push to that edge. As noted in 4.1.5, "determination of IP address allocation size is the responsibility of ARIN." This proposal simply allows the community to request appropriately sized blocks, and ARIN to allocate prefixes of a size that is commensurate with established need. Timetable for implementation: immediate From info at arin.net Fri Mar 2 12:13:31 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:13:31 -0500 Subject: Policy Proposal 2007-7: Creation of Policy for Subsequent End-User IP Requests/Assignments Message-ID: <45E85B3B.2020509@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of 'Creation of Policy for Subsequent End-User IP Requests/Assignments' and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-7: Creation of Policy for Subsequent End-User IP Requests/Assignments The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_7.html All persons in the community are encouraged to discuss Policy Proposal 2007-7 prior to it being presented at the ARIN Public Policy Meeting in San Juan, Puerto Rico, 23-24 April 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-7: Creation of Policy for Subsequent End-User IP Requests/Assignments Author: Alex Rubenstein Proposal Version: 1 Submission Date: 15 February 2007 Proposal type: New Policy term: Permanent Policy statement: 4.3.6, Additional Assignments "In order to justify an additional assignment, end-users must have efficiently utilized at least 80% of all previous assignments, and must provide ARIN with utilization details. The prefix size for an additional assignment is determined by applying policies 4.3.2, and 4.3.3." Rationale: There are no published criteria for additional assignment requests from end-user networks. NRPM 4.3 seems to only cover initial assignments. NRPM 4.3.3 states, in part, "Requesters must show exactly how previous address assignments have been utilized and must provide appropriate details to verify their one-year growth projection." Unfortunately, the above text does not specify any metrics for ARIN staff to apply when determining if an additional assignment is justified. Though most end-users only get one assignment, some end-users request a 2nd or 3rd or Nth assignment. Currently, the ARIN staff applies what they perceive to be "efficient utilization" criteria; for instance, the end-user must have utilized at least 80% of last assignment and must provide ARIN with utilization details. Timetable for implementation: Immediate From info at arin.net Fri Mar 2 12:15:00 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:15:00 -0500 Subject: Policy Proposal 2007-8: Transfer Policy Clarifications Message-ID: <45E85B94.3050007@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of 'Transfer Policy Clarifications' and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-8: Transfer Policy Clarifications. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_8.html All persons in the community are encouraged to discuss Policy Proposal 2007-8 prior to it being presented at the ARIN Public Policy Meeting in San Juan, Puerto Rico, 23-24 April 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-8: Transfer Policy Clarifications Author: Paul Andersen Proposal Version: 1.0 Submission Date: February 22, 2007 Proposal type: Modify Policy term: Permanent Policy statement: That Section 8 of the NRPM is replaced as follows: 8.1. Transfers Number resources are non-transferable and are not assignable to any other organization unless ARIN has expressly and in writing approved a request for transfer. ARIN is tasked with making prudent decisions on whether to approve the transfer of number resources. It should be understood that number resources are not "sold" under ARIN administration. Rather, number resources are assigned to an organization for its exclusive use for the purpose stated in the request, provided the terms of the Registration Services Agreement continue to be met and the stated purpose for the number resources remains the same. Number resources are administered and assigned according to ARIN's published policies. Number resources are issued, based on justified need, to organizations, not to individuals representing those organizations. Thus, if a company goes out of business, regardless of the reason, the point of contact (POC) listed for the number resource does not have the authority to sell, transfer, assign, or give the number resource to any other person or organization. The POC must notify ARIN if a business fails so the assigned number resources can be returned to the available pool of number resources if a transfer is not requested and justified. 8.2 Transfer Requirements ARIN will consider requests for the transfer of number resources only upon receipt of evidence that the new entity has acquired the assets which had, as of the date of the acquisition or proposed reorganization, justified the current entity's use of the number resource. Examples of assets that justify use of the number resource include, but are not limited to: * Existing customer base * Qualified hardware inventory * Specific software requirements 8.3. Documentation Requirements In evaluating a request for transfer, ARIN may require the requesting organization to provide any of the following documents, as applicable, plus any other documents deemed appropriate: * An authenticated copy of the instrument(s) effecting the transfer of assets, e.g., bill of sale, certificate of merger, contract, deed, or court decree * A detailed inventory of all assets utilized by the requesting party in maintaining and using the number resource * A list of the requesting party's customers using the number resources If further justification is required, the requesting party may be asked to provide any of the following, or other supporting documentation, as applicable: * A general listing of the assets or components acquired * A specific description of acquisitions, including: * Type and quantity of equipment * Customer base * A description of how address space is being utilized * Network engineering plans, including: * Host counts * Subnet masking * Network diagrams * Reassignments to customers Rationale: Staff analysis and community comments have a problem with the inconsistent use of the terms "ASN" and "IP Address" in this section which leads to confusion on which resources can be transferred. The entire section now utilizes the term "number resources" to clarify what would appear to be the original intent. A section regarding the handling of customer networks outside ARIN's geographic region has been removed to reflect the actual current procedure utilized that was developed in conjunction with the ERX transfer project. The last section of old text has been removed as it does not appear to be so much policy as guidance. Timetable for implementation: Immediate From info at arin.net Fri Mar 2 12:29:07 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:29:07 -0500 Subject: Policy Proposal 2007-9: Modernization of ISP Immediate Need Policy Message-ID: <45E85EE3.5030100@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of 'Modernization of ISP Immediate Need Policy' and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-9: Modernization of ISP Immediate Need Policy. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_9.html All persons in the community are encouraged to discuss Policy Proposal 2007-9 prior to it being presented at the ARIN Public Policy Meeting in San Juan, Puerto Rico, 23-24 April 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-9: Modernization of ISP Immediate Need Policy Author: Robert Seastrom Proposal Version: 1.0 Submission Date: 22-Feb-2007 Proposal type: modify Policy term: permanent Policy statement: Modify NRPM 4.2.1.6 to read: If an ISP has an immediate need for address space, and can provide justification to show that the address space will be utilized within 30 days of the request, ARIN may issue a block of address space, not larger than a /16 nor smaller than ARIN's customary minimum allocation, to that organization. These cases are exceptional. Current text of 4.2.1.6: If an ISP has an immediate need for address space, i.e., the need exists the day of the request, ARIN may issue a /20 if the organization, such as a new company, shows justification. However, these cases are exceptional. Rationale: ARIN staff and ARIN members have identified a few long-standing problems with the Immediate Need policy. This policy proposal attempts to address the following concerns: * The Immediate Need policy only allows ISPs to qualify for a /20 worth of space, when a larger size block may be necessary to provide proper coverage for the proposed project. An example justifying larger space is an MSOs for which a /20 is insufficient to put an address block larger than a /29 or /30 on each CMTS in a metropolitan area). * Conversely, this policy was written before the current multi-homed policy (which allows allocations of /21s and /22s). The Immediate Need policy should allow assignment of smaller blocks of space if those are justified. * The example used in the Immediate Need policy gives the impression that an immediate need must exist the day of the request. This seems both unfair and unreasonable and should probably be changed to reflect a realistic timeframe. Concerns expressed about the Immediate Need Policy but NOT addressed by this policy proposal (but addressed in a subsequent policy proposal): * The policy as written allows ARIN to issue a /20 to an ISP only. However, section 4.3.4. "Additional Considerations" of the End User Policy in the NRPM states that "End-users may qualify for address space under other policies such as Immediate need [4.2.1.6] or Micro-allocation [4.4].". In order to be consistent, the Immediate Need policy language should be changed to reflect the fact that both ISPs and end-users can qualify under this policy. Timetable for implementation: Immediate From info at arin.net Fri Mar 2 12:31:50 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:31:50 -0500 Subject: Policy Proposal 2007-10: End Site Immediate Need Policy Message-ID: <45E85F86.8050804@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of 'End Site Immediate Need Policy' and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-10: End Site Immediate Need Policy. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_10.html All persons in the community are encouraged to discuss Policy Proposal 2007-10 prior to it being presented at the ARIN Public Policy Meeting in San Juan, Puerto Rico, 23-24 April 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-10: End Site Immediate Need Policy Author: Robert Seastrom Proposal Version: 1.0 Submission Date: 22-Feb-2007 Proposal type: new Policy term: permanent Policy statement: Create new section in NRPM 4.3.6. to mirror the intent of 4.2.1.6, but modified for end sites. If pending proposal "Modernization of ISP Immediate Need Policy" is ratified, this new section will read: 4.3.6 Immediate Need: If an end-user has an immediate need for address space, and can provide justification to show that the address space will be utilized within 30 days of the request, ARIN may issue a block of address space, not larger than a /16 nor smaller than ARIN's customary minimum allocation, to that organization. These cases are exceptional. In the absence of ratification of ""Modernization of ISP Immediate Need Policy", this proposal is to add section 4.3.6 with a modification of the current text of 4.2.1.6 to make it apply to end-users: 4.3.6 Immediate Need: If an end-user has an immediate need for address space, i.e., the need exists the day of the request, ARIN may issue a /20 if the organization, such as a new company, shows justification. However, these cases are exceptional. Rationale: ARIN staff has expressed the concern that the current policy is self-contradictory, in one place stating that the Immediate Need Policy applies to ISPs, and in another place stating that end users can qualify under it. The communication received was: * The policy as written allows ARIN to issue a /20 to an ISP only. However, section 4.3.4. "Additional Considerations" of the End User Policy in the NRPM states that "End-users may qualify for address space under other policies such as Immediate need [4.2.1.6] or Micro-allocation [4.4].". In order to be consistent, the Immediate Need policy language should be changed to reflect the fact that both ISPs and end-users can qualify under this policy. Timetable for implementation: Immediate From info at arin.net Fri Mar 2 12:46:51 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:46:51 -0500 Subject: Policy Proposal 2007-11: Refinement of ISP Initial Allocation Policy Message-ID: <45E8630B.2050700@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of 'Refinement of ISP Initial Allocation Policy' and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-11: Refinement of ISP Initial Allocation Policy. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_11.html All persons in the community are encouraged to discuss Policy Proposal 2007-11 prior to it being presented at the ARIN Public Policy Meeting in San Juan, Puerto Rico, 23-24 April 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-11: Refinement of ISP Initial Allocation Policy Author: Robert Seastrom Proposal Version: 1.0 Submission Date: 22-Feb-2007 Proposal type: modify Policy term: permanent Policy statement: In NRPM 4.2.4.3 (Initial Allocations to ISPs Policy), strike the following sentence: "When completing Section 7 of the ARIN ISP Network Request Template, please keep this in mind" Rationale: Instructions on filling out templates properly belong in the instructions attached to the template, not as part of a policy statement. This reminder makes reference to an obsolete template and section. ARIN released new templates in August 2006 and changed template names, field numbers, and sections which made both of these references obsolete. Timetable for implementation: Immediate From info at arin.net Fri Mar 2 12:46:58 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:46:58 -0500 Subject: Proposed Policy: eGLOP Multicast Address Assignments - not accepted by AC as formal policy proposal Message-ID: <45E86312.3090606@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of the proposed policy 'eGLOP Multicast Address Assignments' and did not accept it as a formal policy proposal. Citing RFC 2050, the AC concluded that ARIN was not empowered to administer multicast address space. During the initial review period the AC may decide to: 1) Accept the proposal as a formal policy proposal as it is presented, 2) Work with the author to clarify, divide or combine it with another proposal, or 3) Not accept the policy proposal. In the event that the AC decides not to accept the proposed policy, then the author may elect to use the petition process to advance the proposal. For petition details see the section called "Petition Process" in the ARIN Internet Resource Policy Evaluation Process which can be found at: http://www.arin.net/policy/irpep.html The deadline for the author to initiate a petition per the ARIN Internet Resource Policy Evaluation Process is 40 days prior to the meeting; the petition deadline for the ARIN XIX Public Policy Meeting is 14 March 2007. If the author chooses not to petition or the petition is unsuccessful, then the proposed policy is closed. If a petition is successful, then the proposal will be numbered and posted for discussion and presented at ARIN's Public Policy Meeting. The proposed policy text can be found at: http://lists.arin.net/pipermail/ppml/2007-February/005970.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Mar 2 12:47:05 2007 From: info at arin.net (Member Services) Date: Fri, 02 Mar 2007 12:47:05 -0500 Subject: Proposed Policy: IPv4 Countdown - not accepted by AC as formal policy proposal Message-ID: <45E86319.5040609@arin.net> On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of the proposed policy 'IPv4 Countdown' and did not accept it as a formal policy proposal. The AC rejected this proposal having taken into consideration the anti-trust issues raised by the ARIN General Counsel and because the AC deemed the proposal to be contrary to ARIN's mission. During the initial review period the AC may decide to: 1) Accept the proposal as a formal policy proposal as it is presented, 2) Work with the author to clarify, divide or combine it with another proposal, or 3) Not accept the policy proposal. In the event that the AC decides not to accept the proposed policy, then the author may elect to use the petition process to advance the proposal. For petition details see the section called "Petition Process" in the ARIN Internet Resource Policy Evaluation Process which can be found at: http://www.arin.net/policy/irpep.html The deadline for the author to initiate a petition per the ARIN Internet Resource Policy Evaluation Process is 40 days prior to the meeting; the petition deadline for the ARIN XIX Public Policy Meeting is 14 March 2007. If the author chooses not to petition or the petition is unsuccessful, then the proposed policy is closed. If a petition is successful, then the proposal will be numbered and posted for discussion and presented at ARIN's Public Policy Meeting. The proposed policy text can be found at: http://lists.arin.net/pipermail/ppml/2007-February/006000.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Mar 7 17:52:15 2007 From: info at arin.net (Member Services) Date: Wed, 7 Mar 2007 17:52:15 -0500 Subject: ARIN XIX Remote Participation and Webcast Information Message-ID: <007401c7610b$404a1580$5f8888c0@arin.net> Are you be unable to join us in San Juan for ARIN XIX in person? If so and you are frustrated at the thought of missing the policy discussions and other interesting presentations, we have a solution for you! In its continuing effort to supply the community with an open forum, ARIN is inviting individuals who cannot attend the meeting in person to participate remotely. Remote participants may post, via e-mail, questions and comments to be addressed in normal question and answer periods throughout the agenda. Remote participation is available to all members of the community that cannot attend the meeting in person. The entire ARIN XIX Public Policy Meeting and ARIN Members Meeting will also be webcast, for use by registered remote participants or anyone who is interested in following the meeting discussions and presentations. Registration for remote participation is available through our online meeting registration system. To register, please visit the ARIN XIX home page at http://www.arin.net/ARIN-XIX/, click the "Register for the Meeting" button at the top of the page, and choose "ARIN XIX Remote Participant" from the drop-down box and complete the subsequent form. Registration for remote participation will close 20 April 2007 at 11:59 PM EDT. The live meeting webcast is available without registering as a remote participant. Comments received during the meeting from remote participants will be moderated and presented during normal question and answer periods. ARIN will use e-mail to provide the interactive portion of the remote participation effort. All remote participants are subject to the Remote Participation Acceptable Use Policy (AUP). Additional information about remote participation and the webcast, including the Remote Participation AUP, is available at: http://www.arin.net/ARIN-XIX/webcast.html Detailed information on how to access the meeting webcast will be posted through the URL above before the meeting. The webcast will be using RealNetworks Helix Server, and the broadcast will begin Monday, 23 April 2007 at 9:00 AM AST (UTC/GMT -4 hours). To view the live or archived feeds, you can use RealPlayer 5.0 and above.20 Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu Mar 8 16:22:16 2007 From: info at arin.net (Member Services) Date: Thu, 08 Mar 2007 16:22:16 -0500 Subject: ARIN Community Consultation - Participation Details Message-ID: <45F07E88.2090902@arin.net> On Monday, 12 March, ARIN will open a community consultation following the guidelines in the ARIN Consultation and Suggestion Process. There will be one week of discussion followed by polling on the subject. Consult at arin.net, an open and archived mailing list, will host the public discussion. Only list subscribers will be eligible to participate in polling. Poll results will be publicly available and will be used by the ARIN President to help determine what course of action, if any, ARIN should take regarding the suggestion. The ACSP documentation is available at: http://www.arin.net/about_us/corp_docs/acsp.html Details on how to subscribe to consult at arin.net are available at: http://www.arin.net/mailing_lists/ We welcome community-wide participation. Please address any questions to info at arin.net. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Mar 12 08:43:34 2007 From: info at arin.net (Member Services) Date: Mon, 12 Mar 2007 08:43:34 -0400 Subject: ARIN XIX - Open Policy Hour Message-ID: <45F54AF6.4060405@arin.net> Some Questions About the Policy Process 1. Do you want to know what policy proposals will be discussed at the upcoming ARIN Public Policy Meeting? 2. Do you have an idea about how ARIN should manage Internet Number Resources? 3. Do you think that a current policy should be enhanced or changed, or even retired? 4. Are you hesitant about making a formal proposal on the Public Policy Mail List (PPML)? 5. Are you new to the Policy Development Process? If the answer to any of these questions is yes, then you should attend the Open Policy Hour! What is The Open Policy Hour? Quite simply, it is your opportunity to get a better understanding of what is going to be discussed at the upcoming Public Policy Meeting or for you to discuss your ideas in an open, informal forum and receive feedback or both! The Open Policy Hour consists of two parts. Part One is the P2B2 or the Policy Proposal Background Briefing. ARIN staff will provide summary information regarding the policy proposals that will be discussed at the meeting. Members of the ARIN Advisory Council will be present to answer general questions about the policy proposals. There will be no discussion of the proposals, just the information that you need to help you understand the nature of the proposals. Part Two is the P2B or the Policy Proposal BoF. This is where you get a chance to "test drive" a policy idea. How can you participate? Bring your ideas and questions. If you have a policy suggestion for which you would like to receive feedback prior to submitting it to the community on the PPML, here is your opportunity. If you have a short (3-minute) presentation prepared you will be given the first opportunity to present it. To sign up to give a presentation please send an e-mail to policy at arin.net by 18 April 2007 with your name, organization, and a brief description of your policy subject. Come join your colleagues in this informal setting. The Open Policy Hour for ARIN XIX will be held on Sunday, 22 April, from 5:00 - 6:00 PM. If you are not familiar with the way policies are developed in the ARIN region, join ARIN staff fifteen minutes earlier, at 4:45 PM, for a review of the Internet Resource Policy Evaluation Process. Registration and hotel information for ARIN XIX is available at: http://www.arin.net/ARIN-XIX/ Contact Member Services at info at arin.net if you have any questions. Regards, Member Services Department American Registry for Internet Numbers From info at arin.net Mon Mar 12 12:13:34 2007 From: info at arin.net (Member Services) Date: Mon, 12 Mar 2007 12:13:34 -0400 Subject: How to Unsubscribe from PPML Successfully Message-ID: <45F57C2E.5090602@arin.net> ARIN is sending PPML subscription invitations to all registered designated member representatives (DMRs), Admin POCs, and Tech POCs. This endeavor has prompted many new individuals to subscribe to the mailing list. However, many individuals are then trying to remove themselves, generating the unsubscribe messages to the list. Sending a message to the mailing list, ppml at arin.net, will not unsubscribe you from the list! To unsubscribe from the Public Policy Mailing List, follow one of the options below: 1) Send an e-mail to ppml-unsubscribe at arin.net from your subscribed e-mail account, with the word "unsubscribe" in the BODY of the message. 2) Visit http://lists.arin.net/mailman/listinfo/ppml. Enter your subscribed e-mail account in the unsubscribe form. Click the Unsubscribe or edit options button. Click the Unsubscribe button on the following page. A confirmation message will be e-mailed to you. You must reply to the message or click the URL in the message to complete the removal process. If you encounter any problems with the above directions, please e-mail info at arin.net. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Mar 12 13:06:55 2007 From: info at arin.net (Member Services) Date: Mon, 12 Mar 2007 13:06:55 -0400 Subject: Community Consultation Underway - Removal of WHOIS Query Result Limit Message-ID: <45F588AF.9050700@arin.net> ARIN is seeking community comments on the following suggestion: Remove the 256 result limit when querying WHOIS. Subscribe to consult at arin.net to participate in the discussion and to be eligible to participate in the subsequent polling. Details on how to subscribe to consult at arin.net are available at: http://www.arin.net/mailing_lists/ The ARIN Consultation and Suggestion Process documentation is available at: http://www.arin.net/about_us/corp_docs/acsp.html We welcome community-wide participation. Please address any questions to info at arin.net. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Mar 14 09:20:01 2007 From: info at arin.net (Member Services) Date: Wed, 14 Mar 2007 09:20:01 -0400 Subject: Initiation of Petition was Re: Proposed Policy: IPv4 Countdown - not accepted by AC as formal policy proposal In-Reply-To: <45F7AAD7.7090609@nic.ad.jp> References: <45E86319.5040609@arin.net> <45F7AAD7.7090609@nic.ad.jp> Message-ID: <45F7F681.7030502@arin.net> The deadline for issuing statements of support for this petition is 12:00 noon ET, 21 March 2007. Per the ARIN Internet Resource Policy Evaluation Process, "People who wish to document their support for the petition must do the following: 1) post a response to the Public Policy Mailing List stating their support for the proposal, and 2) send email to petition at arin.net with full point of contact information, including their telephone number and organizational affiliation. The ARIN President will verify whether people from at least four different organizations support the petitioned policy proposal." If the petition is successful, the policy proposal will be numbered, posted online for discussion, and presented at the upcoming Public Policy Meeting in San Juan. If the petition is not successful, the policy proposal will be considered closed. Regards, Member Services Department American Registry for Internet Numbers Toshiyuki Hosaka wrote: > Dear All, > > This is a formal petition request to advance the policy proposal entitled "IPv4 > Countdown Policy Proposal". The full text of the proposal is posted on the ARIN > website at the following URL: > > http://lists.arin.net/pipermail/ppml/2007-February/006000.html > > This policy proposal was to respond in an orderly way to the upcoming exhaustion > of the IPv4 address space. The AC rejected this proposal due to anti-trust > issues however I strongly believe that we should discuss this kind of policy in > the ARIN open policy forum, rather than simple rejection, since IPv4 address > exhaustion is so important issue to the whole community. > > According to the Internet Policy Evaluation Process, people who wish to document > their support for the petition must do the following within the next five (5) days: > > 1) post a response to the Public Policy Mailing List stating their > support for the proposal, > > and, > > 2) send email to petition at arin.net with full point of contact > information, including their telephone number and organizational > affiliation. > > If you have any questions about this process you can refer to the ARIN website > at http://www.arin.net/policy/ipep.html for the full text explaining the > petition process. > > Thanks and best regards, > Toshi > -- > Toshiyuki Hosaka > JPNIC > > > > Member Services wrote (2007/03/03 2:47): > >>On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of >>the proposed policy 'IPv4 Countdown' and did not accept it as a formal >>policy proposal. >> >>The AC rejected this proposal having taken into consideration the >>anti-trust issues raised by the ARIN General Counsel and because the AC >>deemed the proposal to be contrary to ARIN's mission. >> >>During the initial review period the AC may decide to: >>1) Accept the proposal as a formal policy proposal as it is presented, >>2) Work with the author to clarify, divide or combine it with another >>proposal, or >>3) Not accept the policy proposal. >> >>In the event that the AC decides not to accept the proposed policy, then >>the author may elect to use the petition process to advance the >>proposal. For petition details see the section called "Petition >>Process" in the ARIN Internet Resource Policy Evaluation Process which >>can be found at: >>http://www.arin.net/policy/irpep.html >> >>The deadline for the author to initiate a petition per the ARIN Internet >>Resource Policy Evaluation Process is 40 days prior to the meeting; the >>petition deadline for the ARIN XIX Public Policy Meeting >>is 14 March 2007. If the author chooses not to petition or the petition >>is unsuccessful, then the proposed policy is closed. If a petition is >>successful, then the proposal will be numbered and posted for discussion >>and presented at ARIN's Public Policy Meeting. >> >>The proposed policy text can be found at: >>http://lists.arin.net/pipermail/ppml/2007-February/006000.html >> >>Regards, >> >>Member Services >>American Registry for Internet Numbers (ARIN) >> >>_______________________________________________ >>PPML mailing list >>PPML at arin.net >>http://lists.arin.net/mailman/listinfo/ppml >> > > > > _______________________________________________ > PPML mailing list > PPML at arin.net > http://lists.arin.net/mailman/listinfo/ppml > From info at arin.net Mon Mar 19 09:36:48 2007 From: info at arin.net (Member Services) Date: Mon, 19 Mar 2007 09:36:48 -0400 Subject: Community Consultation Extended - Removal of WHOIS Query Result Limit Message-ID: <45FE91F0.7010503@arin.net> The call for discussion on consult at arin.net is extended to Noon ET, Monday, 26 March. ARIN is soliciting input from the community on a request to remove the ARIN WHOIS query limit of 256 results. Rather than raise the limit to an arbitrary number, ARIN requests that you provide your specific feedback as to what the query results limit should be. ARIN asks for feedback based on your experiences with using ARIN's WHOIS directory service. It would be of particular interest to ARIN to receive input from larger organizations with many registered resources or sub-delegations regarding an appropriate result limit. The call for consultation and discussion to date is archived at: http://lists.arin.net/pipermail/consult/ Subscribe to consult at arin.net and participate in the discussion and the subsequent community polling: http://lists.arin.net/mailman/listinfo/consult A poll on the topic will be conducted beginning Tuesday, 27 March. Subscribers on the consult at arin.net list when discussion ends will be eligible to participate. Poll results will be publicly available and will be used by the ARIN President to help determine what course of action, if any, ARIN should take regarding the suggestion. We welcome community-wide participation. Please address any process questions to info at arin.net. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Mar 19 16:33:00 2007 From: info at arin.net (Member Services) Date: Mon, 19 Mar 2007 16:33:00 -0400 Subject: Understanding the ARIN lawsuit In-Reply-To: References: <735E6901-035A-4EA9-B316-1F470E3D613B@gmail.com> Message-ID: <45FEF37C.5050505@arin.net> Ed, Go to: http://www.arin.net/meetings/minutes/ARIN_XVIII/ppm.html and then click on Transcript under Meeting Called to Order. Steve Ryan's remarks follow the opening announcements so you need to scroll down a bit: http://www.arin.net/meetings/minutes/ARIN_XVIII/ppm1_transcript.html#anchor_1 Regards, Member Services American Registry for Internet Numbers (ARIN) Edward Lewis wrote: > I was going to point to the recording of what was said ARIN's legal > council at the meeting last October, but I don't see a link to any > recording of it on this page: > > http://www.arin.net/meetings/minutes/ARIN_XVIII/ppm.html > > I drink my share of beer, but I could have sworn that there was a > pretty informative and entertaining discussion of all this during the > Public Policy meeting in St. Louis. I don't see anything under the > Member Meeting minutes. > > Maybe I am looking in the wrong place. > > At 11:18 -0400 3/19/07, Daniel Corbe wrote: > >>What exactly brought the lawsuit on to begin with? What did ARIN >>deny Kreman from doing that Kreman thought it appropriate to take >>legal action? >> >>On Mar 19, 2007, at 8:28 AM, John Curran wrote: >> >> >>> At 12:42 PM +0100 3/19/07, Edward Lewis wrote: >>> >>>> I too am curious about the lack of a public statement coming from >>>> ARIN (staff), but thinking this over, perhaps the lack is due to the >>>> fairness principle. >>> >>> The press release is likely the closest your going to see >>> a formal statement, since (as one list member implied), >>> no case is final until the last judge has ruled. >>> >>> /John >>> _______________________________________________ >>> This message sent to you through the ARIN Public Policy Mailing List >>> (PPML at arin.net). >>> Manage your mailing list subscription at: >>> http://lists.arin.net/mailman/listinfo/ppml > > From info at arin.net Tue Mar 20 14:16:38 2007 From: info at arin.net (Member Services) Date: Tue, 20 Mar 2007 14:16:38 -0400 Subject: Initiation of Petition - petition successful In-Reply-To: <45F7F681.7030502@arin.net> References: <45E86319.5040609@arin.net> <45F7AAD7.7090609@nic.ad.jp> <45F7F681.7030502@arin.net> Message-ID: <46002506.2010109@arin.net> The author's petition to advance the policy proposal entitled "IPv4 countdown policy proposal" was successful. This policy proposal will be: ? assigned a policy proposal number ? posted to the Public Policy Mailing List and ARIN website ? included in the agenda at the next ARIN meeting. Regards, Raymond A. Plzak President & CEO ARIN Member Services wrote: > The deadline for issuing statements of support for this petition is > 12:00 noon ET, 21 March 2007. > > Per the ARIN Internet Resource Policy Evaluation Process, "People who > wish to document their support for the petition must do the following: > 1) post a response to the Public Policy Mailing List stating their > support for the proposal, and 2) send email to petition at arin.net with > full point of contact information, including their telephone number and > organizational affiliation. The ARIN President will verify whether > people from at least four different organizations support the petitioned > policy proposal." > > If the petition is successful, the policy proposal will be numbered, > posted online for discussion, and presented at the upcoming Public > Policy Meeting in San Juan. > > If the petition is not successful, the policy proposal will be > considered closed. > > Regards, > > Member Services Department > American Registry for Internet Numbers > > > > Toshiyuki Hosaka wrote: > >>Dear All, >> >>This is a formal petition request to advance the policy proposal entitled "IPv4 >>Countdown Policy Proposal". The full text of the proposal is posted on the ARIN >>website at the following URL: >> >> http://lists.arin.net/pipermail/ppml/2007-February/006000.html >> >>This policy proposal was to respond in an orderly way to the upcoming exhaustion >>of the IPv4 address space. The AC rejected this proposal due to anti-trust >>issues however I strongly believe that we should discuss this kind of policy in >>the ARIN open policy forum, rather than simple rejection, since IPv4 address >>exhaustion is so important issue to the whole community. >> >>According to the Internet Policy Evaluation Process, people who wish to document >>their support for the petition must do the following within the next five (5) days: >> >> 1) post a response to the Public Policy Mailing List stating their >> support for the proposal, >> >> and, >> >> 2) send email to petition at arin.net with full point of contact >> information, including their telephone number and organizational >> affiliation. >> >>If you have any questions about this process you can refer to the ARIN website >>at http://www.arin.net/policy/ipep.html for the full text explaining the >>petition process. >> >>Thanks and best regards, >>Toshi >>-- >>Toshiyuki Hosaka >>JPNIC >> >> >> >>Member Services wrote (2007/03/03 2:47): >> >> >>>On 1 March 2007 the ARIN Advisory Council (AC) concluded its review of >>>the proposed policy 'IPv4 Countdown' and did not accept it as a formal >>>policy proposal. >>> >>>The AC rejected this proposal having taken into consideration the >>>anti-trust issues raised by the ARIN General Counsel and because the AC >>>deemed the proposal to be contrary to ARIN's mission. >>> >>>During the initial review period the AC may decide to: >>>1) Accept the proposal as a formal policy proposal as it is presented, >>>2) Work with the author to clarify, divide or combine it with another >>>proposal, or >>>3) Not accept the policy proposal. >>> >>>In the event that the AC decides not to accept the proposed policy, then >>>the author may elect to use the petition process to advance the >>>proposal. For petition details see the section called "Petition >>>Process" in the ARIN Internet Resource Policy Evaluation Process which >>>can be found at: >>>http://www.arin.net/policy/irpep.html >>> >>>The deadline for the author to initiate a petition per the ARIN Internet >>>Resource Policy Evaluation Process is 40 days prior to the meeting; the >>>petition deadline for the ARIN XIX Public Policy Meeting >>>is 14 March 2007. If the author chooses not to petition or the petition >>>is unsuccessful, then the proposed policy is closed. If a petition is >>>successful, then the proposal will be numbered and posted for discussion >>>and presented at ARIN's Public Policy Meeting. >>> >>>The proposed policy text can be found at: >>>http://lists.arin.net/pipermail/ppml/2007-February/006000.html >>> >>>Regards, >>> >>>Member Services >>>American Registry for Internet Numbers (ARIN) >>> >>>_______________________________________________ >>>PPML mailing list >>>PPML at arin.net >>>http://lists.arin.net/mailman/listinfo/ppml >>> >> >> >> >>_______________________________________________ >>PPML mailing list >>PPML at arin.net >>http://lists.arin.net/mailman/listinfo/ppml >> > > > _______________________________________________ > PPML mailing list > PPML at arin.net > http://lists.arin.net/mailman/listinfo/ppml > From info at arin.net Tue Mar 20 15:48:29 2007 From: info at arin.net (Member Services) Date: Tue, 20 Mar 2007 15:48:29 -0400 Subject: Policy Proposal: 2007-12 IPv4 Countdown Policy Proposal Message-ID: <46003A8D.5070209@arin.net> The author's petition to advance the policy proposal entitled "IPv4 countdown policy proposal" was successful. The proposal is designated Policy Proposal 2007-12: IPv4 Countdown Policy Proposal. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_12.html All persons in the community are encouraged to discuss Policy Proposal 2007-12 prior to it being presented at the ARIN Public Policy Meeting in San Juan, Puerto Rico, 23-24 April 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-12: IPv4 Countdown Policy Proposal Author: Toshiyuki Hosaka (Japan Network Information Center (JPNIC)) Co-Authors: Takashi Arano (Intec Netcore, Inc.) Kuniaki Kondo (Atelier Mahoroba) Tomohiro Fujisaki (NTT) Akinori Maemura (JPNIC) Kosuke Ito (IRI Ubitech) Shuji Nakamura (IPv6 Promotion Council) Tomoya Yoshida (NTT Communications) Susumu Sato (JPNIC) Akira Nakagawa (KDDI) Proposal Version: 1 Submission Date: 22 February 2007 Proposal type: new Policy term: renewable Policy statement: - Set the date for termination of (IPv4) allocations and the date of announcement Set the date to terminate allocations as a general rule, and announce it a certain period in advance. Define the date of announcement as "A-date" and the date to terminate allocations as "T-date". The two dates will be set as follows: A-date (Date of Announcement): - The day in which the IANA pool becomes less than 30*/8 - RIRs must announce "T-date" on this day, which is defined later (*) There will be no changes in the policy on A-date T-date(Date of Termination): - Exactly two years after A-date - 10*/8 blocks should remain at T-date, and defined as two years after A-date, based on the current pace of allocations - It is however possible to move T-date forward at the point where address consumpution exceeds the projections during the course of two years (*) new allocations/assignments from RIRs should terminate on T-date as a general rule. Allocations or assignments to "critical infrastructure" after T-date should be defined by a separate policy. Rationale: 1. Introduction The exhaustion of IPv4 address is approaching round the corner. Geoff Huston's latest projection at Potaroo (as of January 6, 2007) (http://www.potaroo.net/tools/ipv4/) draws the date of IANA pool exhaustion as 31st May 2011, and that of RIR pool as 14th July 2012. Tony Hain projects similar dates based on a different algorithm of his own. From these data, we may observe that if that the current allocation trend continues, the exhaustion of IPv4 address space is expected to take place as early as within the next five years. ICANN/IANA and RIRs must co-ordinate with stakeholders to achieve smooth termination of IPv4 address space as the Internet bodies responsible for stable management and distribution of IP number resources. This proposal provides some ideas as well as concrete examples of the policy that helps IPv4 allocations come to an end with "the minimum confusion" and in "as fair manner as possible". "Five years at the earliest" is not too far in the future for the exhaustion of IPv4 address space. Assuming the minimum of one year is required for sufficient policy discussions with this proposal as a start, and two years for preparation and transfer by LIRs, we need to start the discussions right at this time. 2. Summary of current problems Despite the fact that several projections are made on IPv4 address to run out as early as within the next few years, no discussions are taking place on any of the RIR's policy fora. (we have submitted the same proposal to APNIC on January 2007) This section lists possible problems if no policies are defined to prepare for the terminal period of allocations. 2-1. LIR LIRs currently do not consider IPv4 address exhaustion as an imminent issue in the first place. It is possible that they will finally realize the situation only when impacts of the exhaustion becomes visible as a practical matter, and lead to confusions such as re-addressing their network or making subsequent requests at the last minute in within a limited time frame. There could also be cases where allocations blocks cannot be allocated to some of the LIRs even though requests are submitted on the same day. Moreover, although it would be necessary for LIRs to announce to their customers that IPv4 address space will not be available for assignments eventually, it is difficult to plan this timing without clear policy for the last phase of allocations. As new IPv4 address allocations space will no longer be available, LIRs have no choice but to build networks based on IPv6. However, there are risks of trouble if preparations are made from that point in time, as it will lead to premature actions even if some time can be bought by re-addressing and subsequent allocations. Lastly, using up all available IPv4 address space will disable assignments to services inevitable for co-existence of IPv4 and IPv6 networks, such as the translator service between the two networks, which it may create situation where transfer to IPv6 network will not even be possible. 2-2. RIR/NIR It is likely that smooth allocations by RIRs/NIRs will be hindered by rush of inquiries during the terminal phase of allocations. 2-3. End users End users generally receive address assignments from ISPs accompanied with Internet connection service. If an ISP no longer has IPv4 address space available, nor unable to provide IPv6 service, end users will not be able to receive services from that ISP. Moreover, if the terminal date of allocations remains ambiguous, it may leave end users behind to prepare for IPv6 ready network. 3. Benefits There will be the following benefits by implementing the policy for IPv4 address exhaustion as proposed on this paper. 3-1. LIR LIRs will be able to consciously plan their addressing within their networks if the final date of allocations is clearly demonstrated. Keeping a certain amount of unallocated address blocks enables allocations/assignments for "critical infrastructure" after the termination of regular allocations, which will be explained later section in more details. 3-2. RIR/NIR Announcing the date of terminating allocations in advance and ensuring that all allocations before this date will be made according to the policy at the time enables RIRs/NIRs to make the last allocation without confusions and avoids causing feelings of unfairness among LIRs and end users. In addition, consistent policy applied to all RIRs removes bias towards certain region as well as inter-regional unfairness. The period which IPv6 support is completed becomes clear, therefore, RIRs/NIRs can prepare for this. 3-3. End user As this proposal enables LIRs to prepare for the terminal period of allocations in advance, it reduces the risk of delays/ suspensions of assignments from LIRs to enduers, and end users will be able to continuously receive services from LIRs. As in the case of LIRs, end users will be able to prepare for IPv6 support by the date of allocation termination is clarified. In addition, IPv6 connectivity as well as IPv4 address required during the allocation termination period will be smoothly secured by LIRs preparing for such period. As listed above, there will be important, notable benefits for stakeholders as a result of this policy. It is therefore necessary to take the following actions to achieve a smooth transfer to IPv6 and prevent causing instability in the Internet as well as; - start discussions on allocation scheme during the exhaustion period, - indicate a roadmap to exhaustion after raising awareness on the issue, and - allow enough time for LIRs to plan timing of addressing of their networks, submit allocation requests, and consider how to switch to IPv6. 4. Proposal principles As the first step to discuss IPv4 exhaustion planning, we would like to have an agreement(consensus) on the following four principles. -------------------------------------------------------------------- (1) Global synchronization: All five RIRs will proceed at the same time for measures on IPv4 address exhaustion. (2) Some Blocks to be left: Keep a few /8 stocks instead of distributing all. (3) Keeping current practices until the last moment : Maintain the current policy until the last allocation. (4) Separate discussions on "Recycle" issue : Recovery of unused address space should be discussed separately. -------------------------------------------------------------------- (1) Global synchronization: All RIRs must proceed at the same time to take measures for IPv4 address exhaustion. This is important not only for ensuring fairness for LIRs across the regions, but alsot to prevent confusions such as attempts to receive allocations from an RIR outside their region. The five RIRs should facilitate bottom-up discussions, which should be well coordinated under the leaderships of ICANN ASO and NRO. (2) Some blocks to be left: It is not practical to consider that IPv4 address blocks can be allocated to the last piece. It is expected to cause confusions if one party can receive an allocation while the other has to give up, just with a touch of a difference. The best solution to avoid such confusion is to set in advance, a date in which one is able to receive an allocation if requests are submitted before this timeline. Furthermore, there are few cases where allocations or assignments of IPv4 address space become absolutely necessary in the future. For example, requirements to start a translator service between IPv4 and IPv6 networks should be supported, and there may be some requirements in the future that are beyond our imagination at this current moment. As such, a date to stop allocations under the current policy should be set/defined so that certain number of IPv4 address blocks will be kept as stocks instead of allocating all blocks without remains. (3) Maintaining current practices until the last moment : Allocations should be made based on the current policy until the time to terminate allocations. As the IPv4 Internet has now developed into a social infrastructure supporting large number of businesses, making large changes in the current policy towards conservation within the next one or two years will lead to large-scale confusions, and difficult in the reality. (4) Separate discussion from "Recycle" issue Recovering unused allocated/assigned address blocks is an important measure, and in fact, it has already be discussed and implemented in each RIR regions. This issue, however should be considered separately from this proposal as recovery of a few /8 blocks extends the lifetime of IPv4 for less than one year while efforts for the recovery is expected to require substantial time. 5. Rationale for "A-date" & "T-date" A-date is set in order to: - Allow some grace period and period for networks to be IPv6 ready until the termination of allocations. - Prevent unfairness among LIRs by clarifying the date, such as not being able to receive allocations by a small difference in timing. The rationale for setting A-date as "when IANA pool becomes less than 30*/8" is as follows: The rate of allocations from IANA to RIRs after 2000 is as follows. 2000 : 4*/8 2001 : 6*/8 2002 : 4*/8 2003 : 5*/8 2004 : 9*/8 2005 : 13*/8 2006 : 10*/8 Approximately 10*/8 has been allocated annually after 2003, and the consumption is likely to accelerate with rise of the last minute demands. As it is better to keep minimum stocks of address pool at IANA, 30*/8 is set as the threshold value, and allocations should be terminated two years after it reaches the value, which ensures that IANA/RIRs secure the address space for allocations/assignments to critical infrastructure. 6. Effect on RIR members RIR members are expected to concretely grasp the termination date of allocations and take actions within their organization to prepare for the event. Timetable for implementation: Immediate after all 5 RIRs ratified this policy. From info at arin.net Wed Mar 21 16:07:40 2007 From: info at arin.net (Member Services) Date: Wed, 21 Mar 2007 16:07:40 -0400 Subject: Policy Proposal: 2007-12 IPv4 Countdown Policy Proposal In-Reply-To: <00d001c76bf0$6196e2f0$443816ac@atlanta.polycom.com> References: <20070321132510.GA82184@ussenterprise.ufp.org> <00d001c76bf0$6196e2f0$443816ac@atlanta.polycom.com> Message-ID: <4601908C.6040506@arin.net> Stephen, The ARIN Consultation and Suggestion Process was created for just that purpose. You will find the document outlining the process at: http://www.arin.net/about_us/corp_docs/acsp.html. You may submit a suggestion by following the guidelines on the suggestion template found at: https://app.arin.net/suggestion/ The link to this information is found on the home page, www.arin.net, shown in the right side box as *Suggestions. Regards, Susan Hamlin Director, Member Services American Registry for Internet Numbers(ARIN) Stephen Sprunk wrote: >Thus spake "McTim" > > >>On 3/21/07, michael.dillon at bt.com wrote: >> >> >>>ARIN is a service organization. It runs the in-addr.arpa service, >>>the (creaky old) whois service, a route server, a registry service, >>>and so on. Why not some new stuff too. >>> >>> >>It's my impression that's it's a reluctance to pay for these value >>added services on the part of the ARIN members. >> >> > >Has it ever been put to a vote? Is there even an official way to get such >things onto the agenda besides stuffing the suggestion box and hoping the >BoT/AC will bring it up? > >We have a very good process to make policy changes that affect ARIN's >registry services, but it's unclear to me how much control we have over the >other things ARIN does. And that's not a slam at ARIN at all, since they >have a good track record of doing what we ask, but it makes it difficult to >propose non-registry programs like community outreach (i.e. to people who >aren't on this list or attending meetings, via ads or articles in Network >World, Information Week, CIO, or even the WSJ). It's like we need a >non-policy proposal process. > >Is the consensus truly that ARIN shouldn't do things besides registry >services (i.e. act like a trade association), or do we just not have a >method of telling ARIN it needs to be done combined with them being hesitant >to do (i.e. spend money on) things they haven't been explicitly told to? > >S > >Stephen Sprunk "Those people who think they know everything >CCIE #3723 are a great annoyance to those of us who do." >K5SSS --Isaac Asimov > > >_______________________________________________ >This message sent to you through the ARIN Public Policy Mailing List >(PPML at arin.net). >Manage your mailing list subscription at: >http://lists.arin.net/mailman/listinfo/ppml > > > From info at arin.net Wed Mar 21 16:45:54 2007 From: info at arin.net (Member Services) Date: Wed, 21 Mar 2007 16:45:54 -0400 Subject: PPML Subscription Campaign Results Message-ID: <46019982.6040402@arin.net> In an effort to increase participation in our policy process, ARIN recently invited all registered designated member representatives (DMRs), Admin POCs, and Tech POCs to subscribe to the Public Policy Mailing List (PPML). In terms of numbers, the campaign was a success. The number of subscribed e-mail accounts has grown from 456 to 1,711, a 275% increase. Due to this increase, we?ve also seen several unsubscribe requests posted to the list. We have modified the footer on all mailing list messages to more explicitly direct subscribers to the mailing list management interface. We also posted a message to the PPML with instructions to unsubscribe successfully: http://lists.arin.net/pipermail/ppml/2007-March/006102.html We appreciate your continued patience in this matter. We encourage you to participate in the policy proposal discussions so that all viewpoints can be considered. The PPML is an intrinsic part of ARIN?s Internet Resource Policy Evaluation Process (IRPEP) and broad participation is necessary for its success. It is the public forum in which all policy proposals are introduced and discussed. The feedback given on the list and at the Public Policy Meetings is used by the ARIN Advisory Council to determine community consensus. You can also use the PPML to present and discuss policy ideas before submitting the idea as a policy proposal. ARIN will continue to send PPML subscription invitations to new DMRs, Admin POCs, and Tech POCs as they are registered. You can assist in this effort as well by inviting other interested individuals to join the PPML. The list is open to the public and we look forward to many of you becoming active participants in our policy process. As a list subscriber, please be courteous and remember that you can manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/ppml This includes unsubscribing, updating your e-mail address, changing your settings, and searching the archives. If you set an auto-reply on your e-mail account, we require you to change your mail delivery setting to ?Disabled? during that time. We also request that e-mail accounts with ticketing systems attached be unsubscribed. If you receive any auto-reply messages to a post, please submit it to info at arin.net so that we may investigate. If at any time you have questions about the mailing list, our policy process, or ARIN in general, please contact us at info at arin.net. Regards, Member Services American Registry for Internet Numbers From info at arin.net Thu Mar 22 15:24:57 2007 From: info at arin.net (Member Services) Date: Thu, 22 Mar 2007 15:24:57 -0400 Subject: ARIN XIX: Act Now and Save Money! Message-ID: <4602D809.4030409@arin.net> ARIN looks forward to your participation at the ARIN XIX Public Policy and Members Meeting, taking place 22-25 April 2007, in San Juan, Puerto Rico. Register today to take advantage of the early registration fee of $100 before the increase to $150 on 5 April. Meeting registration and additional ARIN XIX information can be found at http://www.arin.net/ARIN-XIX/. The meeting will take place at the Condado Plaza Hotel, where ARIN XIX attendees are eligible for a special room rate of $160 (USD) if reservations are made before 30 March. Additional hotel and travel information is available through the URL above, and updated agenda information is available at http://www.arin.net/ARIN-XIX/agenda.html. In addition to ARIN policy proposal discussions, the meeting will also feature an informative workshop on Sunday, 22 April titled "Practical Guide to IPv6," that will provide technical, hands-on guidance in using IPv6 on your own computer and provide information on configuring routers for IPv6. Several other special events will be open to all attendees. Sunday, 22 April * A First Timer Lunch from 12:30 - 1:30 PM, where those new to the ARIN community or meetings can meet and talk with members of ARIN's Board, Advisory Council, and staff * A brief session "Introduction to the Internet Resource Policy Evaluation Process" will begin at 4:00 PM * The Open Policy Hour will begin at 4:30 PM * 8th Annual Foosball Tournament kicks off at 6:30 PM Monday, 23 April * The ARIN XIX Social Event, "An Evening of Enchantment" at the Soleil Beach Club from 6:00 PM to 10:00 PM. More information is available at: http://www.arin.net/ARIN-XIX/social.html If you are interested in any of these activities, simply make your selections on your registration form. If you have already registered, but would like to modify your choice of events to attend, simply click on the "Update Existing Registration" link available through the URL at the top of the page to access your registration information. As always, please contact ARIN Member Services at info at arin.net with any questions regarding this meeting. We look forward to seeing you in Puerto Rico! Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Mar 26 14:26:14 2007 From: info at arin.net (Member Services) Date: Mon, 26 Mar 2007 14:26:14 -0400 Subject: ARIN XIX - Policy Proposals Message-ID: <46081046.3030300@arin.net> The following policy proposals have been under discussion on the ARIN Public Policy Mailing List. 2006-7: Changes to IPv6 initial allocation criteria 2007-1: Reinstatement of PGP Authentication Method 2007-2: Documentation of the Mail-From Authentication Method 2007-3: Documentation of the X.509 Authentication Method 2007-4: Changes to IPv6 policy - removal of "interim" consideration 2007-5: Changes to IPv6 policy - removal of "multiple /48" justification 2007-6: IPv4 PI minimum size change 2007-7: Creation of Policy for Subsequent End-User IP Requests/Assignments 2007-8: Transfer Policy Clarifications 2007-9: Modernization of ISP Immediate Need Policy 2007-10: End Site Immediate Need Policy 2007-11: Refinement of ISP Initial Allocation Policy 2007-12: IPv4 Countdown Policy Proposal The full text for each proposal can be found at: http://www.arin.net/policy/proposal_archive.html The proposals will be presented for consideration at the upcoming ARIN XIX Public Policy Meeting in San Juan, Puerto Rico, on 23-24 April 2007. Also on the agenda will be two panel discussions. On Monday will be the 'Legacy Address Space Panel' and on Tuesday, the 'IPv4 Discussion Panel.' Information about these panels can be found at: http://www.arin.net/ARIN-XIX/legacy_panel.html http://www.arin.net/ARIN-XIX/ipv4_panel.html There is still time to register for ARIN XIX; information is available at: http://www.arin.net/ARIN-XIX/ Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Mar 28 15:22:45 2007 From: info at arin.net (Member Services) Date: Wed, 28 Mar 2007 15:22:45 -0400 Subject: NRPM version 2007.1 - New Policy Implementation Message-ID: <460AC085.1090102@arin.net> On 16 November 2006, the ARIN Board of Trustees, based on the recommendation of the Advisory Council and noting that the Internet Resource Policy Evaluation Process had been followed, adopted the following policy proposal: 2006-3: Capturing Originations in Templates This policy proposal has been incorporated into version 2007.1 of the ARIN Number Resource Policy Manual (NRPM) which is effective 28 March 2007. NRPM version 2007.1 supersedes previous versions. See Appendix A of the NRPM for information regarding changes to the manual. Origin AS information for a network can be supplied to ARIN using version 4.1 of the following templates: * ISP Network Request * End-user Network Request * Network Modification * Reallocate * Reassign - Simple * Reassign - Detailed * IPv6 ISP Request * IPv6 End-user Request * IPv6 Modify * IPv6 Reallocate * IPv6 Reassign * Resource Transfer Template Origin AS information cannot be added using previous template versions. ARIN will continue to accept the previous versions of these templates for at least one year so that customers using scripts will have sufficient time to update their software. Origin AS information will be visible via ARIN's WHOIS directory service and available in list format at: ftp://ftp.arin.net/pub/originAS/ The NRPM can be found at: http://www.arin.net/policy/nrpm.html Appendix A can be found at: http://www.arin.net/policy/nrpm_changelog.html Regards, Member Services American Registry for Internet Numbers (ARIN)