From info at arin.net Fri Dec 11 11:10:22 2009 From: info at arin.net (Member Services) Date: Fri, 11 Dec 2009 11:10:22 -0500 Subject: [arin-announce] ARIN Internet Routing Registry (IRR) Upgrade Message-ID: <4B226EEE.6060304@arin.net> ARIN is pleased to announce an upgrade to ARIN's Internet Routing Registry (IRR) service. The upgraded IRR will now support route6 objects, allowing you to record your IPv6 routes within ARIN's IRR. This service is available over both IPv4 and IPv6 transports. ARIN?s IRR will also check route authorization against the ARIN network and Autonomous System registrations and their organization and resource contacts. We are working on additional authentication methods and plan to eventually integrate the IRR service with ARIN Online. All records that were added or modified during the pilot period have been retained and now are reflected in the public service. The aliases used in the pilot have been pointed to production but will be removed within two weeks. Learn more about the IRR at: https://www.arin.net/resources/routing/ Regards, Mark Kosters Chief Technical Officer American Registry for Internet Numbers (ARIN) From info at arin.net Tue Dec 22 13:44:06 2009 From: info at arin.net (Member Services) Date: Tue, 22 Dec 2009 13:44:06 -0500 Subject: [arin-announce] Updated Navigation for www.arin.net Message-ID: <4B311376.3000203@arin.net> We are pleased to announce that we have updated the top-level navigation on the ARIN website, and significantly revised the organization of the Number Resources and Knowledge sections. These changes, based on user feedback, come almost a year after the release of the last website redesign and are intended to further improve your experience at www.arin.net. The reorganized dropdown menu for ?Number Resources? eliminates redundancy and allows for easier navigation to information and request forms. Two new pages are available in this menu. One linking to the ?Services? ARIN offers to assist in the management and administration of your resources, and the other to ?Tools? which features new and developing technologies related to Internet number resources. The ?Knowledge? section now features a ?General Education? page where you can download all of ARIN?s educational materials, and a ?Technical Information? page featuring details about the management of Internet number resources, educational documents, listings of address block allocations, and links to relevant RFCs. Another notable highlight is the update of the IPv6 Info Center. Still available from the ?Quick Links? list on the homepage, the name has changed to ?IPv4/IPv6: The Bottom Line?, and the page now contains even more information to help you understand and explain the issues surrounding these critical issues. From there you can download a copy of the IPv4 Depletion and IPv6 Adoption Community Slide Deck, find information on making the business case for your organization?s IPv6 adoption plan, and find links to the IPv6 wiki and other respected sources of information on the status of the remaining IPv4 free pool. If you have feedback about these changes, please let us know at info at arin.net. If you would like to report a specific issue, please include detailed information, including specific URLs and details about your browser and operating system, including version number. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue Dec 22 14:36:13 2009 From: info at arin.net (Member Services) Date: Tue, 22 Dec 2009 14:36:13 -0500 Subject: [arin-announce] [Fwd: [arin-ppml] Policy Proposal 105: Simplified M&A transfer policy] - new proposal Message-ID: <4B311FAD.1090201@arin.net> The following is a new policy proposal that has been posted to the ARIN Public Policy Mailing List for discussion on that list. Regards, Member Services American Registry for Internet Numbers (ARIN) -------- Original Message -------- Subject: [arin-ppml] Policy Proposal 105: Simplified M&A transfer policy Date: Tue, 22 Dec 2009 14:30:43 -0500 From: Member Services To: arin-ppml at arin.net ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with 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. Draft Policies and Proposals under discussion can be found at: https://www.arin.net/policy/proposals/index.html The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Mailing list subscription information can be found at: https://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 105: Simplified M&A transfer policy Proposal Originator: Scott Leibrand Proposal Version: 1.0 Date: 22 December 2009 Proposal type: new Policy term: permanent Policy statement: Replace section 8.2 with: 8.2. Mergers and Acquisitions ARIN will consider requests for the transfer of number resources in the case of properly documented mergers and acquisitions. ARIN will maintain an up-to-date list of acceptable types of documentation. In the event that number resources of the acquired/merged organization(s) are no longer efficiently utilized at the time ARIN becomes aware of the transaction, through a transfer request or otherwise, ARIN will work with the resource holder(s) to return or aggregate resources as appropriate via the processes outlined in sections 4.6, 4.7, or 12 of the NRPM. Add "In addition to transfers under section 8.2, " at the beginning of section 8.3. Transfers to Specified Recipients. Rationale: This policy proposal: attempts to simplify the M&A transfer section of the NRPM; eliminates the ambiguity discussed at the ARIN Public Policy Meeting (PPM) in Dearborn by clarifying that transfers can occur under either 8.2 or 8.3 independently; and attempts to address the concerns raised in the staff policy implementation report at the Dearborn PPM. The idea here is to simply say that ARIN will allow M&A transfers, and to require the return of any address space that is not efficiently utilized after the acquisition. Preferably that would happen voluntarily under the policies of NRPM 4.6 (Amnesty), but it also leaves the door open for ARIN to revoke space under NRPM 12 (Resource Review) if necessary. This also should dramatically increase the completion rate for transfer requests, as the evaluation of whether space is efficiently utilized after the transfer can occur in parallel, completely independently of the transfer request, and can continue even if the transfer request is abandoned. The bulleted lists of acceptable documentation removed from the NRPM should be maintained by ARIN elsewhere on the website, such as at https://www.arin.net/resources/request/transfers.html Timetable for implementation: Immediate _______________________________________________ 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 Dec 28 12:50:29 2009 From: info at arin.net (Member Services) Date: Mon, 28 Dec 2009 12:50:29 -0500 Subject: [arin-announce] ARIN Board Adopts Bylaws Changes Message-ID: <4B38EFE5.7080605@arin.net> The ARIN Board of Trustees adopted a series of bylaws changes at its meeting on 18 December 2009. These changes include: * Redefined General Membership to require a valid ARIN Registration Services Agreement (RSA) or Legacy RSA for numbering resources * Moved the ?Good Standing? definition from Section 1 (Membership) to section 3 (Membership Rights) * Gave the Board discretion to appoint an additional member with a financial management background * Removed the restriction of number of officer positions a Board member may hold in order to safeguard Board operations * Established an eligibility deadline for voting in elections View these changes in the Bylaws change log at: https://www.arin.net/about_us/corp_docs/bylaws_changelog.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue Dec 29 11:39:49 2009 From: info at arin.net (Member Services) Date: Tue, 29 Dec 2009 11:39:49 -0500 Subject: [arin-announce] [Fwd: [arin-ppml] Policy Proposal 106: Simplified IPv6 policy] - new proposal Message-ID: <4B3A30D5.3030500@arin.net> The following is a new policy proposal that has been posted to the ARIN Public Policy Mailing List for discussion on that list. Regards, Member Services American Registry for Internet Numbers (ARIN) -------- Original Message -------- Subject: [arin-ppml] Policy Proposal 106: Simplified IPv6 policy Date: Tue, 29 Dec 2009 11:38:45 -0500 From: Member Services To: arin-ppml at arin.net ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with 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. Draft Policies and Proposals under discussion can be found at: https://www.arin.net/policy/proposals/index.html The ARIN Policy Development Process can be found at: https://www.arin.net/policy/pdp.html Mailing list subscription information can be found at: https://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 106: Simplified IPv6 policy Proposal Originator: Scott Leibrand Proposal Version: 1.0 Date: 29 December 2009 Proposal type: new Policy term: permanent Policy statement: Delete "6.1 Introduction" This is all historical. Delete "6.2 Definitions" The definitions we need are all defined in section 2. Leave 6.3 as is (renumber to 6.1) I think these still accurately reflect the Goals we want our policy to follow. Move 6.4.1 to 1.1. Retitle to "Number resources not to be considered property" and update text per below. This is a principle more general than just IPv6, and needs to be updated to be ARIN-specific and refer to the RSA. Delete 6.4.2 - 6.4.4 These principles don't seem worthy of elevation to special status. Replace 6.5 Policies for allocations and assignments with text below (renumber to 6.2) This seems to be where most of the changes and simplification are needed. Delete 6.6 References This is all historical, and doesn't need to be part of the NRPM. Delete 6.7 Appendix A: HD-Ratio We can let the HD-Ratio guide policy without making people like David's grandma do the math. Delete 6.8. Appendix B: Background information This is all historical Move 6.9 and 6.10 into 6.2.3.2 below Replacement text: 1.1. Number resources not to be considered property The policies in this document are based upon the understanding that globally-unique number resources are licensed for use rather than owned. Specifically, IP addresses and ASNs will be allocated and assigned as defined in the ARIN Registration Services Agreement. 2.8. Critical Infrastructure Providers Critical infrastructure providers of the Internet include public exchange points, core DNS service providers (e.g. ICANN-sanctioned root, gTLD, and ccTLD operators) as well as the RIRs and IANA. 4.4. Micro-allocation ARIN will make IPv4 micro-allocations to Critical Infrastructure Providers per section 2.8. These allocations will be no longer than a /24. Multiple allocations may be granted in certain situations. 4.4.1. Allocation and assignment from specific blocks Exchange point allocations MUST be allocated from specific blocks reserved only for this purpose. All other micro-allocations WILL be allocated out of other blocks reserved for micro-allocation purposes. ARIN will make a list of these blocks publicly available. 4.4.2. Exchange point requirements Exchange point operators must provide justification for the allocation, including: connection policy, location, other participants (minimum of two total), ASN, and contact information. ISPs and other organizations receiving these micro-allocations will be charged under the ISP fee schedule, while end-users will be charged under the fee schedule for end-users. This policy does not preclude exchange point operators from requesting address space under other policies. 6.2. Policies for IPv6 allocations and assignments 6.2.1. Allocations and assignments To meet the goal of Fairness, ARIN makes both allocations and assignments according to common criteria. Allocations are made to LIRs, and assignments to certain end users. 6.2.2. Assignments from LIRs/ISPs End-users are assigned an end site assignment from their LIR or ISP. The exact size of the assignment is a local decision for the LIR or ISP to make, using a minimum value of a /64 (when only one subnet is anticipated for the end site) up to the normal maximum of /48, except in cases of extra large end sites where a larger assignment can be justified. The following guidelines may be useful (but they are only guidelines): * /64 when it is known that one and only one subnet is needed * /56 for small sites, those expected to need only a few subnets over the next 5 years. * /48 for larger sites For end sites to whom reverse DNS will be delegated, the LIR/ISP should consider making an assignment on a nibble (4-bit) boundary to simplify reverse lookup delegation. 6.2.3. Allocations and assignments from ARIN 6.2.3.1 Goals To balance the goals of Aggregation, Conservation, Fairness, and Minimized Overhead, ARIN normally issues IPv6 addresses only in the discrete sizes of /48, /40, /32, /28, or /24 or larger. Each organization or discrete network may qualify for one allocation or assignment of each size, and must pay fees according to ARIN's fee schedule [https://www.arin.net/fees/fee_schedule.html] for each size issued. 6.2.3.1.1 Allocation and assignment from specific blocks Each allocation/assignment size will be made out of separate blocks reserved for that purpose. Additionally, non-routed assignments for internal infrastructure, and assignments to Critical Infrastructure Providers per section 2.8, will each be made out of separate blocks reserved for those purposes. ARIN will make a list of these blocks publicly available. 6.2.3.2 X-Small (/48) To qualify for a /48 allocation or assignment, an organization must: * Be Multihomed per section 2.7, and qualify for an ASN per section 5; or * Serve at least 1000 hosts; or * Demonstrate efficient utilization of all direct IPv4 assignments and allocations, each of which must be covered by any current ARIN RSA; or * Require a non-routed block for internal infrastructure; or * Be a Critical Infrastructure Provider per section 2.8. 6.2.3.3 Small (/40) To qualify for a /40 allocation or assignment, an organization must: * Have two or more Multihomed sites, each of which would qualify for a /48; or * Serve at least 2000 hosts; or * Be an LIR. 6.2.3.4 Medium (/32) To qualify for a /32 allocation or assignment, an organization must: * Have 100 or more sites, each of which would qualify for a /48; or * Be an existing, known LIR; or * Have a plan to provide IPv6 connectivity to other organizations and assign at least 100 end-site assignments to those organizations within 5 years. 6.2.3.5 Large (/28) To qualify for a /28, an organization must demonstrate the need to make assignments and/or reallocations equal to at least 25,000 /48s. 6.2.3.6 X-Large (/24) To qualify for a /24, an organization must demonstrate the need to make assignments and/or reallocations equal to at least 330,000 /48s. 6.2.3.7 XX-Large (larger than /24) Allocations or assignments larger than /24 may be made only in exceptional cases, to organizations that demonstrate the need to make assignments and/or reallocations equal to at least 4,500,000 /48s. If approved, the allocation prefix length will be based on the number of /24s justified (at 4,500,000 /48s each). 6.3. Registration ''(Copied from NRPM 6.5.5)'' When an organization holding an IPv6 address allocation makes IPv6 address assignments, it must register assignment information in a database, accessible by RIRs as appropriate (information registered by ARIN may be replaced by a distributed database for registering address management information in future). Information is registered in units of assigned /56 networks. When more than a /56 is assigned to an organization, the assigning organization is responsible for ensuring that the address space is registered in an ARIN database. 6.3.1. Residential Customer Privacy ''(Copied from NRPM 6.5.5.1)'' To maintain the privacy of their residential customers, an organization with downstream residential customers may substitute that organization's name for the customer's name, e.g. 'Private Customer - XYZ Network', and the customer's street address may read 'Private Residence'. Each private downstream residential reassignment must have accurate upstream Abuse and Technical POCs visible on the WHOIS record for that block. 6.3.2. Reverse lookup ''(Copied from NRPM 6.5.6)'' When ARIN delegates IPv6 address space to an organization, it also delegates the responsibility to manage the reverse lookup zone that corresponds to the allocated IPv6 address space. Each organization should properly manage its reverse lookup zone. When making an address assignment, the organization must delegate to an assignee organization, upon request, the responsibility to manage the reverse lookup zone that corresponds to the assigned address. Rationale: This policy proposal attempts to simplify IPv6 policy in a number of ways. For example, it: * Deletes a number of historical sections and items that duplicate text elsewhere in the NRPM. * Removes the HD-ratio, instead incorporating values calculated from it as the basis for qualification criteria. It also replaces & rewrites section 6.5 "Policies for allocations and assignments" entirely. This rewrite: * Eliminates the different criteria for allocations (ISPs) vs. assignments (end users) and replaces them with a single common set of criteria for both classes of users. The allocation vs. assignment distinction itself is preserved, as it still forms a useful basis for a cost-recovery fee structure, and for other parts of the NRPM (such as whois policy). * Creates a size-class-based system for allocating IPv6 address blocks. This has a number of advantages over the existing policy: ** Allows for safe filtering of traffic-engineering (TE) more-specific route announcements. ** In exchange (since PA more-specifics are expected to be filterable), allows any multihomed organization to get an assignment from ARIN. The smaller number of such PI assignments (compared to TE more-specifics) should mean that such assignments will largely be accepted across the DFZ. ** Expands the use of discrete blocks from which all allocations will be of identical prefix length and categorization. This will enable safer and easier TE filtering, as mentioned above. ** Expands the availability of non-routed blocks for internal infrastructure. Since routable blocks are available to any multihomed organization, there is no longer a need to restrict the availability of blocks from the non-routable pool. ** Makes allocations available to any LIR. Note: In the event of an M&A transfer per section 8.2 that would result in more than one block of a given size class being held by the combined organization, the organization should be encouraged to renumber into a single larger block and return the smaller block(s) when feasible. However, as long as the organization doesn't require any additional resources, this policy does not force them to make any changes. OTOH, if they request a larger block and still hold two or more smaller blocks, they would be required to return the smaller block as a condition for receiving the larger one. Timetable for implementation: Immediate (as soon as practical). _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML at arin.net). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact info at arin.net if you experience any issues. From info at arin.net Wed Dec 30 12:27:02 2009 From: info at arin.net (Member Services) Date: Wed, 30 Dec 2009 12:27:02 -0500 Subject: [arin-announce] ARIN Board Simplifies Membership Structure Message-ID: <4B3B8D66.7010707@arin.net> During its meeting on 18 December, the Board of Trustees adopted Bylaws changes that simplify ARIN?s membership structure. Beginning 1 January 2010, ARIN membership will be open to those organizations that have a signed Registration Services Agreement (RSA) or Legacy RSA with ARIN and hold Internet number resources under that agreement. Automatic Membership will continue to be granted to organizations with a direct allocation (generally service providers) of IPv4 or IPv6 address space under a signed RSA. Organizations with an AS number (ASN), or a direct assignment of address space from ARIN (generally end-user organizations), or that have a signed Legacy RSA have the option of becoming ARIN Members and participating in the governance of the organization. Feel free to contact us at info at arin.net if you have any questions. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Dec 30 14:01:25 2009 From: info at arin.net (Member Services) Date: Wed, 30 Dec 2009 14:01:25 -0500 Subject: [arin-announce] Election Changes for the New Year Message-ID: <4B3BA385.6050304@arin.net> The ARIN Board of Trustees has implemented a change to the ARIN Election process that will affect the 2010 Elections. General Member organizations must be on record with ARIN by the 1 January to be eligible to vote in elections for that year. All new ARIN Members who join after 1 January, 2010 will become eligible to vote in 2011. Please note that if your Organization is currently a Member this change will not affect your ability to vote. You can view this change in the ARIN bylaws Article VIII, Section 4a at: https://www.arin.net/about_us/corp_docs/bylaws.html#viii_4a If you?d like to learn more about the ARIN Election process please visit ARIN Election Headquarters at: https://www.arin.net/app/election/ If you have additional inquiries, feel free to contact info at arin.net. Happy New Year, Member Services Department American Registry for Internet Numbers (ARIN)