From richardj at arin.net Fri Jan 7 15:52:37 2000 From: richardj at arin.net (Richard Jimmerson) Date: Fri, 7 Jan 2000 15:52:37 -0500 Subject: ARIN Routing Registry Message-ID: <000b01bf5951$21bbebd0$bdfc95c0@ARINNET> The ARIN Routing Registry server, rr.arin.net, now includes daily RPSL data snapshots derived from the data location information that the following routing registries placed in the www.radb.net/list.html URL: Registry Name (Source): bell.db IP address or DNS name: 205.207.237.50 Ftp site: ftp://205.207.237.50/bell/bell.db Type of DB (RIPE181, RPSL?): RPSL Registry Name (Source): RIPE IP address or DNS name: rpslii.ripe.net Ftp site: ftp.ripe.net Type of DB (RIPE181, RPSL?): RPSL Registry Name (Source): LEVEL3 IP address or DNS name: rr.Level3.net Ftp site: ftp://rr.Level3.net/pub/rr/level3.db.gz Type of DB (RIPE181, RPSL?): RPSL Registry Name (Source): RADB IP address or DNS name: whois.radb.net Ftp site: ftp://ftp.radb.net/radb/dbase Type of DB (RIPE181, RPSL?): RPSL Registry Name (Source): VERIO IP address or DNS name: rr.verio.net Ftp site: ftp://rr1.verio.net/verioRR/ Type of DB (RIPE181, RPSL?): RPSL Registry Name (Source): BCONNEX IP address or DNS name: radb.bconnex.ca Ftp site: ftp.bconnex.net://pub/radb/bconnex.db.gz Type of DB (RIPE181, RPSL?): RPSL Registry Name (Source): KOREN IP address or DNS name: whois.koren21.net Ftp site: ftp://ftp.koren21.net/pub/radb Type of DB (RIPE181, RPSL?): RPSL Registry Name (Source): ARCSTAR IP address or DNS name: rr.ntt.net Ftp site: ftp://rr.ntt.net/arcstarRR/ Type of DB (RIPE181, RPSL?): RPSL Please e-mail rtreg at arin.net if your organization would like to contribute a snapshot of its RPSL data to include on rr.arin.net. ARIN will send its next update to this group when rr.arin.net has been configured to mirror off port 43. Please send any other questions or concerns to rtreg at arin.net. Regards, Routing Registry Registration Services Group American Registry for Internet Numbers (ARIN) ========================================================= email rtreg at arin.net ftp ftp.arin.net whois rr.arin.net web http://www.arin.net/rr.htm ========================================================= From richardj at arin.net Fri Jan 21 16:23:08 2000 From: richardj at arin.net (Richard Jimmerson) Date: Fri, 21 Jan 2000 16:23:08 -0500 Subject: FW: Call for Comments Message-ID: <001a01bf6455$b70d6790$bdfc95c0@ARINNET> This is a reminder of the call for comments sent to this list on December 14, 1999. Today ends the period for comments. | Discussion of revising this document will be held on the | IP Allocation Policies Working Group (policy at arin.net) | mailing list. If you would like to participate in this | discussion, please do so on the IP Allocation Policies | Working Group mailing list (policy at arin.net). ARIN welcomes any additional comments on this subject. Please send your comments to the IP Allocation Policies Working Group (policy at arin.net) mailing list. Thank you for your participation. Best Regards, Richard Jimmerson American Registry for Internet Numbers (ARIN) | -----Original Message----- | From: Richard Jimmerson [mailto:richardj at arin.net] | Sent: Tuesday, December 14, 1999 4:40 PM | To: 'arin-announce at arin.net' | Subject: Call for Comments | | | The RIRs are requesting comments on the Provisional IPv6 | Assignment and Allocation Policy Document, the global | guideline for allocating IPv6 addresses. Working closely with | the IPv6 community, this policy document was developed | jointly by ARIN, APNIC, and RIPE NCC, and was submitted to | IANA on May 28, 1999. With some additions, it was approved on | July 14, 1999. Shortly thereafter, IANA made the first formal | delegations of IPv6 address space to the RIRs for their | allocation to qualified organizations. | | Provision was made for a formal revision of the document | after an initial period of operational and administrative | experience. Now that the document has been posted for several | months, and organizations have received sub-TLA allocations, | comments from the community would be helpful in making | insightful revisions. | | The document can be found at the following location: | | http://www.arin.net/regserv/ipv6/IPv6.txt | | While comments are welcome on any subject in the document, | several topics are of particular interest: | | * A definition of "transit provider" | | * Input for sections 4.2.3.2 Multihomed Sites, 2.1.4 NLA | Registries, and 2.1.5 End-sites | | * Revising sections 4.2.8 Allocations to NLA Registries and 4.3.1 | Assignments to End-users | | * Adding sections entitled Guidelines for Allocations to NLAs, | and Guidelines for Assignments to SLAs to aid in providing NLA | and SLA reassignments. | | Discussion of revising this document will be held on the | IP Allocation Policies Working Group (policy at arin.net) | mailing list. If you would like to participate in this | discussion, please do so on the IP Allocation Policies | Working Group mailing list (policy at arin.net). | | If you are not currently subscribed to the above mentioned | mailing list, please visit the following URL and follow the | subscription instructions. | | http://www.arin.net/members/mailing.htm | | The period for comment will end on January 21, 2000. | | Best Regards, | | Richard Jimmerson | American Registry for Internet Numbers (ARIN) | From kimh at arin.net Mon Jan 31 16:35:36 2000 From: kimh at arin.net (Kim Hubbard) Date: Mon, 31 Jan 2000 16:35:36 -0500 Subject: RIR Global Policy Recommendation Message-ID: <4.1.20000131162848.00b936f0@192.149.252.141> Below is a global policy recommention submitted by the RIRs to the ASO AC. Discussion is currently taking place on the ASO policy mailing list. If you have comments on this document or just agree or disagree with it, please let us hear from you. Please sign onto aso-policy at aso.icann.org and send in your comments. Thanks, Kim Hubbard ARIN Proposal for a Global Policy Defining the Delegation of Addresses by the ICANN Purpose The purpose of this proposal is to recommend that the global policy found herein, which clarifies the role of the ICANN in delegating IP addresses, be adopted by the organizations within the Internet registry system. This policy defines the role of the recognized RIRs as having sole responsibility for making all IP allocations, and that of the ICANN as distributing IP addresses only to the RIRs and to no other organizations. It is requested herein that the Address Council within the ASO recommend to the ICANN Board adoption of this matter. Introduction Under the past and current policies and practices of the RIRs and the overall Internet registry system, the RIRs are solely responsible for allocating and assigning IP addresses to requesting organizations that qualify to receive them. This is their primary function and reason for operation. The ICANN is responsible for coordination of all IP address space with the designated RIRs and has been recognized in the past by the RIRs as the authority for IP address numbers and ASNs. ICANN is responsible then for delegating IP addresses to the RIRs for their further allocation to customer organizations, based solely on demonstrated need - a necessary restriction since the amount of available IP numbers is limited. As RIRs need additional blocks of addresses, they request space from the ICANN in order to continue allocating IP numbers to qualified organizations, i.e., those that satisfy the justification and/or utilization requirements. IP requests can come from various organizations, and in different forms according to regional policy. It is the responsibility of the RIRs to ensure that the requesting entity demonstrate a justified need for the IP addresses in accordance with global and local policies. Proposed Global Policy There are three global policies presented herein that are proposed for adoption, as identified below. (1) The ICANN distributes address space only to a recognized RIR and does not make allocations or assignments directly to any other organization. (2) If ICANN, or its affiliates or subordinate entities, is in need of address space for its own use, a request will be made to the RIR responsible for the region wherein the ICANN (or the requesting entity) resides. Appropriate criteria, according to established guidelines, must be met in order to receive an allocation. (3) If ICANN receives a request directly from another organization, the requesting entity will be referred to the appropriate RIR. The ICANN and its subordinate entities are designed to operate in an open and ransparent manner consistent with procedures developed to ensure fairness. In this spirit, it is in the public's best interest for the ICANN and the RIRs to treat every organization (including themselves) equally. It thus is appropriate for all entities, including the ICANN, to formally submit a request for address space when needed for its own purposes, to the appropriate RIR, and to follow the justification requirements that all other organizations must follow. This ensures that the limited amount of IP address space, an important public resource, is distributed fairly to all those in need of its use. Conclusion It is important that all organizations requesting IP address space be held to applicable guidelines and procedures equally and fairly. It is how the registry system works. To do otherwise could be perceived by the industry as a loosely wheeled system having no accountability.