From info at arin.net Wed Apr 1 16:23:48 2009 From: info at arin.net (Member Services) Date: Wed, 01 Apr 2009 16:23:48 -0400 Subject: NRPM version 2009.2 =?windows-1252?Q?=96_New_Policies_Impl?= =?windows-1252?Q?emented?= Message-ID: <49D3CD54.1040407@arin.net> A new version of the ARIN Number Resource Policy Manual (NRPM) has been published to the ARIN website. NRPM version 2009.2 contains the implementation of the following policies: 2007-14: Resource Review Process 2008-5: Dedicated IPv4 block to facilitate IPv6 Deployment 2007-23 (Global): End Policy for IANA IPv4 allocations to RIRs 2007-14 was adopted by the ARIN Board of Trustees on 6 February 2009. 2008-5 was adopted by the ARIN Board on 5 January 2009. 2007-23, a global policy proposal, was adopted by the ARIN Board on 20 June 2008, and, ratified by the ICANN Board of Directors on 6 March 2009. NRPM version 2009.2 is effective 1 April 2009 and supersedes the previous version. See Appendix A of the NRPM for information regarding changes to the manual. The NRPM can be found at: https://www.arin.net/policy/nrpm.html Appendix A can be found at: https://www.arin.net/policy/nrpm_changelog.html Draft policies and proposals can be found at: https://www.arin.net/policy/proposals/ Board of Trustees Meeting Minutes are available at: https://www.arin.net/about_us/bot/index.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu Apr 2 09:51:49 2009 From: info at arin.net (Member Services) Date: Thu, 02 Apr 2009 09:51:49 -0400 Subject: =?windows-1252?Q?Re=3A_=5Barin-ppml=5D_Draft_Policy_2008?= =?windows-1252?Q?-7=3A_Identify_Invalid_WHOIS_POC=92s?= In-Reply-To: <49C7DD6E.3010106@arin.net> References: <49C7DD6E.3010106@arin.net> Message-ID: <49D4C2F5.8050908@arin.net> Draft Policy 2008-7 Identify Invalid WHOIS POC?s 2008-7 has been revised. This draft policy is open for discussion on this mailing list and will be on the agenda at the upcoming ARIN XXIII Public Policy Meeting in San Antonio. Draft Policy 2008-7 is below and can be found at: https://www.arin.net/policy/proposals/2008_7.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Draft Policy 2008-7 Identify Invalid WHOIS POC?s Date: 2 April 2009 Policy Statement: During ARINs annual WHOIS POC validation, an e-mail will be sent to every POC in the WHOIS database. Each POC will have a maximum of 60 days to respond with an affirmative that their WHOIS contact information is correct and complete. Unresponsive POC email addresses shall be marked as such in the database. If ARIN staff deems a POC to be completely and permanently abandoned or otherwise illegitimate, the record shall be deleted. ARIN will maintain, and make readily available to the community, a current list of number resources with no valid POC; this data will be subject to the current bulk WHOIS policy. Timetable for implementation: Immediate From info at arin.net Wed Apr 8 14:49:29 2009 From: info at arin.net (Member Services) Date: Wed, 08 Apr 2009 14:49:29 -0400 Subject: ARIN XXIII Open Policy Hour Message-ID: <49DCF1B9.1040509@arin.net> Sign up today to present your ideas at the ARIN XXIII Open Policy Hour, Sunday, 26 April, from 4:45-5:45 PM (CDT). The Open Policy Hour (OPH) is a showcase for new policy ideas, and we want to hear from you. Sign up before Friday, 24 April to guarantee your chance at the microphone. Send an e-mail to policy at arin.net with your name, organization, and a general description of the policy subject you wish to present. Everyone is invited to attend the session and raise ideas and suggestions. You do not need to have a formal presentation in order to participate. Signing up in advance allows us to confirm your turn to present your policy idea. Details available at: https://www.arin.net/participate/meetings/ARIN-XXIII/oph.html If you won?t be with us in San Antonio, we are offering remote participation during the Open Policy Hour, and throughout the Public Policy and Members Meeting. Get all the details and register as a remote participant at: https://www.arin.net/participate/meetings/ARIN-XXIII/remote.html We look forward to your participation in ARIN XXIII. Please contact Member Services at info at arin.net if you have any questions. Regards, Member Services Department American Registry for Internet Numbers (ARIN) From info at arin.net Mon Apr 13 15:42:49 2009 From: info at arin.net (Member Services) Date: Mon, 13 Apr 2009 15:42:49 -0400 Subject: [arin-ppml] Policy Proposal: IPv6 Multiple Discrete Networks - Accepted on AC's Docket In-Reply-To: <49C1416C.9070203@arin.net> References: <49C1416C.9070203@arin.net> Message-ID: <49E395B9.3050105@arin.net> Policy Proposal 84 IPv6 Multiple Discrete Networks On 8 April 2009 the ARIN Advisory Council (AC) reviewed the following proposal and accepted it onto the AC's docket for development and evaluation: Policy Proposal 84: IPv6 Multiple Discrete Networks Proposal texts are available at: https://www.arin.net/policy/proposals/proposal_archive.html The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Regards, Member Services American Registry for Internet Numbers (ARIN) Member Services wrote: > ARIN received the following policy proposal and is posting it to the > Public Policy Mailing List (PPML) in accordance with Policy Development > Process. > > This proposal is in the first stage of the Policy Development Process. > ARIN staff will perform the Clarity and Understanding step. Staff does > not evaluate the proposal at this time, their goal is to make sure that > they understand the proposal and believe the community will as well. > Staff will report their results to the ARIN Advisory Council (AC) within > 10 days. > > The AC will review the proposal at their next regularly scheduled > meeting (if the period before the next regularly scheduled meeting is > less than 10 days, then the period may be extended to the subsequent > regularly scheduled meeting). The AC will decide how to utilize the > proposal and announce the decision to the PPML. > > In the meantime, the AC invites everyone to comment on the proposal on > the PPML, particularly their support or non-support and the reasoning > behind their opinion. Such participation contributes to a thorough > vetting and provides important guidance to the AC in their deliberations. > > The ARIN Policy Development Process can be found at: > http://www.arin.net/policy/pdp.html > > Mailing list subscription information can be found at: > http://www.arin.net/mailing_lists/ > > Regards, > > Member Services > American Registry for Internet Numbers (ARIN) > > > ## * ## > > Policy Proposal Name: IPv6 Multiple Discrete Networks > > Proposal Originator: David Divins > > Proposal Version: 1 > > Date: 3/17/2009 > > Proposal type: Add > > Policy term: Permanent > > Policy statement: > > Organizations with multiple discrete IPv6 networks desiring to request > new or additional address space under a single Organization ID must meet > the following criteria: > > 1. The organization shall be a single entity and not a consortium > of smaller independent entities. > > 2. The organization must have compelling criteria for creating > discrete networks. Examples of a discrete network might include: > > 1. Regulatory restrictions for data transmission, > > 2. Geographic distance and diversity between networks, > > 3. Autonomous multihomed discrete networks. > > 3. The organization must keep detailed records on how it has > allocated space to each location, including the date of each allocation. > > 4. The organization should notify ARIN at the time of the request > their desire to apply this policy to their account. > > Rationale: > > This proposed policy is suggested as NRPM 6.11. The policy is intended > to provide parity between current IPv4 policy and allow discrete network > operators to obtain IPv6 space. > > Timetable for implementation: Immediately > > > > > > _______________________________________________ > 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 Mon Apr 13 15:44:30 2009 From: info at arin.net (Member Services) Date: Mon, 13 Apr 2009 15:44:30 -0400 Subject: [arin-ppml] Revision to Policy Proposal: Sunset 2008-6/2009-1 on schedule - Abandoned In-Reply-To: <49DB5C05.7090207@arin.net> References: <49DB5C05.7090207@arin.net> Message-ID: <49E3961E.4010308@arin.net> Policy Proposal 85 Sunset 2008-6/2009-1 on schedule On 8 April 2009 the ARIN Advisory Council (AC) abandoned Policy Proposal 85: Sunset 2008-6/2009-1 on schedule. The AC provided the following explanation of their decision: ##### This proposal was abandoned due to the fact that 2008-6 is officially adopted and still has a valid ?sunset clause? in it. The issue with whether or not to remove the ?sunset clause? from 2008-6 is being reviewed under Draft Policy 2009-1. The AC felt that this proposal was redundant. ##### The AC abandoned the proposal. Per the ARIN Policy Development Process, ?Any member of the community, including a proposal originator, may initiate a Discussion Petition if they are dissatisfied with the action taken by the Advisory Council regarding any specific policy proposal. If successful, this petition will change the policy proposal to a draft policy which will be published for discussion and review by the community on the PPML and at an upcoming public policy meeting.? Note that we have passed the deadline for petitions for the upcoming meeting in San Antonio (as posted to PPML on 9 March 2009); a successful petition at this time would be for the Fall ARIN meeting. The deadline to begin a petition for this proposal is 20 April 2009. Petitions must include the proposal and a petition statement. Once begun, a petition lasts for 5 business days. Success is measured as support from at least 10 different people from 10 different organizations. Should an actual petition begin, ARIN staff will post additional information. The text for Draft Policies and Proposals is available at: https://www.arin.net/policy/proposals/ The ARIN Policy Development Process is available at: https://www.arin.net/policy/pdp.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Member Services wrote: > Policy Proposal 85: Sunset 2008-6 on schedule > > The proposal originator submitted a revised version of the proposal. > > The AC will review this proposal at their next regularly scheduled > meeting and decide how to utilize the proposal. Their decision will be > announced to the PPML. > > In the meantime, the AC invites everyone to comment on this proposal on > the PPML, particularly their support or non-support and the reasoning > behind their opinion. Such participation contributes to a thorough > vetting and provides important guidance to the AC in their deliberations. > > The ARIN Policy Development Process can be found at: > http://www.arin.net/policy/pdp.html > > Mailing list subscription information can be found at: > http://www.arin.net/mailing_lists/ > > Regards, > > Member Services > American Registry for Internet Numbers (ARIN) > > ##*## > > Policy Proposal Name: Sunset 2008-6/2009-1 on schedule > Proposal Originator: Owen DeLong > Proposal Version: 2.0 > Date: 06-April-2009 > > Proposal type: delete > Policy term: permanent > > Policy statement: The changes made to the NRPM by proposals 2008-6 and > 2009-1 are removed effective Dec. 31, 2012. > > Policy Rationale: Part of the policy that the community developed > consensus for in 2008-6 included a sunset clause. The ARIN Board in an > unprecedented action > chose to discard this clause while approving the remainder of the > policy. This proposal is intended to restore the will of the community > and ensure > that this policy remains temporary as intended. > > Timetable for implementation: December 31, 2012 > > < END> > _______________________________________________ > 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 Apr 21 10:07:00 2009 From: info at arin.net (Member Services) Date: Tue, 21 Apr 2009 10:07:00 -0400 Subject: ARIN XXIII Policy Discussions Message-ID: <49EDD304.7000302@arin.net> The ARIN XXIII Public Policy and Members Meeting will be held next week in San Antonio. Whether you?re attending in person or participating remotely, be sure to review the agenda so you don?t miss you chance to share your thoughts during the draft policy discussions: Monday, 27 April * 2009-1: Transfer Policy * 2008-7: Identify Invalid WHOIS POC?s * 2009-4: IPv4 Recovery Fund Tuesday, 28 April * 2009-3 (Global): Allocation of IPv4 Blocks to Regional Internet Registries * 2009-2: Depleted IPv4 Reserves * 2008-3: Community Networks IPv6 Assignment View the agenda for specific times: https://www.arin.net/participate/meetings/ARIN-XXIII/agenda.html Complete information on the text of the draft policies being discussed is available at: https://www.arin.net/policy/proposals/ If you won?t be attending in person, you can still take advantage of remote participation features that will allow your voice to be heard during critical policy discussions. In addition to viewing the webcast, you can read along with the live transcript and submit questions and comments and vote in straw polls via Jabber chat. To register as a remote participant, learn more about the remote participation services, and access the meeting materials please go to: https://www.arin.net/participate/meetings/ARIN-XXIII/remote.html We look forward to your participation. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue Apr 21 15:40:56 2009 From: info at arin.net (Member Services) Date: Tue, 21 Apr 2009 15:40:56 -0400 Subject: Draft Policy 2009-1: Transfer Policy - Staff Assessment In-Reply-To: <49C911A8.5020009@arin.net> References: <49C911A8.5020009@arin.net> Message-ID: <49EE2148.3050301@arin.net> Draft Policy 2009-1 Title: Transfer Policy Date Submitted: 24 March 2009 Date of Assessment: 21 April 2009 ARIN Staff Assessment The assessment of this draft policy includes comments from ARIN staff and the ARIN General Counsel. It contains analysis of procedural, legal, and resource concerns regarding the implementation of this draft policy as it is currently stated. Any changes to the language may necessitate further analysis by staff and Counsel. I. Draft Policy Available below and at: https://www.arin.net/policy/proposals/2009_1.html II. Summary ARIN staff understands that this policy provides a new definition in NRPM for the term organization, modifies the structure of the Transfer policy (NRPM 8), adds a new condition to the Transfer policy that allows an authorized resource holder to transfer number resources via ARIN to a recipient who can justify the resource(s) under a current ARIN policy, and changes the criteria established by 2008-6 to include: opens transfers to all number resources (IPv4, IPv6 and ASNs), removes the sunset clause, and requires that the resource holder and recipient be within the ARIN region. III. Comments A. ARIN Staff 1. In section 2.8, the term organization is defined as one ?parent? organization be responsible for all of its associated companies? or subsidiaries? interactions with ARIN. Today ARIN allows companies and their subsidiaries to open multiple accounts in order to accommodate their network needs, completely independent of their organization/legal structure. If this definition is applied exactly as written, it could affect many policies in NRPM that contain the term organization and could also affect ARIN?s customers ability to manage their networks independently. 2. In Section 8.2, the word ?affecting? should be changed back to ?effecting?. 3. In Section 8.3, we recommend changing "by any authorized resource holder" to "by the authorized resource holder," for additional clarity. 4. Section 8.3 states that the recipient must ?demonstrate the need for such resources in the exact amount which they can justify under current ARIN policies.? (This criterion was initially defined in 2008-6 and was carried over into 2009-1). Current ARIN policies do not allow the issuance of /23s and /24s with the exception of the micro-allocation policy. As written, this policy would exclude /23s and /24s from being transferred. B. ARIN General Counsel The core of 2009-1 is an NRPM friendly restatement of the policy sent to the Board by the AC. It contains several language changes suggested by counsel and others from Board members. The proposed policy significantly reduces legal risks, fees and expenses for ARIN. Facts available indicate a nascent black market in number resource transfers has begun, transfers are being made in contravention of ARIN policy, and these would continue to expand in number and importance absent immediate implementation of a policy like 2009-1. By providing a clear transfer policy, consistent with RFC 2008 and RFC 2050, 2009-1 will also result in the appropriate and useful transfer of unused or under utilized IPV4 number resources to organizations who need them. Therefore, it may provide a critical cushion of time for recipients of resources who utilize the policy in the period when exhaustion of new IPV4 resources is becoming imminent or is occurring. This is consistent with ARIN's mission with regard to fair allocation. The new policy also provides a substantial beneficial reason for legacy holders to sign LRSAs, which, in turn, will provide important benefits to ARIN, the law enforcement community, and Internet community. One aspect of 2009-1 is materially different from 2008-6 ? specifically the three year sunset provision in 2008-6 has not been included. Counsel did not ask for this change, but believes it is useful from a legal perspective. The deletion of the sunset provision means a mandatory review of the policy does not have to be undertaken at a single fixed point in time chosen now. I believe this policy is likely to be reconsidered and amended several times before the three year sunset provision is reached, assuming it is adopted. This three year sunset provision was not tied to a specific rationale, such as the date of expected exhaustion of RIR issuance of IPV4 space, or a year after that date. The stability of a transfer policy without such a predetermined sunset provision is legally preferable, absent a compelling and particular reason why the sunset date chosen is important. The sunset provision did not further any legal objective. Since this policy, if completed , can be amended or repealed at any point, and sunset provisions have not been routinely utilized to require reevaluation of controversial ARIN policies, the absence of a sunset provision is legally preferable.' Counsel has no position on the definition of organization. IV. Resource Impact ? Moderate The resource impact of implementing this policy is viewed as minimal. It is estimated that this policy may require up to 90 days to implement following ratification by the ARIN Board of Trustees. It may require the following: ? Guidelines Changes ? Staff training ? All internal registration procedures to be rewritten in order to accommodate the new definition of organization. Regards, Member Services American Registry for Internet Numbers (ARIN) ##*## > Draft Policy 2009-1 > Transfer Policy > > Originator: ARIN Board of Trustees (using the Emergency PDP provision in > the ARIN Policy Development Process) > > Date: 24 March 2009 > > Policy statement: > > Insert into the ARIN Number Resource Policy Manual as follows: > > Add Section 2.8: > > ?Organization. An Organization is one or more legal entities under > common control or ownership.? > > Replace Section 8 as follows: > > 8. Transfers > > 8.1. Principles > 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. Mergers and Acquisitions > ARIN will consider requests for the transfer of number resources in the > case of mergers and acquisitions 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. > > 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) affecting 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 resource. > > 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: > > o Type and quantity of equipment > o Customer base > > ? A description of how number resources are being utilized > ? Network engineering plans, including: > > o Host counts > o Subnet masking > o Network diagrams > o Reassignments to customers > > 8.3 Transfers to Specified Recipients > Number resources may be released, in whole or in part, to ARIN for > transfer to another specified organizational recipient, by any > authorized resource holder within the ARIN region. Such transferred > number resources may only be received by organizations that are within > the ARIN region and can demonstrate the need for such resources in the > exact amount which they can justify under current ARIN policies. > > ##### > > Notes: > > Most of the existing Section 8 is left unchanged. List of changes: > > 2.8 New. > 8.1 Changes from ?Transfers? to ?Principles.? > 8.2 Changes from ?Transfer Requirements? to ?Mergers and Acquisitions.? > 8.2 The word ?only? is removed. > 8.3 Merged up into 8.2. > 8.3 Edited version of the adopted 2008-6. > >