From memsvcs at arin.net Wed Sep 4 10:34:21 2002 From: memsvcs at arin.net (Member Services) Date: Wed, 4 Sep 2002 10:34:21 -0400 (EDT) Subject: ARIN X Meeting Registration Now Available Message-ID: Registration is now open for the ARIN X Public Policy and Members meetings to be held in Eugene, Oregon beginning Wednesday, October 30 through noon on Friday, November 1. For the first time, the ARIN fall meeting is being held immediately following NANOG, so be certain to take advantage of the joint location and register for both meetings. The ARIN X meeting home page is available at: http://www.arin.net/ARIN-X/index.html >From here you can proceed to an online registration form, find hotel information, and the meeting agenda. Check out the sponsorship link for exciting opportunities still available. Add your company logo to the list of sponsors! ARIN thanks the following meeting sponsors: Sprint and the University of Oregon for all network related activities throughout the ARIN meeting and Preferred Communications Inc., NW for the Thursday breakfast. Be sure to visit the ARIN X web page later this month and leading up to the meeting for specific agenda items. If you have any questions regarding ARIN X, please contact memsvcs at arin.net or call 703-227-9878. We look forward to seeing you in Eugene. ARIN Member Services From memsvcs at arin.net Thu Sep 12 13:50:40 2002 From: memsvcs at arin.net (Member Services) Date: Thu, 12 Sep 2002 13:50:40 -0400 (EDT) Subject: DNS Security Extensions Workshop Message-ID: ARIN is sponsoring a two-day workshop on the DNS Security Extensions. The workshop will be held on October 7-8 in Northern Virginia. The exact location has not been finalized and will be announced in a subsequent message. Attendance will be limited to 20 on a first come, first served registration basis. There is no registration fee, but attendees are responsible for their own travel, accommodations, and meals. More details will be made available upon request. To request additional information or register for the workshop, send e-mail to memsvcs at arin.net. ARIN Member Services From memsvcs at arin.net Mon Sep 16 14:29:37 2002 From: memsvcs at arin.net (Member Services) Date: Mon, 16 Sep 2002 14:29:37 -0400 (EDT) Subject: Take Action: Nominate Candidates and Register for ARIN X Message-ID: ARIN encourages you to get involved this fall by participating in the ARIN election process and by voicing your opinions at the upcoming Public Policy meeting. As an ARIN member you have until September 30 to nominate candidates you would like to see run for the ARIN Board of Trustees and Advisory Council. Self-nomination by ARIN members is also encouraged. In addition, anyone may nominate candidates for the open seat on the ICANN ASO Address Council from the ARIN region. For election details and nomination forms see: http://www.arin.net/elections/index.html Registration is now open for the ARIN X Public Policy and Members meetings to be held October 30 - November 1. The meetings will be held in Eugene, Oregon immediately following NANOG 26, so take advantage of the joint location and plan to attend both. ARIN is seeking sponsors for a variety of events in Eugene. Be sure to consider these opportunities to contribute to the IP address community. Meeting details can be found at: http://www.arin.net/ARIN-X/index.html Regards, ARIN Member Services From memsvcs at arin.net Mon Sep 23 13:36:52 2002 From: memsvcs at arin.net (Member Services) Date: Mon, 23 Sep 2002 13:36:52 -0400 (EDT) Subject: ARIN Policy Proposals Message-ID: To All Interested Parties: ARIN will hold its next Public Policy Meeting in Eugene, Oregon on October 30 through 31, 2002. Meeting and registration details can be found at: http://www.arin.net/ARIN-X/index.html ARIN's Internet Resource Policy Evaluation Process specifies that policy proposals must be posted to the ARIN mailing lists at least 30 days prior to an ARIN meeting where they will be discussed. ARIN's Internet Resource Policy Evaluation Process is described at: http://www.arin.net/policy/ipep.html ARIN staff has received from various sources policy proposals to be discussed at the upcoming Public Policy Meeting. Each of these proposals will be released as a separate e-mail to the public policy mailing list over the next several days. The progress of each policy proposal will be tracked and documented at the following location. http://www.arin.net/policy/proposal_archive.html The entire Internet community is invited and encouraged to participate in these policy discussions. Your active participation in these discussions will help to form policies that are beneficial to all. Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) From memsvcs at arin.net Mon Sep 23 15:10:27 2002 From: memsvcs at arin.net (Member Services) Date: Mon, 23 Sep 2002 15:10:27 -0400 (EDT) Subject: Policy Proposal 2002-2 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Eugene, Oregon, scheduled for October 30-31, 2002. All feedback received on the mailing list about this policy proposal will be included in the discussions that will take place at the upcoming Public Policy Meeting. This policy proposal discussion will take place on the ARIN Public Policy Mailing List (ppml at arin.net). Subscription information is available at http://www.arin.net/mailing_lists/index.html Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) ### * ### Policy Proposal 2002-2: Experimental Internet Resource Allocations There have been a number of experimental address allocations undertaken in the Internet over the past decade. These experimental address allocations have been made by the IANA in coordination with standards bodies, such as the IETF, on an ad hoc basis. There is currently no systematic means of receiving other Numbering Resources on a temporary basis as part of a recognised experiment in Internet technology deployment. The following policy is proposed: The RIRs will allocate Numbering Resources to entities requiring temporary Numbering Resources for a fixed period of time under the terms of recognised experimental activity. The following criteria for this policy are proposed: 1. Public Disclosure of Experimental Requests The organisation requesting the resources will have to detail what experimental work they are going to carry out. Such detail can usually be made either: * by submitting a proposal that references a current IETF Experimental RFC (Detail Two), or * by submitting an 'experiment proposal' detailing what resources are required, and what activities will be carried out (Detail Three). Such experimental proposals will, in the normal course of events be made public upon acceptance of the proposal by an RIR. Consideration will be given to non-disclosure constraints, but this is anticipated to be a prohibitive constraint upon the use of public Numbering Resources, even in an experimental context. The RIR will not allocate resources if the entire research experiment cannot be publicly disclosed as per Details Two and Three following. 2. Resource Coordination with Standards Development Bodies The IETF from time to time describes experimental activities and associated requirements for resources that will be required by participants in the experiment. It is considered as being acceptable for the organisation to reference a current Experimental RFC and indicate the organisation's participation in the experiment. Organisations such as the IETF, who describe experimental activities as part of their standards development process, need to consider the associated Numbering Resource requirements with any proposed experiment, and under this proposal will need to liaise with the RIRs as part of the process of publishing a draft as an experimental RFC. 3. Resource Coordination with Independent Experiments For experimental proposals not covered by Detail Two, the RIR will require the experiment's aims and objectives to be published in a publicly accessible document. The RIRs have a strong preference for the use of an Experimental RFC published through the IETF, but will accept other publication mechanisms where the experiment's objectives and practices are publicly and openly available free of charges and free of any constraints of disclosure. The RIRs would also normally require that the experiment's outcomes be published in an openly and freely available document, again free of charges and free of any constraints of disclosure. 4. Resource Allocation Term and Renewal The Numbering Resources are allocated on a lease/license basis for a period of one year. The allocation can be renewed on application to the issuing RIR providing information as per in Detail One. The identity and details of the applicant and the allocated Numbering Resources will be published under the conditions of the RIR's normal publication policy (for example, listed as a temporary allocation in the RIR's database). 5. Single Resource Allocation per Experiment The RIR will make one-off allocations only, on an annual basis. Additional allocations outside the annual cycle will not be made unless justified by a subsequent complete application. It's important for the requesting organisation to ensure they have sufficient resources requested as part of their initial application for the proposed experimental use. 6. Resource Allocation Fees Each RIR may charge an administration fee to cover each allocation made of these experimental resources. This fee simply covers registration and maintenance, rather than the full allocation process for standard RIR members. This administration fee should be as low as possible as these requests do not have to undergo the same evaluation process as those requested in the normal policy environment. 7. Resource Allocation Size The Numbering Resources requested come from the global Internet Resource space, and are not from private or other non-routable Internet Resource space. The allocation size should be consistent with the existing RIR minimum allocation sizes, unless small allocations are intended to be explicitly part of the experiment. If an organisation requires more resource than stipulated by the minimum allocation sizes in force at the time of their request, they should include in their research proposal why this is required. 8. Commercial Use Prohibited If there is any evidence that the temporary resource is being used for commercial purposes, or is being used for any activities not documented in the original experiment description provided to the RIR, the issuing RIR reserves the right to immediately withdraw the resource and reassign it to the free pool. 9. Resource Request Appeal or Arbitration The RIRs should be in a position to assess and comment on the objectives of the experiment with regard to the requested amount of Numbering Resources. The issuing RIR should be able to modify the requested allocation as appropriate, and in agreement with the proposer. In the event that the proposed modifications are not acceptable, the requesting organization may request an appeal or arbitration using the normal procedures of the RIR. In this case, the original standards body that endorsed the experimental action may be requested to provide additional information regarding the experiment and its objectives to assist in the resolution of the appeal. ### end ### From memsvcs at arin.net Mon Sep 23 15:14:04 2002 From: memsvcs at arin.net (Member Services) Date: Mon, 23 Sep 2002 15:14:04 -0400 (EDT) Subject: Policy Proposal 2002-3 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Eugene, Oregon, scheduled for October 30-31, 2002. All feedback received on the mailing list about this policy proposal will be included in the discussions that will take place at the upcoming Public Policy Meeting. This policy proposal discussion will take place on the ARIN Public Policy Mailing List (ppml at arin.net). Subscription information is available at http://www.arin.net/mailing_lists/index.html Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) ### * ### Policy Proposal 2002-3: Micro-Assignments for Multihomed Networks ARIN's current minimum assignment size is a /20. The following is proposed to enable multihomed networks to obtain their IPv4 address space directly from ARIN: Multihomed networks not meeting ARIN's current allocation guidelines may receive a properly justified /21-/24 sized network provided they have no other ARIN assigned space, and return all non-portable address space within 3 months of receiving their allocation. No justification (other than being multihomed, having no other allocations, and returning all other non-portable space) is required for a /24. ### end ### From memsvcs at arin.net Tue Sep 24 13:58:11 2002 From: memsvcs at arin.net (Member Services) Date: Tue, 24 Sep 2002 13:58:11 -0400 (EDT) Subject: Policy Proposal 2002-4 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Eugene, Oregon, scheduled for October 30-31, 2002. All feedback received on the mailing list about this policy proposal will be included in the discussions that will take place at the upcoming Public Policy Meeting. This policy proposal discussion will take place on the ARIN Public Policy Mailing List (ppml at arin.net). Subscription information is available at http://www.arin.net/mailing_lists/index.html Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) ### * ### Policy Proposal 2002-4: Bulk Copies of ARIN WHOIS Policy 2001-7 allows organizations to obtain bulk copies of ARIN WHOIS data, minus point of contact information, after signing ARIN's acceptable use policy for bulk WHOIS data. Many organizations require the bulk WHOIS data, and also need the accompanying point of contact information. Although the point of contact information is not currently supplied with the bulk copies of ARIN WHOIS data, it is openly available by submitting individual queries to ARIN's WHOIS servers. Organizations may currently obtain bulk copies of WHOIS data from APNIC and RIPE NCC that include point of contact information, but continue to have to obtain the data from ARIN's WHOIS services, one query at a time. The following policy is proposed: ARIN will provide a bulk copy of WHOIS output, including point of contact information, on the ARIN site for download by any organization that wishes to obtain the data providing they agree to ARIN's acceptable use policy. It is also proposed the existing ARIN Bulk WHOIS Acceptable Use Policy... ##The ARIN WHOIS data is for Internet operational or technical research purposes pertaining to Internet operations only. It may not be used for advertising, direct marketing, marketing research, or similar purposes. Use of the ARIN WHOIS data for these activities is explicitly forbidden. ARIN requests to be notified of any such activities or suspicions thereof.## ...be applied in the implementation of any policy that results from this policy proposal with the addition of the following text: Redistributing bulk ARIN WHOIS data is explicitly forbidden. It is permissible to publish the data an individual query or small number of queries at a time, as long as reasonable precautions are taken to prevent automated querying by database harvesters. ### END ### From memsvcs at arin.net Tue Sep 24 14:01:25 2002 From: memsvcs at arin.net (Member Services) Date: Tue, 24 Sep 2002 14:01:25 -0400 (EDT) Subject: Policy Proposal 2002-5 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Eugene, Oregon, scheduled for October 30-31, 2002. All feedback received on the mailing list about this policy proposal will be included in the discussions that will take place at the upcoming Public Policy Meeting. This policy proposal discussion will take place on the ARIN Public Policy Mailing List (ppml at arin.net). Subscription information is available at http://www.arin.net/mailing_lists/index.html Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) ### * ### Policy Proposal 2002-5: Amnesty Requests If an organization, whether a member or non-member, ISP or end-user, relinquishes a block of address space to ARIN, they shall be allowed to select any smaller size of block in exchange, and shall not be required to justify their use of that space. That is, anyone should be able to decrease their use of address space at any time without fear of the effects of a utilization audit. ARIN staff shall, at their discretion, determine whether the smaller replacement block shall be a subnet of the returned block, or a block allocated from some different range. In the case of an organization name change for address resource records, ARIN's normal transfer policies will apply. ###END### From memsvcs at arin.net Wed Sep 25 15:22:32 2002 From: memsvcs at arin.net (Member Services) Date: Wed, 25 Sep 2002 15:22:32 -0400 (EDT) Subject: ARIN Policy Proposal 2002-6 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Eugene, Oregon, scheduled for October 30-31, 2002. All feedback received on the mailing list about this policy proposal will be included in the discussions that will take place at the upcoming Public Policy Meeting. This policy proposal discussion will take place on the ARIN Public Policy Mailing List (ppml at arin.net). Subscription information is available at http://www.arin.net/mailing_lists/index.html Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) ### * ### Policy Proposal 2002-6: Aggregation Requests If an organization, whether a member or non-member, ISP or end-user, relinquishes a group of non-aggregatable address blocks to ARIN, they shall be allowed to select a block in exchange, of no less than /24, and no more than the next greater than the sum of the blocks relinquished. For example, if an organization relinquished three /24s, they should be allowed to take either a /24, a /23, or a /22 in exchange. If all of the previous address blocks were maintained in the ARIN database without maintenance fees, the replacement space shall be as well, but if any one of the returned blocks had associated maintenance fees, then the replacement block shall also be subject to maintenance fees. ###END### From memsvcs at arin.net Wed Sep 25 15:36:48 2002 From: memsvcs at arin.net (Member Services) Date: Wed, 25 Sep 2002 15:36:48 -0400 (EDT) Subject: ARIN Policy Proposal 2002-7 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Eugene, Oregon, scheduled for October 30-31, 2002. All feedback received on the mailing list about this policy proposal will be included in the discussions that will take place at the upcoming Public Policy Meeting. This policy proposal discussion will take place on the ARIN Public Policy Mailing List (ppml at arin.net). Subscription information is available at http://www.arin.net/mailing_lists/index.html Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) ### * ### Policy Proposal 2002-7: Micro-Assignments for Multihomed Organizations Arin should reduce the current minimum IP allocation requirement to /21 -/24 if an organization is multihomed and actively using AS number(s). Arin may periodically inquire and verify that the multihomed organization is actively using AS number(s). ARIN may reclaim its IP's from organizations that no longer are multihomed and/or stop using AS number(s). The following new fee schedule for /21 - /24 should be implemented as follows (based on the current fee schedule with a smaller minimum): $400.00 per year for /23 - /24 $1000.00 per year for /21 - /22 1. ARIN's current minimum IP allocation policy has a direct correlation with the size of a company. Generally a company that uses a /20 IP allocation has a larger network and customer base, therefore they would be considered in the category of large size companies. This policy currently discriminates, puts a small business at a disadvantage and promotes and helps to monopolize large ISP's and upstream providers. 2. Currently, many ISP's and upstream providers are in bankruptcy and/or have gone out of business; therefore, getting IP's from upstream providers is no longer a good solution since small businesses will have the disadvantage of returning and re-numbering their IP's. 3. Once a small business obtains IP addresses from their upstream providers, upstream providers are able to hold that small business "hostage" and increase their rate without any consequences, because the level of difficulty to move to another upstream provider is great and could put the small company out of business. 4. The global routing table and its minimum allocation requirement must be investigated by several third party technology companies, who are non-partial and do not benefit from ARIN's decision in any way. They could determine what is the best minimum requirement in order for the Internet to run at its optimum and without any routing table problems. 5. ARIN's current policy of the minimum requirement of /20 addresses promotes IP usage and reduces the ability to conserve IPs, such as virtual hosting, for web sites. Companies now have to come up with wasteful uses for IPs that they don't really need, just to qualify for the current policy minimum. 6. ARIN's current policy automatically qualifies a multihome organization to obtain an AS number. There isn't any minimum IP requirement to obtain AS numbers and AS numbers have the direct effect of increasing the global routing table. 7. Regarding the global routing table issue, memory is very inexpensive now, and Cisco is introducing new router models with a larger D-RAM size, that are reasonably priced and affordable by small businesses. 8. Theoretically, there are 4 billion IPv4 addresses available. Out of that, only a small fraction of them (Approx. 100 million) are being used and approx. 2.3 billion are being allocated. This makes the current minimum allocation policy not practical. Large organizations are sitting on an exorbitant amount of IP addresses that they are not using and/or not capable of ever being used. As an example, there is a company that owns approximately 7 million IP addresses and has roughly 153,000 employees (employees as of Nov, 1999). What is the justification for receiving such large IP space, when a small business is not allocated any IP space? ###END### From memsvcs at arin.net Wed Sep 25 15:40:40 2002 From: memsvcs at arin.net (Member Services) Date: Wed, 25 Sep 2002 15:40:40 -0400 (EDT) Subject: ARIN Policy Proposal 2002-8 Message-ID: ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Eugene, Oregon, scheduled for October 30-31, 2002. All feedback received on the mailing list about this policy proposal will be included in the discussions that will take place at the upcoming Public Policy Meeting. This policy proposal discussion will take place on the ARIN Public Policy Mailing List (ppml at arin.net). Subscription information is available at http://www.arin.net/mailing_lists/index.html Richard Jimmerson Director of Operations American Registry for Internet Numbers (ARIN) ### * ### Policy Proposal 2002-8: Privatizing POC Information ARIN's new database allows an organization to designate several points of contact for their organization and resource records. Available types of POCs are Admin, Technical, Abuse, and NOC. If an organization designates several POCs for the management of their organization or resource records in the ARIN database, they are made available via ARIN WHOIS. In order for a point of contact to conduct resource administration for a given resource record in the ARIN database, that POC does have to be associated with the resource record in the ARIN database, and therefore is listed in ARIN WHOIS. It is proposed organizations be able to designate certain points of contact as hidden from ARIN WHOIS, with the exception that, at the minimum, one point of contact be viewable. ### END ### From memsvcs at arin.net Thu Sep 26 09:54:35 2002 From: memsvcs at arin.net (Member Services) Date: Thu, 26 Sep 2002 09:54:35 -0400 (EDT) Subject: [arin-announce] Last Call for Nominations Message-ID: Nominations of candidates to run for open seats on the ARIN Board of Trustees, ARIN Advisory Council, and the ASO AC from the ARIN region will be accepted until 23:59 ET on Monday, September 30, 2002. You can find information concerning these positions and how to submit nominations on the ARIN website at: http://www.arin.net/elections/index.html Please note that members and non-members alike are eligible to submit nominations for the ASO AC seat. You must, however, be a member in good standing to submit a nomination or self-nomination for the ARIN Board and Advisory Council seats. A petition process is available to non-members. The list of candidates for each election will be posted on the ARIN website by October 10, along with bios and a form for submitting statements of support. Please contact memsvcs at arin.net if you have any questions regarding this nomination process. ARIN Member Services