From info at arin.net Fri Sep 12 11:07:33 2008 From: info at arin.net (Member Services) Date: Fri, 12 Sep 2008 11:07:33 -0400 Subject: ARIN XXII: All We Are Missing Is You! Message-ID: <48CA85B5.30405@arin.net> We are looking forward to the ARIN XXII Public Policy and Members Meeting, taking place 15-17 October 2008, in Los Angeles, California, and we hope you are too. Come be a part of the community in action - don?t let your voice go unheard! Register today to take advantage of the early registration fee of $100. It increases to $150 on 15 September. The meeting will take place at the Millennium Biltmore Hotel. ARIN XXII attendees are eligible for a special room rate of $189 (USD), based on availability, if reservations are made before 19 September. In addition to the Public Policy and Members Meeting, there will be a number of informative events, including a introduction to the ARIN Policy development process and Open Policy Hour. The meeting will open on Wednesday with a special panel discussion, co-hosted with NANOG, titled ?What Would Jon have done about the Addressing Challenges Currently Facing Us?? Hotel and travel information, meeting registration, and an agenda overview are available through http://www.arin.net/ARIN-XXII/. A more detailed agenda will be posted soon. Can?t make it to the meeting? Be on the lookout for details on new and improved remote participation opportunities. As always, please contact ARIN Member Services at info at arin.net with any questions. We look forward to seeing you in LA! Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue Sep 16 10:31:17 2008 From: info at arin.net (Member Services) Date: Tue, 16 Sep 2008 10:31:17 -0400 Subject: 2008-3: Community Networks IPv6 Allocation - Revised Message-ID: <48CFC335.9030207@arin.net> Policy Proposal "2008-3: Community Networks IPv6 Allocation" has been revised. This proposal is open for discussion on this mailing list and will be on the agenda at the upcoming ARIN XXII Public Policy Meeting in Los Angeles. The current policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2008_3.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2008-3 Community Networks IPv6 Allocation Author: Joshua King Date: 16 September 2008 Proposal type: new Policy term: permanent Policy statement: [Add Section 2.8 to the NRPM.] 2.8 Community Network A community network is a generic reference to a network that is operated by a group of people living in a particular local area organized for the purposes of delivery or provision of free or low-cost network services to the residents of an incorporated or unincorporated regional municipality, city, town, village, rural municipality, township, county, district or other municipality or other such geographic space, however designated. In order to qualify as a community network under this policy, the community network must certify to ARIN that their staff is at least half volunteer and that their annual revenue is less than $250000 (in 2009 dollars, adjusted for inflation). Legal responsibility for the network as a whole must be held by an organization either possessing non-profit status or fiscally sponsored by a non-profit organization or university. [Modify 6.5.8.1b as follows.] b. qualify for an IPv4 assignment or allocation from ARIN under the IPv4 policy currently in effect or be a qualifying Community Network as defined in Section 2.8, with allocation criteria defined in section 6.5.9. [Add Section 6.5.9 to the NRPM.] 6.5.9 Community Network Allocations 6.5.9.1. Initial assignment size Organizations defined as Community Networks under section 2.8 are eligible to receive a direct assignment. The minimum size of the assignment is /48. Organizations requesting a larger assignment must provide documentation of the characteristics of the Community Network's size and architecture that require the use of additional subnets. An HD-Ratio of .94 with respect to subnet utilization within the network must be met for all assignments larger than a /48. These assignments shall be made from a distinctly identified prefix and shall be made with a reservation for growth of at least a /44. This reservation may be assigned to other organizations later, at ARIN's discretion. 6.5.9.2. Subsequent assignment size Additional assignments may be made when the need for additional subnets is justified. Justification will be determined based on a detailed plan of the network's architecture and the .94 HD-Ratio metric. When possible, assignments will be made from an adjacent address block. 6.5.9.3. Number of customers Community Networks seeking an allocation must demonstrate that they provide for a user base of at least 100 through connectivity to homes and businesses, public facilities, public access points, or mobile users. Community Networks with user bases of under 200 must also submit a plan for doubling their service base over the next year. Rationale: There are currently a number of projects globally that aim to develop community network infrastructure and related technologies. These are usually coordinated by volunteer-run, grassroots organizations which lack many of the resources of traditional internet service providers and other network operators. They have diverse goals, including public policy, software development, and implementation of community services and resources. Many of them provide services free of charge, and thus lack any paying user base. However, in order to create and maintain community networks that are often composed of hundreds if not thousands of inexpensive consumer-grade network devices, a significant amount of address space will be required. Current-generation workarounds to this problem, such as NAT, not only make it difficult to develop next-generation decentralized network technology by segmenting the community's architecture from the Internet as a whole, but will cease to be as viable a stopgap as the Internet moves towards IPv6 integration. Community-based, volunteer-run organizations that are operated with an eye towards the public good often do not have the resources to qualify as an LIR under the current policy. They are often multi-homed networks utilizing multiple, relatively inexpensive consumer-grade internet uplinks and lacking the funds to meet the qualifications for an IPv4 allocation, but which wish an avenue to develop future IPv6 capability for their constituent users. If this proposal is adopted, I intend to immediately move forward with the process to request a change in fee structure for community networks so that they are permitted to pay a small percentage of their annual revenue in lieu of a flat fee. By establishing a procedure by which these organizations can seek to acquire the resources they require for further development, ARIN can reach out to this active community and establish a small but definite space for them in the future of Internet. Timetable for implementation: Immediate. From info at arin.net Tue Sep 16 10:33:34 2008 From: info at arin.net (Member Services) Date: Tue, 16 Sep 2008 10:33:34 -0400 Subject: Policy Proposals and Draft Agenda Message-ID: <48CFC3BE.6020301@arin.net> The following policy proposals have been under discussion on the ARIN Public Policy Mailing List and will be presented for consideration at the upcoming ARIN XXII Public Policy Meeting in Los Angeles on 15-16 October 2008. 2007-14: Resource Review Process 2008-2: IPv4 Transfer Policy Proposal 2008-3: Community Networks IPv6 Allocation 2008-4: Minimum Allocation in the Caribbean Region 2008-5: Dedicated IPv4 block to facilitate IPv6 Deployment 2008-6: Emergency Transfer Policy for IPv4 Addresses 2008-7: Whois Integrity Policy Proposal The full text for each proposal can be found at: http://www.arin.net/policy/proposal_archive.html Agenda information has been updated. Find the draft agenda as well as hotel information at: http://www.arin.net/ARIN-XXII/ ARIN XXII attendees: To ensure you get the special reserved rate of $189 single/double, please make your reservation before 19 September! Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu Sep 18 09:22:37 2008 From: info at arin.net (Member Services) Date: Thu, 18 Sep 2008 09:22:37 -0400 Subject: Policy Proposal 2008-2: IPv4 Transfer Policy Proposal - Revised Message-ID: <48D2561D.2040205@arin.net> Policy Proposal "2008-2: IPv4 Transfer Policy Proposal" has been revised. This proposal is open for discussion on this mailing list and will be on the agenda at the upcoming ARIN XXII Public Policy Meeting in Los Angeles. The current policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2008_2.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2008-2 IPv4 Transfer Policy Proposal Author: ARIN Advisory Council Proposal Version: 1.4 Date: 09/18/2008 Proposal type: modify Policy term: permanent Policy statement: Modify the current NRPM section 8 as follows -- 8. Transfers [8.1. Transfers ? retain as is] [8.2 ? remove the word ?only?, and retitle to ?Transfers as an Artifact of Change in Resource Holder Ownership?] [Renumber existing 8.3 to 8.2.1 and retitle to ?Documentation Requirements for Transfers as an Artifact of Change in Resource Holder Ownership?] [Add the following new section:] 8.3. Simple Transfer of IPv4 Addresses In light of the pending exhaustion of the IANA IPv4 free pool, ARIN will also process IPv4 address transfer requests subject to the following conditions. These conditions apply only to Simple IPv4 transfers, not to transfers performed according to section 8.2. 8.3.1 Conditions on the transferor (the organization providing addresses for transfer): ? The transferor has no outstanding balances with ARIN. ? The transferor has not received any IPv4 allocations or assignments from ARIN (through ordinary allocations or assignments, or through this Simple Transfer policy) within the preceding 12 months. ? If the transferor elects to retain a portion of a block pursuant to 8.3.6, rather than transferring an entire block, the transferor must sign (or have previously signed) a RSA or LRSA covering the retained portion. 8.3.2 Conditions on the transferee (the organization receiving the transferred addresses): ? The transferee intends to use the transferred IPv4 addresses within the ARIN service area. ? The transferee has no outstanding balances with ARIN. ? The transferee?s need is confirmed by ARIN, according to current ARIN policies. ? The transferee signs (or has previously signed) an RSA covering the IPv4 addresses transferred. ? The transferee may request and receive a contiguous CIDR block large enough to provide a 12 month supply of IPv4 addresses. ? The transferee may only receive one IPv4 address transfer through this Simple Transfer process every 6 months. 8.3.3 Conditions on the IPv4 address block to be transferred: ? The IPv4 block must comply with applicable ARIN allocation requirements, including minimum allocation size. However, an IPv4 allocation or assignment of /24 or larger, but smaller than the current minimum allocation size, may be transferred as a whole resource (but may not be subdivided). ? The IPv4 block must currently be registered for use within the ARIN service area. ? There must be no dispute as to the status of the IPv4 block or regarding the allocation or assignment of such block to the transferor. 8.3.4 [Section omitted] 8.3.5 Pre-qualification ? An interested transferee must seek pre-qualification from ARIN to confirm its eligibility to receive a transfer (including satisfaction of need according to current ARIN policies) before making any solicitation for transfer. Upon pre-qualification, ARIN will provide the transferee with documentation of the pre-qualification, including the size (CIDR prefix length) of the largest IPv4 address block the transferee is eligible to receive, and the expiration date of the pre-qualification. ? An interested transferor may seek pre-qualification from ARIN to confirm its eligibility to offer a transfer before offering IPv4 address resources for transfer. Upon pre-qualification, ARIN will provide the transferor with documentation of the pre-qualification, including the network block and the expiration date of the pre-qualification. 8.3.6 Deaggregation when Permitted by ARIN ARIN may allow transferors to subdivide network blocks. ARIN will attempt to ensure an adequate supply of small blocks while minimizing deaggregation. 8.3.7. Safe Harbor The fact that an IPv4 address holder is making IPv4 addresses available for transfer, pursuant to this policy, does not, in and of itself, indicate that the address holder lacks the need required for an allocation under ARIN policy. 8.3.8. Organizations under Common Ownership or Control If an IPv4 transferor or transferee is under common ownership or control with any other organization that holds one or more IPv4 blocks, the IPv4 transfer request must report all such organizations under common ownership or control. When evaluating compliance with IPv4 Simple Transfer conditions, ARIN may consider a transfer request in light of requests from other organizations under common ownership or control. 8.3.9. Record-keeping and Publication ARIN will develop and operate a listing service to assist interested transferors and transferees by providing them a centralized location to post information about IPv4 blocks available from pre-qualified transferors and IPv4 blocks needed by pre-qualified transferees. Participation in the listing service is voluntary. After completion of a transfer, ARIN will update the registration and WHOIS records pertaining to the IPv4 block. ARIN will also publish a log of all transfers, including block, transferor, transferee, and date. Rationale: The ARIN Board of Trustees asked the Advisory Council to consider a set of questions around the depletion of the free pool of IPv4 addresses, the transition to IPv6 for Internet address needs in the future, and ARIN's possible role in easing the transition. Over the course of the year, the Advisory Council has worked to solicit input from all parts of the policy-making community, through the ARIN XXI public policy meeting, the Public Policy Mailing List (PPML), sector meetings, and a poll of PPML subscribers. As a result of the input received, this policy has been simplified considerably, removing or modifying text and restrictions deemed unnecessary, while preserving those aspects that seem to be supported by consensus. This policy proposal would create a transfer mechanism for IPv4 number resources between those who have excess resources and those who have a need, thereby allowing ARIN to continue to serve its mission after IANA free pool exhaustion. This proposal would also set conditions on such transfers intended to preserve as much as possible the existing policy related to efficient, needs-based resource issuance, and would leverage ARIN's control systems, audit trails, and recognized position as a trusted agent to avoid speculation and hoarding and diminish the likelihood and extent of an uncontrolled 'black market' where the risk and potential for fraud is immeasurably higher. Many of the transfer conditions are self-explanatory, but some worth highlighting are that: ? To discourage speculation, a waiting period (proposed at 12 months) is required before a recipient of space can transfer it to another organization. ? Transferees must qualify for IPv4 space (just as they do today when getting it from ARIN) before they can receive address space by transfer, or solicit space on a listing service. ? To discourage unnecessarily rapid growth of routing tables, an allocation or assignment may not be arbitrarily deaggregated. To ensure an adequate supply of small blocks while minimizing deaggregation, ARIN may allow transferors to subdivide network blocks. A suggested starting point is to allow transferors to subdivide an IPv4 block into up to four smaller blocks on CIDR bit-boundaries, provided each resulting block satisfies the minimum allocation size. ? A transferee may receive one transfer every 6 months, and may receive at least 12 months worth of space, so they?ll be incented to transfer a block appropriately sized for their needs, which will further discourage deaggregation and keep smaller blocks available for smaller organizations. The proposal would also have ARIN develop and operate a listing service to facilitate transfers and provide an authoritative central source of information on space available and requested for transfer. It would not prohibit private party transactions, but would encourage potential transferors and transferees be pre-qualified first, so that neither party will encounter any surprises when they ask ARIN to process the transfer. Timetable for implementation: immediately upon ratification by the Board of Trustees From info at arin.net Fri Sep 19 13:59:09 2008 From: info at arin.net (Member Services) Date: Fri, 19 Sep 2008 13:59:09 -0400 Subject: Policy Proposal: whois POC e-mail cleanup - Revised Message-ID: <48D3E86D.1020003@arin.net> The author submitted a revised version of their proposal. The ARIN Advisory Council (AC) will review this proposal at their next regularly scheduled meeting. The AC may decide to: 1. Accept the proposal as written. If the AC accepts the proposal, it will be posted as a formal policy proposal to PPML and it will be presented at a Public Policy Meeting. 2. Postpone their decision regarding the proposal until the next regularly scheduled AC meeting in order to work with the author. The AC will work with the author to clarify, combine or divide the proposal. At their following meeting the AC will accept or not accept the proposal. 3. Not accept the proposal. If the AC does not accept the proposal, the AC will explain their decision via the PPML. If a proposal is not accepted, then the author may elect to use the petition process to advance their proposal. If the author elects not to petition or the petition fails, then the proposal will be closed. In the meantime, the AC invites everyone to comment on this proposal on the PPML, particularly their support or non-support and the reasoning behind their opinion. Such participation contributes to a thorough vetting and provides important guidance to the AC in their deliberations. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html Mailing list subscription information can be found at: http://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal Name: whois POC e-mail cleanup Author: Ted Mittelstaedt Proposal Version: 2 Submission Date: 9/19/2008 Proposal type: new Policy term: permanent Policy statement: Under Directory Services in the NRPM add section 3.6 titled "Reliability of Whois information" 3.6.1 ARIN will use an automated system that once a year will attempt to e-mail all separate e-mail addresses in the directory. (including abuse addresses) At it's discretion, ARIN will attempt to contact by regular mail or phone any POC entries that have invalid e-mail addresses (i.e. e-mail addresses that bounce mail sent to them) and give them a 3 month deadline for correction of their mail address. The automated system will not use a mail cluster or other mail transmission software that is incompatible with commonly available anti-spam technologies, such as greylisting. ALL POC's that fail to respond to paper mails or telephone calls after the deadline will have their e-mail address replaced with "FAILED TO RESPOND, PRIOR ADDRESS: " in the directory. The automated e-mails will have a text string titled "ARIN Automated POC e-mail test" identifying them so that automated trouble ticket systems can be programmed to automatically delete the mail messages instead of replying to them. 3.6.2 ARIN will supply a report to the community, updated monthly, that lists the percentage of "FAILED TO RESPOND" POCs, the percentage of POCs that accept e-mails, and the percentage of POC addresses that have a response pending. Rationale: As the entire Internet community gets closer to the date that IPv4 will be exhausted, more attention is being focused on the possibility that there is significant amounts of allocated IPv4 that is abandoned. There are also concerns that as the amount of usable IPv4 space gets more and more crowded, that Internet criminals are turning to abandoned IPv4 space that is still listed as allocated in the whois directories to use to make attacks on hosts on the Internet. Because of these reasons, it is becoming more important that users of ARIN's whois data have a reasonable expectation that it is accurate. The current NRPM has a mechanism for adding, modifying, and deleting POCs. However it also carries an assumption that POCs belonging to defunct companies will be removed when the bills for allocated IP addressing cease being paid, and the address resources are then returned to the ARIN pool as a result. The problem is that this assumption does not hold true for so-called "Legacy" IP address holders since they do not pay a yearly fee. Furthermore, billing for the IP addressing allocations is done through paper mail, thus it is possible for a POC to have a valid street address, but an invalid E-mail address, and not be caught because they are current on their account. This is becoming a serious issue because contacting a POC via a street address is too slow for victims of an attack from a hijacked IP block to be able to complain to the block owners and the block owners to be able to catch the perpetrators. This proposal is a "first step" proposal to attack the problem of invalid e-mail addresses in the WHOIS database. It is specifically intended to be an automated mechanism. It is understood that IP address hijackers could hijack a legacy block and setup a mailserver to respond to a POC address on the block and thus dodge this system. (assuming the domain name used in the defunct POC e-mail address was available, which is not likely) Detecting such a setup is going to require more advanced mechanisms than are appropriate to be spelled out in a policy manual, and this proposal in no way precludes such mechanisms from being employed. Fundamentally, ARIN cannot guarantee the validity of WHOIS entries in the directory that belong to legacy holders who have not signed an LRSA, there's some legal challenges to proving that a legacy holder who is masquerading as a defunct organization is in fact a hijacker. This proposal SPECIFICALLY DOES NOT require a POC to make a response. All that is needed is for the POC e-mail address to be accepting mail. The difficulties in dealing with the large number of responses back, plus the fact that it's likely that many responses back will be sent from e-mail addresses other than what is listed in the POC, would make requiring ARIN to get a response back to determine legitimacy to greatly increase the complexity of this proposal and make it likely to be unworkable. The report of FAILED TO RESPOND POCS needs to be monthly because there is NO REQUIREMENT that ARIN contact ALL POCS in the database ON THE SAME DATE. It is assumed that ARIN would e-mail only 1/12'th of all POC's in the database at the beginning of every month to spread out the workload. There is a mechanism already defined in the NRPM to get a bulk dump of the whois database, which would of course contain the FAILED TO RESPOND entries. Timetable for implementation: Immediate From info at arin.net Wed Sep 24 13:38:00 2008 From: info at arin.net (Member Services) Date: Wed, 24 Sep 2008 13:38:00 -0400 Subject: NRPM version 2008.4 - New Policy Implementation Message-ID: <48DA7AF8.1080301@arin.net> On 11 August 2008 the ARIN Board of Trustees, acting on the recommendation of the Advisory Council and noting that the Internet Resource Policy Evaluation Process had been followed, adopted the following policy proposal: * Policy Proposal 2007-17: Legacy Outreach and Partial Reclamation On 31 July 2008 the ICANN Board ratified the following global policy proposal: * Policy Proposal 2007-19: IANA Policy for Allocation of ASN Blocks to RIRs These policies have been incorporated into version 2008.4 of the ARIN Number Resource Policy Manual (NRPM). NRPM version 2008.4 is effective 24 September 2008 and supersedes previous versions. See Appendix A of the NRPM for information regarding changes to the manual. 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) From info at arin.net Thu Sep 25 11:57:41 2008 From: info at arin.net (Member Services) Date: Thu, 25 Sep 2008 11:57:41 -0400 Subject: ARIN XXII Open Policy Hour Message-ID: <48DBB4F5.4010005@arin.net> Sign up today to present your ideas at the ARIN XXII Open Policy Hour, Tuesday, 14 October, from 6:00-7:00 PM (PDT). The Open Policy Hour (OPH) is a showcase for your policy ideas. If you have a policy proposal you'd like to debut, prior to formally submitting it, here is your opportunity. Sign up by Friday, 10 October to ensure your chance to take 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. Information on this and other sessions is available at: http://www.arin.net/ARIN-XXII/agenda.html We are in the process of upgrading our remote participation options. These new features will be available during the Open Policy Hour. Be on the lookout for more details on how you can join in the discussion even if you can't be with us in Los Angeles. We look forward to your participation in ARIN XXII. Meeting details are available at http://www.arin.net/ARIN-XXII/. Please contact Member Services at info at arin.net if you have any questions. Regards, Member Services Department American Registry for Internet Numbers (ARIN)