Network Working Group S. Hollenbeck
Request for Comments: 3375 Verisign, Inc.
Category: Informational September 2002
Network Working Group S. Hollenbeck
Request for Comments: 3375 Verisign, Inc.
Category: Informational September 2002
Generic Registry-Registrar Protocol Requirements
通用注册表注册器协议要求
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 (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This document describes high-level functional and interface requirements for a client-server protocol for the registration and management of Internet domain names in shared registries. Specific technical requirements detailed for protocol design are not presented here. Instead, this document focuses on the basic functions and interfaces required of a protocol to support multiple registry and registrar operational models.
本文档描述了用于在共享注册中心注册和管理Internet域名的客户端-服务器协议的高级功能和接口要求。此处不提供协议设计的具体技术要求。相反，本文档侧重于协议所需的基本功能和接口，以支持多个注册表和注册器操作模型。
Conventions Used In This Document
本文件中使用的公约
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
Table of Contents
目录
1. Introduction ....................................... 2
1.1 Definitions, Acronyms, and Abbreviations ........... 2
2. General Description ................................ 4
2.1 System Perspective ................................. 4
2.2 System Functions ................................... 4
2.3 User Characteristics ............................... 5
2.4 Assumptions ........................................ 5
3. Functional Requirements ............................ 5
3.1 Session Management ................................. 6
3.2 Identification and Authentication .................. 6
3.3 Transaction Identification ......................... 7
3.4 Object Management .................................. 7
3.5 Domain Status Indicators ........................... 13
1. Introduction ....................................... 2
1.1 Definitions, Acronyms, and Abbreviations ........... 2
2. General Description ................................ 4
2.1 System Perspective ................................. 4
2.2 System Functions ................................... 4
2.3 User Characteristics ............................... 5
2.4 Assumptions ........................................ 5
3. Functional Requirements ............................ 5
3.1 Session Management ................................. 6
3.2 Identification and Authentication .................. 6
3.3 Transaction Identification ......................... 7
3.4 Object Management .................................. 7
3.5 Domain Status Indicators ........................... 13
3.6 Transaction Completion Status ...................... 13
4. External Interface Requirements .................... 14
4.1 User, Hardware, and Software Interfaces ............ 14
4.2 Communications Interfaces .......................... 14
5. Performance Requirements ........................... 14
6. Design Constraints ................................. 14
6.1 Standards Compliance ............................... 14
6.2 Hardware Limitations ............................... 15
7. Service Attributes ................................. 15
7.1 Reliability ........................................ 15
7.2 Availability ....................................... 15
7.3 Scalability ........................................ 16
7.4 Maintainability .................................... 16
7.5 Extensibility ...................................... 16
7.6 Security ........................................... 16
8. Other Requirements ................................. 17
8.1 Database Requirements .............................. 17
8.2 Operational Requirements ........................... 17
8.3 Site Adaptation Requirements ....................... 17
8.4 Data Collection Requirements ....................... 17
9. Internationalization Requirements .................. 18
10. IANA Considerations ................................ 18
11. Security Considerations ............................ 18
12. Acknowledgements ................................... 19
13. References ......................................... 19
14. Editor's Address ................................... 20
15. Full Copyright Statement ........................... 21
3.6 Transaction Completion Status ...................... 13
4. External Interface Requirements .................... 14
4.1 User, Hardware, and Software Interfaces ............ 14
4.2 Communications Interfaces .......................... 14
5. Performance Requirements ........................... 14
6. Design Constraints ................................. 14
6.1 Standards Compliance ............................... 14
6.2 Hardware Limitations ............................... 15
7. Service Attributes ................................. 15
7.1 Reliability ........................................ 15
7.2 Availability ....................................... 15
7.3 Scalability ........................................ 16
7.4 Maintainability .................................... 16
7.5 Extensibility ...................................... 16
7.6 Security ........................................... 16
8. Other Requirements ................................. 17
8.1 Database Requirements .............................. 17
8.2 Operational Requirements ........................... 17
8.3 Site Adaptation Requirements ....................... 17
8.4 Data Collection Requirements ....................... 17
9. Internationalization Requirements .................. 18
10. IANA Considerations ................................ 18
11. Security Considerations ............................ 18
12. Acknowledgements ................................... 19
13. References ......................................... 19
14. Editor's Address ................................... 20
15. Full Copyright Statement ........................... 21
The advent of shared domain name registration systems illustrates the utility of a common, generic protocol for registry-registrar interaction. A standard generic protocol will allow registrars to communicate with multiple registries through a common interface, reducing operational complexity. This document describes high level functional and interface requirements for a generic provisioning protocol suitable for registry-registrar operations. Detailed technical requirements are not addressed in this document.
共享域名注册系统的出现说明了一种通用的注册商交互协议的实用性。标准通用协议将允许登记员通过一个通用接口与多个登记处通信，从而降低操作复杂性。本文档描述了适用于注册表注册器操作的通用配置协议的高级功能和接口要求。本文件未说明详细的技术要求。
ccTLD: Country Code Top Level Domain. ".us" is an example of a ccTLD.
国家代码顶级域。“.us”是ccTLD的一个示例。
DNS: Domain Name System
域名系统
gTLD: Generic Top Level Domain. ".com" is an example of a gTLD.
gTLD：通用顶级域。“.com”是gTLD的一个示例。
IANA: Internet Assigned Numbers Authority
IANA：互联网分配号码管理局
IETF: Internet Engineering Task Force
因特网工程任务组
IP Address: Either or both IPv4 or IPv6 address.
IP地址：IPv4或IPv6地址中的一个或两个。
IPv4: Internet Protocol version 4
IPv4:Internet协议版本4
IPv6: Internet Protocol version 6
IPv6：Internet协议版本6
RRP: Registry-Registrar Protocol
注册登记协议
TLD: Top Level Domain. A generic term used to describe both gTLDs and ccTLDs that exist under the top-level root of the domain name hierarchy.
TLD：顶级域。一个通用术语，用于描述存在于域名层次结构顶层根下的GTLD和CCTLD。
Exclusive Registration System: A domain name registration system in which registry services are limited to a single registrar. Exclusive Registration Systems are either loosely coupled (in which case the separation between registry and registrar systems is readily evident), or tightly coupled (in which case the separation between registry and registrar systems is obscure).
专有注册系统：一种域名注册系统，其中注册服务仅限于一个注册商。排他性登记系统要么松散耦合（在这种情况下，登记册系统和登记册系统之间的分离很明显），要么紧密耦合（在这种情况下，登记册系统和登记册系统之间的分离很模糊）。
Name Space: The range of values that can be assigned within a particular node of the domain name hierarchy.
名称空间：可以在域名层次结构的特定节点内分配的值的范围。
Object: A generic term used to describe entities that are created, updated, deleted, and otherwise managed by a generic registry-registrar protocol.
对象：一个通用术语，用于描述由通用注册表注册器协议创建、更新、删除和以其他方式管理的实体。
Registrant: An entity that registers domain names in a registry through the services provided by a registrar. Registrants include individuals, organizations, and corporations.
注册人：通过注册人提供的服务在注册中心注册域名的实体。注册者包括个人、组织和公司。
Registrar: An entity that provides front-end domain name registration services to registrants, providing a public interface to registry services.
注册商：向注册人提供前端域名注册服务的实体，为注册服务提供公共接口。
Registry: An entity that provides back-end domain name registration services to registrars, managing a central repository of information associated with domain name delegations. A registry is typically responsible for publication and distribution of zone files used by the Domain Name System.
注册中心：向注册者提供后端域名注册服务的实体，管理与域名授权相关的信息的中央存储库。注册表通常负责发布和分发域名系统使用的区域文件。
Shared Registration System: A domain name registration system in which registry services are shared among multiple independent registrars. Shared Registration Systems require a loose coupling between registrars and a registry.
共享注册系统：一种域名注册系统，其中注册服务在多个独立注册商之间共享。共享注册系统需要注册器和注册器之间的松散耦合。
Thick Registry: A registry in which all of the information associated with registered entities, including both technical information (information needed to produce zone files) and social information (information needed to implement operational, business, or legal practices), is stored within the registry repository.
厚注册表：一种注册表，其中与注册实体相关的所有信息，包括技术信息（生成区域文件所需的信息）和社会信息（实施运营、业务或法律实践所需的信息），都存储在注册表存储库中。
Thin Registry: A registry in which all elements of the social information associated with registered entities is distributed between a shared registry and the registrars served by the registry.
精简注册表：一种注册表，其中与注册实体相关的社会信息的所有元素分布在共享注册表和该注册表所服务的注册者之间。
Zone: The complete set of information for a particular "pruned" subtree of the domain space. The zone concept is described fully in [RFC1035].
区域：域空间中特定“修剪”子树的完整信息集。区域概念在[RFC1035]中有详细描述。
A basic understanding of domain name registration systems provides focus for the enumeration of functional and interface requirements of a protocol to serve those systems. This section provides a high-level description of domain name registration systems to provide context for the requirements identified later in this document.
通过对域名注册系统的基本理解，可以重点列举服务于这些系统的协议的功能和接口需求。本节提供了域名注册系统的高级描述，为本文档后面确定的要求提供上下文。
A domain name registration system consists of a protocol and associated software and hardware that permits registrars to provide Internet domain name registration services within the name spaces administered by a registry. A registration system can be shared among multiple competing registrars, or it can be served by a single registrar that is either tightly or loosely coupled with back-end registry services. The system providing registration services for the .com, .net, and .org gTLDs is an example of a shared registration system serving multiple competing registrars. The systems providing registration services for some ccTLDs and the .gov and .mil gTLDs are examples of registration systems served by a single registrar.
域名注册系统由协议和相关软件和硬件组成，允许注册者在注册中心管理的名称空间内提供互联网域名注册服务。注册系统可以在多个相互竞争的注册商之间共享，也可以由一个与后端注册服务紧密或松散耦合的注册商提供服务。为.com、.net和.org gTLDs提供注册服务的系统是服务于多个竞争注册商的共享注册系统的一个示例。为某些国家/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/地区/。
Registrars access a registry through a protocol to register objects and perform object management functions. Required functions include session management; object creation, update, renewal, and deletion; object query; and object transfer.
注册器通过协议访问注册器，以注册对象并执行对象管理功能。所需功能包括会话管理；对象创建、更新、更新和删除；对象查询；和对象转移。
A registry generates DNS zone files for the name spaces it serves. Zone files are created and distributed to a series of name servers that provide the foundation for the domain name system.
注册表为其服务的名称空间生成DNS区域文件。区域文件被创建并分发给一系列名称服务器，这些域名服务器为域名系统提供了基础。
Protocol users fall into two broad categories: entities that use protocol client implementations and entities that use protocol server implementations, though an entity can provide both client and server services if it provides intermediate services. A protocol provides a loose coupling between these communicating entities.
协议用户分为两大类：使用协议客户机实现的实体和使用协议服务器实现的实体，但如果实体提供中间服务，则可以同时提供客户机和服务器服务。协议在这些通信实体之间提供松散耦合。
There is one and only one registry that is authoritative for a given name space and zone.
对于给定的名称空间和区域，只有一个且仅有一个具有权威性的注册表。
A registry can be authoritative for more than one name space and zone. Some registry operations can be billable. The impact of a billable operation can be mitigated through the specification of non-billable operations that allow a registrar to make informed decisions before executing billable operations.
注册表可以是多个名称空间和区域的权威。某些注册表操作可以计费。可计费操作的影响可以通过非计费操作的规范来减轻，该规范允许注册官在执行计费操作之前做出明智的决定。
A registry can choose to implement a subset of the features provided by a generic registry-registrar protocol. A thin registry, for example, might not provide services to register social information. Specification of minimal implementation compliance requirements is thus an exercise left for a formal protocol definition document that addresses the functional requirements specified here.
注册表可以选择实现由通用注册表注册器协议提供的功能子集。例如，精简注册表可能不提供注册社交信息的服务。因此，最低实现合规性需求的规范是一个正式协议定义文档的练习，该文档解决了此处指定的功能需求。
A protocol that meets the requirements described here can be called something other than "Generic Registry Registrar Protocol".
满足此处所述要求的协议可以称为“通用注册表注册器协议”以外的其他协议。
The requirements described in this document are not intended to limit the set of objects that can be managed by a generic registry-registrar protocol.
本文档中描述的要求并非旨在限制可由通用注册表注册器协议管理的对象集。
This section describes functional requirements for a registry-registrar protocol. Technical requirements that describe how these requirements are to be met are out of scope for this document.
本节描述注册表注册器协议的功能要求。描述如何满足这些要求的技术要求不在本文件范围内。
[1] The protocol MUST provide services to explicitly establish a client session with a registry server.
[1] 协议必须提供服务，以明确地建立与注册表服务器的客户端会话。
[2] In a connection-oriented environment, a server MUST respond to connection attempts with information that identifies the server and the default server protocol version.
[2] 在面向连接的环境中，服务器必须使用标识服务器和默认服务器协议版本的信息响应连接尝试。
[3] The protocol MUST provide services that allow a client to request use of a specific protocol version as part of negotiating a session.
[3] 协议必须提供服务，允许客户端在协商会话时请求使用特定的协议版本。
[4] The protocol MUST provide services that allow a server to decline use of a specific protocol version as part of negotiating a session.
[4] 协议必须提供服务，允许服务器在协商会话时拒绝使用特定协议版本。
[5] A session MUST NOT be established if the client and server are unable to reach agreement on the protocol version to be used for the requested session.
[5] 如果客户端和服务器无法就用于请求会话的协议版本达成一致，则不得建立会话。
[6] The protocol MUST provide services to explicitly end an established session.
[6] 协议必须提供明确结束已建立会话的服务。
[7] The protocol MUST provide services that provide transactional atomicity, consistency, isolation, and durability in the advent of session management failures.
[7] 协议必须提供在会话管理失败时提供事务原子性、一致性、隔离性和持久性的服务。
[8] The protocol MUST provide services to confirm that a transaction has been completed if a session is aborted prematurely.
[8] 如果会话提前中止，协议必须提供确认事务已完成的服务。
[1] The protocol or another layered protocol MUST provide services to identify registrar clients and registry servers before granting access to other protocol services.
[1] 协议或其他分层协议必须提供服务，以在授予对其他协议服务的访问权限之前识别注册器客户端和注册服务器。
[2] The protocol or another layered protocol MUST provide services to authenticate registrar clients and registry servers before granting access to other protocol services.
[2] 在授予对其他协议服务的访问权之前，协议或其他分层协议必须提供服务来验证注册器客户端和注册服务器。
[3] The protocol or another layered protocol MUST provide services to negotiate an authentication mechanism acceptable to both client and server.
[3] 协议或其他分层协议必须提供服务，以协商客户端和服务器都可以接受的身份验证机制。
[1] Registry operations that create, modify, or delete objects MUST be associated with a registry-unique identifier. The protocol MUST allow each transaction to be identified in a permanent and globally unique manner to facilitate temporal ordering and state management services.
[1] 创建、修改或删除对象的注册表操作必须与注册表唯一标识符相关联。协议必须允许以永久和全局唯一的方式标识每个事务，以促进时间顺序和状态管理服务。
This section describes requirements for object management, including identification, registration, association, update, transfer, renewal, deletion, and query.
本节描述对象管理的要求，包括标识、注册、关联、更新、转移、续订、删除和查询。
Some objects, such as name servers and contacts, have utility in multiple registries. However, maintaining disjoint copies of object information in multiple registries can lead to inconsistencies that have adverse consequences for the Internet. For example, changing a name server name in one registry, but not in a second registry that refers to the server for domain name delegation, can produce unexpected DNS query results.
某些对象（如名称服务器和联系人）在多个注册表中具有实用程序。然而，在多个注册中心维护对象信息的不相交副本可能会导致不一致，从而对互联网产生不利影响。例如，在一个注册表中更改名称服务器名称，而不是在引用域名委派服务器的第二个注册表中更改名称服务器名称，可能会产生意外的DNS查询结果。
[1] The protocol MUST provide services to associate an object identifier with every object.
[1] 协议必须提供将对象标识符与每个对象关联的服务。
[2] Object identifiers MUST be globally unique.
[2] 对象标识符必须是全局唯一的。
[3] An object's identifier MUST NOT change during the lifetime of the object in a particular repository, even if administrative control of the object changes over time.
[3] 在特定存储库中对象的生命周期内，对象的标识符不得更改，即使对象的管理控制随时间而更改。
[4] An object identifier MUST contain information that unambiguously identifies the object.
[4] 对象标识符必须包含明确标识对象的信息。
[5] Object identifier format specified by the protocol SHOULD be easily parsed and understood by humans.
[5] 协议指定的对象标识符格式应该易于解析并被人类理解。
[6] An object's identifier MUST be generated and stored when an object is created.
[6] 创建对象时，必须生成并存储对象的标识符。
[1] The protocol MUST provide services to register Internet domain names.
[1] 协议必须提供注册Internet域名的服务。
[2] The protocol MUST permit a starting and ending time for a domain name registration to be negotiated, thereby allowing a registry to implement policies allowing a range of registration validity periods (the start and end points in time during which one normally assumes that an object will be active), and enabling registrars to select a period for each registration they submit from within the valid range based on out-of-band negotiation between the registrar and the registrant. Registries SHOULD be allowed to accept indefinitely valid registrations if the policy that they are implementing permits, and to specify a default validity period if one is not selected by a registrar. Registries MUST be allowed to specify minimal validity periods consistent with prevailing or preferred practices for fee-for-service recovery. The protocol MUST provide features to ensure that both registry and registrar have a mutual understanding of the validity period at the conclusion of a successful registration event.
[2] 协议必须允许协商域名注册的开始和结束时间，从而允许注册中心实施允许一系列注册有效期的策略（通常假设对象处于活动状态的开始和结束时间点），以及使注册人能够根据注册人和注册人之间的带外协商，在有效范围内为其提交的每次注册选择一个期限。如果注册中心实施的政策允许，则应允许注册中心接受无限期有效的注册，如果注册中心未选择有效期，则应指定默认有效期。必须允许登记处规定最低有效期，该有效期应与服务收费回收的现行或首选做法相一致。议定书必须提供一些特点，以确保登记处和书记官长在成功登记活动结束时相互了解有效期。
[3] The protocol MUST provide services to register name servers. Name server registration MUST NOT be limited to a specific period of time. Name servers MUST be registered with a valid IPv4 or IPv6 address when a "glue record" is required for delegation. A name server MAY be registered with multiple IP addresses. Multiple name servers using distinct server names MAY share an IP address.
[3] 协议必须提供注册名称服务器的服务。名称服务器注册不得限制在特定的时间段内。当委派需要“粘合记录”时，名称服务器必须使用有效的IPv4或IPv6地址注册。名称服务器可以使用多个IP地址注册。使用不同服务器名称的多个名称服务器可能共享一个IP地址。
[4] The protocol MUST provide services to manage delegation of zone authority. Names of name servers MUST NOT be required to be tied to the name of the zone(s) for which the server is authoritative.
[4] 协议必须提供管理区域授权委托的服务。名称服务器的名称不必绑定到服务器授权的区域的名称。
[5] The protocol MUST provide services to register social information describing human and organizational entities. Registration of social information MUST NOT be limited to a specific period of time. Social information MAY include a name (individual name, organization name, or both), address (including street address, city, state or province (if applicable), postal code, and country), voice telephone number, email address, and facsimile telephone number.
[5] 协议必须提供服务来注册描述人类和组织实体的社会信息。社会信息的登记不得限于特定的时间段。社会信息可能包括姓名（个人姓名、组织名称或两者）、地址（包括街道地址、城市、州或省（如适用）、邮政编码和国家）、语音电话号码、电子邮件地址和传真电话号码。
[6] Protocol services to register an object MUST be available to all authorized registrars.
[6] 注册对象的协议服务必须可供所有授权注册者使用。
[1] The protocol MUST provide services to associate name servers with domain names to delegate authority for zones. A domain name MAY have multiple authoritative name servers. Name servers MAY be authoritative for multiple zones.
[1] 协议必须提供将名称服务器与域名关联的服务，以便为区域委派权限。一个域名可以有多个权威名称服务器。名称服务器可能是多个区域的权威服务器。
[2] The protocol MUST provide services to associate IP addresses with name servers. A name server MAY have multiple IP addresses. An IP address MAY be associated with multiple name server registrations.
[2] 协议必须提供将IP地址与名称服务器关联的服务。名称服务器可以有多个IP地址。IP地址可能与多个名称服务器注册相关联。
[3] The protocol MUST provide services to associate social information with other objects. Social information associations MUST be identified by type. "Registrant" is an example social information type that might be associated with an object such as a domain name.
[3] 协议必须提供将社会信息与其他对象关联的服务。社会信息协会必须按类型确定。“注册人”是一个示例社会信息类型，可能与域名等对象关联。
[4] The protocol MUST provide services to associate object management capabilities on a per-registrar basis.
[4] 协议必须提供服务，以便在每个注册器的基础上关联对象管理功能。
[5] Some managed objects represent shared resources that might be referenced by multiple registrars. The protocol MUST provide services that allow a registrar to associate an existing shared resource object with other registered objects sponsored by a second registrar. For example, authority for the example.tld zone (example.tld domain object managed by registrar X) and authority for the test.tld zone (test.tld domain object managed by registrar Y) might be delegated to server ns1.example.tld (managed by registrar X). Registrar X maintains administrative control over domain object example.tld and server object ns1.example.tld, and registrar Y maintains administrative control over domain object test.tld. Registrar Y does not have administrative control over server object ns1.example.tld.
[5] 一些托管对象表示多个注册器可能引用的共享资源。协议必须提供服务，允许注册器将现有共享资源对象与第二个注册器赞助的其他注册对象相关联。例如，example.tld区域的权限（example.tld域对象由注册器X管理）和test.tld区域的权限（test.tld域对象由注册器Y管理）可以委托给服务器ns1.example.tld（由注册器X管理）。注册器X维护对域对象example.tld和服务器对象ns1.example.tld的管理控制，注册器Y维护对域对象test.tld的管理控制。注册器Y对服务器对象ns1.example.tld没有管理控制权。
[1] The protocol MUST provide services to update information associated with registered Internet domain names.
[1] 协议必须提供更新与已注册的Internet域名相关的信息的服务。
[2] The protocol MUST provide services to update information associated with registered name servers.
[2] 协议必须提供服务来更新与注册名称服务器关联的信息。
[3] The protocol MUST provide services to update social information associated with registered human and organizational entities.
[3] 协议必须提供服务，以更新与已注册的个人和组织实体相关的社会信息。
[4] The protocol MUST provide services to limit requests to update a registered object to the registrar that currently sponsors the registered object.
[4] 协议必须提供服务，以限制向当前发起注册对象的注册者更新注册对象的请求。
[5] The protocol MUST provide services to explicitly reject unauthorized attempts to update a registered object.
[5] 协议必须提供明确拒绝更新已注册对象的未经授权尝试的服务。
[1] The protocol MUST provide services to transfer domain names among authorized registrars. Name servers registered in a domain being transferred MUST be transferred along with the domain itself. For example, name servers "ns1.example.tld" and "ns2.example.tld" MUST be implicitly transferred when domain "example.tld" is transferred.
[1] 该协议必须提供在授权注册商之间传输域名的服务。在正在传输的域中注册的名称服务器必须与域本身一起传输。例如，在传输域“example.tld”时，必须隐式传输名称服务器“ns1.example.tld”和“ns2.example.tld”。
[2] The protocol MUST provide services to describe all objects, including associated objects, that are transferred as a result of an object transfer.
[2] 协议必须提供服务来描述作为对象传输结果传输的所有对象，包括关联对象。
[3] The protocol MUST provide services to transfer social information objects among authorized registrars.
[3] 协议必须提供服务，以便在授权注册者之间传输社会信息对象。
[4] Protocol transfer requests MUST be initiated by the registrar who wishes to become the new administrator of an object.
[4] 协议传输请求必须由希望成为对象新管理员的注册者发起。
[5] The protocol MUST provide services to confirm registrar authorization to transfer an object.
[5] 协议必须提供服务，以确认注册器对传输对象的授权。
[6] The protocol MUST provide services that allow the requesting registrar to cancel a requested object transfer before the request has been approved or rejected by the original sponsoring registrar. Requests to cancel the transfer of registered objects MUST be limited to the registrar that requested transfer of the registered object. Unauthorized attempts to cancel the transfer of a registered object MUST be explicitly rejected.
[6] 协议必须提供服务，允许请求登记员在请求被原始发起登记员批准或拒绝之前取消请求的对象转移。取消登记对象转让的请求必须限于请求转让登记对象的登记员。必须明确拒绝取消已注册对象传输的未经授权尝试。
[7] The protocol MUST provide services that allow the original sponsoring registrar to approve or reject a requested object transfer. Requests to approve or reject the transfer of registered objects MUST be limited to the registrar that currently sponsors the registered object. Unauthorized attempts to approve or reject the transfer of a registered object MUST be explicitly rejected.
[7] 协议必须提供服务，允许原始发起注册人批准或拒绝请求的对象传输。批准或拒绝转让登记客体的请求必须限于目前赞助登记客体的登记官。必须明确拒绝批准或拒绝已注册对象转让的未经授权尝试。
[8] The protocol MUST provide services that allow both the original sponsoring registrar and the potential new registrar to monitor the status of both pending and completed transfer requests.
[8] 协议必须提供服务，使原始发起登记员和潜在的新登记员能够监测未决和已完成的转移请求的状态。
[9] Transfer of an object MAY extend the object's registration period. If an object's registration period will be extended as the result of a transfer, the new expiration date and time MUST be returned after successful completion of a transfer request.
[9] 转让标的物可以延长标的物的登记期。如果对象的注册期因转移而延长，则必须在成功完成转移请求后返回新的过期日期和时间。
[10] Requests to initiate the transfer of a registered object MUST be available to all authorized registrars.
[10] 所有授权登记人都必须可以申请发起登记对象的转让。
[11] Registrars might become non-functional and unable to respond to transfer requests. It might be necessary for one registrar to assume management responsibility for the objects associated with another registrar in the event of registrar failure. The protocol MUST NOT restrict the ability to transfer objects in the event of registrar failure.
[11] 登记员可能无法正常工作，无法响应转账请求。在登记员失败的情况下，一名登记员可能有必要对与另一名登记员有关的物品承担管理责任。协议不得限制在注册失败的情况下传输对象的能力。
[1] The protocol MUST provide services to renew or extend the validity period of registered domain names. If applicable, the new expiration date and time MUST be returned after successful completion of a request to renew or extend the validity period.
[1] 协议必须提供更新或延长注册域名有效期的服务。如果适用，在成功完成续订或延长有效期的请求后，必须返回新的到期日期和时间。
[2] Requests to renew or extend the validity period of a registered object MUST be limited to the registrar that currently sponsors the registered object. Unauthorized attempts to renew or extend the validity period of a registered object MUST be explicitly rejected.
[2] 更新或延长注册对象有效期的请求必须限于当前发起注册对象的注册官。必须明确拒绝未经授权的更新或延长注册对象有效期的尝试。
[1] The protocol MUST provide services to remove a domain name from the registry.
[1] 协议必须提供从注册表中删除域名的服务。
[2] The protocol MUST provide services to remove a name server from the registry.
[2] 协议必须提供从注册表中删除名称服务器的服务。
[3] The protocol MUST provide services to remove a social information object from the registry.
[3] 协议必须提供从注册表中删除社交信息对象的服务。
[4] Requests to remove a registered object MUST be limited to the registrar that currently sponsors the registered object. Unauthorized attempts to remove a registered object MUST be explicitly rejected.
[4] 移除注册对象的请求必须限于当前赞助该注册对象的注册人。必须明确拒绝移除已注册对象的未经授权尝试。
This section describes requirements for a lightweight query mechanism whose sole purpose is to determine if an object exists in a registry.
本节描述了轻量级查询机制的需求，该机制的唯一目的是确定注册表中是否存在对象。
[1] The protocol MUST provide services to determine if a domain name exists in the registry. Domain names MUST be searchable by fully qualified name.
[1] 协议必须提供服务来确定注册表中是否存在域名。域名必须可以通过完全限定名进行搜索。
[2] The protocol MUST provide services to determine if a name server exists in the registry. Name servers MUST be searchable by fully qualified name.
[2] 协议必须提供服务来确定注册表中是否存在名称服务器。名称服务器必须可以通过完全限定的名称进行搜索。
[3] The protocol MUST provide services to determine if a social information object exists in the registry. Social information MUST be searchable by a registry-unique identifier.
[3] 协议必须提供服务来确定注册表中是否存在社交信息对象。社会信息必须可以通过注册表唯一标识符进行搜索。
[4] A query to determine if an object exists in the registry MUST return only a positive or negative response so that server software that responds to this query can be optimized for speed.
[4] 确定注册表中是否存在对象的查询必须只返回肯定或否定响应，以便响应此查询的服务器软件可以优化速度。
[5] Requests to determine the existence of a registered object MUST be available to all authorized registrars.
[5] 所有经授权的注册人必须能够获得确定注册物体存在的请求。
This section describes requirements for a query mechanism whose purpose is to provide detailed information describing objects that exist in a registry.
本节描述查询机制的需求，该机制的目的是提供描述注册表中存在的对象的详细信息。
[1] The protocol MUST provide services to retrieve information describing a domain name from the registry. Returned information MUST include the identifier of the current sponsoring registrar, the identifier of the registrar that originally registered the domain, the creation date and time, the expiration date and time (if any), the date and time of the last successful update (if any), the identifier of the registrar that performed the last update, the date and time of last completed transfer (if any), the current status of the domain, authorization information, identifiers describing social information associated with the domain, and the subordinate name servers registered in the domain. Authorization information MUST only be returned to the current sponsoring registrar.
[1] 协议必须提供从注册表检索描述域名的信息的服务。返回的信息必须包括当前发起注册商的标识符、最初注册域的注册商的标识符、创建日期和时间、到期日期和时间（如有）、上次成功更新的日期和时间（如有）、执行上次更新的注册商的标识符，上次完成传输的日期和时间（如有）、域的当前状态、授权信息、描述与域关联的社会信息的标识符以及在域中注册的从属名称服务器。授权信息只能返回给当前的发起注册人。
[2] The protocol MUST provide services to retrieve information describing a name server from the registry. Returned information MUST include the identifier of the current sponsoring registrar, the identifier of the registrar that originally registered the name server, the creation date and time, the date and time of the last successful update (if any), the identifier of the registrar that performed the last update, the date and time of last completed transfer (if any), and the IP addresses currently associated with the name server.
[2] 协议必须提供从注册表检索描述名称服务器的信息的服务。返回的信息必须包括当前发起注册人的标识符、最初注册名称服务器的注册人的标识符、创建日期和时间、上次成功更新的日期和时间（如有）、执行上次更新的注册人的标识符，上次完成传输的日期和时间（如果有），以及当前与名称服务器关联的IP地址。
[3] The protocol MUST provide services to retrieve social information from the registry. Returned information MUST include identification attributes (which MAY include name, address, telephone numbers, and email address), the identifier of the registrar that originally
[3] 协议必须提供从注册表检索社会信息的服务。返回的信息必须包括标识属性（可能包括姓名、地址、电话号码和电子邮件地址），即最初使用的注册者的标识符
registered the information, the creation date and time, the date and time of the last successful update (if any), the identifier of the registrar that performed the last update, the date and time of last completed transfer (if any), and authorization information. Authorization information MUST only be returned to the current sponsoring registrar.
注册信息、创建日期和时间、上次成功更新的日期和时间（如有）、执行上次更新的注册人的标识符、上次完成传输的日期和时间（如有）以及授权信息。授权信息只能返回给当前的发起注册人。
[4] The protocol MUST provide services to identify all associated object references, such as name servers associated with domains (including delegations and hierarchical relationships) and contacts associated with domains. This information MUST be visible if the object associations have an impact on the success or failure of protocol operations.
[4] 协议必须提供识别所有关联对象引用的服务，例如与域关联的名称服务器（包括委托和层次关系）以及与域关联的联系人。如果对象关联对协议操作的成功或失败有影响，则此信息必须可见。
[5] Requests to retrieve information describing a registered object MAY be granted by the registrar that currently sponsors the registered object. Unauthorized attempts to retrieve information describing a registered object MUST be explicitly rejected.
[5] 检索描述注册对象的信息的请求可由当前发起该注册对象的注册官批准。必须明确拒绝检索描述已注册对象的信息的未经授权的尝试。
[1] The protocol MUST provide status indicators that identify the operational state of a domain name. Indicators MAY be provided to identify a newly created state (the domain has been registered but has not yet appeared in a zone), a normal active state (the domain can be modified and is published in a zone), an inactive state (the domain can be modified but is not published in a zone because it has no authoritative name servers), a hold state (the domain can not be modified and is not published in a zone), a lock state (the domain can not be modified and is published in a zone), a pending transfer state, and a pending removal state.
[1] 协议必须提供识别域名运行状态的状态指示器。可以提供指示符来标识新创建的状态（域已注册但尚未出现在区域中）、正常活动状态（域可以修改并在区域中发布）、非活动状态（域可以修改但未在区域中发布，因为它没有权威名称服务器）、保留状态（无法修改域且未在区域中发布）、锁定状态（无法修改域且已在区域中发布）、挂起传输状态和挂起删除状态。
[2] If provided, protocol indicators for hold and lock status MUST allow independent setting by both registry and registrar.
[2] 如果提供，保持和锁定状态的协议指示器必须允许注册表和注册器进行独立设置。
[3] A domain MAY have multiple statuses at any given time. Some statuses MAY be mutually exclusive.
[3] 一个域在任何给定时间都可能有多个状态。某些状态可能相互排斥。
[1] The protocol MUST provide services that unambiguously note the success or failure of every transaction. Individual success and error conditions MUST be noted distinctly.
[1] 协议必须提供明确记录每个事务成功或失败的服务。必须清楚地注意个别成功和错误情况。
External interfaces define the interaction points between a system and entities that communicate with the system. Specific areas of interest include user interfaces, hardware interfaces, software interfaces, and communications interfaces.
外部接口定义了系统和与系统通信的实体之间的交互点。感兴趣的特定领域包括用户界面、硬件界面、软件界面和通信界面。
[1] The protocol MUST define a wire format for data exchange, not an application design for user, hardware, or software interfaces so that any application able to create the same bits on the wire, and to maintain the image of the same integrity constraints, is a valid implementation of the protocol.
[1] 协议必须定义数据交换的有线格式，而不是用户、硬件或软件接口的应用程序设计，以便任何能够在有线上创建相同位并维护相同完整性约束的映像的应用程序都是协议的有效实现。
[1] Registries, registrars, and registrants interact using a wide spectrum of communications interfaces built upon multiple protocols, including transport layer protocols such as TCP and application layer protocols such as SMTP. The protocol MUST only be run over IETF approved protocols that feature congestion control, such as TCP and SCTP.
[1] 注册中心、注册者和注册者使用基于多种协议的广泛通信接口进行交互，包括传输层协议（如TCP）和应用层协议（如SMTP）。该协议只能在IETF批准的具有拥塞控制功能的协议上运行，如TCP和SCTP。
[1] Run-time performance is an absolutely critical aspect of protocol usability. While performance is very heavily dependent on the hardware and software architecture that implements a protocol, protocol features can have a direct impact on the ability of the underlying architecture to provide optimal performance. The protocol MUST be usable in both high volume and low volume operating environments.
[1] 运行时性能是协议可用性的一个绝对关键的方面。虽然性能在很大程度上取决于实现协议的硬件和软件体系结构，但协议功能会直接影响底层体系结构提供最佳性能的能力。该协议必须在高容量和低容量操作环境中都可用。
Protocol designers need to be aware of issues beyond functional and interface requirements when balancing protocol design decisions. This section describes additional factors that might have an impact on protocol design, including standards compliance and hardware limitations.
在平衡协议设计决策时，协议设计者需要意识到功能和接口需求以外的问题。本节介绍可能影响协议设计的其他因素，包括标准符合性和硬件限制。
[1] The protocol MUST conform to current IETF standards. Standards for domain and host name syntax, IP address syntax, security, and transport are particularly relevant. Emerging standards for the Domain Name System MUST be considered as they approach maturity.
[1] 协议必须符合当前的IETF标准。域名和主机名语法、IP地址语法、安全性和传输标准尤其相关。域名系统的新兴标准在接近成熟时必须予以考虑。
[2] The protocol MUST NOT reinvent services offered by lower layer protocol standards. For example, the use of a transport that provides reliability is to be chosen over use of a non-reliable transport with the protocol itself using retransmission to achieve reliability.
[2] 该协议不得重新创造低层协议标准提供的服务。例如，要选择使用提供可靠性的传输，而不是使用不可靠的传输，协议本身使用重传来实现可靠性。
[1] The protocol MUST NOT define any features that preclude hardware independence.
[1] 协议不得定义任何妨碍硬件独立性的功能。
Elements of service beyond functional and interface requirements are essential factors to consider as part of a protocol design effort. This section describes several important service elements to be addressed by protocol designers, including reliability, availability, scalability, maintainability, extensibility, and security.
超出功能和接口要求的服务元素是作为协议设计工作的一部分考虑的重要因素。本节描述了协议设计者需要解决的几个重要服务元素，包括可靠性、可用性、可扩展性、可维护性、可扩展性和安全性。
[1] Reliability is a measure of the extent to which a protocol provides a consistent, dependable level of service. Reliability is an important attribute for a domain name management protocol. An unreliable protocol increases the risk of data exchange errors, which at one extreme can have a direct impact on protocol usability and at the other extreme can introduce discontinuity between registry and registrar data stores. The protocol MUST include features that maximize reliability at the application protocol layer. Services provided by underlying transport, session, and presentation protocols SHOULD also be considered when addressing application protocol reliability.
[1] 可靠性是对协议提供一致、可靠服务水平的程度的度量。可靠性是域名管理协议的一个重要属性。不可靠的协议会增加数据交换错误的风险，一个极端会直接影响协议的可用性，另一个极端会在注册表和注册器数据存储之间引入不连续性。协议必须包括在应用程序协议层实现可靠性最大化的功能。在解决应用程序协议可靠性问题时，还应考虑底层传输、会话和表示协议提供的服务。
[2] The protocol MUST be run over the most reliable transport option available in a given environment. The protocol MUST NOT implement a service that is otherwise available in an applicable standard transport.
[2] 协议必须在给定环境中可用的最可靠传输选项上运行。协议不得实现适用标准传输中可用的服务。
[3] Default protocol actions for when a request or event times out MUST be well defined.
[3] 必须明确定义请求或事件超时时的默认协议操作。
[1] Availability is a measure of the extent to which the services provided by a protocol are accessible for an intended use. Availability of an application layer protocol is primarily dependent on the software and hardware systems that implement the protocol.
[1] 可用性是衡量协议提供的服务可用于预期用途的程度。应用层协议的可用性主要取决于实现该协议的软件和硬件系统。
The protocol MUST NOT include any features that impinge on the underlying availability of the software and hardware systems needed to service the protocol.
协议不得包含任何影响协议服务所需软件和硬件系统基础可用性的功能。
[1] Scalability is a measure of the extent to which a protocol can accommodate use growth while preserving acceptable operational characteristics. The protocol MUST be capable of operating at an acceptable level as the load on registry and registrar systems increases.
[1] 可伸缩性是对协议在保持可接受的操作特性的同时能够适应使用增长的程度的度量。随着注册表和注册器系统负载的增加，协议必须能够在可接受的水平上运行。
[1] Maintainability is a measure of the extent to which a protocol can be adapted or modified to address unforeseen operational needs or defects. The protocol SHOULD be developed under the nominal working group processes of the IETF to provide a well-known mechanism for ongoing maintenance.
[1] 可维护性是一种衡量协议可调整或修改的程度，以解决不可预见的操作需求或缺陷。该协议应在IETF的名义工作组过程下制定，以提供一个众所周知的持续维护机制。
[1] Extensibility is a measure of the extent to which a protocol can be adapted for future uses that were not readily evident when the protocol was originally designed. The protocol SHOULD provide features that at a minimum allow for the management of new object types without requiring revisions to the protocol itself.
[1] 可扩展性是一种衡量协议在多大程度上可以适应未来的用途的指标，这些用途在协议最初设计时并不明显。协议应提供至少允许管理新对象类型的功能，而无需修改协议本身。
[2] The requirements described in this document are not intended to limit the set of objects that might be managed by the protocol. The protocol MUST include features that allow extension to object types that are not described in this document.
[2] 本文档中描述的要求无意限制协议可能管理的对象集。协议必须包括允许扩展到本文档中未描述的对象类型的功能。
[3] The protocol MUST provide an optional field within all commands whose format and use will be controlled by individual registry policy.
[3] 协议必须在其格式和使用将由单个注册表策略控制的所有命令中提供可选字段。
[1] Transactional privacy and integrity services MUST be available at some protocol layer.
[1] 事务隐私和完整性服务必须在某些协议层可用。
[2] This document describes requirements for basic user identification and authentication services. A generic protocol MAY include additional security services to protect against the attacks described here. A generic protocol MUST depend on other-layered protocols to provide security services that are not provided in the generic protocol itself. A generic protocol that relies on security
[2] 本文件描述了基本用户标识和身份验证服务的要求。通用协议可包括额外的安全服务，以防止此处所述的攻击。通用协议必须依赖于其他分层协议来提供通用协议本身未提供的安全服务。依赖于安全性的通用协议
services from other-layered protocols MUST specify the protocol layers needed to provide security services.
来自其他分层协议的服务必须指定提供安全服务所需的协议层。
Certain aspects of anticipated operational environments have to be considered when designing a generic registry-registrar protocol. Areas of concern include database operations, operations, site adaptation, and data collection.
在设计通用注册表注册器协议时，必须考虑预期操作环境的某些方面。关注领域包括数据库操作、操作、站点调整和数据收集。
[1] The protocol MUST NOT have any database dependencies. However, efficient use of database operations and resources has to be considered as part of the protocol design effort. The protocol SHOULD provide atomic features that can be efficiently implemented to minimize database load.
[1] 协议不得具有任何数据库依赖项。但是，必须将数据库操作和资源的有效使用视为协议设计工作的一部分。该协议应提供可有效实现的原子特性，以最小化数据库负载。
[1] Registry-registrar interactions at the protocol level SHOULD operate without human intervention. However, intermediate services that preserve the integrity of the protocol MAY be provided. For example, an intermediate service that determines if a registrant is authorized to register a name in a name space can be provided.
[1] 协议级别的注册表注册器交互应在没有人为干预的情况下运行。然而，可以提供保持协议完整性的中间服务。例如，可以提供确定注册人是否被授权在名称空间中注册名称的中间服务。
[2] The protocol MUST provide services that allow clients and servers to maintain a consistent understanding of the current date and time to effectively manage objects with temporal properties.
[2] 协议必须提供服务，允许客户端和服务器保持对当前日期和时间的一致理解，以便有效地管理具有时间属性的对象。
[1] Registries and registrars have varying business and operational requirements. Several factors, including governance standards, local laws, customs, and business practices all play roles in determining how registries and registrars are operated. The protocol MUST be flexible enough to operate in diverse registry-registrar environments.
[1] 登记处和登记处有不同的业务和运营要求。若干因素，包括治理标准、当地法律、习俗和商业惯例，都在决定登记处和登记处的运作方式方面发挥作用。协议必须足够灵活，以在不同的注册表注册器环境中运行。
[1] Some of the data exchanged between a registrar and registry might be considered personal, private, or otherwise sensitive. Disclosure of such information might be restricted by laws and/or business practices. The protocol MUST provide services to identify data collection policies.
[1] 登记员和登记处之间交换的一些数据可能被视为个人、私人或其他敏感数据。此类信息的披露可能受到法律和/或商业惯例的限制。协议必须提供识别数据收集策略的服务。
[2] Some of the social information exchanged between a registrar and registry might be required to create, manage, or operate Internet or DNS infrastructure facilities, such as zone files. Such information is subject to public disclosure per relevant IETF standards.
[2] 创建、管理或操作Internet或DNS基础设施（如区域文件）可能需要注册中心和注册中心之间交换的一些社交信息。此类信息应根据相关IETF标准公开披露。
[1] [RFC1035] describes Internet host and domain names using characters traditionally found in a subset of the 7-bit US-ASCII character set. More recent standards, such as [RFC2130] and [RFC2277], describe the need to develop protocols for an international Internet. These and other standards MUST be considered during the protocol design process to ensure world-wide usability of a generic registry registrar protocol.
[1] [RFC1035]使用7位US-ASCII字符集子集中的传统字符描述Internet主机和域名。较新的标准，如[RFC2130]和[RFC2277]，描述了为国际互联网开发协议的必要性。在协议设计过程中必须考虑这些标准和其他标准，以确保通用注册表注册器协议的全球可用性。
[2] The protocol MUST allow exchange of data in formats consistent with current international agreements for the representation of such objects. In particular, this means that addresses MUST include country, that telephone numbers MUST start with the international prefix "+", and that appropriate thought be given to the usability of information in both local and international contexts. This means that some elements (like names and addresses) might need to be represented multiple times, or formatted for different contexts (for instance English/French in Canada, or Latin/ideographic in Japan).
[2] 该议定书必须允许以符合关于此类物体表示的现行国际协定的格式交换数据。特别是，这意味着地址必须包括国家，电话号码必须以国际前缀“+”开头，并适当考虑信息在本地和国际环境中的可用性。这意味着某些元素（如名称和地址）可能需要多次表示，或针对不同的上下文进行格式化（例如加拿大的英语/法语，或日本的拉丁语/表意文字）。
[3] All date and time values specified in a generic registry-registrar protocol MUST be expressed in Universal Coordinated Time. Dates and times MUST include information to represent a four-digit calendar year, a calendar month, a calendar day, hours, minutes, seconds, fractional seconds, and the time zone for Universal Coordinated Time. Calendars apart from the Gregorian calendar MUST NOT be used
[3] 通用注册表注册器协议中指定的所有日期和时间值必须以通用协调时间表示。日期和时间必须包含表示四位数日历年、日历月、日历日、小时、分钟、秒、分数秒以及通用协调时间时区的信息。不得使用公历以外的日历
This document does not require any action on the part of IANA. Protocol specifications that require IANA action MUST follow the guidelines described in [RFC2434].
本文件不要求IANA采取任何行动。需要IANA操作的协议规范必须遵循[RFC2434]中描述的指南。
Security services, including confidentiality, authentication, access control, integrity, and non-repudiation SHOULD be applied to protect interactions between registries and registrars as appropriate. Confidentiality services protect sensitive exchanged information from inadvertent disclosure. Authentication services confirm the claimed identity of registries and registrars before engaging in online transactions. Access control services control access to data and
安全服务，包括保密性、身份验证、访问控制、完整性和不可否认性，应酌情应用于保护注册中心和注册中心之间的交互。保密服务可保护交换的敏感信息不被无意中泄露。认证服务在进行在线交易之前确认登记处和登记人的身份。访问控制服务控制对数据和数据的访问
services based on identity. Integrity services guarantee that exchanged data has not been altered between the registry and the registrar. Non-repudiation services provide assurance that the sender of a transaction can not deny being the source of the transaction, and that the recipient cannot deny being the receiver of the transaction.
基于身份的服务。完整性服务保证注册中心和注册中心之间交换的数据不会被更改。不可抵赖服务保证交易的发送方不能否认自己是交易的来源，接收方不能否认自己是交易的接收方。
This document was originally written as an individual submission Internet-Draft. The provreg working group later adopted it as a working group document and provided many invaluable comments and suggested improvements. The author wishes to acknowledge the efforts of WG chairs Edward Lewis and Jaap Akkerhuis for their process and editorial contributions.
本文件最初是作为个人提交的互联网草案编写的。provreg工作组后来将其作为工作组文件通过，并提出了许多宝贵的意见和改进建议。作者希望感谢工作组主席Edward Lewis和Jaap Akkerhuis的工作过程和编辑贡献。
Specific comments that helped guide development of this document were provided by Harald Tveit Alvestrand, Christopher Ambler, Karl Auerbach, Jorg Bauer, George Belotsky, Eric Brunner-Williams, Jordyn Buchanan, Randy Bush, Bruce Campbell, Dan Cohen, Andre Cormier, Kent Crispin, Dave Crocker, Ayesha Damaraju, Lucio De Re, Mats Dufberg, Peter Eisenhauer, Sheer El-Showk, Urs Eppenberger, Patrik Faltstrom, Paul George, Patrick Greenwell, Jarle Greipsland, Olivier Guillard, Alf Hansen, Paul Hoffman, Paul Kane, Shane Kerr, Elmar Knipp, Mike Lampson, Matt Larson, Ping Lu, Klaus Malorny, Bill Manning, Michael Mealling, Patrick Mevzek, Peter Mott, Catherine Murphy, Martin Oldfield, Geva Patz, Elisabeth Porteneuve, Ross Wm. Rader, Budi Rahardjo, Annie Renard, Scott Rose, Takeshi Saigoh, Marcos Sanz, Marcel Schneider, J. William Semich, James Seng, Richard Shockey, Brian Spolarich, William Tan, Stig Venaas, Herbert Vitzthum, and Rick Wesson.
Harald Tveit Alvestrand、Christopher Ambler、Karl Auerbach、Jorg Bauer、George Belotsky、Eric Brunner Williams、Jordyn Buchanan、Randy Bush、Bruce Campbell、Dan Cohen、Andre Cormier、Kent Crispin、Dave Crocker、Ayesa Damaraju、Lucio De Re、Mats Dufberg、，彼得·艾森豪尔、谢尔·艾尔肖克、乌斯·艾彭伯格、帕特里克·法茨特罗姆、保罗·乔治、帕特里克·格林威尔、贾勒·格雷普兰、奥利维尔·吉拉德、阿尔夫·汉森、保罗·霍夫曼、保罗·凯恩、谢恩·科尔、埃尔玛·克尼普、迈克·兰普森、马特·拉森、平·路、克劳斯·马洛尼、比尔·曼宁、迈克尔·米林、帕特里克·梅夫泽克、彼得·莫特、凯瑟琳·墨菲、马丁·奥德菲尔德、，格瓦·帕茨，伊丽莎白·波特纽夫，罗斯·西蒙斯。雷德、布迪·拉哈德乔、安妮·雷纳德、斯科特·罗斯、塔克希·塞戈、马科斯·桑兹、马塞尔·施耐德、J·威廉·塞米奇、詹姆斯·森、理查德·肖基、布莱恩·斯波拉里奇、威廉·谭、斯蒂格·维纳斯、赫伯特·维茨坦和里克·韦森。
Normative References:
规范性引用文件：
[RFC2119] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
Informative References:
参考资料：
[RFC1035] Mockapetris, P., "Domain Names - Implementation and Specification", STD 13, RFC 1035, November 1987.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[RFC2130] Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson, R., Cripsin, M. and P. Svanberg, "The Report of the IAB Character Set Workshop", RFC 2130, April 1997.
[RFC2130]Weider，C.，Preston，C.，Simonsen，K.，Alvestrand，H.，Atkinson，R.，Cripsin，M.和P.Svanberg，“IAB字符集研讨会报告”，RFC 21301997年4月。
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998.
[RFC2277]Alvestrand，H.，“IETF字符集和语言政策”，BCP 18，RFC 2277，1998年1月。
Scott Hollenbeck VeriSign Global Registry Services 21345 Ridgetop Circle Dulles, VA 20166-6503 USA
Scott Hollenbeck VeriSign全球注册服务21345 Ridgetop Circle Dulles，弗吉尼亚州20166-6503美国
EMail: shollenbeck@verisign.com
EMail: shollenbeck@verisign.com
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
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编辑功能的资金目前由互联网协会提供。