Network Working Group Z. Wenzel
Request for Comments: 2901 J. Klensin
FYI: 37 R. Bush
Category: Informational S. Huter
Network Startup Resource Center
August 2000
Network Working Group Z. Wenzel
Request for Comments: 2901 J. Klensin
FYI: 37 R. Bush
Category: Informational S. Huter
Network Startup Resource Center
August 2000
Guide to Administrative Procedures of the Internet Infrastructure
互联网基础设施管理程序指南
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
This document describes the administrative procedures for networks seeking to connect to the global Internet. This includes the steps and operations necessary for address space allocation and registration, routing database registration, and domain name registration. The document also contains information about the required forms and how to obtain them.
本文档描述了寻求连接到全球互联网的网络的管理程序。这包括地址空间分配和注册、路由数据库注册和域名注册所需的步骤和操作。该文件还包含有关所需表格以及如何获取表格的信息。
Table of Contents
目录
Who Should Read This Document ................................... 2
Checklist ....................................................... 3
Prerequisites ................................................... 3
I. Preparation of Systems and Network Planning ............... 4
A. What do I need to connect to the Internet? .......... 4
B. What connectivity medium should I choose? ........... 4
C. What else do I need to do? .......................... 4
D. How do I get the documents referred to in this guide? 6
E. Section References .................................. 6
II. Address Space Allocation .................................. 7
A. Who is my upstream provider? ........................ 7
B. How much address space should I ask for? ............ 8
C. What is CIDR? ....................................... 9
D. How do I request and register address space? ........ 10
E. Section References .................................. 13
Who Should Read This Document ................................... 2
Checklist ....................................................... 3
Prerequisites ................................................... 3
I. Preparation of Systems and Network Planning ............... 4
A. What do I need to connect to the Internet? .......... 4
B. What connectivity medium should I choose? ........... 4
C. What else do I need to do? .......................... 4
D. How do I get the documents referred to in this guide? 6
E. Section References .................................. 6
II. Address Space Allocation .................................. 7
A. Who is my upstream provider? ........................ 7
B. How much address space should I ask for? ............ 8
C. What is CIDR? ....................................... 9
D. How do I request and register address space? ........ 10
E. Section References .................................. 13
III. Autonomous Systems (AS) ................................... 13
A. What is an ASN and do I need one? ................... 13
B. How do I register an ASN? ........................... 14
C. Section References .................................. 15
IV. Routing and Exchange Points ............................... 15
A. Do I need to register with a routing database? ...... 15
B. What about CIDR and routing? ........................ 16
C. How do I choose a routing database? ................. 16
D. How do I register in the RADB (The Americas)? ....... 17
E. Section References .................................. 18
V. Domain Name Registration .................................. 18
A. What is a country domain? ........................... 18
B. How do I register as a country domain? .............. 18
C. What if my country is already registered? ........... 19
D. How do I resolve a country domain name dispute? ..... 19
E. Section References .................................. 19
VI. IN-ADDR.ARPA Domain Delegation ............................ 19
A. What is an IN-ADDR.ARPA domain and do I need one? ... 20
B. How do I register an IN-ADDR.ARPA domain? ........... 20
VII. Security .................................................. 21
A. Is there a way to prevent unauthorized changes to my
objects? ................................................ 21
VIII. Network Optimization and Management ....................... 22
A. How do I optimize traffic on my network? ............ 22
Security Considerations ......................................... 22
Acknowledgements ................................................ 22
References ...................................................... 22
Authors' Addresses .............................................. 24
Appendix A: The Internet Agencies .............................. 25
Appendix B: Documentation ...................................... 28
Appendix C: Country Codes ...................................... 29
Appendix D: Acronyms ........................................... 30
Full Copyright Statement ........................................ 31
III. Autonomous Systems (AS) ................................... 13
A. What is an ASN and do I need one? ................... 13
B. How do I register an ASN? ........................... 14
C. Section References .................................. 15
IV. Routing and Exchange Points ............................... 15
A. Do I need to register with a routing database? ...... 15
B. What about CIDR and routing? ........................ 16
C. How do I choose a routing database? ................. 16
D. How do I register in the RADB (The Americas)? ....... 17
E. Section References .................................. 18
V. Domain Name Registration .................................. 18
A. What is a country domain? ........................... 18
B. How do I register as a country domain? .............. 18
C. What if my country is already registered? ........... 19
D. How do I resolve a country domain name dispute? ..... 19
E. Section References .................................. 19
VI. IN-ADDR.ARPA Domain Delegation ............................ 19
A. What is an IN-ADDR.ARPA domain and do I need one? ... 20
B. How do I register an IN-ADDR.ARPA domain? ........... 20
VII. Security .................................................. 21
A. Is there a way to prevent unauthorized changes to my
objects? ................................................ 21
VIII. Network Optimization and Management ....................... 22
A. How do I optimize traffic on my network? ............ 22
Security Considerations ......................................... 22
Acknowledgements ................................................ 22
References ...................................................... 22
Authors' Addresses .............................................. 24
Appendix A: The Internet Agencies .............................. 25
Appendix B: Documentation ...................................... 28
Appendix C: Country Codes ...................................... 29
Appendix D: Acronyms ........................................... 30
Full Copyright Statement ........................................ 31
Who Should Read This Document
谁应该阅读这份文件
This document is intended for system engineers and technical managers of networks who want to make a connection to the Internet. It assumes a basic knowledge of the Internet and networking.
本文档适用于希望连接到Internet的系统工程师和网络技术经理。它假定具备互联网和网络的基本知识。
This information is intended to help new or expanding networks understand and follow the Internet administrative procedures, and to provide assistance in filling out the various templates and registration forms. Appendix D is a glossary of acronyms.
这些信息旨在帮助新的或正在扩大的网络了解和遵守互联网管理程序，并在填写各种模板和登记表方面提供帮助。附录D是首字母缩略词词汇表。
Checklist
清单
This document will explain the following procedures:
本文件将解释以下程序：
o Determine your organization type and current status. o Determine your administrative and technical contacts. o Determine your budget (and chargeback system) and choice of carriers. o Determine to whom you will connect. o Predict your current and projected address space needs. o Set-up your system to connect. o Request and register your address space allocation. o Request and register an autonomous system number, if needed. o Register with a routing database, if needed. o Register your country's domain name, if needed. o Request and register your IN-ADDR.ARPA domain name, if needed.
o 确定您的组织类型和当前状态。o确定您的管理和技术联系人。o确定您的预算（和退单系统）和运营商的选择。o确定您将连接到谁。o预测您当前和预计的地址空间需求。o将系统设置为连接。o请求并注册您的地址空间分配。o如果需要，请求并注册自主系统编号。o如果需要，向路由数据库注册。o如果需要，注册您所在国家的域名。o如果需要，请求并注册您的IN-ADDR.ARPA域名。
Prerequisites
先决条件
This document assumes that you have examined different alternatives for physical connectivity and will assist you in navigating the Internet infrastructure so that you can use that connectivity. In choosing your upstream provider, you should consider their ability to deal with the Internet infrastructure.
本文档假设您已经研究了物理连接的不同备选方案，并将帮助您导航Internet基础设施，以便您可以使用该连接。在选择上游供应商时，你应该考虑他们处理互联网基础设施的能力。
What will you be doing and what role will you play?
你将要做什么？你将扮演什么角色？
o If you are interested in connecting yourself (or a small organization), you are an Internet end user. You will probably want to contact an Internet Service Provider (ISP) for most of your needs. Read section I and the first part of section II.
o 如果您对连接自己（或小型组织）感兴趣，那么您就是Internet最终用户。您可能需要联系Internet服务提供商（ISP）以满足大部分需求。阅读第一节和第二节第一部分。
o If you are interested in connecting your organization and in having address space to distribute within your network, you are an Internet high volume end user. You will need more address space, but still may chose to work with an Internet Service Provider (ISP) for most of your needs. Read sections I and II.
o 如果您对连接您的组织和在网络中分配地址空间感兴趣，那么您就是Internet高容量最终用户。您将需要更多的地址空间，但仍然可以选择与Internet服务提供商（ISP）合作来满足您的大部分需求。阅读第一节和第二节。
o If you are interested in connecting your organization, and in distributing addresses to your clients (who are end users), you are an Internet Service Provider (ISP). You will need to contact a Local Internet Registry (if one is available, or your upstream provider). Read section I and continue reading the rest of this document.
o 如果您有兴趣连接您的组织，并向您的客户（最终用户）分发地址，则您是Internet服务提供商（ISP）。您需要联系当地的Internet注册中心（如果有，或您的上游提供商）。阅读第一节，继续阅读本文件的其余部分。
o If you are interested in distributing addresses to your clients and your clients are in turn distributing addresses, you are a Local Internet Registry or large ISP. You will probably need to contact the Regional Internet Registry in your geographical area. Read section I and continue reading the rest of this document.
o 如果您有兴趣向您的客户分发地址，而您的客户又在分发地址，那么您就是本地Internet注册中心或大型ISP。您可能需要联系您所在地理区域的区域互联网注册中心。阅读第一节，继续阅读本文件的其余部分。
I. Preparation of Systems and Network Planning
一、系统准备和网络规划
STEP ONE: PREPARE INFORMATION, ORGANIZE HARDWARE, FIGURE OUT TO WHOM YOU WILL CONNECT, AND TEST IN-COUNTRY SYSTEMS.
第一步：准备信息、组织硬件、确定要连接到谁，并测试国内系统。
A. What do I need to connect to the Internet?
A.连接到Internet需要什么？
You can connect using dial-up or dedicated lines, and you can choose UUCP or IP. It is preferable to be running the UNIX operating system with TCP/IP over a dedicated line, although you can begin by using UUCP over a dial-up line. Although there are alternatives to UNIX, for historical reasons and robustness UNIX is better prepared to handle Internet connectivity. It is best to use TCP/IP inside your network even if you use another method for your external connectivity.
您可以使用拨号或专用线路连接，也可以选择UUCP或IP。最好通过专用线路运行带有TCP/IP的UNIX操作系统，尽管可以通过拨号线路使用UUCP开始。尽管有UNIX的替代品，但由于历史原因和健壮性，UNIX更好地准备处理Internet连接。最好在网络内部使用TCP/IP，即使您使用其他方法进行外部连接。
You will need to obtain an Internet Protocol (IP) address, or block of addresses, and a domain name. You may also need an Autonomous System Number (ASN) and an IN-ADDR.ARPA (reverse addressing) domain name. However, you may begin by having dial-up connectivity to another organization that supports one or more mail exchange (MX) record(s) for your site. This would allow you to receive email at your own domain name without requiring you to invest as much initially.
您需要获取一个Internet协议（IP）地址或地址块以及域名。您可能还需要一个自治系统号（ASN）和一个IN-ADDR.ARPA（反向寻址）域名。但是，您可以先与支持站点的一个或多个邮件交换（MX）记录的其他组织建立拨号连接。这将允许您在自己的域名上接收电子邮件，而不需要您最初投入那么多资金。
B. What connectivity medium should I choose?
B.我应该选择什么连接介质？
You may be constrained by telecommunications regulations in your country as to your choice of dial-up, digital phone lines, fiber optic cable, or satellite suppliers. If not, cost, bandwidth, and reliability will determine your choice.
在选择拨号、数字电话线、光纤电缆或卫星供应商方面，您可能受到所在国家电信法规的限制。否则，成本、带宽和可靠性将决定您的选择。
C. What else do I need to do?
我还需要做什么？
Before you do anything else:
在做任何其他事情之前：
1. Designate an administrative contact person and a technical contact person.
1. 指定一名行政联系人和一名技术联系人。
Choose one person to be the administrative contact and another person to be the technical contact. Write down their full names, email and postal addresses, and telephone and fax numbers (with country
选择一个人作为行政联系人，另一个人作为技术联系人。写下他们的全名、电子邮件和邮政地址以及电话和传真号码（注明国家/地区）
prefixes in the form + country code (e.g., +011), city code, and local telephone number). The administrative contact should be a member of your organization and must reside in the country. The technical contact should be the key network support person and may be represented initially by someone outside of the country. Note that the technical contact must transition to a network support person residing in the country. The Internet Registries will request this information in the form of database entries called objects. For example, on the RIPE template, the administrative contact should be listed in the admin-c field in the database objects, and the technical contact in the tech-c field in the database objects (more information on database objects follows in section II D below).
前缀形式为+国家代码（例如，+011）、城市代码和本地电话号码）。行政联系人应该是您组织的成员，并且必须居住在您所在的国家/地区。技术联系人应为关键网络支持人员，最初可由境外人员代表。请注意，技术联系人必须过渡到居住在该国的网络支持人员。互联网注册处将以称为对象的数据库条目的形式请求这些信息。例如，在RIME模板上，管理联系人应列在数据库对象的admin-c字段中，技术联系人列在数据库对象的tech-c字段中（关于数据库对象的更多信息见下文第II D节）。
2. Determine your cost-recovery charging scheme, if needed, so that you can sustain operations.
2. 如果需要，确定您的成本回收收费方案，以便您能够维持运营。
No form or record will specifically request this, but it is important that you project your costs adequately so that you can assess fees to cover them and ensure stability of operations.
没有任何表格或记录会特别要求这样做，但重要的是，您必须充分预测您的成本，以便您能够评估费用以涵盖这些成本，并确保运营的稳定性。
3. Diagram your network topology.
3. 绘制网络拓扑图。
Determine the number of groups and end users. Describe the size and shape of your current network. Design your addressing plan based on this information. It may be helpful to consider your organization chart when doing this, if you anticipate it to be fairly stable.
确定组和最终用户的数量。描述您当前网络的大小和形状。根据这些信息设计您的寻址计划。如果你认为你的组织结构图是相当稳定的，那么在考虑这一点时可能会有所帮助。
If you are restricted to using the local telecommunications company's telephone circuit, choose your circuit carrier based on capacity and where it lands geographically. Consider an asymmetric circuit, e.g., 128kbps in and 64kbps out, if you expect to have more incoming traffic than outgoing (e.g., if most of the traffic is expected to originate from web servers outside your network).
如果您被限制使用当地电信公司的电话线路，请根据容量及其地理位置选择线路载波。考虑一个不对称的电路，例如，128kbps和64 kbps的输出，如果您期望的输入流量比传出的要多（例如，如果大多数流量来自于您的网络之外的Web服务器）。
4. Determine to whom you will connect.
4. 确定您将连接到谁。
See the prerequisites section for types of connection providers that might be appropriate for your situation. Determine which ISP or telecommunications company best fits your connectivity needs.
有关可能适合您的情况的连接提供程序类型，请参阅“先决条件”部分。确定哪家ISP或电信公司最适合您的连接需求。
5. Predict your address space and bandwidth requirements from end user needs.
5. 根据最终用户需求预测您的地址空间和带宽需求。
Since address space is finite and must be conserved, end users are not permitted to reserve address space. Address space is based on what your needs are and how you justify those needs. Evaluation of IP address space requests is usually based on the documentation you provide for the following 24 months (as per RFC 2050), as specified
由于地址空间是有限的，必须保存，因此不允许最终用户保留地址空间。地址空间基于您的需求以及您如何证明这些需求。IP地址空间请求的评估通常基于以下24个月（根据RFC 2050）提供的文件，如规定
in the address space usage template and in the addressing plan you submit. Once you have used your assigned address space, you can request additional space based on an updated estimate of growth in your network. This usually includes detailed documentation, updating the appropriate regional registry database with details of your end user assignments, and assigning address space both conservatively and efficiently.
在地址空间使用模板和您提交的地址计划中。使用分配的地址空间后，您可以根据网络增长的最新估计请求额外空间。这通常包括详细的文档、使用最终用户分配的详细信息更新相应的区域注册表数据库，以及保守而高效地分配地址空间。
You will need to justify your needs for address space by communicating your network design and should be prepared to clearly present your plan for effective use of the request. Determine your current and future user needs. If you are offering virtual web services, it is no longer necessary to assign one IP address per domain. HTTP/1.1 defines the "host" header to allow vanity names without the use of an IP address. Allocations for points of presence (POP) throughout your region should also be determined. Predictions of user behavior can be based on analysis of published rates, interviews with individual and institutional subscribers, and case histories of other countries (see "History of the Internet in Thailand"). For example,
您需要通过沟通您的网络设计来证明您对地址空间的需求，并且应该准备清楚地展示您的计划，以便有效地使用请求。确定您当前和未来的用户需求。如果您提供虚拟web服务，则不再需要为每个域分配一个IP地址。HTTP/1.1定义了“主机”头，允许在不使用IP地址的情况下使用虚拟名称。还应确定您所在区域内存在点（POP）的分配。对用户行为的预测可以基于对公布费率的分析、对个人和机构订户的访谈以及其他国家的案例（见“泰国互联网历史”）。例如
Area1 10 dialup modems 10 leased lines to organization's LANs (size of the LANs) Area2 5 dialup modems Main POP 5 servers: mail, WWW, DNS, FTP, etc.
区域1 10拨号调制解调器10到组织局域网的租用线路（局域网的大小）区域2 5拨号调制解调器主要POP 5服务器：邮件、WWW、DNS、FTP等。
When you design your plan, you should design it for what you need now, what you believe you will need six months from now, and then one year and two years from now.
当你设计你的计划时，你应该为你现在需要的，你认为六个月后需要的，以及一年两年后需要的而设计。
6. Set up, connect, and test your hardware and software.
6. 设置、连接和测试您的硬件和软件。
It is important to ensure that you have enough representative systems set up and their connectivity tested using temporary addresses before contacting the appropriate agency for address space.
在联系适当的机构获取地址空间之前，务必确保已设置足够多的代表性系统，并使用临时地址测试其连接性。
D. How do I get the documents referred to in this guide?
D.如何获取本指南中提及的文件？
See Appendix B for details on obtaining the documents referred to in this guide.
有关获取本指南中提及的文件的详细信息，请参见附录B。
E. Section References
E.章节参考资料
For more information on TCP/IP, see RFC 2151, "A Primer on Internet and TCP/IP Tools and Utilities".
有关TCP/IP的更多信息，请参阅RFC 2151，“Internet和TCP/IP工具和实用程序入门”。
II. Address Space Allocation
二,。地址空间分配
STEP TWO: OBTAIN ADDRESS SPACE ALLOCATION AND REGISTRATION FROM THE ISP YOU ARE CONNECTING TO, OR (AS A LAST RESORT) YOUR REGIONAL REGISTRY.
第二步：从您连接的ISP或（作为最后手段）您的区域注册中心获得地址空间分配和注册。
Internet Protocol (IP) addresses (under the current version 4) are 32-bit numbers usually expressed as 4 octets in dotted decimal notation (for example, 128.223.162.27, which is the IP address for the Network Startup Resource Center (NSRC) web server at the time of this writing). Public IP addresses make up the Internet address space. Addresses are allocated in a hierarchical manner and are designed to be unique.
Internet协议（IP）地址（在当前版本4下）是32位数字，通常用点十进制表示法表示为4个八位字节（例如，128.223.162.27，这是撰写本文时网络启动资源中心（NSRC）web服务器的IP地址）。公共IP地址构成了Internet地址空间。地址以分层方式分配，并设计为唯一。
The Internet Assigned Numbers Authority (IANA) allocates large address blocks to the three current Regional Internet Registries (IRs): ARIN, APNIC, and RIPE NCC which, in turn, allocate smaller blocks to Local Internet Registries or large ISPs. Local Internet Registries, which are typically ISPs or collections of ISPs represented at a country level, and large ISPs process the vast majority of address space assignments to ISPs and end users
互联网分配号码管理局（IANA）将较大的地址块分配给三个当前的区域互联网注册中心（IRs）：ARIN、APNIC和NCC，而这三个注册中心又将较小的地址块分配给本地互联网注册中心或大型ISP。本地互联网注册中心（通常是国家一级的ISP或ISP集合）和大型ISP处理绝大多数分配给ISP和最终用户的地址空间
Contact the Internet service provider from whom you are getting your connectivity services (your upstream provider) with an address allocation request. It is important and required that you contact your upstream provider first, and not the Regional IR automatically. The first question the Regional Registry will ask you is why you cannot get address space from your upstream provider.
通过地址分配请求，联系您获得连接服务的Internet服务提供商（您的上游提供商）。您必须首先联系上游供应商，而不是自动联系区域IR。区域注册中心会问您的第一个问题是，为什么您无法从上游提供商处获得地址空间。
A. Who is my upstream provider?
谁是我的上游供应商？
If there is an ISP already functioning in your country, contact them directly. If you are to be the first connection in your country, you may need to contact your Regional IR in your geographic region, but you should always contact your upstream provider first for assistance and guidance. Since address allocation is hierarchical, the administrative organizations and procedures also represent this hierarchical structure. It is important not to skip a step in the hierarchy. Current Regional Registries include ARIN (the Americas, Caribbean, and Africa), RIPE (Europe, Africa, and the Middle East), and APNIC (the Pacific Rim and Asia). Contact information for these organizations is listed in Appendix A.
如果您所在的国家已经有ISP，请直接与他们联系。如果您要成为您所在国家的第一个连接，您可能需要联系您所在地理区域的区域IR，但您应该始终首先联系您的上游供应商以获得帮助和指导。由于地址分配是分层的，所以管理组织和程序也代表这种分层结构。不要跳过层次结构中的一个步骤，这一点很重要。目前的区域注册包括ARIN（美洲、加勒比和非洲）、RIME（欧洲、非洲和中东）和APNIC（环太平洋和亚洲）。附录A中列出了这些组织的联系信息。
You should contact your Regional Internet Registry if 1) the ISP you are connecting to is unable or unwilling to provide address space, or 2) your particular connectivity requirements will result in non-local data to your customers possibly taking a different route over the Internet than data destined for your upstream provider's customers,
如果1）您所连接的ISP无法或不愿意提供地址空间，或者2）您的特殊连接要求将导致非本地数据发送给您的客户，可能会在Internet上采用与发送给上游提供商客户的数据不同的路由，则您应联系您的区域Internet注册中心，
or 3) you anticipate a quick growth rate that may require changing your current upstream provider to a larger one and you wish to avoid the renumbering that such a move would require.
或者3）您预计增长速度很快，可能需要将您当前的上游供应商更换为更大的供应商，并且您希望避免这样做所需的重新编号。
B. How much address space should I ask for?
我需要多少地址空间？
Regional IRs typically assign address blocks on the basis of an immediate need and projected utilization rate within one year. (If you are in the ARIN region, it is one year for end user organizations and three months for ISPs.) Calculate your address space request accordingly. It is recommended to include the organization chart and network topology diagram referred to in section I.C, number 3 (above). Note that address space is allocated based on CIDR bit boundaries (see next section). The registries will need to understand your network engineering and deployment plans in significant detail before they can allocate address space. Therefore, the more detailed information you can provide, the more likely your request will be processed quickly.
区域IRs通常根据即时需求和一年内的预计利用率分配地址块。（如果您在ARIN地区，最终用户组织为一年，ISP为三个月。）相应地计算您的地址空间请求。建议包括第I.C节第3号（上文）中提到的组织结构图和网络拓扑图。请注意，地址空间是根据CIDR位边界分配的（请参阅下一节）。在分配地址空间之前，注册中心需要非常详细地了解您的网络工程和部署计划。因此，您提供的信息越详细，您的请求就越有可能得到快速处理。
If you obtain address space from your ISP, it is very likely that you will need to renumber should you decide to change upstream providers and/or if you grow considerably. As this renumbering may affect your customers (and their customers, etc.) if they are using dedicated lines, you should carefully weigh the cost/benefit involved in obtaining address space from your upstream provider.
如果您从ISP获得地址空间，如果您决定更改上游提供商和/或如果您的业务量大幅增长，则很可能需要重新编号。由于这种重新编号可能会影响您的客户（及其客户等），如果他们使用专用线路，您应该仔细权衡从上游提供商处获得地址空间所涉及的成本/收益。
If you are singly homed, you should obtain your address space from your upstream ISP. If you plan on enlarging but remaining singly homed, you should continue to obtain space this way as it promotes aggregation. If, however, you plan to be multi-homed as part of your growth plan, it would make sense to become a member of an appropriate Regional IR (or, if one exists in your region, a national Network Information Center (NIC) and obtain a /19 or "provider aggregatable" address space.
如果您是单亲家庭，您应该从上游ISP获得地址空间。如果您计划扩大但保持单独居住，您应该继续以这种方式获得空间，因为它促进了聚合。但是，如果您计划作为增长计划的一部分，成为适当的区域IR（或者，如果您所在区域存在国家网络信息中心（NIC））的成员，并获得/19或“提供商可聚合”地址空间，这将是有意义的。
The minimum routable block is often a /19, so if you plan on enlarging, it is better to pay the fees to the Regional IR now and obtain a /19 block so that you will not have to renumber later. Note that if you are an ISP in the ARIN region, ARIN has special requirements before you can do this in terms of the amount of address space you have previously used, which must be a /21. The current policy is that you must have used a /19 previously from your upstream ISP before going to ARIN, or you must be multi-homed and show you have used a /21 and be willing to renumber and ARIN will issue a /20 from a reserved /19.
最小可路由块通常是a/19，因此如果您计划扩大，最好现在就向区域IR支付费用并获得a/19块，这样您以后就不必重新编号。请注意，如果您是ARIN地区的ISP，ARIN对您以前使用的地址空间量（必须是a/21）有特殊要求，才能执行此操作。目前的政策是，您必须在前往ARIN之前使用过上游ISP提供的a/19，或者您必须是多址用户，并表明您使用过a/21，并且愿意重新编号，ARIN将从保留的a/19中发出a/20。
As of February 8, 1999, ARIN lowered the minimum allocation size for IP addresses from a /19 to a /20. ARIN will issue initial allocations of prefixes no longer than /20. If allocations smaller than /20 are needed, ISPs and end users should request address space from their upstream provider. ARIN does not guarantee that addresses will be globally routable.
截至1999年2月8日，ARIN将IP地址的最低分配大小从a/19降低到a/20。ARIN将发布不超过/20的前缀初始分配。如果需要小于/20的分配，ISP和最终用户应向其上游提供商请求地址空间。ARIN不保证地址是全局可路由的。
APNIC and RIPE NCC do not have these requirements. For APNIC, new allocations to members will be a /19.
APNIC和NCC没有这些要求。对于APNIC，对成员的新分配将是a/19。
Remember that your upstream provider should route you if you ask them. You are a customer of the ISP, so if the service is not what you need you should change ISPs.
请记住，如果您要求，您的上游供应商应该为您提供路线。您是ISP的客户，因此如果您不需要该服务，您应该更换ISP。
IF YOU ARE CONNECTED TO ONLY ONE PROVIDER, AND ARE NOT VERY LARGE YET, GET AN ADDRESS RANGE FROM YOUR PROVIDER. SKIP THE REST OF THIS SECTION AND ALL OF SECTION V.
如果您只连接到一个提供商，并且还不是很大，请从提供商处获取地址范围。跳过本节的其余部分和第五节的全部内容。
C. What is CIDR?
什么是苹果酒？
CIDR stands for Classless Inter-Domain Routing. Historically, IP addresses were assigned within classes: Class A (8 bits of network address, 24 bits of host address), Class B (16 bits of network address, 16 bits of host address), or Class C (24 bits of network address, 8 bits of host address). With the advent of CIDR, address space is now allocated and assigned on bit boundaries. Using CIDR means you are able to assign addresses corresponding with the number of hosts on the network, thereby conserving address space.
CIDR代表无类域间路由。历史上，IP地址是在类别中分配的：类别A（8位网络地址，24位主机地址）、类别B（16位网络地址，16位主机地址）或类别C（24位网络地址，8位主机地址）。随着CIDR的出现，地址空间现在在位边界上分配和分配。使用CIDR意味着您能够分配与网络上主机数量对应的地址，从而节省地址空间。
The following table illustrates this:
下表说明了这一点：
Addrs Bits Pref Class Mask
Addrs位前置类掩码
1 0 /32 255.255.255.255 2 1 /31 255.255.255.254 4 2 /30 255.255.255.252 8 3 /29 255.255.255.248 16 4 /28 255.255.255.240 32 5 /27 255.255.255.224 64 6 /26 255.255.255.192 128 7 /25 255.255.255.128 256 8 /24 1C 255.255.255.0 512 9 /23 2C 255.255.254.0 1K 10 /22 4C 255.255.252.0 2K 11 /21 8C 255.255.248.0 4K 12 /20 16C 255.255.240.0 8K 13 /19 32C 255.255.224.0
1 0/32 255.255.255.255 2 1/31 255.255.255.255.254 4 2/30 255.255.255.252 8 3/29 255.255.255.248 16 4/28 255.255.255.240 32 5/27 255.255.255.224 64 6/26 255.255.255.125.192 128 7/25 255.255.255.128 256 8/24 1C 255.255.255.255.255.0 512 9/23 2C 255.255.255.254.254.0 1K 10/22 4C 255.255.255.252.252.0 2K 11/21 8C.255.255.255.0 4K 12/25.255.255.255.255.258.258.258.258.258.28C.28C.28C.28K/329255.255.224.0
Addrs Number of addresses available; note that the number of addressable hosts normally is 2 less than this number because the host parts with all equal bits (all 0s, all 1s) are reserved.
地址可用的地址数；请注意，可寻址主机的数量通常比这个数字少2个，因为具有所有相等位（所有0、所有1）的主机部分都是保留的。
Bits Size of the allocation/assignment in bits of address space.
位分配/分配的大小，以地址空间的位为单位。
Pref Length of the prefix covering this address space. This is sometimes used to indicate the size of an allocation/assignment.
覆盖此地址空间的前缀的Pref长度。这有时用于指示分配/分配的大小。
Class Size of the address space in terms of class C network numbers.
以C类网络号表示的地址空间的类大小。
Mask The network mask defining the routing prefix in dotted quad notation.
掩码以虚线四元表示法定义路由前缀的网络掩码。
(From http://www.ibm.net.il/~hank/cidr.html)
(From http://www.ibm.net.il/~hank/cidr.html)
D. How do I request and register address space?
D.如何请求和注册地址空间？
You will need to send a database object to the appropriate registry to request and register address space. The registration databases are composed of records that are a series of fields separated by one or more blank lines; each field consists of two parts, the tag and the value. Do not modify the tags in the templates or errors will occur. Values for particular fields are specified in the templates; be careful to enter appropriate information.
您需要将数据库对象发送到相应的注册表以请求和注册地址空间。注册数据库由记录组成，这些记录是由一个或多个空行分隔的一系列字段；每个字段由两部分组成，标记和值。不要修改模板中的标记，否则会出现错误。模板中指定了特定字段的值；注意输入适当的信息。
The first line of a template denotes the record type. For example, an IP address template's first line is inetnum, therefore the record is known as an inetnum object. This first line is also used as the primary key for the record, therefore if you want to modify the first field of the record, the only way to do so is to delete the record entirely and add a new record with the corrected information.
模板的第一行表示记录类型。例如，IP地址模板的第一行是inetnum，因此该记录称为inetnum对象。第一行还用作记录的主键，因此，如果要修改记录的第一个字段，唯一的方法是完全删除该记录，并添加一个包含更正信息的新记录。
For illustration, here is the RIPE inetnum object.
为了进行说明，这里是成熟的inetnum对象。
inetnum: [IP address range that will be assigned] netname: Network-Name descr: Network-Name Communications Company, Town admin-c: NIC-handle of administrative contact tech-c: NIC-handle of technical contact country: ISO 3166-country-code
inetnum:[将分配的IP地址范围]网络名称：网络名称描述：网络名称通信公司，城镇管理员-c:管理联系人的NIC句柄tech-c:技术联系人国家/地区的NIC句柄：ISO 3166国家/地区代码
rev-srv: ns.someserver.net rev-srv: ns.otherserver.net status: assigned pa (provider aggregatable) or assigned pi (provider independent) changed: email@address.net 960731 source: RIPE
rev srv:ns.someserver.net rev srv:ns.otherserver.net状态：分配的pa（提供程序可聚合）或分配的pi（提供程序独立）已更改：email@address.net960731资料来源：成熟
For Countries in the APNIC Region
适用于亚太地区的国家
In order to obtain services from APNIC, you will need to become a member. APNIC-070 is the APNIC Membership Application. It is located at:
为了从APNIC获得服务，您需要成为会员。APNIC-070是APNIC会员申请。它位于：
ftp://ftp.apnic.net/apnic/docs/membership-application
ftp://ftp.apnic.net/apnic/docs/membership-application
Send the completed form via email to APNIC at:
将填妥的表格通过电子邮件发送至APNIC，地址为：
member-apply@apnic.net
成员-apply@apnic.net
APNIC Address Allocation Requests:
APNIC地址分配请求：
Once you have become a member, you can request IP address space using one of the three IP address request forms. If you are an organization that will use address space internally only (e.g., large enterprises such as universities, government ministries, large corporations, etc.), choose #1 (End User Address Request). If you are an organization that plans to sub-delegate address space to customers (e.g., you are an ISP), choose #2 (ISP Address Request). If you are a confederation of ISPs (e.g., national NICs, etc.), choose #3 (Confederation Address Request).
成为会员后，您可以使用三种IP地址请求表单之一请求IP地址空间。如果您是只在内部使用地址空间的组织（例如，大学、政府部门、大公司等大型企业），请选择#1（最终用户地址请求）。如果您是一家计划将地址空间再委托给客户的组织（例如，您是ISP），请选择#2（ISP地址请求）。如果您是ISP联盟（如国家NIC等），请选择#3（联盟地址请求）。
1. APNIC-074 is the APNIC End User Internet Address Request Form.
1. APNIC-074是APNIC最终用户互联网地址请求表。
2. APNIC-065 is the APNIC Internet Services Provider Internet Address Request Form.
2. APNIC-065是APNIC互联网服务提供商互联网地址请求表。
3. Confederations are a means by which service providers can group together to provide resource allocation and registration services tailored to their specific local language and cultural requirements. For details on how to become an APNIC recognized confederation, please see APNIC Confederation Concepts and Requirements located at:
3. 联合会是一种手段，通过这种方式，服务提供商可以组合在一起，根据其特定的当地语言和文化要求提供资源分配和注册服务。有关如何成为APNIC认可的联盟的详细信息，请参阅位于以下位置的APNIC联盟概念和要求：
ftp://ftp.apnic.net/apnic/docs/confed-requirements
ftp://ftp.apnic.net/apnic/docs/confed-requirements
APNIC-074 is the APNIC Confederation Internet Address Request Form.
APNIC-074是APNIC联合会互联网地址请求表。
Copies of all forms can be found in the following directory:
可在以下目录中找到所有表格的副本：
ftp://ftp.apnic.net/apnic/docs
or
http://www.apnic.net/reg.html
ftp://ftp.apnic.net/apnic/docs
or
http://www.apnic.net/reg.html
All completed forms should be sent to:
所有填妥的表格应发送至：
hostmaster@apnic.net
hostmaster@apnic.net
If there are strong reasons why you cannot obtain address space from your upstream ISP, and you require address space as a one-time allocation only, you can obtain address space as a "non member". For more details, see APNIC-071:
如果您无法从上游ISP获得地址空间有充分的理由，并且您只需要一次性分配地址空间，那么您可以作为“非成员”获得地址空间。有关更多详细信息，请参阅APNIC-071：
http://ftp.apnic.net/apnic/docs/non-member-application
http://ftp.apnic.net/apnic/docs/non-member-application
and send the completed form to:
并将填妥的表格发送至：
billing@apnic.net
billing@apnic.net
For Countries in the ARIN Region
适用于ARIN地区的国家
Membership in ARIN is optional and not a requirement for requesting IP address space from the registry or from your Internet service provider. If you are a large end user organization, choose #1. If you are an ISP, choose #2.
ARIN成员资格是可选的，不需要从注册表或Internet服务提供商请求IP地址空间。如果您是大型最终用户组织，请选择#1。如果您是ISP，请选择#2。
1. The form for network number assignments is located at:
1. 网络号码分配表位于：
ftp://rs.arin.net/templates/networktemplate.txt
or
http://www.arin.net/templates/networktemplate.txt
ftp://rs.arin.net/templates/networktemplate.txt
or
http://www.arin.net/templates/networktemplate.txt
2. The form for ISPs to obtain a CIDR block of IP network numbers is located at:
2. ISP获取IP网络号码CIDR块的表格位于：
ftp://rs.arin.net/templates/isptemplate.txt
or
http://www.arin.net/templates/isptemplate.txt
ftp://rs.arin.net/templates/isptemplate.txt
or
http://www.arin.net/templates/isptemplate.txt
Send either completed form via email to ARIN at:
通过电子邮件将填妥的表格发送至ARIN，地址为：
hostmaster@arin.net
hostmaster@arin.net
with "IP request" (if you chose #1) or "ISP CIDR request" (if you chose #2) in the subject field, as appropriate.
在主题字段中选择“IP请求”（如果选择#1）或“ISP CIDR请求”（如果选择#2），视情况而定。
For Countries in the RIPE Region
适用于成熟地区的国家
RIPE NCC provides IP address space allocation only to contributing local Internet registries. For a description of the European Internet Registry policies and procedures, see RIPE-159, "European Internet Registry Policies and Procedures". It is located at:
成熟的NCC只向本地Internet注册中心提供IP地址空间分配。有关欧洲互联网注册政策和程序的说明，请参阅RIME-159，“欧洲互联网注册政策和程序”。它位于：
ftp://ftp.ripe.net/ripe/docs/ripe-159.txt
ftp://ftp.ripe.net/ripe/docs/ripe-159.txt
RIPE-160 is Guidelines for Setting up a Local Internet Registry. It is located at:
RIME-160是建立本地互联网注册的指南。它位于：
ftp://ftp.ripe.net/docs/ripe-160.txt
ftp://ftp.ripe.net/docs/ripe-160.txt
If you have questions regarding setting up a new local IR, please contact the RIPE NCC at:
如果您对设置新的本地IR有任何疑问，请联系成熟的NCC：
new-lir@ripe.net
新的-lir@ripe.net
Once your local IR is established, you will get detailed information on how to submit requests to the RIPE NCC hostmaster.
建立本地IR后，您将获得有关如何向成熟的NCC主机提交请求的详细信息。
Send the completed form via email to RIPE NCC at:
将填妥的表格通过电子邮件发送至NCC，地址为：
ncc@ripe.net
ncc@ripe.net
If you have general queries, please contact RIPE NCC at:
如果您有一般疑问，请通过以下方式与NCC联系：
ncc@ripe.net
ncc@ripe.net
E. Section References
E.章节参考资料
For more information on IP addresses, see RFC 1518, "An Architecture for IP Address Allocation with CIDR" and RFC 2050, "Internet Registry IP Allocation Guidelines".
有关IP地址的更多信息，请参阅RFC 1518“使用CIDR分配IP地址的体系结构”和RFC 2050“Internet注册表IP分配指南”。
III. Autonomous Systems (AS)
三、 自治系统（AS）
STEP THREE: IF NEEDED, OBTAIN AN AUTONOMOUS SYSTEM NUMBER.
第三步：如果需要，获取自主系统编号。
A. What is an ASN and do I need one?
什么是ASN？我需要ASN吗？
Autonomous System Numbers (ASNs) are used to facilitate routing in multi-homed environments. They are allocated when your routing policy is different from your provider's. This generally means your site is multi-homed. In nearly all cases, unless you are multi-homed to more than one ISP, you will not need an ASN. If your routing policy does not differ from your service provider's, you should use
自治系统编号（ASN）用于促进多宿环境中的路由。当您的路由策略与提供商的路由策略不同时，将分配这些策略。这通常意味着您的站点是多宿主的。在几乎所有情况下，除非您是多个ISP的多址用户，否则您将不需要ASN。如果您的路由策略与服务提供商的路由策略没有差异，则应使用
the service provider's ASN. If there is constant traffic between you and a point in another country, you may want to connect to a second ISP in that country. Note that the resultant multi-homing generally makes the system more robust and may also change registry (and therefore request) relationships. It also increases costs greatly.
服务提供商的ASN。如果您与另一个国家/地区的某个点之间存在持续流量，您可能需要连接到该国家/地区的第二个ISP。请注意，由此产生的多归宿通常会使系统更加健壮，并且可能会更改注册表（因此也会更改请求）关系。这也大大增加了成本。
You may have to reduce traffic on your international lines by choosing to connect to a local exchange point. This allows traffic to stay within your country and off of expensive international links. If you implement this plan, you will be multi-homed and will need to read the autonomous systems and routing sections of this document.
您可能必须通过选择连接到本地交换点来减少国际线路的流量。这使得交通停留在您的国家和昂贵的国际链接。如果您实施此计划，您将是多宿的，并且需要阅读本文档的自治系统和路由部分。
B. How do I register an ASN?
B.如何注册ASN？
Since the ASN space is quite limited, request only what you really need when you need it.
由于ASN空间非常有限，所以在需要时只请求您真正需要的内容。
For Countries in the APNIC Region
适用于亚太地区的国家
APNIC-066 is the ASN Request Form. The form is located at:
APNIC-066是ASN申请表。表格位于：
http://ftp.apnic.net/apnic/docs/asn-request
http://ftp.apnic.net/apnic/docs/asn-request
Send the completed form via email to APNIC at:
将填妥的表格通过电子邮件发送至APNIC，地址为：
hostmaster@apnic.net
hostmaster@apnic.net
For Countries in the ARIN Region
适用于ARIN地区的国家
A complete listing of assigned ASNs is located at:
已分配ASN的完整列表位于：
ftp://rs.arin.net/netinfo/asn.txt
ftp://rs.arin.net/netinfo/asn.txt
The ASN registration form is located at:
ASN登记表位于：
ftp://rs.arin.net/templates/asntemplate.txt
or
http://www.arin.net/templates/asntemplate.txt
ftp://rs.arin.net/templates/asntemplate.txt
or
http://www.arin.net/templates/asntemplate.txt
Send the completed form via email to ARIN at:
将填妥的表格通过电子邮件发送至ARIN，地址为：
hostmaster@arin.net
hostmaster@arin.net
with "ASN request" in the subject field.
在主题字段中使用“ASN请求”。
For Countries in the RIPE Region
适用于成熟地区的国家
The European Autonomous System Number Application Form and Supporting Notes form (RIPE-147) is located at:
欧洲自治系统编号申请表和支持说明表（RIME-147）位于：
ftp://ftp.ripe.net/ripe/docs/ripe-147.txt
ftp://ftp.ripe.net/ripe/docs/ripe-147.txt
Local IRs can send the completed form via email to RIPE at:
当地国税局可通过电子邮件将填妥的表格发送至：
hostmaster@ripe.net
hostmaster@ripe.net
C. Section References
C.章节参考资料
For more information on ASNs, see RFC 1930, "Autonomous Systems (AS)".
有关ASN的更多信息，请参阅RFC 1930，“自治系统（AS）”。
IV. Routing and Exchange Points
四、 路由和交换点
STEP FOUR: IF NEEDED, REGISTER WITH A ROUTING DATABASE.
第四步：如果需要，向路由数据库注册。
A. Do I need to register with a routing database?
A.我需要向路由数据库注册吗？
You do not need to register with a routing database if you are simply carrying default routes to your (single) ISP. If you get your address space from an ISP, the ISP will register you. If you are connected to more than one ISP, then you should register with a routing database.
如果您只是将默认路由传送到（单个）ISP，则无需向路由数据库注册。如果您从ISP获得地址空间，ISP将为您注册。如果您连接到多个ISP，则应向路由数据库注册。
The more multi-homed you are, the larger your routing tables need to be. If you are connected to public exchange points (see examples below), or to more than one backbone ISP, you need to carry full routing tables and run without a default route.
多宿越多，路由表就需要越大。如果您连接到公共交换点（请参见下面的示例）或多个主干ISP，则需要携带完整的路由表，并且在没有默认路由的情况下运行。
Example European Exchange Points:
欧洲交换点示例：
LINX London Internet Exchange M9-IX Moscow Internet Exchange NIX.CZ Neutral Internet Exchange, Czech Republic
LINX伦敦互联网交易所M9-IX莫斯科互联网交易所NIX.CZ中立互联网交易所，捷克共和国
Example Asia/Pacific Exchange Points:
亚太地区交换点示例：
AUIX Australia Internet Exchange HKIX Hong Kong Internet Exchange JPIX Japan Internet Exchange
AUIX澳大利亚互联网交易所HKIX香港互联网交易所JPIX日本互联网交易所
Example Americas Exchange Points:
美洲交换点示例：
MAE-EAST Metropolitan Area Ethernet - East MAE-WEST Metropolitan Area Ethernet - West PAIX Palo Alto Internet Exchange
MAE-东部城域以太网-东部MAE-西部城域以太网-西部PAIX Palo Alto互联网交换机
Depending on the requirements of your international ISP, you may be able to have only a default route to them and specific routes to other suppliers if you have an in-country exchange point. Or they may require that you carry a full set of routes, treating your connection to the in-country exchange point as if it were a multi-homed connection.
根据您的国际ISP的要求，如果您有国内交换点，您可能只能有到他们的默认路由和到其他供应商的特定路由。或者，他们可能要求您携带全套路线，将您与国内交换点的连接视为多家连接。
B. What about CIDR and routing?
那么CIDR和路由呢？
All registries use CIDR. All major router vendors (Cisco, 3Com, Nortel, Proteon, IBM, etc.) support CIDR. CIDR Internet routers use only the prefix of the destination address to route traffic to a subnetted environment.
所有注册中心都使用CIDR。所有主要路由器供应商（Cisco、3Com、Nortel、Proteon、IBM等）都支持CIDR。CIDR Internet路由器仅使用目标地址的前缀将流量路由到子网环境。
C. How do I choose a routing database?
C.如何选择路由数据库？
The Internet Routing Registry (IRR) describes registries maintained by several national and international networking organizations. These currently include the RIPE Network Coordination Centre (NCC), ANS (Advanced Network Solutions, Inc.), Bell Canada (formerly CA*net), Cable and Wireless (CW), and the Routing Arbiter Database (RADB). The IRR is a way for ASNs to publicize their own intended routing policies without having to request a change from a go-between.
Internet路由注册中心（IRR）描述了几个国家和国际网络组织维护的注册中心。目前包括成熟的网络协调中心（NCC）、ANS（高级网络解决方案公司）、Bell Canada（前身为CA*net）、Cable and Wireless（CW）和路由仲裁数据库（RADB）。IRR是ASN宣传其预期路由策略的一种方式，无需从中间人处请求更改。
"whois" queries to "whois.ra.net" return data that they gather from the entire IRR set of routing registries. Tools such as "peval" and "rtconfig" return data only from the RADB. Thus, when running those tools and desiring data from a set of registries, one must enumerate them as in the following example. "whois" queries to the client configure the precedence of routing databases. For example:
对“whois.ra.net”的“whois”查询返回从整个IRR路由注册表集中收集的数据。“peval”和“rtconfig”等工具仅从RADB返回数据。因此，当运行这些工具并希望从一组注册中心获得数据时，必须像下面的示例中那样枚举它们。对客户端的“whois”查询配置路由数据库的优先级。例如：
@RtConfig set sources = "TEST, RADB, RIPE, ANS, BELL, CW"
@RtConfig set sources=“测试、RADB、成熟、ANS、贝尔、CW”
There are several other registries, such as ALTDB. A list, and other information on RADB, is available at:
还有其他几个注册中心，如ALTDB。有关RADB的列表和其他信息，请访问：
http://www.radb.net/
http://www.radb.net/
As of January 1, 2000, the transition to the Routing Policy Specification Language (RSPL) is complete. RIPE-181 object submissions are no longer accepted. For more information, see:
从2000年1月1日起，到路由策略规范语言（RSPL）的转换已经完成。不再接受RIME-181对象提交。有关详细信息，请参阅：
http://www.merit.edu/radb/announce.html
http://www.merit.edu/radb/announce.html
With the exception of the Routing Arbiter Database, each registry serves a limited customer base. ANS, Cable and Wireless, and Bell Canada accept routing registrations for their customers alone, and the RIPE NCC oversees European registrations. The Routing Arbiter Database is unique in that it handles registrations for networking organizations not covered by the other routing registries. The Routing Arbiter also provides coordination among all the registries to ensure consistent representation of routing policies.
除了路由仲裁器数据库之外，每个注册中心都服务于有限的客户群。ANS、Cable and Wireless和Bell Canada只接受客户的路由注册，成熟的NCC监督欧洲注册。路由仲裁器数据库的独特之处在于它处理其他路由注册中心未涵盖的网络组织的注册。路由仲裁器还提供所有注册中心之间的协调，以确保路由策略的一致表示。
All Regional IRs need to register with one (only one) of the routing databases in the IRR. If you are announcing routes via BGP4, you need to register your routes in the Routing Registry in only one of the IRR's. Logically, this will be the "closest" IRR to you. However, note that some ISPs do not use the regional registries or RADB.
所有区域IRs需要向IRR中的一个（仅一个）路由数据库注册。如果您通过BGP4宣布路线，则只需在其中一个IRR中的路线注册表中注册路线。从逻辑上讲，这将是与您“最接近”的内部收益率。但是，请注意，一些ISP不使用区域注册或RADB。
D. How do I register in the RADB (The Americas)?
D.我如何在RADB（美洲）注册？
You need to submit three types of database records to the RADB: one or more maintainer objects, an AS object, and one or more route objects.
您需要向RADB提交三种类型的数据库记录：一个或多个maintainer对象、一个AS对象和一个或多个route对象。
To specify the individuals who are allowed to update your records in the RADB, fill out one or more maintainer objects and send them via email to:
要指定允许更新RADB中记录的个人，请填写一个或多个maintainer对象，并通过电子邮件发送至：
db-admin@radb.net
分贝-admin@radb.net
You need to submit a maintainer object before you can register any AS or route objects.
在注册任何AS或route对象之前，需要提交一个maintainer对象。
To describe the autonomous system that announces your routes, fill out an AS object and submit it via email to:
要描述宣布路线的自治系统，请填写AS对象并通过电子邮件提交至：
auto-dbm@radb.net
自动的-dbm@radb.net
AS objects are also called aut-num objects.
AS对象也称为aut num对象。
To register your routes, fill out one or more route objects, and send them to RADB via email to:
要注册路由，请填写一个或多个路由对象，并通过电子邮件将其发送至RADB：
auto-dbm@radb.net
自动的-dbm@radb.net
Note that most of the IRR participants have the auto-dbm@xx.net email address function for accepting updates to the IRR automatically.
请注意，大多数IRR参与者都有自动-dbm@xx.net自动接受IRR更新的电子邮件地址功能。
E. Section References
E.章节参考资料
For more information on routers, see RFC 1812, "Requirements for IP Version 4 Routers". See also RFC 1786, "Representation of IP Routing Policies in a Routing Registry (ripe-181++)".
有关路由器的更多信息，请参阅RFC 1812，“IP版本4路由器的要求”。另请参见RFC1786，“路由注册表中IP路由策略的表示（RIME-181++）”。
For more information on CIDR and routing, see RFC 1817, "CIDR and Classful Routing".
有关CIDR和路由的更多信息，请参阅RFC1817，“CIDR和类路由”。
V. Domain Name Registration
五、域名注册
STEP FIVE: REGISTER YOUR DOMAIN NAME.
第五步：注册你的域名。
A. What is a country domain?
什么是国家域？
The Domain Name System (DNS) specifies the naming of computers within a hierarchy. Top-Level Domain (TLD) names include generic TLDs (gTLDs) and two-letter country codes (ccTLDs). Examples of gTLDs include .com (commercial), .net (network), and .org (organization). Examples of two-letter country codes are .ca for Canada, .fr for France, and .id for Indonesia. ISO 3166 is used as a basis for country code top-level domain names. Country codes are assigned by the International Organization for Standardization (ISO) in cooperation with the United Nations. The Internet Assigned Numbers Authority (IANA) directly registers all country-code top-level domains, however it is not involved in the allocation of codes to countries. IANA is a function of the Internet Corporation for Assigned Names and Numbers (ICANN, see Appendix A). See ISO 3166 for more information and a current listing of country codes (Appendix C).
域名系统（DNS）指定层次结构中计算机的命名。顶级域名（TLD）包括通用TLD（GTLD）和两个字母的国家代码（CCTLD）。GTLD的示例包括.com（商业）、.net（网络）和.org（组织）。两个字母的国家代码的示例包括：加拿大的.ca、.fr和印度尼西亚的.id。ISO 3166用作国家代码顶级域名的基础。国家代码由国际标准化组织（ISO）与联合国合作分配。互联网分配号码管理局（IANA）直接注册所有国家代码顶级域，但不参与向国家分配代码。IANA是互联网名称和号码分配公司（ICANN，见附录a）的一个职能部门。有关更多信息和国家代码的最新列表，请参见ISO 3166（附录C）。
A hierarchy of names may, and normally should be, created under each TLD. There is a wide variation in the structure of country domains. In some countries there is a substantial hierarchy, while in others the structure is flat. In some country domains the second levels are generic categories, while in others they are based on geography, and in still others, organization names are listed directly under the country code. Examples of second level generic categories are ac or edu (academic or education), co or com (corporate or commercial), and go or gov (government).
可以并且通常应该在每个TLD下创建名称的层次结构。国家领域的结构差异很大。在一些国家，存在着实质性的等级制度，而在另一些国家，这种结构是扁平的。在一些国家域中，第二级为一般类别，而在另一些国家域中，第二级为地理类别，还有一些国家域中，组织名称直接列在国家代码下。第二级通用类别包括ac或edu（学术或教育）、co或com（公司或商业）和go或gov（政府）。
B. How do I register as a country domain?
B.如何注册为国家域名？
First check that: (1) the domain is still available, few are, (2) you have someone in your country as the administrative contact, and (3) your name servers are prepared (see RFC 1912 for information on common errors in preparing name servers).
首先检查：（1）域名仍然可用，很少可用，（2）您的国家/地区有人作为管理联系人，（3）您的名称服务器已准备就绪（有关准备名称服务器时常见错误的信息，请参阅RFC 1912）。
The whois master database is the authoritative source of information on .com, .net, .org, and .edu domain name registrations. It is currently maintained by Network Solutions, Inc. and holds referral pointers to which whois database contains the record for the domain name.
whois主数据库是.com、.net、.org和.edu域名注册信息的权威来源。它目前由Network Solutions，Inc.维护，并持有whois数据库包含域名记录的引用指针。
To apply to manage a country code top-level domain you should:
要申请管理国家/地区代码顶级域，您应该：
1. First, if you are on a UNIX host, use the "whois" command to see if the domain is already registered:
1. 首先，如果您在UNIX主机上，请使用“whois”命令查看域是否已注册：
whois =<domain>
whois =<domain>
2. If the domain does not already have an administrative contact, request a Domain Name Agreement template from IANA by sending email to:
2. 如果域尚未具有管理联系人，请通过向以下地址发送电子邮件向IANA请求域名协议模板：
iana@iana.org
iana@iana.org
C. What if my country is already registered?
C.如果我的国家已经注册怎么办？
If your country is already registered, contact the country-code administrator to register a new second-level domain name.
如果您的国家/地区已注册，请联系国家/地区代码管理员以注册新的二级域名。
Please note that ARIN, RIPE, and APNIC do not handle domain names (other than IN-ADDR.ARPA). If you want to register a domain name directly under a top-level domain (TLD), please contact the appropriate TLD administrator.
请注意，ARIN、RIME和APNIC不处理域名（IN-ADDR.ARPA除外）。如果要直接在顶级域（TLD）下注册域名，请联系相应的TLD管理员。
D. How do I resolve a country domain name dispute?
D.如何解决国家/地区域名争议？
See RFC 1591 for domain name dispute information. Note that you will need to resolve the dispute within your country before you contact IANA.
域名争议信息见RFC 1591。请注意，在联系IANA之前，您需要解决您所在国家的争议。
E. Section References
E.章节参考资料
For more information on domain names, see RFC 1591, "Domain Name System Structure and Delegation"; RFC 1713, "Tools for DNS Debugging"; and RFC 1912, "Common DNS Operational and Configuration Errors".
有关域名的更多信息，请参阅RFC 1591，“域名系统结构和授权”；RFC 1713，“DNS调试工具”；RFC1912，“常见DNS操作和配置错误”。
VI. IN-ADDR.ARPA Domain Delegation
六、 IN-ADDR.ARPA域委派
STEP SIX: IF NEEDED, REGISTER YOUR IN-ADDR.ARPA DOMAIN.
第六步：如果需要，注册你的IN-ADDR.ARPA域。
A. What is an IN-ADDR.ARPA domain and do I need one?
什么是IN-ADDR.ARPA域，我需要吗？
An IN-ADDR.ARPA domain allows for mapping of IP addresses into domain names. This is often referred to as "inverse addressing" because it is the opposite of the domain name to IP address resolution. IN-ADDR domains are represented using the network number in reverse. For example, the IN-ADDR domain for network 123.45.67.0 is represented as 67.45.123.in-addr.arpa.
一个IN-ADDR.ARPA域允许将IP地址映射到域名。这通常被称为“反向寻址”，因为它与域名到IP地址解析相反。IN-ADDR域使用网络号反向表示。例如，网络123.45.67.0的IN-ADDR域表示为67.45.123.IN-ADDR.arpa。
You almost always need reverse resolution.
您几乎总是需要反向分辨率。
B. How do I register an IN-ADDR.ARPA domain?
B.如何注册IN-ADDR.ARPA域？
You should ask your upstream provider about registering your IN-ADDR.ARPA domains. If you are working directly with a regional registry, see below.
您应该询问您的上游提供商关于注册IN-ADDR.ARPA域的事宜。如果您直接与区域注册中心合作，请参见下文。
For Countries in the APNIC Region
适用于亚太地区的国家
The IN-ADDR.ARPA Delegation Form is APNIC-064 and is located at:
IN-ADDR.ARPA授权表为APNIC-064，位于：
ftp://ftp.apnic.net/apnic/docs/in-addr-request
ftp://ftp.apnic.net/apnic/docs/in-addr-request
CAUTION: You must set-up your name server to accept the delegation prior to submission of this form.
注意：在提交此表单之前，您必须设置名称服务器以接受委托。
Send the completed form via email to APNIC at:
将填妥的表格通过电子邮件发送至APNIC，地址为：
domreg@rs.apnic.net
domreg@rs.apnic.net
For Countries in the ARIN Region
适用于ARIN地区的国家
How IN-ADDR.ARPA is registered is dependent on the registration of the block needing reverse entries. For example, all blocks that have been registered directly from the Regional IR may have IN-ADDR.ARPA delegation established by ARIN. In this case, IN-ADDR.ARPA delegations are registered using the ARIN modify template. This template can be found at:
IN-ADDR.ARPA的注册方式取决于需要反向输入的块的注册。例如，直接从区域IR注册的所有区块可能具有ARIN建立的IN-ADDR.ARPA委托。在这种情况下，使用ARIN修改模板注册In-ADDR.ARPA委托。此模板可在以下位置找到：
ftp://ftp.arin.net/templates/modifytemplate.txt
or
http://www.arin.net/templates/modifytemplate.txt
ftp://ftp.arin.net/templates/modifytemplate.txt
or
http://www.arin.net/templates/modifytemplate.txt
Instructions for completing the template can be found at the bottom of the template.
完成模板的说明可在模板底部找到。
CAUTION: Do not list your network number in reverse on the template.
注意：不要在模板上反向列出您的网络号码。
Send the completed form via email to ARIN at:
将填妥的表格通过电子邮件发送至ARIN，地址为：
hostmaster@arin.net
hostmaster@arin.net
All blocks that have been reassigned to your organization by an ISP will have IN-ADDR.ARPA established by your provider. In this case, contact the ISP that reassigned IP address space to your organization and coordinate IN-ADDR.ARPA delegation.
ISP重新分配给您组织的所有数据块都将由您的提供商建立IN-ADDR.ARPA。在这种情况下，请联系为您的组织重新分配IP地址空间的ISP，并协调In-ADDR.ARPA委派。
For Countries in the RIPE Region
适用于成熟地区的国家
The domain object needs to be entered in the RIPE database before requesting reverse delegation.
在请求反向委托之前，需要在成熟的数据库中输入域对象。
domain: 0.194.in-addr.arpa descr: Our organization allocation admin-c: NIC-handle of administrative contact (e.g., JLC-2RIPE) tech-c: NIC-handle of technical contact zone-c: NIC-handle of zone contact nserver: Name server (e.g., ns.someserver.net) nserver: ns.otherserver.net nserver: ns.ripe.net changed: email@address.net 960731 source: RIPE
域：0.194.in-addr.arpa descr:我们的组织分配admin-c:管理联系人的NIC句柄（例如，JLC-2RIPE）tech-c:技术联系人区域的NIC句柄c:区域联系人的NIC句柄nserver:名称服务器（例如，ns.someserver.net）nserver:ns.otherserver.net nserver:ns.net更改：email@address.net960731资料来源：成熟
NOTE: One of the name servers has to be ns.ripe.net
注意：其中一个名称服务器必须是ns.RIME.net
The domain object described above should be included in the request, as well as zone file entries for the zone above the one requested. For example, if a reverse delegation is requested for 1.193.in-addr.arpa, the relevant zone file entries should be included for 193.in-addr.arpa; whereas if a reverse delegation is requested for 2.2.193.in-addr.arpa, the zone file entries should be included for 2.193.in-addr.arpa.
请求中应包含上述域对象，以及请求区域上方区域的区域文件条目。例如，如果为1.193.in-addr.arpa请求反向委托，则应为193.in-addr.arpa包含相关区域文件条目；然而，如果为2.2.193.in-addr.arpa请求反向委托，则应为2.193.in-addr.arpa包含区域文件条目。
Send the completed object(s) via email to RIPE at:
通过电子邮件将完成的对象发送至：
auto-inaddr@ripe.net
自动的-inaddr@ripe.net
VII. Security
七,。安全
A. Is there a way to prevent unauthorized changes to my objects?
A.有没有办法防止对我的对象进行未经授权的更改？
Registries provide various security measures to prevent unauthorized changes to your database entries. Contact your regional IR for more information. Note that the contact information you provide in the database object registrations is not private.
注册表提供了各种安全措施，以防止对数据库条目进行未经授权的更改。有关更多信息，请联系您的区域IR。请注意，您在数据库对象注册中提供的联系人信息不是私有的。
VIII. Network Optimization and Management
八,。网络优化与管理
A. How do I optimize traffic on my network?
A.如何优化网络流量？
Contact the Cooperative Association for Internet Data Analysis (CAIDA). CAIDA is a collaborative undertaking to promote greater cooperation in the engineering and maintenance of a robust, scalable global Internet infrastructure. CAIDA provides a neutral framework to support these cooperative endeavors.
联系互联网数据分析合作协会（CAIDA）。CAIDA是一项合作项目，旨在促进在设计和维护强健、可扩展的全球互联网基础设施方面的更大合作。CAIDA提供了一个中立的框架来支持这些合作努力。
The CAIDA web-site is located at:
CAIDA网站位于：
http://www.caida.org/
http://www.caida.org/
Send email with questions or comments to:
将带有问题或意见的电子邮件发送至：
info@caida.org
info@caida.org
Security Considerations
安全考虑
Security is discussed in section VII.
第七节讨论了安全问题。
Acknowledgements
致谢
Thanks to Brian Candler, David Conrad, John Heasley, Kim Hubbard, Daniel Karrenberg, Anne Lord, Dawn Martin, Charles Musisi, Jon Postel, and April Marine and the IETF User Services Working Group for reviewing various versions of this document; and to Hank Nussbacher for permission to reprint his table on CIDR.
感谢Brian Candler、David Conrad、John Heasley、Kim Hubbard、Daniel Karrenberg、Anne Lord、Dawn Martin、Charles Musisi、Jon Postel和April Marine以及IETF用户服务工作组审查了本文件的各种版本；并向Hank Nussbacher申请在CIDR上重印他的表格。
Special thanks are also due to Dr. Steven Goldstein of the National Science Foundation for his contributions and suggestions, and to the National Science Foundation for partial funding of this work.
特别感谢也归功于Steven Goldstein博士的国家科学基金会的贡献和建议，以及国家科学基金会部分资助这项工作。
This material is based upon work supported by the National Science Foundation under Grant No. NCR-961657. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.
该材料是基于国家科学基金会NCR-961657号批准的工作。在该材料中所表达的任何意见、结果、结论或建议都是作者的观点，并不一定反映国家科学基金会的观点。
References
工具书类
[1] Malkin, G., "Internet Users' Glossary", FYI 18, RFC 1983, August 1996.
[1] Malkin，G.“互联网用户词汇表”，第18财年，RFC 1983年，1996年8月。
[2] Hinden, R., Editor, "Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)", RFC 1517, September 1993.
[2] Hinden，R.，编辑，“实现无类域间路由（CIDR）的适用性声明”，RFC 1517，1993年9月。
[3] Rekhter, Y. and T. Li, "An Architecture for IP Address Allocation with CIDR", RFC 1518, September 1993.
[3] Rekhter，Y.和T.Li，“使用CIDR的IP地址分配架构”，RFC 1518，1993年9月。
[4] Fuller, V., Li, T., Yu, J. and K. Varadhan, "Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy", RFC 1519, September 1993.
[4] Fuller，V.，Li，T.，Yu，J.和K.Varadhan，“无类域间路由（CIDR）：地址分配和聚合策略”，RFC 1519，1993年9月。
[5] Rekhter, Y. and C. Topolcic, "Exchanging Routing Information Across Provider Boundaries in the CIDR Environment", RFC 1520, September 1993.
[5] Rekhter，Y.和C.Topolocic，“在CIDR环境中跨提供商边界交换路由信息”，RFC 1520，1993年9月。
[6] Postel, J., "Domain Name System Structure and Delegation", RFC 1591, March 1994.
[6] Postel，J.，“域名系统结构和授权”，RFC15911994年3月。
[7] Wijnen, B., Carpenter, G., Curran, K., Sehgal, A. and G. Waters, "Simple Network Management Protocol Distributed Protocol Interface Version 2.0", RFC 1592, March 1994.
[7] Wijnen，B.，Carpenter，G.，Curran，K.，Sehgal，A.和G.Waters，“简单网络管理协议分布式协议接口版本2.0”，RFC 1592，1994年3月。
[8] Ramao, A., "Tools for DNS debugging", RFC 1713, November 1994.
[8] Ramo，A.，“DNS调试工具”，RFC 1713，1994年11月。
[9] Baker, F., "Requirements for IP Version 4 Routers", RFC 1812, June 1995.
[9] Baker，F.，“IP版本4路由器的要求”，RFC 1812，1995年6月。
[10] Rekhter, Y., "CIDR and Classful Routing", RFC 1817, August 1995.
[10] Rekhter，Y.，“CIDR和分级路由”，RFC 1817，1995年8月。
[11] Barr, D., "Common DNS Operational and Configuration Errors", RFC 1912, February 1996.
[11] Barr，D.“常见DNS操作和配置错误”，RFC 1912，1996年2月。
[12] Hawkinson, J. and T. Bates, "Guidelines for Creation, Selection, and Registration of an Autonomous System", RFC 1930, March 1996.
[12] 霍金森，J.和T.贝茨，“自主系统的创建、选择和注册指南”，RFC 1930，1996年3月。
[13] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[13] Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第一部分：互联网邮件正文格式”，RFC 20451996年11月。
[14] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D. and J. Postel, "Internet Registry IP Allocation Guidelines", BCP 12, RFC 2050, November 1996.
[14] 哈伯德，K.，科斯特斯，M.，康拉德，D.，卡伦伯格，D.和J.波斯特尔，“互联网注册IP分配指南”，BCP 12，RFC 2050，1996年11月。
[15] Kessler, G. and S. Shepard, "A Primer On Internet and TCP/IP Tools and Utilities", FYI 30, RFC 2151, June 1997.
[15] Kessler，G.和S.Shepard，“互联网和TCP/IP工具和实用程序入门”，FYI 30，RFC 2151，1997年6月。
[16] ISO 3166: "Codes for the Representation of Names of Countries"
[16] ISO 3166：“国家名称表示代码”
[17] Palasri, S., Huter, S., and Wenzel, Z. "The History of the Internet in Thailand", University of Oregon Books, 1999.
[17] Palasri、美国、Huter、美国、文策尔、Z.《泰国互联网史》，俄勒冈大学图书，1999。
Authors' Addresses
作者地址
Zita Wenzel, Ph.D. Network Startup Resource Center (NSRC) 1225 Kincaid Street 1212-University of Oregon Eugene, OR 97403-1212 USA
Zita Wenzel博士。美国俄勒冈州尤金大学金凯街1225号网络创业资源中心（NSRC），邮编：97403-1212
EMail: zita@nsrc.org
EMail: zita@nsrc.org
John C. Klensin, Ph.D. Network Startup Resource Center (NSRC) 1225 Kincaid Street 1212-University of Oregon Eugene, OR 97403-1212 USA
约翰·C·克伦星博士。美国俄勒冈州尤金大学金凯街1225号网络创业资源中心（NSRC），邮编：97403-1212
EMail: klensin@nsrc.org
EMail: klensin@nsrc.org
Randy Bush Network Startup Resource Center (NSRC) 1225 Kincaid Street 1212-University of Oregon Eugene, OR 97403-1212 USA
兰迪·布什网络创业资源中心（NSRC）美国俄勒冈州尤金大学金凯街1225号1212，邮编：97403-1212
EMail: randy@nsrc.org
EMail: randy@nsrc.org
Steven Huter Network Startup Resource Center (NSRC) 1225 Kincaid Street 1212-University of Oregon Eugene, OR 97403-1212 USA
Steven Huter网络创业资源中心（NSRC）美国俄勒冈州尤金大学金凯街1225号1212，邮编：97403-1212
EMail: sghuter@nsrc.org
EMail: sghuter@nsrc.org
Appendix A: The Internet Agencies
附录A：互联网机构
o The Internet Assigned Numbers Authority (IANA)
o 互联网分配号码管理局（IANA）
IANA is the central coordinator for the assignment of unique parameter values for Internet protocols and for all address space and name space used in the Internet. IANA allocates parts of the Internet address space to Regional Internet Registries (IRs) for distribution to Local IRs and ISPs. IANA is also responsible for the coordination and management of the Domain Name System (DNS).
IANA是为互联网协议以及互联网中使用的所有地址空间和名称空间分配唯一参数值的中央协调人。IANA将部分互联网地址空间分配给区域互联网注册中心（IRs），以便分配给本地IRs和ISP。IANA还负责协调和管理域名系统（DNS）。
Note that as of 1999, IANA is a function of the Internet Corporation for Assigned Names and Numbers (ICANN), the non-profit corporation that is the top-level administration authority of the global Internet.
请注意，自1999年起，IANA是互联网名称和号码分配公司（ICANN）的一个职能部门，ICANN是一家非营利公司，是全球互联网的顶级管理机构。
Email: iana@iana.org
Postal: 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
USA
Telehone: +1-310-823-9358
Fax: +1-310-823-8649
Internet: http://www.iana.org/
Email: iana@iana.org
Postal: 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
USA
Telehone: +1-310-823-9358
Fax: +1-310-823-8649
Internet: http://www.iana.org/
o Internet Corporation for Assigned Names and Numbers (ICANN)
o 互联网名称和号码分配公司（ICANN）
From the ICANN web site:
从ICANN网站：
The Internet Corporation for Assigned Names and Numbers (ICANN) is a technical coordination body for the Internet. Created in October 1998 by a broad coalition of the Internet's business, technical, academic, and user communities, ICANN is assuming responsibility for a set of technical functions previously performed under U.S. Government contract by IANA and other groups.
互联网名称和号码分配公司（ICANN）是一个互联网技术协调机构。ICANN成立于1998年10月，由互联网的商业、技术、学术和用户群体组成的广泛联盟创建。ICANN负责一系列技术功能，这些功能以前由IANA和其他团体根据美国政府合同履行。
Specifically, ICANN coordinates the assignment of the following identifiers that must be globally unique for the Internet to function: Internet domain names, IP address numbers, protocol parameter and port numbers. In addition, ICANN coordinates the stable operation of the Internet's root server system.
具体而言，ICANN负责协调以下标识符的分配，这些标识符必须是全球唯一的，才能使互联网正常运行：互联网域名、IP地址号、协议参数和端口号。此外，ICANN还负责协调互联网根服务器系统的稳定运行。
As a non-profit, private-sector corporation, ICANN is dedicated to preserving the operational stability of the Internet; to promoting competition; to achieving broad representation of global Internet communities; and to developing policy through private-sector, bottom-up, consensus-based means. ICANN welcomes the participation of any interested Internet user, business, or organization.
作为一家非营利性私营公司，ICANN致力于维护互联网的运营稳定性；促进竞争；实现全球互联网社区的广泛代表性；以及通过私营部门、自下而上、基于共识的手段制定政策。ICANN欢迎任何感兴趣的互联网用户、企业或组织的参与。
Email: icann@icann.org
Postal: Internet Corporation for Assigned Names and Numbers
(ICANN)
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
USA
Telehone: +1-310-823-9358
Fax: +1-310-823-8649
Internet: http://www.icann.org/
Email: icann@icann.org
Postal: Internet Corporation for Assigned Names and Numbers
(ICANN)
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
USA
Telehone: +1-310-823-9358
Fax: +1-310-823-8649
Internet: http://www.icann.org/
o InterNIC
o 内部的
The InterNIC was a cooperative activity between the National Science Foundation, General Atomics, AT&T, and Network Solutions, Inc. The joint activity InterNIC no longer exists.
InNIC是美国国家科学基金会、通用原子公司、AT&T和网络解决方案公司之间的合作活动，联合活动互联网络不再存在。
Currently, Network Solutions runs the central registry according to the shared registry model specified by ICANN for registration of second-level domain names under the generic top-level domains .com, .net, and .org.
目前，Network Solutions根据ICANN指定的共享注册模型运行中央注册中心，以便在通用顶级域名.com、.net和.org下注册二级域名。
For information on accredited registrars for .com, .net, and .org, please see:
有关.com、.net和.org的注册信息，请参阅：
http://www.icann.org/registrars/accredited-list.html
http://www.icann.org/registrars/accredited-list.html
(note that Network Solutions is an accredited registrar as well as the entity running the registry).
（请注意，Network Solutions是经认可的注册机构，也是运行注册机构的实体）。
Email: hostmaster@netsol.com
Postal: Network Solutions, Inc.
505 Huntmar Park Dr.
Herndon, VA 20170 US
Telephone: +1-703-742-4777
Fax: +1-703-742-9552
Internet: http://www.networksolutions.com/
Email: hostmaster@netsol.com
Postal: Network Solutions, Inc.
505 Huntmar Park Dr.
Herndon, VA 20170 US
Telephone: +1-703-742-4777
Fax: +1-703-742-9552
Internet: http://www.networksolutions.com/
Regional Internet Registries (IRs)
区域互联网注册处（IRs）
Regional IRs operate in large geopolitical regions such as continents. Currently, there are three Regional IRs: ARIN for the Americas, the Caribbean, and Africa; RIPE NCC for Europe, Africa, and the Middle East; and APNIC for the Asia Pacific region. The specific duties of the Regional IRs include coordination and representation of all local Internet Registries in their respective region.
区域IRs在大陆等大型地缘政治区域运作。目前，有三个区域IRs：美洲、加勒比和非洲的ARIN；欧洲、非洲和中东的成熟NCC；亚太地区的APNIC。区域IRs的具体职责包括协调和代表其各自区域内的所有本地互联网注册中心。
o APNIC
o 呼吸暂停
Asia Pacific Network Information Center (APNIC) is a non-profit Internet registry for the Asia Pacific region. APNIC provides IP address allocation, Autonomous System Number (ASN) assignment, and IN-ADDR.ARPA registration.
亚太网络信息中心（APNIC）是亚太地区的非营利互联网注册中心。APNIC提供IP地址分配、自主系统号（ASN）分配和IN-ADDR.ARPA注册。
Email: hostmaster@apnic.net
Postal: APNIC Box 2131
Milton Queensland 4064
Australia
Telephone: +61-7-3367-0490
Fax: +61-7-3367-0482
Internet: http://www.apnic.net/
Email: hostmaster@apnic.net
Postal: APNIC Box 2131
Milton Queensland 4064
Australia
Telephone: +61-7-3367-0490
Fax: +61-7-3367-0482
Internet: http://www.apnic.net/
o ARIN
o 阿林
The American Registry for Internet Numbers (ARIN) is a non-profit Internet registry that was established for the purpose of administration and registration of Internet Protocol (IP) numbers to the geographical areas that were previously managed by Network Solutions, Inc. These areas include, but are not limited to, North America, South America, Africa, and the Caribbean region. ARIN provides IP address allocation, Autonomous System Number (ASN) assignment, and IN-ADDR.ARPA registration.
美国互联网号码注册中心（ARIN）是一家非营利性互联网注册中心，旨在管理和注册以前由Network Solutions，Inc.管理的地理区域的互联网协议（IP）号码。这些区域包括但不限于北美洲、南美洲、，非洲和加勒比区域。ARIN提供IP地址分配、自主系统号（ASN）分配和IN-ADDR.ARPA注册。
Email: hostmaster@arin.net
Postal: 4506 Daly Drive
Suite 200
Chantilly, VA 20151
Telephone: +1-703-227-0660
Fax +1-703-227-0676
Internet: http://www.arin.net/
Email: hostmaster@arin.net
Postal: 4506 Daly Drive
Suite 200
Chantilly, VA 20151
Telephone: +1-703-227-0660
Fax +1-703-227-0676
Internet: http://www.arin.net/
o RIPE NCC
o 成熟NCC
Reseaux IP Europens Network Coordination Centre (RIPE NCC) is a non-profit Internet registry for the European, North African, and Middle East regions. RIPE NCC provides IP address allocation, Autonomous System Number (ASN) assignment, and IN-ADDR.ARPA registration.
Reseaux IP欧洲网络协调中心（CREAME NCC）是欧洲、北非和中东地区的非营利互联网注册中心。成熟的NCC提供IP地址分配、自主系统号（ASN）分配和IN-ADDR.ARPA注册。
Email: ncc@ripe.net
Postal: Singel 258
1016 AB Amsterdam
The Netherlands
Phone: +31-20-535-4444
Fax: +31-20-535-4445
Internet: http://www.ripe.net/
Email: ncc@ripe.net
Postal: Singel 258
1016 AB Amsterdam
The Netherlands
Phone: +31-20-535-4444
Fax: +31-20-535-4445
Internet: http://www.ripe.net/
Appendix B: Documentation
附录B：文件
Internet Documentation
互联网文档
For general Internet documentation, "ftp" to rfc-editor.org and "cd" to the /rfc subdirectory for Request for Comments documents.
对于一般的互联网文档，“ftp”到rfc-editor.org，“cd”到/rfc子目录以请求评论文档。
Details on obtaining these documents via ftp or email may be obtained by sending an email message to:
有关通过ftp或电子邮件获取这些文件的详细信息，请发送电子邮件至：
rfc-info@rfc-editor.org
rfc-info@rfc-编辑网
with the message body help: ways_to_get_rfcs. For example:
使用消息正文帮助：获取RFC的方法。例如：
To: rfc-info@isi.edu Subject: getting rfcs
收件人：rfc-info@isi.edu主题：获取RFC
help: ways_to_get_rfcs
帮助：获取RFC的方法
Documents, Templates, and Forms
文档、模板和表单
The documents, templates, and forms referenced in this guide are available from the document stores in the directories listed in the URLs (Uniform Resource Locators). Organizations without connectivity wishing to obtain copies of the referenced documents should contact their Local IR to arrange postal delivery of one or more of the documents. Note that fees may be associated with the delivery of hardcopy versions of documents.
本指南中引用的文档、模板和表单可从URL（统一资源定位器）中列出的目录中的文档存储中获得。无连接的组织希望获得参考文件的副本，应联系其当地IR，以安排邮寄一份或多份文件。请注意，费用可能与文件硬拷贝版本的交付有关。
The document stores can be accessed in two ways:
可以通过两种方式访问文档存储：
1. Via anonymous FTP (File Transfer Protocol).
1. 通过匿名FTP（文件传输协议）。
Using your ftp program, connect to the appropriate host computer shown below using your email address as the password. Use the "cd" (change directory) command to connect to the appropriate subdirectory, then use the "get" command to retrieve the specific file. For example:
使用ftp程序，使用您的电子邮件地址作为密码连接到下面所示的相应主机。使用“cd”（更改目录）命令连接到相应的子目录，然后使用“get”命令检索特定文件。例如：
ftp rs.apnic.net (for countries in the Asia/Pacific region) ftp rs.arin.net (for countries in the Americas) ftp rs.ripe.net (for countries in Europe or North Africa)
ftp rs.apnic.net（适用于亚太地区国家）ftp rs.arin.net（适用于美洲国家）ftp rs.ripe.net（适用于欧洲或北非国家）
login: anonymous password: your_email_address
登录：匿名密码：您的电子邮件地址
cd netinfo get <domain>_info.txt
cd netinfo get<domain>\u info.txt
2. Via electronic mail, ftp, or the World Wide Web.
2. 通过电子邮件、ftp或万维网。
Send email to the appropriate address shown below with the message body as specified.
按照指定的邮件正文，将电子邮件发送到如下所示的适当地址。
APNIC Documentation
APNIC文件
For APNIC documents and templates, "ftp" to ftp.apnic.net and "cd" to /apnic/docs. APNIC no longer has an electronic mail method of form retrieval. Many of APNIC's request forms are also available on the web site at:
对于APNIC文档和模板，“ftp”至ftp.APNIC.net，“cd”至/APNIC/docs。APNIC不再使用电子邮件方式进行表单检索。APNIC的许多申请表也可在以下网站上获得：
http://www.apnic.net/reg.html
http://www.apnic.net/reg.html
ARIN Documentation
ARIN文件
For ARIN templates, "ftp" to rs.arin.net and "cd" to /templates.
对于ARIN模板，“ftp”到rs.ARIN.net，“cd”到/templates。
You can also obtain templates via the web site at:
您还可以通过以下网站获取模板：
http://www.arin.net/templates.html
http://www.arin.net/templates.html
Other ARIN documentation is available at:
其他ARIN文件可从以下网址获得：
http://www.arin.net/docs.html
http://www.arin.net/docs.html
Or send email to:
或发送电子邮件至：
hostmaster@arin.net
hostmaster@arin.net
RIPE Documentation
成熟的文件
For RIPE documents and forms, "ftp" to ftp.ripe.net/ripe and "cd" to /docs or cd to /forms.
对于成熟的文档和表单，“ftp”到ftp.RIPE.net/RIPE，“cd”到/docs或cd到/forms。
Or send email to:
或发送电子邮件至：
mail-server@ripe.net
邮寄-server@ripe.net
with send help in the body of the message.
在邮件正文中使用“发送帮助”。
Appendix C: Country Codes
附录C：国家代码
The International Organization for Standardization (ISO) 3166 Maintenance Agency and ISO 3166 current list of two-letter country codes is available via:
国际标准化组织（ISO）3166维护机构和ISO 3166两个字母国家代码的当前列表可通过以下途径获得：
http://www.iso.ch/infoe/agency/3166-1.htm
http://www.iso.ch/infoe/agency/3166-1.htm
Appendix D: Acronyms
附录D：首字母缩略词
ANS Advanced Network Services, Inc. ASN Autonomous System Number APNIC Asia Pacific Network Information Center ARIN American Registry for Internet Numbers AS Autonomous System CANET Canada Net CIDR Classless Inter-Domain Routing DNS Domain Name System gTLD Generic Top-Level Domain IANA Internet Assigned Numbers Authority InterNIC Internet Network Information Center IP Internet Protocol IR Internet Registry IRR Internet Routing Registry ISO International Organization for Standardization ISP Internet Service Provider LINX London Internet Exchange NCC Network Coordination Centre NIC Network Information Center NSRC Network Startup Resource Center POP Point of Presence RADB Routing Arbiter Data Base RFC Request for Comments RIPE Reseaux IP Europeans TCP/IP Transmission Control Protocol/Internet Protocol TLD Top-Level Domain
ANS高级网络服务，Inc.ASN自治系统编号APNIC亚太网络信息中心ARIN美国互联网号码注册处AS自治系统CANET加拿大网络CIDR无类域间路由DNS域名系统gTLD通用顶级域IANA互联网分配号码管理局互联网网络信息中心IP互联网协议IR Internet注册表IRR Internet路由注册表ISO国际标准化组织ISP Internet服务提供商LINX伦敦Internet Exchange NCC网络协调中心NIC网络信息中心NSRC网络启动资源中心POP存在点RADB路由仲裁器数据库RFC征求意见IP欧洲TCP/IP传输控制协议/互联网协议TLD顶级域
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。