From memsvcs at arin.net Tue Mar 4 10:15:43 2003 From: memsvcs at arin.net (Member Services) Date: Tue, 4 Mar 2003 10:15:43 -0500 (EST) Subject: [arin-announce] ARIN Policy Proposals Message-ID: <200303041515.KAA12686@ops.arin.net> To All Interested Parties: ARIN will hold its next Public Policy Meeting in Memphis, Tennessee on April 7-8, 2003. Meeting and registration details can be found at: http://www.arin.net/ARIN-XI/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 Tue Mar 4 11:35:23 2003 From: memsvcs at arin.net (Member Services) Date: Tue, 4 Mar 2003 11:35:23 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-1: Human Point of Contact Message-ID: <200303041635.LAA26505@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-1: Human Point of Contact 1. Statement of proposed Policy: ARIN shall require each ORG or other body receiving resources from ARIN to register at least one POC which is a human being. ARIN shall amend the registration services agreement to include this requirement and shall further require that each ORG or other body agree to keep such contact up to date within 10 days of any change. Further, at least one human contact shall be viewable, at least as a reference, on each resource record visible in the public WHOIS information. 2. Argument for the proposal and general discussion of the issue. Issue: Automated systems do fail. In a case where the only contact information available to resolve such a failure is the system which has failed, the problem becomes one which cannot be resolved. The ISPs which are most likely to take advantage of the ability to hide behind role accounts are the ones most likely to have issues which require human intervention. Argument in favor: When an automated system fails, it becomes important to be able to reach a human being capable of intervening or contacting an intervenor. It is OK if the POC information (address, phone number, etc.) is a work number, or NOC, or even a switchboard, as long as it is a point of contact which leads to a real person with some ability to close the loop. Problems: I understand the issue of hate mail, threats, and the general difficulty of dealing with irate complainers. However, in any business, there are risks. Being the human lightning rod for these complaints at a large provider is not a lot of fun, but it is a job which must be done. Nobody likes to clean the restroom. 3. Proposed timetable for implementation: Once this proposal is ratified, ARIN should update it's registration services agreement to reflect the new policy within 30 days. Existing ORG and other bodies should receive notification of the change and the requirement to comply during that same period. They should be required to comply within 90 days of the date the notification is sent to the existing ADMIN-C. After that time has elapsed, ARIN staff should be expected to investigate and take further appropriate action on any complaint received about lack of human contact in any resource record. Appropriate action is left to the discretion of the ARIN AC, but should include ARIN staff contacting the hidden human contacts to try and find resolution. From memsvcs at arin.net Tue Mar 4 12:43:18 2003 From: memsvcs at arin.net (Member Services) Date: Tue, 4 Mar 2003 12:43:18 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-2: Network Abuse Message-ID: <200303041743.MAA08404@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-2: Network Abuse Proposal for a world wide IP Range Policy for fighting Network Abuse. 1. All networks should have valid owner name or Company name with a valid mailing address and phone number. Phone number and address doesn't need to be visible through the WHOIS Database, but the Regional Internet Registries [APNIC, ARIN, LACNIC, and RIPE NCC] should have that information. 2. All networks should [regardless of geographical location] provide a valid e-mail contact for network [NOC@] and abuse [Abuse@] contact. Make it standard. 3. Regional Internet Registries [APNIC, ARIN, LACNIC, and RIPE NCC] should set up a simple auto system that would periodically send an auto e-mail every quarter to all networks using their services to check reliability of contact information to help regulate distribution of IP Ranges and network security. Those networks would be responsible to reply back to the system within a set time period to confirm network contact. It could all be done with little or no staffing once set-up. 4. If an IP Range / Network or Dial-Up is found to have invalid contact information, address, phone #, e-mail address etc, Regional Internet Registries [APNIC, ARIN, LACNIC, and RIPE NCC] should try to contact then via e-mail first [which is already being done]. At that time if contact is not established via e-mail and returned Failure/Undeliverable, they should be contacted via phone or mail with the understanding that if they do not reply with in say 30 days their IP range will be terminated and no connections will be allowed in or out of their network until they comply to the terms of service. 5. All large networks and Dial-ups should have some type of security system or team that regulate the network to some level or extent. Whether it's a few people, a team of people or some type of software. Most do but not all. 6. All Network administrators responsible for reviewing network abuse reports sent about their end users, accused of malicious activity should be judge on the level of severity by the reported service used, not the number of access attempts to a network or end user. I say this because I have time and time again got replies back from networks stating, it was only one or two access attempts, we will warn them, regardless of what service they used to try to access, and then that same individual is right back at you. A Sub7 Trojan Horse is not a friendly thing, nor is it a mistake etc. I believe that the service greatly shows their intent, if your venerable it only takes one try regardless of service. If you break down someone's door on their home, it only takes once, the police don't tell the home owner, well he only broke your door down once, we will warn him, let us know if he breaks your door down again. 7. There should be some type of database that all IPS's / Dial-Ups use and could reference to check new users real names to determine whether new subscribers have a past history of network abuse and hacking. This database could be managed and updated, all ISP would add new names of users that we're found to be guilty of or had had their account terminated due to network abuse complaints etc. The dial-up provider could at that time at least be alerted to a possible situation. This would also make it difficult for hackers to jump from ISP to ISP. From memsvcs at arin.net Tue Mar 4 13:07:00 2003 From: memsvcs at arin.net (Member Services) Date: Tue, 4 Mar 2003 13:07:00 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-3: Residential Customer Privacy Message-ID: <200303041807.NAA12423@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-3: Residential Customer Privacy Privacy of Residential Customer Name and Address Information In WHOIS Policy Proposal Statement: ARIN guidelines presently state that privacy of an individual's residential address information may be protected in WHOIS by indicating "Private Residence". This policy proposal is intended to provide additional information privacy through omission of an individual's name from WHOIS, replacing their name with "Private Individual". The proposed policy would amend and modify the existing ARIN guideline, forming a new, permanent policy. Rationale and Justification: With the continued growth and popularity of DSL service, increasing numbers of individuals and small home-based businesses are taking advantage of this technology. Many of these customers require /29 or larger assignments to support small networks. Knowing that WHOIS is a public database, the majority of these customers have a viable concern regarding the publication of their name and address information in WHOIS. It is the responsibility of an ISP to support the needs of their customers, and protect customer privacy whenever possible. This policy specifically addresses the privacy issue on behalf of home/residential customers. The omission of personal name and address information from WHOIS is analogous to residential telephone service. When residential phone service is activated, the individual's name, address and phone number are listed in the telephone directory. The individual may, however, request an "unlisted" number, and their information is omitted from the directory. This policy proposes the "listing" of the IP subnet in WHOIS, but individual name and address information would be "unlisted". It is the responsibility of the ISP to maintain complete and accurate information regarding the customer's name, address, etc. This information would be made available to ARIN (if requested) for audit of netblock utilization in support of future allocations. In these difficult times, home security and privacy is on everyone's mind. As internet users, service providers and overseers, it is our combined responsibility to do whatever is necessary to ensure the safety, and protect the privacy of the internet community at large. From memsvcs at arin.net Wed Mar 5 08:54:51 2003 From: memsvcs at arin.net (Member Services) Date: Wed, 5 Mar 2003 08:54:51 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-4: IPv6 Policy Changes Message-ID: <200303051354.IAA14561@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-4: IPv6 Policy Changes The current IPv6 policies are described in the IPv6 Address Allocation and Assignment Policy document. http://www.arin.net/policy/ipv6_policy.html It is proposed the IPv6 policy document be updated to include the following language and that the changed document be adopted as policy. 5.1.1 [under d) add: Other organizations are defined as any customer of the LIR. No distinction will be made in terms of number of IP addresses required, even if that number is one. 5.8 Allocation for Early Adopters 5.8.1 Waiver of criteria listed in 5.1.1 (d) To promote the allocation of IPv6 space the requirement to make 200 /48 assignments within two years shall be waived for anyone requesting IPv6 space before Dec 31, 2004 or until this policy is amended. In the event that this policy is amended the existing IPv6 space holders shall not be subject to new or waived criteria for a period of 10 years from their initial allocation date. 5.8.2 Waiver of fees a) To promote the allocation of IPv6 space all IPv6 related fees shall be waived until Dec 31, 2006 for anyone requesting and receiving space before Dec 31, 2004. In the even that this policy is amended the existing IPv6 space holders shall under no circumstances be subject to waived or new fees until Dec 31, 2006. b) For billing purposes fees will be due according to normal ARIN billing policies on Jan 1, 2007. All early adopters will have the same billing date regardless of the date they received their allocation. 5.8.3 Micro Allocations a) To promote the allocation and deployment of IPv6 all the criteria in 5.1.1 shall be waived to those requesting a /48 micro allocation before Dec 31, 2004, or until this policy is changed. If this policy is changed, current space holders shall not be subject to any new or waived criteria. b) All fees shall be waived under the same rules listed in 5.8.2. c) Those receiving micro allocations shall not be allowed to make further allocations or assignments out of their /48. It is intended for their internal use only. d) When possible those receiving micro allocations shall return their allocation and receive a new /48 from their upstream provider (a LIR). This is requested in a good faith manner until Jan 1, 2007 at which time all micro allocations granted under these waived criteria must be returned. From memsvcs at arin.net Thu Mar 6 12:06:41 2003 From: memsvcs at arin.net (Member Services) Date: Thu, 6 Mar 2003 12:06:41 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-5: RWhois Server Use Requirements Message-ID: <200303061706.MAA21950@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-5: RWhois Server Use Requirements Background: RWhois was created in part to allow ISP's locally operate and control their own reassignment information. The purpose of placing this data in a RWhois server was two-fold: 1) Allow RIR staff to examine reassignment utilization 2) Allow access to the general public on reassignment information. Many ISPs have opted to use RWhois servers for their reassignment information over sending SWIPs to ARIN. But some of the ISP's who have selected to use RWhois servers for their reassignment information have not kept the servers operational 24x7, contents of the database up to-date, or are restricting access only to ARIN staff. This lack of a uniform set of operations of RWhois servers has resulted in confusion for end-users and ARIN staff. Policy Proposal: Therefore, it is proposed a set of minimal requirements of operating a RWhois server for those ISPs who decide to use RWhois to manage their IP reassignment information be established and enforced. The proposed minimal RWhois requirements are: The RWhois server must be operational 24 hours a day, 7 days a week to both the general public and ARIN staff. The RWhois server must allow public access to reassignment information. The ISP may restrict the number of queries allowed per time interval from a host or subnet to defend against DDOS attacks, remote mirroring attempts, and other nefarious acts. The RWhois server must return reassignment information for the IP address queried. The RWhois server may follow the privacy protections for customers as described in the multi-homed policy. The RWhois server must give customer information as described in the multi-homed policy to ARIN staff. The RWhois server may return results for non-IP queries. The RWhois server must respond to a query with the minimal set of attributes per object as defined by ARIN staff. The RWhois server may include optional attributes per object that are defined by the operator. The RWhois server must return results that are up-to-date on reassignment information. From memsvcs at arin.net Thu Mar 6 12:25:03 2003 From: memsvcs at arin.net (Member Services) Date: Thu, 6 Mar 2003 12:25:03 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-6: Micro-Assignments with Sponsorship Message-ID: <200303061725.MAA25058@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-6: Micro-Assignments with Sponsorship Proposal for Micro-Assignments with Sponsorship from Subscriber Members Organization or individuals not meeting minimum criteria for end-user assignment as specified in ARIN end-user assignment policy may request IP space as end-user directly from ARIN if it has sponsorship of two or more ARIN subscriber members. To be a sponsor an ARIN member must have existing business relationship with the end-user and agree that: 1. It will act as first-level contact regarding IP requests by the end-user to ARIN and verify technical requirements for end-user according to ARIN policies 2. If in the future the business relationship is terminated, the sponsor will notify ARIN no longer then 30 days after such an event 3. In the event that a sponsor becomes aware that any information regarding IP block assigned under this policy is no longer valid, a sponsor must notify ARIN or verify that sponsored organization or individual has already made necessary updates to the information with ARIN. Information changes include all of the following: a. Changes in contact information such as physical address or email address b. Changes to the legal name of sponsored organization or individual c. Changes in the technical requirements that may make original request invalid or impact size of the required IP block End-users requesting IP block under this policy agree to the following: 1. If in the future a request is made to ARIN for additional IP block according to this or any other policy, end-user agrees that if the new request is approved it will renumber into new IP block in 6 months or less and then return the original block received under this policy. An exception is allowed when new IP block is requested under micro-allocation policy for exchange block or other critical infrastructure. 2. When end-user terminates relationship with one or more of its sponsors it must notify ARIN about this and in case there are less than two sponsors left, it must secure sponsorship of another ARIN member in 30 days or less. If the number of sponsors is less than two for period longer then 60 days, an end-user agrees that ARIN has the right to withdraw the assignment. 3. An end user is responsible with providing correct contact information to ARIN and in case of any changes such as change in legal name, physical or email address, it must contact ARIN and update the information. If ARIN becomes aware that information regarding end-user is incorrect it must contact end-user to request an updated information, assistance from sponsors maybe thought in such situations. If ARIN is unable to make proper contact with end user and the information in ARIN records remains incorrect for period of 60 days or more, ARIN has the right to withdraw the assignment. 4. An end-user is responsible with making regular yearly maintenance fee payments according to special micro-assignments schedule to be adapted by ARIN board of trustees. ARIN will provide a renewal invoice to last known mailing address and if the payment is not received 30 days after the due date, ARIN may contact all sponsors to verify correct billing information. In the event that ARIN is unable to make proper contact with end-user or when payment is still not received 90 days after the due date, ARIN has the right to withdraw the assignment. 5. When assignment has been withdrawn end-user agrees to make no further use of the IP block An assignment maybe withdrawn by ARIN if it meats the criteria specified #2, #3 or #4 above or if ARIN becomes aware that any information in the original request for assignment was incorrect and otherwise end-user would not have qualified for the assignment. In such cases: 1. ARIN must provide 30 day written notice to the last known mailing address and to all contact email addresses before withdrawing the assignment. 2. Under special circumstances an end-user may request postponement, which can be no longer then 12 months. All decisions on these requests are to be made by ARIN staff which may ask for assistance of board of advisors. In all circumstances the decisions by ARIN are final and may not be challenged by end-user by legal or any other means. 3. When an assignment is to be withdrawn, ARIN will provide a notice by both email and conventional mail to the sponsors and specify the reason for withdrawing the assignment and the date when it will be withdrawn. 4. When assignment is withdrawn, ARIN will change WHOIS information to specify that assignment is no longer valid and has been withdrawn. The WHOIS data as was last known regarding end-user and the assignment must be maintained for a period of at least 6 months. 5. An IP block assignment which was withdrawn may not be used for new assignments for at least 12 months. All assignments under this policy must be in according with guidelines listed in RFC2050, except where other ARIN policies may take precedence. In particular one of the following is required in order to qualify for the assignment: 1. Multihomed organizations may request a minimum assignment of /24 without any other justification OR 2. Requesters must show exactly how previous address assignments have been utilized and must provide appropriate details to verify their one-year growth projection. The basic criteria that must be met are: * 25% immediate utilization rate, and * 50% utilization rate within one year Before this policy is used a new maintenance fee schedule and other fees that are related to this policy must be adapted by the ARIN Board of Trustees. It is recommended that yearly maintenance fee schedule be scaled with 2-4 additional levels that the scale be in accordance with the size of IP block such that fee for /24 block is about 1/4 of the fee for /21 IP block. An additional one-time setup fee is also recommended to be equivalent to yearly maintenance fee. From memsvcs at arin.net Thu Mar 6 12:32:15 2003 From: memsvcs at arin.net (Member Services) Date: Thu, 6 Mar 2003 12:32:15 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-7: Announcement of New ARIN IPv4 Blocks Message-ID: <200303061732.MAA26419@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-7: Announcement of New ARIN IPv4 Blocks ARIN should make an effort to allocate and assign IP blocks so that allocations and assignments of the same size (such as micro-allocations, small, middle, large IP blocks) are made of the same /8 block as much as possible. In cases of allocations and assignments smaller then current minimum allocation size for ISP subscriber members (so called micro-allocations and micro- assignments), these allocations and assignments should be made from the IP block specifically reserved for micro-allocations and assignments. Minimum size allocations and assignments for each /8 block should be listed on the ARIN website and with additional information about the blocks where micro-allocation and assignments are made. ARIN should request new /8 blocks from IANA at least 6 months in advance of expected need and allow at least 4 months wait period between the time it received the block and first allocation or assignment that is made out of new /8. After IANA has made an assignment ARIN should provide information regarding new IP block and expected minimum allocations and assignments to be made out each /8 block ARIN has received to ARIN announcement mailing lists, network engineering mailing lists as well as send email to technical contacts for all ISP subscriber members and end-users regarding this new IANA assigned block. An additional announcement should be made one month or less prior to first assignment or allocation. If complaints are received by ARIN regarding routability problems with new IP block, ARIN may make additional announcements on mailing lists as needed and all complains received by ARIN regarding operational issues with new IP allocations and assignments should also be forwarded to proper regional mailing list (such as NANOG). When changes are made in the future regarding minimum allocation or assignments from any /8 block, additional announcement must be made at least 30 days prior to first smaller size assignment or allocation. From memsvcs at arin.net Thu Mar 6 12:39:42 2003 From: memsvcs at arin.net (Member Services) Date: Thu, 6 Mar 2003 12:39:42 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-8: End-User to Subscriber Member Status Change Message-ID: <200303061739.MAA27498@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-8: End-User to Subscriber Member Status Change An organization which previously received IP block(s) from ARIN as end-user may change its status and become subscriber member and keep existing IP block(s) as allocation from ARIN under the following conditions and procedures: 1. An organization has changed its business plan and new plans makes it necessary to sub-allocate parts of IP space to organization's customers. 2. ALL ARIN assigned IP blocks have to go through new audit and be justified under ISP initial address space request policy, except that - the organization must be at try to justify IP block allocation equivalent to what it has received as an assignment - If justified allocation size is smaller then current assignment(s), ARIN may require an organization to give up a part of its assignment before it can become a subscriber member - If justified allocation is larger or equal to the current minimum allocation for ISPs but existing assignment(s) were of smaller size, then organization may be allocated by ARIN one larger block equivalent to its requirements, in which case organization has 12 months to renumber and return previously assigned IP block(s) - For the justifications "internal use" as with end-user policies should be permitted but evidence (such as new business plan as in #1) must be shown that at least some IP space will be allocated to other organizations or assigned to end-users. 3. After the change organization may not apply for any additional IP blocks as end-user and must do it as ISP even for IP blocks intended primarily for internal use. 4. Organization maybe required to pay one-time fee to process this assignment->allocation change request and thereafter organization must pay for its IP blocks according to ISP subscriber member fee schedule. From memsvcs at arin.net Thu Mar 6 12:47:15 2003 From: memsvcs at arin.net (Member Services) Date: Thu, 6 Mar 2003 12:47:15 -0500 (EST) Subject: [arin-announce] Policy Proposal 2003-9: WHOIS Acceptable Use Message-ID: <200303061747.MAA28873@ops.arin.net> ARIN welcomes feedback and discussion about the following policy proposal in the weeks leading to the ARIN Public Policy Meeting in Memphis, Tennessee, scheduled for April 7-8, 2003. 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 2003-9: WHOIS Acceptable Use This proposal changes current Bulk WHOIS Acceptable Use Policy to become general WHOIS Acceptable Use policy that would apply to all WHOIS queries. In particular: 1. A new acceptable use policy called "WHOIS Acceptable Use Policy" is to be published on ARIN website as follows: "The ARIN WHOIS Data is for Internet operations and technical research purposes pertaining to Internet Operations only. It may not be used for advertising, direct marketing, marketing research or similar purposes. Use of ARIN WHOIS data for these activities is explicitly forbidden. ARIN requests to be notified of any such activities or suspicions thereof. ARIN reserves the right to restrict access to the WHOIS database in its sole discretion to ensure operational stability. ARIN may restrict or terminate your access to the WHOIS database for failure to abide by these terms of use." 2. Access to WHOIS data with individual queries (such as by using WHOIS protocol) must in the output either include entire 'ARIN WHOIS Acceptable Use Policy' in the comments or provide a one-line statement that data is provided and can only be used according to 'ARIN WHOIS Acceptable Use Policy' with a link to where the policy is published on ARIN website. 3. High frequency individual query access and access to either entire WHOIS database or large portion of it must be provided with authentication to persons and organizations authorized by ARIN. These organizations must sign 'Acceptable Use Policy for Bulk Copies of ARIN WHOIS Data' agreement which shall include 'WHOIS Acceptable Use Policy' and additional statement that "Redistributing bulk ARIN WHOIS Data is explicitly forbidden. It is permissible to publish data on an individual query or small number of queries at a time basis as long as reasonable precautions are taken to prevent automated querying by database harvesters" Organizations that need access to ARIN WHOIS data on regular basis maybe required to resubmit the agreement on monthly basis at which time authentication settings may need to be changed. From memsvcs at arin.net Mon Mar 10 10:43:52 2003 From: memsvcs at arin.net (Member Services) Date: Mon, 10 Mar 2003 10:43:52 -0500 (EST) Subject: [arin-announce] The last day to book hotel rooms for ARIN XI is Friday, March 14th. Message-ID: Time is running out! If you haven't registered for ARIN XI in Memphis, it's time to get involved. For those who have already registered, time is also running very short to book hotel rooms at our host hotel! The Peabody Memphis has a limited number of rooms reserved for our meeting. These rooms are being held until Friday, March 14th, so book now by calling the Peabody Memphis at 1-800-PEABODY. To register for ARIN XI, please visit our website: http://www.arin.net/ARIN-XI/index.html ARIN graciously thanks both NASA and Comcast for sponsoring portions of ARIN XI. As part of their sponsorship, NASA will be supplying the network connectivity, and will also be setting up and managing the wireless network. Comcast will be sponsoring this year's social event at BB King's, and sponsoring the audio-visual requirements in Memphis! We are still accepting sponsorship offers for the terminal room/learning center, as well as the continental breakfasts and lunches during the meeting. For more information about the meeting as well as sponsorship opportunities, contact Edward Pizzarello, ARIN Event Coordinator, at (703) 227-9878 or memsvcs at arin.net. ARIN Member Services From memsvcs at arin.net Tue Mar 18 17:15:24 2003 From: memsvcs at arin.net (Member Services) Date: Tue, 18 Mar 2003 17:15:24 -0500 (EST) Subject: [arin-announce] ARIN XI Meeting Agenda and Registration Message-ID: ARIN XI in Memphis, TN is fast approaching! The expanded agenda has just been posted to the meeting web page. View the agenda and register for the meeting at the following url: http://www.arin.net/ARIN-XI/index.html Our host hotel, The Peabody, has informed us they have a limited amount of rooms still available at the $170 rate for Sunday, April 6th through Wednesday, April 9th. These rooms are available on a first-come, first-served basis. If you still need a room, please call The Peabody directly at 901-529-4000 for reservations. If you have questions regarding ARIN XI, please feel free to contact Edward Pizzarello, ARIN Event Coordinator, at 703-227-9878, or via e-mail at pizza at arin.net. ARIN Member Services =================================================================== email memsvcs at ARIN.NET ftp ftp.arin.net whois whois.arin.net website http://www.arin.net =================================================================== From memsvcs at arin.net Wed Mar 19 10:35:17 2003 From: memsvcs at arin.net (Member Services) Date: Wed, 19 Mar 2003 10:35:17 -0500 (EST) Subject: [arin-announce] Annual Maintenance Fees Message-ID: <200303191535.KAA00770@ops.arin.net> At the ARIN X Public Policy Meeting held in Eugene, Oregon, October 30-31, 2002, a discussion about adjusting maintenance fees was held. There was general agreement amongst the attendees that the maintenance fees needed adjustment. The minutes of the ARIN X Public Policy Meeting are available at http://www.arin.net/policy/pol_min.html. At its January 10, 2003 meeting, the ARIN Board of Trustees discussed the issue of adjusting maintenance fees. It was the sense of the Board that since there was community support at the ARIN Public Policy Meeting to adjust the fees, the Board would adopt the fee change, and it could be further discussed at the ARIN meeting in April in Memphis, TN. The minutes of the ARIN Board of Trustees meeting are available at http://www.arin.net/library/minutes/bot/bot2003_0110.html. Beginning July 1, 2003, the annual maintenance fee will be $100. In cases where a single organization has more than one registration record in the ARIN database that is normally charged annual maintenance fees, only a single consolidated maintenance fee of $100 will be invoiced. Member Services American Registry for Internet Numbers (ARIN) From memsvcs at arin.net Thu Mar 20 15:08:04 2003 From: memsvcs at arin.net (Member Services) Date: Thu, 20 Mar 2003 15:08:04 -0500 (EST) Subject: [arin-announce] Advisory Council Appointment Message-ID: On March 18, 2003, the Board of Trustees confirmed the Advisory Council's appointment of Andrew Dul to a seat on the Council. Andrew will fill the vacant seat created by Tanya Hinman's recent resignation. The appointment is for the remainder of the year. Raymond A. Plzak President & CEO American Registry for Internet Numbers (ARIN) From memsvcs at arin.net Tue Mar 25 15:09:12 2003 From: memsvcs at arin.net (Member Services) Date: Tue, 25 Mar 2003 15:09:12 -0500 (EST) Subject: [arin-announce] Be a Part of ARIN XI, April 6-9 in Memphis Message-ID: There is still time to make plans to attend ARIN's Public Policy and Members meeting at the Peabody Hotel in Memphis, Tennessee beginning Sunday afternoon, April 6. Remember, all ARIN member organizations may send two representatives at no cost. Links to the agenda, registration and hotel information can be found at: http://www.arin.net/ARIN-XI/index.html With over a dozen policy proposals on the agenda, there is certain to be at least one issue discussed that could impact your business. If you can't make it to Memphis, use the public policy mailing list, ppml at arin.net, to register your opinion concerning any of the proposals. You can subscribe to this public list at: http://ww1.arin.net/mailing_lists/index.html We look forward to seeing many of you in April. ARIN Member Services =================================================================== email memsvcs at ARIN.NET ftp ftp.arin.net whois whois.arin.net website http://www.arin.net =================================================================== From memsvcs at arin.net Wed Mar 26 16:13:23 2003 From: memsvcs at arin.net (Member Services) Date: Wed, 26 Mar 2003 16:13:23 -0500 (EST) Subject: [arin-announce] ARIN Web-based Templates Available Message-ID: Web-based versions of the ISP Network Request and AS Number Request templates are now available. Links to these two new templates are available at http://www.arin.net/library/index.html. Using the web-based templates: --Enter all registration and justification information in the appropriate data fields --Provide your e-mail address when prompted --Hit submit button --Conduct final review of template when it is e-mailed back to you --To complete the request process, an authoritative POC must send the template to hostmaster at arin.net Please contact the Registration Services Help Desk if you have any questions, or if you experience any difficulty in completing or submitting the templates. Registration Services Department American Registry for Internet Numbers From memsvcs at arin.net Wed Mar 26 16:25:25 2003 From: memsvcs at arin.net (Member Services) Date: Wed, 26 Mar 2003 16:25:25 -0500 (EST) Subject: [arin-announce] Opening Mailing List to the Public Message-ID: Beginning March 28, 2003, the ARIN Announce Mailing List (arin-announce at arin.net) will be open to the general public. Any interested person may join ARIN Announce and receive e-mails. However, only ARIN staff can broadcast information to this List. All announcements relating to ARIN meetings, elections, and activities will be made through ARIN Announce and may be posted on the website. We will continue to send notification of policy discussions to both ARIN Announce and the Public Policy Mailing List (ppml at arin.net), where all policy discussions take place. In opening ARIN Announce to the public, duplicate announcements concerning events and elections will no longer be sent to the PPML. Anyone interested in information about ARIN events should join arin-announce at arin.net. Subscription instructions are available at: http://www.arin.net/mailing_lists/index.html Member Services Department American Registry for Internet Numbers(ARIN)