Network Working Group S. Hollenbeck
Request for Comments: 2832 M. Srivastava
Category: Informational Network Solutions, Inc. Registry
May 2000
Network Working Group S. Hollenbeck
Request for Comments: 2832 M. Srivastava
Category: Informational Network Solutions, Inc. Registry
May 2000
NSI Registry Registrar Protocol (RRP) Version 1.1.0
NSI注册表注册器协议（RRP）1.1.0版
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 a protocol for the registration and management of second level domain names and associated name servers in both generic Top Level Domains (gTLDs) and country code Top Level Domains (ccTLDs). This protocol was developed by the Network Solutions Registry for use within the Shared Registration System and is being published "as-is" to document the protocol implementation developed by the Network Solutions, Inc. Registry.
本文档描述了通用顶级域（GTLD）和国家代码顶级域（CCTLD）中二级域名和相关名称服务器的注册和管理协议。本协议由Network Solutions Registry开发，用于共享注册系统中，并将“按原样”发布，以记录Network Solutions，Inc.注册表开发的协议实施。
Internet domain name registration typically involves three entities: a registrant who wishes to register a domain name, a registrar who provides services to the registrant, and a registry that provides services to the registrar while serving as the authoritative repository of all functional information required to resolve names registered in the registry's TLDs. This document describes a protocol for registry-registrar communication only. The protocol does not provide any registrant services.
互联网域名注册通常涉及三个实体：希望注册域名的注册人，向注册人提供服务的注册人，以及一个注册中心，该注册中心向注册中心提供服务，同时作为解析注册中心TLD中注册的名称所需的所有功能信息的权威存储库。本文档描述了仅用于注册表注册器通信的协议。该协议不提供任何注册人服务。
This document is being discussed on the "rrp" mailing list. To join the list, send a message to <majordomo@NSIRegistry.com> with the words "subscribe rrp" in the body of the message. There is also a web site for the mailing list archives at <http://www.NSIRegistry.net/maillist/rrp>.
本文件正在“rrp”邮件列表中讨论。若要加入列表，请向发送消息<majordomo@NSIRegistry.com>消息正文中带有“订阅rrp”字样。还有一个用于邮件列表存档的网站<http://www.NSIRegistry.net/maillist/rrp>.
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 [MUSTSHOULD]. Further,
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[必须”中的说明进行解释。进一步的
the term "implicit attribute" refers to an entity attribute whose value is derived either from another attribute or is dependent on an established RRP session.
术语“隐式属性”是指其值从另一个属性派生或依赖于已建立的RRP会话的实体属性。
In examples, "C:" represents lines sent by the registrar client and "S:" represents lines sent by the registry server.
在示例中，“C:”表示注册器客户端发送的行，“S:”表示注册服务器发送的行。
The term "System" is used in this document to collectively refer to this protocol and the software and hardware that implements the protocol.
本文件中的术语“系统”是指本协议以及实施本协议的软件和硬件的统称。
Table of Contents
目录
1. Introduction ................................................. 3
2. Security Services ............................................ 4
2.1 Connection Security ......................................... 4
2.2 System Data Security ........................................ 5
3. Connection Model ............................................. 5
4. Protocol Description ......................................... 6
4.1 Request Format .............................................. 7
4.2 Response Format ............................................. 8
4.3 Protocol Commands ........................................... 8
4.3.1 ADD ....................................................... 8
4.3.2 CHECK ..................................................... 11
4.3.3 DEL ....................................................... 12
4.3.4 DESCRIBE .................................................. 14
4.3.5 MOD ....................................................... 14
4.3.6 QUIT ...................................................... 16
4.3.7 RENEW ..................................................... 17
4.3.8 SESSION ................................................... 18
4.3.9 STATUS .................................................... 18
4.3.10 TRANSFER ................................................. 21
5. Response Codes ............................................... 23
5.1 Response Code Summary ....................................... 23
5.2 Command-Response Correspondence ............................. 28
6. Domain Status Codes .......................................... 29
6.1 Domain Status Code Description .............................. 30
7. Formal Syntax ................................................ 30
8. Internationalization ......................................... 35
9. Known Issues ................................................. 35
10. Security Considerations ..................................... 37
11. IANA Considerations ......................................... 37
12. References .................................................. 37
13. Acknowledgments ............................................. 38
14. Authors' Addresses .......................................... 38
15. Full Copyright Statement .................................... 39
1. Introduction ................................................. 3
2. Security Services ............................................ 4
2.1 Connection Security ......................................... 4
2.2 System Data Security ........................................ 5
3. Connection Model ............................................. 5
4. Protocol Description ......................................... 6
4.1 Request Format .............................................. 7
4.2 Response Format ............................................. 8
4.3 Protocol Commands ........................................... 8
4.3.1 ADD ....................................................... 8
4.3.2 CHECK ..................................................... 11
4.3.3 DEL ....................................................... 12
4.3.4 DESCRIBE .................................................. 14
4.3.5 MOD ....................................................... 14
4.3.6 QUIT ...................................................... 16
4.3.7 RENEW ..................................................... 17
4.3.8 SESSION ................................................... 18
4.3.9 STATUS .................................................... 18
4.3.10 TRANSFER ................................................. 21
5. Response Codes ............................................... 23
5.1 Response Code Summary ....................................... 23
5.2 Command-Response Correspondence ............................. 28
6. Domain Status Codes .......................................... 29
6.1 Domain Status Code Description .............................. 30
7. Formal Syntax ................................................ 30
8. Internationalization ......................................... 35
9. Known Issues ................................................. 35
10. Security Considerations ..................................... 37
11. IANA Considerations ......................................... 37
12. References .................................................. 37
13. Acknowledgments ............................................. 38
14. Authors' Addresses .......................................... 38
15. Full Copyright Statement .................................... 39
This document describes the specifications for the NSI Registry Registrar Protocol (RRP) version 1.1.0, a TCP-based, 7-bit US-ASCII text protocol that permits multiple registrars to provide second level Internet domain name registration services in the top level domains (TLDs) administered by a TLD registry. RRP is specified using Augmented Backus-Nauer Form (ABNF) as described in [ABNF]. Note that all ABNF string literals are case-insensitive and the examples provided in this document may use mixed case to improve readability.
本文件描述了NSI注册机构协议（RRP）版本1.1.0的规范，该协议是一种基于TCP的7位US-ASCII文本协议，允许多个注册机构在TLD注册机构管理的顶级域（TLD）中提供二级Internet域名注册服务。RRP使用[ABNF]中所述的增广巴科斯诺尔形式（ABNF）指定。请注意，所有ABNF字符串文字都不区分大小写，本文档中提供的示例可能使用大小写混合，以提高可读性。
RRP was developed by the Network Solutions, Inc. Registry under the auspices of the Shared Registration System program. The protocol was initially deployed in April 1999 as part of a test bed implementation of the Shared Registration System with five registrars. Additional registrars began using the protocol in July 1999. The operational experiences of both the registry and the registrars identified several "lessons learned" which have been documented here as "Known Issues".
RRP由Network Solutions，Inc.注册中心在共享注册系统计划的支持下开发。该议定书最初于1999年4月部署，作为与五名登记员共享登记系统试验台实施的一部分。其他登记员于1999年7月开始使用该议定书。书记官处和书记官长的业务经验确定了若干“经验教训”，这些经验教训在这里被记录为“已知问题”。
This document provides both a description of a protocol and notice of learned operational issues that may be useful as first steps in developing a standards track domain registration services protocol. This document and the protocol it describes may be modified in the future based on continued operational experience and community reaction.
本文档提供了协议的描述和了解到的操作问题的通知，这些问题可能是开发标准跟踪域注册服务协议的第一步。本文件及其描述的协议可能在未来根据持续运行经验和社区反应进行修改。
The registry stores information about registered domain names and associated name servers. A domain name's data includes its name, name servers, registrar, registration expiration date, and status. A name server's data includes its server name, IP addresses, and registrar. A registrar MAY perform the following registration service procedures using RRP:
注册表存储有关已注册域名和关联名称服务器的信息。域名的数据包括其名称、名称服务器、注册商、注册截止日期和状态。名称服务器的数据包括其服务器名称、IP地址和注册器。注册官可使用RRP执行以下注册服务程序：
- Determine if a domain name has been registered. - Register a domain name. - Renew the registration of a domain name. - Cancel the registration of a domain name. - Update the name servers of a domain name. - Transfer a domain name from another registrar. - Examine the status of domain names that the registrar has registered. - Modify the status of domain names that the registrar has registered. - Determine if a name server has been registered. - Register a name server. - Update the IP addresses of a name server.
- 确定域名是否已注册。-注册一个域名更新域名注册。-取消域名注册。-更新域名的名称服务器。-从另一个注册商处转移域名。-检查注册商已注册的域名的状态。-修改注册人已注册的域名的状态。-确定是否已注册名称服务器。-注册一个名称服务器。-更新名称服务器的IP地址。
- Delete a name server. - Examine the status of name servers that the registrar has registered.
- 删除名称服务器。-检查注册器已注册的名称服务器的状态。
All RRP commands include features to provide idempotency. That is, the effect of each command is the same if the command is executed once or if the command is executed multiple times. This property is extremely useful in situations when a command is retried due to an error condition that results in a missed command response and a command retry is attempted. Command retries will be caught by the System and rejected with an appropriate error response code. Command parameters that do not provide idempotency will be explained fully as part of the appropriate command description.
所有RRP命令都包含提供幂等性的功能。也就是说，如果命令执行一次或多次，则每个命令的效果相同。此属性在由于错误条件而重试命令时非常有用，该错误条件会导致错过命令响应，并且尝试重试命令。系统将捕获命令重试，并使用适当的错误响应代码拒绝。不提供幂等性的命令参数将作为相应命令描述的一部分进行完整解释。
RRP provides only basic password-based registrar authentication services. Additional security services, including privacy and registrar authentication using public key cryptography, are provided through other System features.
RRP只提供基本的基于密码的注册认证服务。通过其他系统功能提供额外的安全服务，包括使用公钥加密的隐私和注册认证。
Each RRP session MUST be encrypted using the Secure Socket Layer (SSL) v3.0 protocol as specified in [SSL]. SSL provides privacy services that reduce the risk of inadvertent disclosure of registrar-sensitive information, such as the registrar's user identifier and password.
必须使用[SSL]中指定的安全套接字层（SSL）v3.0协议对每个RRP会话进行加密。SSL提供隐私服务，可降低无意中泄露注册官敏感信息（如注册官的用户标识符和密码）的风险。
SSL supports mutual authentication of both the client and server using signed digital certificates. The Shared Registration System implemented by the NSI Registry requires digital certificates issued by a commercial certification authority for both registrar clients and public registry RRP servers. Both the registrar client and the public registry RRP server are authenticated when establishing an SSL connection. Further, a registrar MUST be authenticated when establishing an RRP connection via the RRP SESSION command by providing a registrar user identifier and password known only to the registrar and the System. Registrars may change their session password at any time using the RRP SESSION command.
SSL支持使用签名数字证书对客户端和服务器进行相互身份验证。NSI注册中心实施的共享注册系统要求商业认证机构为注册中心客户端和公共注册中心RRP服务器颁发数字证书。在建立SSL连接时，注册器客户端和公共注册表RRP服务器都经过身份验证。此外，当通过RRP会话命令建立RRP连接时，必须通过提供仅注册器和系统知道的注册器用户标识符和密码来认证注册器。注册者可随时使用RRP会话命令更改其会话密码。
The SSL protocol is not an IETF Standards Track protocol. The Transport Layer Security protocol, specified in [TLS], is a Standards Track protocol that provides SSL v3.0 compatibility features.
SSL协议不是IETF标准跟踪协议。[TLS]中指定的传输层安全协议是提供SSL v3.0兼容性功能的标准跟踪协议。
The System stores information about the registered domain names and their name servers. Only the current registrar of a registered domain name is authorized to query it, update its name servers, and cancel or renew it. Any registrar can request a transfer of a domain name and its associated name servers from another registrar to the requesting registrar. Only the current sponsoring registrar can receive and explicitly approve or reject domain transfer requests.
系统存储有关注册域名及其名称服务器的信息。只有注册域名的当前注册人有权查询、更新其名称服务器以及取消或续订该域名。任何注册商均可请求将域名及其相关名称服务器从另一注册商转移到请求注册商。只有当前的发起注册机构才能接收并明确批准或拒绝域转移请求。
Only a name server's registrar can query, update, and delete it. In general, name servers must be registered through the current registrar of the name server's parent domain name, though an implementation MAY allow use of name servers registered in other TLDs without specifying IP addresses or requiring parent domain registration. Use of ccTLD name servers for a gTLD domain name is one such example.
只有名称服务器的注册器可以查询、更新和删除它。通常，名称服务器必须通过名称服务器父域名的当前注册器注册，尽管实现可能允许使用在其他TLD中注册的名称服务器，而无需指定IP地址或要求父域名注册。将ccTLD名称服务器用于gTLD域名就是这样一个例子。
Name servers are implicitly transferred by the System when their parent domain name is transferred. In addition, a name server cannot be deleted if it is hosting domain names.
名称服务器在传输其父域名时由系统隐式传输。此外，如果名称服务器承载域名，则无法将其删除。
IANA has assigned TCP port 648 for RRP use. All RRP implementations MUST provide RRP services over SSL on TCP port 648. An RRP server MUST return a banner in the following format to confirm that a connection has been established:
IANA已将TCP端口648分配给RRP使用。所有RRP实施必须在TCP端口648上通过SSL提供RRP服务。RRP服务器必须返回以下格式的横幅，以确认已建立连接：
<registry name> RRP Server version <version><crlf>
<server build date and time><crlf>
<registry name> RRP Server version <version><crlf>
<server build date and time><crlf>
Each line ends with carriage return and line feed characters. The server build date and time string includes the day, month, date, time (specified in hours, minutes, and seconds), the local time zone, and the four-digit year. A dot (".") in column one on a line by itself marks the end of banner text.
每行以回车符和换行符结尾。服务器生成日期和时间字符串包括天、月、日期、时间（以小时、分钟和秒为单位指定）、本地时区和四位数的年份。一行第一列中的点（“.”）本身标记横幅文本的结尾。
Example
实例
A registrar successfully establishes a connection with the NSI Registry on TCP port 648:
注册器成功地在TCP端口648上与NSI注册表建立连接：
S:NSI RRP Server version 1.1.0 S:Mon Oct 25 20:20:34 EDT 1999 S:.
S:NSI RRP服务器版本1.1.0 S:Mon-Oct 25 20:20:34 EDT 1999 S:。
A typical RRP session will go through a number of states during its lifetime. Figure 1 illustrates the possible states of an RRP server.
一个典型的RRP会话在其生命周期中将经历许多状态。图1说明了RRP服务器的可能状态。
Initially, the server waits for a client connection and authentication (PRE). All client connections MUST be authenticated.
最初，服务器等待客户端连接和身份验证（PRE）。所有客户端连接都必须经过身份验证。
|
|
v
+-----------------+ Timeout
| Waiting for |-------------------+
Authentication Succeeded | Client | |
+---------| Authentication | Authentication |
| | (PRE) |-----+ Failed |
| +-----------------+ | |
| | |
V V |
+-----------+ Succeeded +--------------------+ |
|Waiting for|<-----------------| Waiting for | |
| Command |----------+ |Authentication Retry| |
| (WFC) | Timeout | | (WFR) | |
+-----------+ | +--------------------+ |
| ^ | | | |
| | | Timeout | | Failed |
Request V |Response | | | |
+-----------+ | V V V
| Executing | | +--------------------+
| Command | +--------->| Disconnected |
| (EXE) |-------------------->| (DIS) |
+-----------+ QUIT +--------------------+
|
|
v
+-----------------+ Timeout
| Waiting for |-------------------+
Authentication Succeeded | Client | |
+---------| Authentication | Authentication |
| | (PRE) |-----+ Failed |
| +-----------------+ | |
| | |
V V |
+-----------+ Succeeded +--------------------+ |
|Waiting for|<-----------------| Waiting for | |
| Command |----------+ |Authentication Retry| |
| (WFC) | Timeout | | (WFR) | |
+-----------+ | +--------------------+ |
| ^ | | | |
| | | Timeout | | Failed |
Request V |Response | | | |
+-----------+ | V V V
| Executing | | +--------------------+
| Command | +--------->| Disconnected |
| (EXE) |-------------------->| (DIS) |
+-----------+ QUIT +--------------------+
Figure 1: RRP Server Finite State Machine
图1:RRP服务器有限状态机
If the authentication fails, the server gives the client another chance to identify itself (WFR). If the authentication fails again, the server disconnects (DIS). Otherwise, the server waits for a request from the client (WFC). Upon receiving a request, the server executes it and responds to the client with the result (EXE). The server then waits again for another request from the client (WFC). If the client sends a QUIT command, the server ends the session and disconnects (DIS). To keep its state in sync with that of the server, the client SHOULD wait for a response from the server before sending another request on the same connection. The following table summarizes these states:
如果身份验证失败，服务器将为客户端提供另一个识别自身的机会（WFR）。如果身份验证再次失败，服务器将断开连接（DIS）。否则，服务器将等待来自客户端（WFC）的请求。收到请求后，服务器将执行该请求，并使用结果（EXE）响应客户端。然后，服务器再次等待来自客户端（WFC）的另一个请求。如果客户端发送QUIT命令，服务器将结束会话并断开连接（DIS）。要使其状态与服务器的状态保持同步，客户端应等待服务器的响应，然后再在同一连接上发送另一个请求。下表总结了这些状态：
PRE Waiting for client connection and authentication WFR Waiting for authentication retry WFC Waiting for a command from an authenticated client EXE Executing a command DIS Disconnected
预等待客户端连接和身份验证WFR等待身份验证重试WFC等待来自已验证客户端EXE的命令执行命令DIS DIS DIS DIS Disconnected
The WFR and WFC states MAY time out. An implementation SHOULD define inactivity timeout periods for these states based on System-specific factors, including (but not limited to) resource availability and security risk. In the absence of other factors, a default timeout period of 10 minutes SHOULD be used. The server MAY disconnect if the server is in one of these states and no message is received from the client during the timeout period.
WFR和WFC状态可能超时。实现应根据系统特定的因素，包括（但不限于）资源可用性和安全风险，为这些状态定义非活动超时时间。在没有其他因素的情况下，应使用10分钟的默认超时时间。如果服务器处于这些状态之一，并且在超时期间未收到来自客户端的消息，则服务器可能会断开连接。
An RRP request nominally consists of a command name, an entity block, command options, and an end-of-command delimiter. Command options and entity blocks collectively define command parameters and their specification is order independent; examples provided in this document specify entity blocks before command options.
RRP请求名义上由命令名、实体块、命令选项和命令结束分隔符组成。命令选项和实体块共同定义命令参数，其规格与顺序无关；本文档中提供的示例在命令选项之前指定实体块。
CommandName [EntityBlock] [CommandOptions] EndOfCommand
CommandName[EntityBlock][CommandOptions]EndOfCommand
A command name specifies the type of an RRP request. A command is a word or abbreviation terminated by a carriage-return linefeed (crlf) sequence.
命令名指定RRP请求的类型。命令是由回车换行符（crlf）序列终止的单词或缩写。
CommandName<crlf>
命令名<crlf>
An entity block specifies the data in an RRP request. It consists of attribute name-value pairs specifying the entity and all of the attributes of the entity. Each attribute name-value pair starts with the attribute name, followed by a colon, the attribute value, and is finally terminated by a carriage-return linefeed sequence. Entity blocks are optional for some requests.
实体块指定RRP请求中的数据。它由指定实体和实体所有属性的属性名称-值对组成。每个属性名称-值对以属性名称开头，后跟冒号（属性值），最后以回车换行序列终止。对于某些请求，实体块是可选的。
entityName:entityValue<crlf>
attributeName:attributeValue<crlf>
entityName:entityValue<crlf>
attributeName:attributeValue<crlf>
Command options specify control parameters for an RRP request. A command option starts with a dash, followed by the option name, a colon, the option value, and is finally terminated by a carriage-return linefeed sequence.
命令选项指定RRP请求的控制参数。命令选项以破折号开始，后跟选项名称、冒号和选项值，最后以回车换行序列终止。
-commandOptionName:commandOptionValue<crlf>
-commandOptionName:commandOptionValue<crlf>
An EndOfCommand delimiter specifies the end of an RRP request. It consists of a dot (".") in column one followed by a carriage-return linefeed sequence.
EndOfCommand分隔符指定RRP请求的结束。它由第一列中的一个点（“.”）和一个回车换行序列组成。
.<crlf>
.<crlf>
An RRP response starts with a three-digit response code, followed by a space, an ASCII text description of the response, a carriage-return linefeed sequence, and zero or more attribute name-value pair lines. An RRP response is terminated by a dot in column one followed by a carriage-return linefeed sequence.
RRP响应以三位响应代码开始，后跟空格、响应的ASCII文本描述、回车换行序列和零行或多行属性名称-值对。RRP响应由第1列中的点终止，后跟回车换行序列。
ResponseCode<space>responseDescription<crlf>
[attributeName:attributeValue<crlf>]
.<crlf>
ResponseCode<space>responseDescription<crlf>
[attributeName:attributeValue<crlf>]
.<crlf>
Implementations of RRP commands MUST provide "all or nothing" success and failure operation. Failed command execution MUST leave the System in the same state it was in before the command was attempted and failed.
RRP命令的实现必须提供“全部或无”成功和失败操作。执行失败的命令必须使系统保持与尝试执行命令失败前相同的状态。
All RRP commands include features to provide idempotency. Command features that are not idempotent are explained fully as needed as part of the appropriate command description.
所有RRP命令都包含提供幂等性的功能。非幂等的命令功能将根据需要作为相应命令描述的一部分进行充分解释。
This command allows a registrar to register a domain name or a name server in the System.
此命令允许注册者在系统中注册域名或名称服务器。
The request to register a domain name MUST contain the following data:
注册域名的请求必须包含以下数据：
- The "EntityName" parameter set to value "Domain". - Fully qualified second level domain name in the "DomainName" parameter.
- “EntityName”参数设置为值“Domain”。-“DomainName”参数中的完全限定二级域名。
The request to register a domain name MAY contain 1 or more, and a maximum of 13, fully qualified name servers hosting the domain name in multiple instances of the "NameServer" parameter. The name servers MUST have already been registered in the registry. Implementations MAY allow specification of name servers associated with domains registered in other TLDs. For example, an implementation MAY allow use of ccTLD name servers for gTLD domain name registration.
注册域名的请求可能包含1个或多个、最多13个完全限定的名称服务器，这些服务器在“NameServer”参数的多个实例中托管域名。名称服务器必须已在注册表中注册。实现可能允许指定与在其他TLD中注册的域关联的名称服务器。例如，实现可能允许使用ccTLD名称服务器进行gTLD域名注册。
The request to register a domain name MAY contain the initial registration period in years for the domain being registered in a single instance of the "Period" parameter. The System MUST provide a default initial registration period in years if the "Period" parameter is not provided. The acceptable year values for the "Period" parameter are implementation specific.
注册域名的请求可能包含在“period”参数的单个实例中注册的域名的初始注册期限（以年为单位）。如果未提供“期间”参数，系统必须提供默认的初始注册期间（以年为单位）。“Period”参数的可接受年份值是特定于实现的。
The System will register the domain name to the registrar for the period specified by the registrar. If the registrar does not specify a registration period, a System-specified default value MUST be used for the initial registration period. If the domain name is successfully registered, the System MUST return the registration expiration date in the "registration expiration date" attribute in the response.
系统将在注册官指定的期限内向注册官注册域名。如果注册官未指定注册期，则必须在初始注册期使用系统指定的默认值。如果域名注册成功，系统必须在响应中的“注册截止日期”属性中返回注册截止日期。
Authorized User: All registrars MAY use the ADD command to register domain names.
授权用户：所有注册者都可以使用ADD命令注册域名。
Examples
例子
A registrar registers a domain name without specifying name servers:
注册商注册域名而不指定名称服务器：
C:add<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:-Period:10<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:registration expiration date:2009-09-22 10:27:00.0<crlf>
S:status:ACTIVE<crlf>
S:.<crlf>
C:add<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:-Period:10<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:registration expiration date:2009-09-22 10:27:00.0<crlf>
S:status:ACTIVE<crlf>
S:.<crlf>
A registrar registers a domain name using previously-registered name servers:
注册商使用以前注册的名称服务器注册域名：
C:add<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example2.com<crlf>
C:-Period:10<crlf>
C:NameServer:ns1.example.com<crlf>
C:NameServer:ns2.example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:registration expiration date:2000-09-22 10:27:00.0<crlf>
S:status:ACTIVE<crlf>
S:.<crlf>
C:add<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example2.com<crlf>
C:-Period:10<crlf>
C:NameServer:ns1.example.com<crlf>
C:NameServer:ns2.example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:registration expiration date:2000-09-22 10:27:00.0<crlf>
S:status:ACTIVE<crlf>
S:.<crlf>
The request to register a name server MUST contain the following data:
注册名称服务器的请求必须包含以下数据：
- The "EntityName" parameter set to value "NameServer". - Fully qualified server name of the name server in the "NameServer" parameter.
- “EntityName”参数设置为值“NameServer”。-“NameServer”参数中名称服务器的完全限定服务器名称。
If the name server being registered is the child of a registered domain name, the name server registration request MUST include one or more, and a maximum of 13, name server IP addresses in multiple instances of the "IPAddress" parameter. Name servers associated with domains registered in other TLDs SHOULD NOT be specified with IP addresses to reduce the possibility of duplicating DNS NS records for the name servers in multiple zone files.
如果要注册的名称服务器是已注册域名的子级，则名称服务器注册请求必须在“IPAddress”参数的多个实例中包含一个或多个名称服务器IP地址，最多13个。不应使用IP地址指定与在其他TLD中注册的域关联的名称服务器，以减少在多个区域文件中复制名称服务器的DNS NS记录的可能性。
The registrar MUST register the name server in the System before using it to host domain names. Further, the name server MUST be registered through the same registrar that is the current registrar of its parent domain name. The System MAY allow any registrar to use the name server to host domain names.
注册商必须在系统中注册名称服务器，然后才能将其用于承载域名。此外，名称服务器必须通过其父域名的当前注册机构注册。系统可能允许任何注册者使用名称服务器托管域名。
Authorized User: All registrars MAY use the ADD command to register name servers.
授权用户：所有注册者都可以使用ADD命令注册名称服务器。
Examples
例子
A registrar registers a new name server in an existing domain name:
注册商在现有域名中注册新的名称服务器：
C:add<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.example.com<crlf>
C:IPAddress:198.41.1.11<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:add<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.example.com<crlf>
C:IPAddress:198.41.1.11<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
This command allows a registrar to determine if a domain name or name server has been registered in the System.
此命令允许注册器确定域名或名称服务器是否已在系统中注册。
The request to determine if a domain name is registered MUST contain the following data:
确定域名是否已注册的请求必须包含以下数据：
- The "EntityName" parameter set to value "Domain". - Fully qualified second level domain name in the "DomainName" parameter.
- “EntityName”参数设置为值“Domain”。-“DomainName”参数中的完全限定二级域名。
The System MUST provide a positive or negative response to document domain name availability at the moment the command is executed.
在执行命令时，系统必须提供对文档域名可用性的肯定或否定响应。
Authorized User: All registrars MAY use the CHECK command to determine if a domain name has been registered or not.
授权用户：所有注册者都可以使用CHECK命令来确定域名是否已注册。
Examples
例子
A registrar checks the availability of a domain name in the System:
注册商检查系统中域名的可用性：
C:check<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:211 Domain name not available<crlf>
S:.<crlf>
C:check<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:211 Domain name not available<crlf>
S:.<crlf>
The request to determine if a name server is registered MUST contain the following data:
确定名称服务器是否已注册的请求必须包含以下数据：
- The "EntityName" parameter set to value "NameServer". - Fully qualified server name in the "NameServer" parameter.
- “EntityName”参数设置为值“NameServer”。-“NameServer”参数中的完全限定服务器名称。
The System MUST provide a positive or negative response to document name server availability at the moment the command is executed. If the name server has been registered, the System MUST return the IP address(es) of the name server.
在执行命令时，系统必须提供对文档名服务器可用性的肯定或否定响应。如果名称服务器已注册，系统必须返回名称服务器的IP地址。
Authorized User: All registrars MAY use the CHECK command to determine if a name server has been registered or not.
授权用户：所有注册者都可以使用CHECK命令来确定名称服务器是否已注册。
Examples
例子
A registrar checks the availability of a server name in the System:
注册器检查系统中服务器名称的可用性：
C:check<crlf>
C:EntityName:Nameserver<crlf>
C:Nameserver:ns1.example.com<crlf>
C:.<crlf>
S:213 Name server not available<crlf>
S:ipAddress:192.10.10.10<crlf>
S:.<crlf>
C:check<crlf>
C:EntityName:Nameserver<crlf>
C:Nameserver:ns1.example.com<crlf>
C:.<crlf>
S:213 Name server not available<crlf>
S:ipAddress:192.10.10.10<crlf>
S:.<crlf>
This command allows a registrar to delete (cancel the registration) of a domain name or delete a name server.
此命令允许注册者删除（取消注册）域名或删除名称服务器。
The request to cancel the registration of a domain name MUST contain the following data:
取消域名注册的请求必须包含以下数据：
- The "EntityName" parameter set to value "Domain". - Fully qualified second level domain name in the "DomainName" parameter.
- “EntityName”参数设置为值“Domain”。-“DomainName”参数中的完全限定二级域名。
A request to delete a domain name SHOULD cause the deletion of all name servers that are children of the domain name being deleted. The name servers SHOULD be deleted if they are not actively hosting other domains. A domain MUST not be deleted if it has child name servers hosting other domains.
删除域名的请求应导致删除作为被删除域名的子项的所有名称服务器。如果名称服务器未主动承载其他域，则应将其删除。如果域具有托管其他域的子名称服务器，则不得删除该域。
Authorized User: The current registrar of a domain name MAY use the DEL command to delete a domain name from the System.
授权用户：域名的当前注册者可以使用DEL命令从系统中删除域名。
Examples
例子
A registrar deletes a domain name, implicitly deleting all name servers registered in the domain:
注册器删除域名，隐式删除在域中注册的所有名称服务器：
C:del<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:del<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
The request to delete a name server MUST contain the following data:
删除名称服务器的请求必须包含以下数据：
- The "EntityName" parameter set to value "NameServer". - Fully qualified name of the name server in the "NameServer" parameter.
- “EntityName”参数设置为值“NameServer”。-“NameServer”参数中名称服务器的完全限定名。
A name server MUST not be deleted if it is hosting domains. Deleting such domains or name servers is prohibited because their deletion WILL result in orphaning the hosted domains.
如果名称服务器承载域，则不得将其删除。禁止删除此类域或名称服务器，因为删除它们将导致托管域孤立。
Authorized User: The current registrar of a name server MAY use the DEL command to delete a name server from the System.
授权用户：名称服务器的当前注册者可以使用DEL命令从系统中删除名称服务器。
Examples
例子
A registrar deletes a name server that is not hosting domains:
注册器删除不承载域的名称服务器：
C:del<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:del<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
A registrar tries to delete a name server that is hosting domains:
注册器尝试删除承载域的名称服务器：
C:del<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
S:532 Domain names linked with name server<crlf>
S:.<crlf>
C:del<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
S:532 Domain names linked with name server<crlf>
S:.<crlf>
This command allows a registrar to obtain general information about an RRP implementation. The command MAY contain the following parameters:
此命令允许注册器获取有关RRP实现的一般信息。该命令可能包含以下参数：
- The "Target" parameter set to value "Protocol".
- “目标”参数设置为值“协议”。
The implementation MUST return the protocol version number whether or not the request contains the "Target" parameter.
无论请求是否包含“Target”参数，实现都必须返回协议版本号。
Authorized User: All registrars MAY use the DESCRIBE command.
授权用户：所有注册者都可以使用descripe命令。
Examples
例子
A registrar obtains general information about an RRP implementation:
注册官获取RRP实施的一般信息：
C:describe<crlf>
C:-Target:Protocol<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:Protocol:RRP 1.1.0<crlf>
S:.<crlf>
C:describe<crlf>
C:-Target:Protocol<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:Protocol:RRP 1.1.0<crlf>
S:.<crlf>
This command allows a registrar to update a registered domain name or a name server. The command allows the following operations on an attribute value for both single-valued and multi-valued attributes:
此命令允许注册者更新已注册的域名或名称服务器。该命令允许对单值和多值属性的属性值执行以下操作：
- Add an attribute value. The value to be added MUST be unique among the values of the attribute. For a single-valued attribute, it replaces the current value. - Remove an attribute value. The value to be removed MUST exist. Further, an attribute value cannot be removed if it is the only value of a required attribute.
- 添加属性值。要添加的值在属性值中必须是唯一的。对于单值属性，它将替换当前值。-删除属性值。要删除的值必须存在。此外，如果属性值是所需属性的唯一值，则无法删除该属性值。
Attribute values to be removed are identified by tagging with an "=" suffix.
要删除的属性值通过使用“=”后缀进行标记来标识。
The request to modify a registered domain name MUST contain the following data:
修改注册域名的请求必须包含以下数据：
- The "EntityName" parameter set to value "Domain". - Fully qualified second level domain name in the "DomainName" parameter.
- “EntityName”参数设置为值“Domain”。-“DomainName”参数中的完全限定二级域名。
The registrar can perform the following update operations on the domain name:
注册人可以对域名执行以下更新操作：
- Update the name servers of the domain name by setting one or more instances of the "NameServer" parameter. - Update the status of the domain name by setting one or more instances of the "Status" parameter. Valid values for the "Status" parameter are defined in Section 6.
- 通过设置“NameServer”参数的一个或多个实例来更新域名的名称服务器。-通过设置“status”参数的一个或多个实例来更新域名的状态。第6节定义了“状态”参数的有效值。
Authorized User: The current registrar of a domain name MAY use the MOD command to modify the attributes of a domain name.
授权用户：域名的当前注册者可以使用MOD命令修改域名的属性。
Examples
例子
A registrar removes one name server (ns1) from a domain and adds a new name server (ns3) to the same domain:
注册器从域中删除一个名称服务器（ns1），并向同一域中添加一个新的名称服务器（ns3）：
C:mod<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:NameServer:ns3.registrarA.com<crlf>
C:NameServer:ns1.registrarA.com=<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:mod<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:NameServer:ns3.registrarA.com<crlf>
C:NameServer:ns1.registrarA.com=<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
The request to update a name server MUST contain the following data:
更新名称服务器的请求必须包含以下数据：
- The "EntityName" parameter set to value "NameServer". - Fully qualified server name of the name server in the "NameServer" parameter.
- “EntityName”参数设置为值“NameServer”。-“NameServer”参数中名称服务器的完全限定服务器名称。
The registrar can perform the following update operations on the name server:
注册器可以在名称服务器上执行以下更新操作：
- Update the "NameServer" attribute of the name server. This allows a registrar to change the name of a name server while preserving all existing associations. - Update the IP addresses of the name server by setting one or more instances of the "IPAddress" parameter.
- 更新名称服务器的“NameServer”属性。这允许注册器更改名称服务器的名称，同时保留所有现有关联。-通过设置“IPAddress”参数的一个或多个实例来更新名称服务器的IP地址。
Authorized User: The current registrar of a name server MAY use the MOD command to modify the attributes of a domain name.
授权用户：名称服务器的当前注册者可以使用MOD命令修改域名的属性。
Examples
例子
A registrar changes the name and IP address of a name server:
注册器更改名称服务器的名称和IP地址：
C:mod<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:NewNameServer:ns2.registrarA.com<crlf>
C:IPAddress:198.42.1.11<crlf>
C:IPAddress:198.41.1.11=<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:mod<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:NewNameServer:ns2.registrarA.com<crlf>
C:IPAddress:198.42.1.11<crlf>
C:IPAddress:198.41.1.11=<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
This command allows a registrar to close an RRP connection. A response MUST be sent before closing the connection.
此命令允许注册器关闭RRP连接。必须在关闭连接之前发送响应。
Authorized User: All registrars MAY use the QUIT command.
授权用户：所有注册者都可以使用QUIT命令。
Examples
例子
A registrar ends an RRP session and closes an existing connection:
注册器结束RRP会话并关闭现有连接：
C:quit<crlf>
C:.<crlf>
S:220 Command completed successfully. Server closing connection<crlf>
S:.<crlf>
C:quit<crlf>
C:.<crlf>
S:220 Command completed successfully. Server closing connection<crlf>
S:.<crlf>
This command allows a registrar to renew a domain name in the System. The request to renew a domain name MUST contain the following data:
此命令允许注册者在系统中续订域名。域名续订请求必须包含以下数据：
- The "EntityName" parameter set to value "Domain". - Fully qualified second level domain name in the "DomainName" parameter.
- “EntityName”参数设置为值“Domain”。-“DomainName”参数中的完全限定二级域名。
The request to renew a domain name MAY contain the renewal period in years for the domain being renewed in a single instance of a "Period" parameter and a single instance of a "CurrentExpirationYear" parameter. These parameters MUST appear together if either is specified, though the order in which the parameters appear is insignificant. The "Period" parameter identifies the number of years to be added to the registration. The "CurrentExpirationYear" parameter identifies the current expiration year, and is required to ensure that repeated attempts to retry this command do not result in multiple successful renewals. The System MUST provide a default number of renewal years if the "Period" and "CurrentExpirationYear" parameters are not provided. Repeated use of this command without the "Period" and "CurrentExpirationYear" parameters may result in repeated successful renewals since idempotency is not provided when these parameters are not used. The acceptable year values for the "Period" parameter are implementation specific subject to syntax restrictions.
续订域名的请求可能包含在单个“period”参数实例和单个“CurrentExpirationYear”参数实例中续订的域名的续订期限（以年为单位）。如果指定了其中一个参数，则这些参数必须同时显示，尽管参数的显示顺序无关紧要。“Period”参数标识要添加到注册中的年数。“CurrentExpirationYear”参数标识当前到期年，是确保重复尝试重试此命令不会导致多次成功续订所必需的。如果未提供“Period”和“CurrentExpirationYear”参数，则系统必须提供默认的续订年数。在不使用“Period”和“CurrentExpirationYear”参数的情况下重复使用此命令可能会导致重复的成功续订，因为不使用这些参数时不提供幂等性。“Period”参数的可接受年份值是特定于实现的，受语法限制。
The System renews the domain name for a period specified by the registrar. If the domain name renewal is completed successfully, the System MUST return the new registration expiration date in the "RegistrationExpirationDate" attribute in the response.
系统将域名续展一段注册人指定的时间。如果域名续订成功完成，系统必须在响应中的“RegistrationExpirationDate”属性中返回新的注册过期日期。
Authorized User: The current registrar of a domain name MAY use the RENEW command.
授权用户：域名的当前注册者可以使用续订命令。
Examples
例子
A registrar renews a domain name using a specified renewal period:
注册商使用指定的续展期续展域名：
C:renew<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:-Period:9<crlf>
C:-CurrentExpirationYear:2001<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:registration expiration date:2010-09-22 10:27:00.0<crlf>
S:.<crlf>
C:renew<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:-Period:9<crlf>
C:-CurrentExpirationYear:2001<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:registration expiration date:2010-09-22 10:27:00.0<crlf>
S:.<crlf>
This command allows a registrar to establish an RRP session. A registrar can also use this command to change their password. The request to establish an RRP connection MUST contain the following command parameters:
此命令允许注册器建立RRP会话。注册者也可以使用此命令更改其密码。建立RRP连接的请求必须包含以下命令参数：
- The "Id" parameter set to the registrar's System user ID. - The "Password" parameter set to the registrar's current System password.
- “Id”参数设置为注册器的系统用户Id.“密码”参数设置为注册器的当前系统密码。
The request to establish an RRP session MAY contain a new password for the registrar in a single instance of the "NewPassword" parameter.
建立RRP会话的请求可以在“NewPassword”参数的单个实例中包含注册器的新密码。
The registrar MUST send this command to the System before any other command. If the command fails due to invalid information (such as an invalid registrar ID or password), the registrar can resend this request with corrected information. If the command fails a second time, the System SHOULD close the connection.
注册器必须在发送任何其他命令之前将此命令发送到系统。如果由于无效信息（例如无效的注册器ID或密码）导致命令失败，注册器可以使用更正的信息重新发送此请求。如果命令再次失败，系统应关闭连接。
Authorized User: All registrars MAY use the SESSION command.
授权用户：所有注册者都可以使用会话命令。
Examples
例子
A registrar establishes an RRP session:
注册官建立RRP会话：
C:session<crlf>
C:-Id:registrarA<crlf>
C:-Password:i-am-registrarA<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:session<crlf>
C:-Id:registrarA<crlf>
C:-Password:i-am-registrarA<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
This command allows a registrar to determine the current status of a domain name or name server.
此命令允许注册者确定域名或名称服务器的当前状态。
The request to query a domain name MUST contain the following data:
查询域名的请求必须包含以下数据：
- The "EntityName" parameter set to value "Domain". - Fully qualified second level domain name in the "DomainName" parameter.
- “EntityName”参数设置为值“Domain”。-“DomainName”参数中的完全限定二级域名。
The response from the System MAY contain the following data:
来自系统的响应可能包含以下数据：
- Fully qualified server names of name servers hosting the domain name in multiple instances of the "nameserver" attribute. - Registration expiration date in the "registration expiration date" attribute. - ID of the current registrar of the domain name in the "registrar" attribute. - Date the domain name was transferred by the current registrar in the "registrar transfer date" attribute. - Current statuses of the domain name in multiple instances of the "status" attribute. - Date the domain name was originally registered in the "created date" attribute. - ID of the registrar that originally registered the domain name in the "created by" attribute. - Date the domain name was last updated in the "updated date" attribute. - ID of the entity (either a registrar or the registry) that last updated the domain name in the "updated by" attribute.
- 在“nameserver”属性的多个实例中承载域名的名称服务器的完全限定服务器名称。-“注册截止日期”属性中的注册截止日期。-“注册商”属性中域名的当前注册商ID。-当前注册机构在“注册机构转让日期”属性中转让域名的日期。-“状态”属性的多个实例中域名的当前状态。-域名最初在“创建日期”属性中注册的日期。-最初在“创建人”属性中注册域名的注册人ID。-“更新日期”属性中上次更新域名的日期。-上次在“更新人”属性中更新域名的实体（注册商或注册中心）的ID。
Authorized User: The current registrar of a domain name MAY use the STATUS command to view current domain name attributes.
授权用户：域名的当前注册者可以使用STATUS命令查看当前域名属性。
Examples
例子
The current registrar of a domain name queries the domain name:
域名的当前注册人查询域名：
C:status<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:nameserver:ns2.registrarA.com<crlf>
S:nameserver:ns3.registrarA.com<crlf>
S:registration expiration date:2010-09-22 10:27:00.0<crlf>
S:registrar:registrarA<crlf>
S:registrar transfer date:1999-09-22 10:27:00.0<crlf>
S:status:ACTIVE<crlf>
S:created date:1998-09-22 10:27:00.0<crlf>
S:created by:registrarA<crlf>
S:updated date:2002-09-22 10:27:00.0<crlf>
S:updated by:registrarA<crlf>
S:.<crlf>
C:status<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:nameserver:ns2.registrarA.com<crlf>
S:nameserver:ns3.registrarA.com<crlf>
S:registration expiration date:2010-09-22 10:27:00.0<crlf>
S:registrar:registrarA<crlf>
S:registrar transfer date:1999-09-22 10:27:00.0<crlf>
S:status:ACTIVE<crlf>
S:created date:1998-09-22 10:27:00.0<crlf>
S:created by:registrarA<crlf>
S:updated date:2002-09-22 10:27:00.0<crlf>
S:updated by:registrarA<crlf>
S:.<crlf>
A registrar queries a domain name currently registered by another registrar:
注册商查询另一注册商当前注册的域名：
C:status<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:531 Authorization failed<crlf>
S:.<crlf>
C:status<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:531 Authorization failed<crlf>
S:.<crlf>
The request to query a name server MUST contain the following data:
查询名称服务器的请求必须包含以下数据：
- The "EntityName" parameter set to value "NameServer". - Fully qualified name of the name server in the "NameServer" parameter.
- “EntityName”参数设置为值“NameServer”。-“NameServer”参数中名称服务器的完全限定名。
The response from the System MAY contain the following data:
来自系统的响应可能包含以下数据：
- Fully qualified name of the name server in the "nameserver" attribute. - IP addresses of the name server in multiple instances of the "ipaddress" attribute. - ID of the current registrar of the name server in the "registrar" attribute. - Date the name server was transferred by the current registrar in the "registrar transfer date" attribute. - Date the name server was registered in the "created date" attribute. - ID of the entity that registered the name server in the "created by" attribute. - Date the name server was last updated in the "updated date" attribute. - ID of the entity that last updated the name server in the "updated by" attribute.
- “nameserver”属性中名称服务器的完全限定名。-“ipaddress”属性的多个实例中名称服务器的IP地址。-“注册器”属性中名称服务器的当前注册器ID。-名称服务器由当前注册器在“注册器传输日期”属性中传输的日期。-名称服务器在“创建日期”属性中注册的日期。-在“创建人”属性中注册名称服务器的实体的ID。-名称服务器上次在“更新日期”属性中更新的日期。-上次在“更新人”属性中更新名称服务器的实体的ID。
Authorized User: The current registrar of a name server MAY use the STATUS command to view current domain name attributes.
授权用户：名称服务器的当前注册者可以使用STATUS命令查看当前域名属性。
Examples
例子
The current registrar of a name server queries the name server:
名称服务器的当前注册器查询名称服务器：
C:status<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
C:status<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:ipaddress:198.42.1.11<crlf>
S:registrar:registrarA<crlf>
S:registrar transfer date:1999-09-22 10:27:00.0<crlf>
S:CreatedDate:1998-09-22 10:27:00.0<crlf>
S:CreatedBy:registrarA<crlf>
S:UpdatedDate:2002-09-22 10:27:00.0<crlf>
S:UpdatedBy:registrarA<crlf>
S:.<crlf>
S:200 Command completed successfully<crlf>
S:ipaddress:198.42.1.11<crlf>
S:registrar:registrarA<crlf>
S:registrar transfer date:1999-09-22 10:27:00.0<crlf>
S:CreatedDate:1998-09-22 10:27:00.0<crlf>
S:CreatedBy:registrarA<crlf>
S:UpdatedDate:2002-09-22 10:27:00.0<crlf>
S:UpdatedBy:registrarA<crlf>
S:.<crlf>
A registrar queries a name server that was registered by another registrar:
注册商查询由另一注册商注册的名称服务器：
C:status<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
S:531 Authorization failed<crlf>
S:.<crlf>
C:status<crlf>
C:EntityName:NameServer<crlf>
C:NameServer:ns1.registrarA.com<crlf>
C:.<crlf>
S:531 Authorization failed<crlf>
S:.<crlf>
This command allows a registrar to request transfer of domain name sponsorship from a second registrar and to approve or reject transfer requests initiated by other registrars. The request to transfer a domain name MUST contain the following data:
此命令允许注册商请求从第二个注册商转移域名赞助，并批准或拒绝其他注册商发起的转移请求。传输域名的请求必须包含以下数据：
- The "EntityName" parameter set to value "Domain". - Fully qualified second level domain name in the "DomainName" parameter.
- “EntityName”参数设置为值“Domain”。-“DomainName”参数中的完全限定二级域名。
The identity of the requesting registrar is derived from the current active session. The identity of the current sponsoring registrar (the registrar who must approve or reject the transfer request) is known by the registry and does not need to be known by the requesting registrar in advance of issuing the transfer request.
请求注册器的标识来自当前活动会话。登记处知道当前担保登记员（必须批准或拒绝转让请求的登记员）的身份，而请求登记员无需在发出转让请求之前知道。
The System MUST notify the potential losing registrar when a domain transfer request has been received using an out-of-band transport mechanism such as electronic mail and/or transaction reporting. The losing registrar SHOULD then explicitly approve or reject the transfer. A request to approve or reject a transfer request MUST contain a single instance of the "Approve" parameter with a value of "Yes" to approve the transfer or a value of "No" to reject the transfer. A server implementation MAY provide a default approval or rejection action to be taken if the losing registrar does not explicitly approve or reject the transfer request within a fixed amount of time. The criteria used by registrars to approve or deny
当使用带外传输机制（如电子邮件和/或交易报告）收到域转移请求时，系统必须通知潜在的丢失注册人。然后，败诉登记官应明确批准或拒绝转让。批准或拒绝转账请求的请求必须包含“批准”参数的单个实例，其值为“是”以批准转账，或值为“否”以拒绝转账。如果丢失的注册器未在固定时间内明确批准或拒绝传输请求，则服务器实现可提供要采取的默认批准或拒绝操作。注册人用于批准或拒绝的标准
requested transfers are typically based on business policies that are beyond the scope of this document.
请求的传输通常基于超出本文档范围的业务策略。
Approval of a transfer by the current sponsoring registrar results in a change of sponsorship to the original requesting registrar. Approval attempts by any other registrar MUST result in explicit failure of the attempted approval. Rejection of the transfer by the current sponsoring registrar results in an end to the transfer request with no change in sponsorship. Rejection attempts by any other registrar MUST result in explicit failure of the attempted rejection.
当前担保登记官对转让的批准导致担保变更至原始请求登记官。任何其他注册机构的批准尝试必须导致尝试批准的明确失败。当前担保登记官拒绝转让将导致转让请求终止，担保权不变。任何其他注册机构的拒绝尝试必须导致拒绝尝试的明确失败。
Name servers MUST be implicitly transferred when their parent domain name is transferred.
在传输其父域名时，名称服务器必须隐式传输。
Authorized User: All registrars MAY use the TRANSFER command to request transfer of registration service authority to the requesting registrar. Only the current sponsoring registrar of a domain name may explicitly approve or reject a requested transfer. The registry MAY implicitly approve or reject requested transfers after a fixed amount of time.
授权用户：所有注册人可使用转移命令向请求注册人请求注册服务权限的转移。只有域名的当前发起注册机构可以明确批准或拒绝请求的转移。登记处可在一段固定时间后默示批准或拒绝所请求的转让。
Examples
例子
A registrar requests transfer of a domain name from another registrar:
注册商请求从另一注册商处转移域名：
C:transfer<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:transfer<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
The original registrar approves the transfer request:
原注册官批准转让请求：
C:transfer<crlf>
C:-Approve:Yes<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
C:transfer<crlf>
C:-Approve:Yes<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
RRP commands may return a variety of response codes to signify normal completion or error conditions. This section documents all of the defined RRP response codes.
RRP命令可能返回各种响应代码，以表示正常完成或错误情况。本节记录了所有已定义的RRP响应代码。
200 Command completed successfully This is the normal response for successful completion of most RRP commands.
200命令成功完成这是成功完成大多数RRP命令的正常响应。
210 Domain name available This is the normal response for successful completion of an RRP CHECK command for a domain name that is not currently registered.
210域名可用这是成功完成当前未注册域名的RRP检查命令的正常响应。
211 Domain name not available This is the normal response for successful completion of an RRP CHECK command for a domain name that is currently registered.
211域名不可用这是成功完成当前注册域名的RRP检查命令的正常响应。
212 Name server available This is the normal response for successful completion of an RRP CHECK command for a name server that is not currently registered.
212名称服务器可用这是当前未注册的名称服务器成功完成RRP CHECK命令的正常响应。
213 Name server not available This is the normal response for successful completion of an RRP CHECK command for a name server that is currently registered.
213名称服务器不可用这是成功完成当前注册的名称服务器的RRP检查命令的正常响应。
220 Command completed successfully. Server closing connection This is the normal response for successful completion of an RRP QUIT command. It may also be returned by other RRP commands if a transient situation is noted that requires closing the connection after successfully completing the RRP command.
220命令已成功完成。服务器关闭连接这是成功完成RRP QUIT命令的正常响应。如果注意到需要在成功完成RRP命令后关闭连接的瞬态情况，则其他RRP命令也可能会返回该消息。
420 Command failed due to server error. Server closing connection A transient server error has caused RRP command failure and session termination. A new session must be established before continued processing can be attempted.
由于服务器错误，420命令失败。服务器关闭连接暂时性服务器错误导致RRP命令失败和会话终止。必须先建立新会话，然后才能尝试继续处理。
421 Command failed due to server error. Client should try again A transient server error has caused RRP command failure. A subsequent retry may produce successful results.
由于服务器错误，421命令失败。客户端应重试暂时的服务器错误导致RRP命令失败。随后的重试可能会产生成功的结果。
500 Invalid command name A client-specified RRP command name was not recognized as a valid RRP command name.
500无效命令名客户端指定的RRP命令名未被识别为有效的RRP命令名。
501 Invalid command option A client-specified RRP command parameter was not recognized as a valid RRP command parameter.
501无效命令选项客户端指定的RRP命令参数未被识别为有效的RRP命令参数。
502 Invalid entity value The "value" of an entity name-value pair is invalid. Command blocks that require an "EntityName" parameter also require a value that specifies the entity name, and the provided value is invalid.
502无效实体值实体名称-值对的“值”无效。需要“EntityName”参数的命令块还需要指定实体名称的值，并且提供的值无效。
503 Invalid attribute name A client-specified RRP command parameter was not recognized as a valid RRP command parameter.
503无效的属性名称客户端指定的RRP命令参数未被识别为有效的RRP命令参数。
504 Missing required attribute A parameter required to execute the RRP command was not provided by the client. The command should be retried with all required parameters specified.
504缺少必需属性客户端未提供执行RRP命令所需的参数。应在指定所有必需参数的情况下重试该命令。
505 Invalid attribute value syntax A supplied parameter value is syntactically incorrect. For example, a year value digit such as "5" may be required but the client provided a string of characters such as "five".
505无效属性值语法提供的参数值在语法上不正确。例如，可能需要诸如“5”之类的年份值数字，但客户机提供了诸如“5”之类的字符串。
506 Invalid option value A client-specified value for an RRP command parameter is out-of-bounds or otherwise not within acceptable System limits.
506无效选项值RRP命令参数的客户端指定值超出范围或不在可接受的系统限制内。
507 Invalid command format The specified command does not resemble a well-formed RRP command. The command should be retried using the proper command structure and syntax.
507无效的命令格式指定的命令与格式良好的RRP命令不相似。应使用正确的命令结构和语法重试该命令。
508 Missing required entity An entity required for command completion was not provided by the client. For example, the CHECK command requires specification of either a "Domain" entity or a "Nameserver" entity.
508缺少必需的实体客户端未提供完成命令所需的实体。例如，CHECK命令要求指定“域”实体或“名称服务器”实体。
509 Missing command option A command parameter that isn't really optional (such as the registrar ID in a SESSION command) was not provided by the client. The command should be retried with all needed parameters.
509缺少命令选项客户端未提供并非真正可选的命令参数（例如会话命令中的注册器ID）。应使用所有需要的参数重试该命令。
520 Server closing connection. Client should try opening new connection; <why> A timeout event has been detected, and the client's session is being ended. The System SHOULD define timeout periods to begin a client
520服务器正在关闭连接。客户端应尝试打开新连接<why>检测到超时事件，客户端会话正在结束。系统应定义启动客户端的超时时间
command, complete a client command, and for the duration of an open session. The reason for the timeout MUST be provided at the end of the response code string.
命令，完成客户端命令，并在打开的会话期间执行。超时原因必须在响应代码字符串的末尾提供。
521 Too many sessions open. Server closing connection A System-defined limit on the number of open connections has been exceeded, and it is impossible to establish a new session at the moment. It may be possible to establish a session by waiting for a few moments or by closing existing unused sessions.
521打开的会话太多。服务器关闭连接已超过系统定义的打开连接数限制，目前无法建立新会话。可以通过等待片刻或关闭现有未使用的会话来建立会话。
530 Authentication failed The client-supplied registrar identifier or password was not recognized by the System. A subsequent retry with valid values may produce successful results. Repeated authorization failures MAY result in termination of the TCP connection.
530身份验证失败系统无法识别客户端提供的注册器标识符或密码。使用有效值进行后续重试可能会产生成功的结果。反复授权失败可能导致TCP连接终止。
531 Authorization failed Registrars may not view or alter data associated with either the registry or another registrar. This response code is typically returned when a registrar attempts to view or modify data belonging to either the registry or another registrar. A typical situation includes doing a STATUS command for a domain registered to another registrar.
531授权失败的注册人不得查看或更改与注册处或其他注册人相关的数据。当注册器试图查看或修改属于注册器或其他注册器的数据时，通常会返回此响应代码。典型情况包括对注册到另一个注册器的域执行状态命令。
532 Domain names linked with name server The name server is hosting active domains. This error occurs when a registrar is trying to delete a server that is the name server for active domains. The registry MUST not allow the registrar to delete this server. All of the domain names using this server MUST be modified to use a different name server before the name server can be deleted.
532与名称服务器链接的域名名称服务器正在承载活动域。当注册器试图删除作为活动域名称服务器的服务器时，会发生此错误。注册表不得允许注册器删除此服务器。在删除名称服务器之前，必须修改使用此服务器的所有域名以使用其他名称服务器。
533 Domain name has active name servers The domain name has active name servers. The registrar is trying to delete a domain name that is a parent domain of an active name server, i.e., a server that is hosting active domains. All of the name servers within the domain MUST be removed from service before the domain can be deleted.
533域名有活动名称服务器该域名有活动名称服务器。注册器正在尝试删除作为活动名称服务器父域的域名，即承载活动域的服务器。必须先从服务中删除域中的所有名称服务器，然后才能删除域。
534 Domain name has not been flagged for transfer The registrar is trying to approve or reject a domain name transfer for a domain name that is not pending transfer.
534域名尚未标记为转移注册官正在尝试批准或拒绝未挂起转移的域名的域名转移。
535 Restricted IP address IANA identifies certain IP address ranges that are not valid for normal use. The registrar is trying to use an IP address that is in a restricted IP address range as identified by IANA.
535受限IP地址IANA标识某些IP地址范围，这些范围对于正常使用无效。注册器正在尝试使用IANA标识的受限IP地址范围内的IP地址。
536 Domain already flagged for transfer The registrar tried to perform a transfer command for a domain name that is awaiting approval of an earlier transfer request.
536已标记为传输的域注册器尝试对正在等待先前传输请求批准的域名执行传输命令。
540 Attribute value is not unique A supplied attribute value is not unique. This occurs when the registrar is adding a domain name that already exists in the registry, a server that already exists in the registry, or an IP address that is already being used by another server in the registry. Another possibility occurs when performing domain modifications and the registrar is adding a server that is already in the list of servers for the domain name or setting a domain name to a status to which it is already set. The RRP STATUS command MAY be used to determine current domain name status before attempting to change the status. When modifying or adding a name server, the IP address of the name server might not be unique. The registry MUST not allow IP addresses to be used by more than one server.
540属性值不唯一提供的属性值不唯一。当注册器添加已存在于注册表中的域名、已存在于注册表中的服务器或已被注册表中的其他服务器使用的IP地址时，会发生这种情况。另一种可能是在执行域修改时，注册器正在添加一个已在域名服务器列表中的服务器，或者将域名设置为已设置的状态。RRP STATUS命令可用于在尝试更改状态之前确定当前域名状态。修改或添加名称服务器时，名称服务器的IP地址可能不唯一。注册表不得允许多台服务器使用IP地址。
541 Invalid attribute value A supplied parameter value is invalid. Examples of invalid attribute values include an invalid IP address, an invalid domain name, an invalid server name, or an invalid renewal period.
541无效属性值提供的参数值无效。无效属性值的示例包括无效的IP地址、无效的域名、无效的服务器名或无效的续订期。
542 Invalid old value for an attribute A current attribute value to be modified is invalid. The registrar is trying to modify an attribute of a server or a domain name that does not exist in the registry.
542属性的旧值无效要修改的当前属性值无效。注册器正试图修改注册表中不存在的服务器或域名的属性。
543 Final or implicit attribute cannot be updated The registrar is attempting to modify an attribute that is only modifiable by the registry. Registrars can not modify final or implicit attribute values.
543无法更新最终或隐式属性注册器正在尝试修改仅可由注册表修改的属性。注册器不能修改最终或隐式属性值。
544 Entity on hold The attempted operation was rejected because the entity is on HOLD status. If the HOLD status was set by the registrar, the status can be changed using the MOD command and the requested command can be retried. If the HOLD status was set by the registry, the registrar must contact the registry to change the status before the command can be successful.
544实体处于保留状态由于实体处于保留状态，尝试的操作被拒绝。如果注册器设置了保持状态，则可以使用MOD命令更改状态，并且可以重试请求的命令。如果注册中心设置了保持状态，注册中心必须联系注册中心更改状态，然后命令才能成功。
545 Entity reference not found A required entity reference was not found. This occurs when the registrar tries to add a new name server and the parent domain of the name server does not exist in the registry. It also occurs when the user is trying to add a new name server to a domain name when the name server does not exist in the registry.
545未找到实体引用未找到所需的实体引用。当注册器尝试添加新的名称服务器，并且名称服务器的父域在注册表中不存在时，会发生这种情况。当注册中心中不存在名称服务器时，当用户试图向域名添加新的名称服务器时，也会发生这种情况。
546 Credit limit exceeded The registrar's credit limit has been exceeded. This is an implementation specific error that occurs when a potentially billable operation, such as adding a domain name, renewing a domain name, or transferring a domain name, is attempted and the registrar does not have sufficient financial standing with the registry to complete the operation.
546信用额度超过注册官的信用额度已超过。这是一个特定于实现的错误，当尝试添加域名、续订域名或转移域名等可能计费的操作时，注册官在注册中心没有足够的财务状况来完成该操作时，会发生此错误。
547 Invalid command sequence RRP commands are issued using a well-formed syntax that requires entry of command structures in particular sequences. This response code indicates that an ill-formed command was received and rejected.
547无效命令序列RRP命令使用格式良好的语法发出，该语法要求在特定序列中输入命令结构。此响应代码表示收到并拒绝了格式错误的命令。
548 Domain is not up for renewal A RENEW command was attempted during a period in which the domain can not be renewed. Implementations MAY limit renewal periods to particular time frames, such as within 90 days of the domain's expiration. This response indicates that the RENEW command was received outside of the System-defined domain renewal period.
548域未进行续订在无法续订域的期间尝试了续订命令。实现可能会将续费期限限制在特定的时间范围内，例如域到期后的90天内。此响应表示在系统定义的域续订期间之外接收到续订命令。
549 Command failed A System error prevented successful completion of the requested RRP command. Retrying the command might produce success, but a repeated failure indicates a System error condition.
549命令失败系统错误阻止请求的RRP命令成功完成。重试该命令可能会导致成功，但重复失败表示出现系统错误情况。
550 Parent domain not registered The parent domain of a name server being registered is not registered. This occurs when the registrar tries to add a new name server and the parent domain for the server does not exist in the registry.
550父域未注册正在注册的名称服务器的父域未注册。当注册器尝试添加新的名称服务器，而该服务器的父域在注册表中不存在时，就会发生这种情况。
551 Parent domain status does not allow for operation The status of the parent domain does not allow the requested operation. This occurs when a registrar tries to modify a server whose parent domain is flagged as LOCK or HOLD in the registry.
551父域状态不允许操作父域的状态不允许请求的操作。当注册器试图修改其父域在注册表中标记为锁定或保留的服务器时，会发生这种情况。
552 Domain status does not allow for operation The status of the domain does not allow the requested operation. This occurs when a registrar tries to modify or delete a domain that is flagged as LOCK or HOLD in the registry.
552域状态不允许操作域的状态不允许请求的操作。当注册器试图修改或删除注册表中标记为锁定或保留的域时，会发生这种情况。
553 Operation not allowed. Domain pending transfer The status of the domain does not allow the requested operation. The registrar is attempting to delete a domain that is pending approval or denial of a transfer request.
553操作不允许。域挂起传输域的状态不允许请求的操作。注册器正试图删除一个待批准或拒绝传输请求的域。
554 Domain already registered A registrar tried to register a domain name that has already been registered by the same registrar.
554域名已注册一个注册商试图注册一个已由同一注册商注册的域名。
555 Domain already renewed A registrar tried to renew a domain using the same parameters as specified for an earlier, successful renewal. This will commonly occur when executing the same RENEW command more than once.
555域已续订一个注册器尝试使用为较早的成功续订指定的相同参数续订域。这通常在多次执行同一个RENEW命令时发生。
556 Maximum registration period exceeded A registrar tried to renew a domain registration, and the resulting new registration period exceeds the System-defined maximum registration period. If there is renewal time available with the System-defined maximum registration period it may be possible to retry the RENEW command with specified renewal period parameters.
556最长注册期超过了注册商尝试续订域注册，并且由此产生的新注册期超过了系统定义的最长注册期。如果系统定义的最长注册期有可用的续订时间，则可以使用指定的续订期参数重试续订命令。
The session between the client and the server is intended to be an alternating dialogue. Each command issued by a client MUST be acted upon by the server, which MUST return a response code to document the success or failure of command execution. "Success" means that the command completed normal execution without error. "Failure" means that the System did not complete the command as requested. Failure may be due to either syntax, semantic, data, or System errors.
客户端和服务器之间的会话是一种交替对话。客户端发出的每个命令都必须由服务器执行，服务器必须返回一个响应代码来记录命令执行的成功或失败。“成功”意味着命令无误地完成了正常执行。“故障”表示系统未按要求完成命令。失败可能是由于语法、语义、数据或系统错误造成的。
A complete list of response codes for each RRP command is listed below.
下面列出了每个RRP命令的完整响应代码列表。
Command: ADD Success: 200, 220 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 535, 540, 541, 545, 546, 547, 549, 550, 554
命令：添加成功：200、220失败：420、421、500、502、503、504、505、507、508、520、531、535、540、541、545、546、547、549、550、554
Command: CHECK Success: 210, 211, 212, 213 Failure: 220, 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 541, 547, 549
命令：检查成功：210、211、212、213失败：220、420、421、500、502、503、504、505、507、508、520、541、547、549
Command: DEL Success: 200, 220 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 532, 533, 541, 544, 545, 547, 549, 551, 552, 553
命令：DEL成功：200220失败：4204215005025035005070508520531532543541454547553
Command: DESCRIBE Success: 200, 220 Failure: 420, 421, 500, 501, 506, 507, 509, 520, 547, 549
命令：描述成功：200220失败：42042150050150650070952054749
Command: MOD Success: 200, 220 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 535, 540, 541, 542, 543, 544, 545, 547, 549, 550, 551, 552, 553
命令：MOD Success:200220 Failure:4204215005025050705085205315353555425435445454749550551553
Command: QUIT Success: 220 Failure: 420, 421, 500, 507, 520, 547, 549
命令：退出成功：220失败：420、421、500、507、520、547、549
Command: RENEW Success: 200, 220 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 541, 545, 546, 547, 548, 549, 552, 553, 555, 556
命令：续订成功：200、220失败：420、421、500、502、503、504、505、507、508、520、531、541、545、546、547、548、549、552、553、555、556
Command: SESSION Success: 200, 220 Failure: 420, 421, 500, 501, 506, 507, 508, 509, 520, 521, 530, 531, 547, 549
命令：会话成功：200、220失败：420、421、500、501、506、507、508、509、520、521、530、531、547、549
Command: STATUS Success: 200, 220 Failure: 420, 421, 500, 501, 502, 503, 504, 505, 506, 507, 508, 520, 531, 541, 545, 547, 549
命令：状态成功：200、220失败：420、421、500、501、502、503、504、505、506、507、508、520、531、541、545、547、549
Command: TRANSFER Success: 200, 220 Failure: 420, 421, 500, 501, 502, 503, 504, 505, 506, 507, 508, 520, 531, 534, 536, 541, 544, 545, 546, 547, 549, 552, 553
命令：传输成功：200、220失败：420、421、500、501、502、503、504、505、506、507、508、520、531、534、536、541、544、545、546、547、549、552、553
The status of a domain can be viewed using the RRP STATUS command and modified using the RRP MOD command. Both the registry and the sponsoring registrar MAY view and change the status of a domain. The criteria for status changes are highly dependent on registry and registrar business models and are thus beyond the scope of this specification.
可以使用RRP status命令查看域的状态，并使用RRP MOD命令修改域的状态。注册处和主办注册处均可查看和更改域名的状态。状态更改的标准高度依赖于注册表和注册器业务模型，因此超出了本规范的范围。
The domain's status SHOULD have a direct bearing on whether or not the domain appears in the appropriate TLD zone file and whether or not the domain can be modified. A domain can have more than one assigned status, e.g., REGISTRAR-HOLD and REGISTRAR-LOCK. If a domain is in ACTIVE status, then the domain name can only be in this status. When a registrar sets a domain name to REGISTRAR-LOCK, the registry MUST automatically remove the ACTIVE status. When the registrar removes the REGISTRAR-LOCK and other domain statuses, the registry MUST automatically set the domain name status to ACTIVE.
域的状态应直接影响域是否出现在相应的TLD区域文件中，以及域是否可以修改。一个域可以有多个分配的状态，例如，注册商持有和注册商锁定。如果域处于活动状态，则域名只能处于此状态。当注册机构将域名设置为registrar-LOCK时，注册机构必须自动删除活动状态。当注册机构删除注册机构锁定和其他域状态时，注册机构必须自动将域名状态设置为活动。
ACTIVE: This is the default status of a domain at registration time. The registry sets the domain to this status. The domain is modifiable by the registrar. The domain can be renewed. The domain SHALL be included in the zone file when in this status if the domain has at least one associated name server.
活动：这是注册时域的默认状态。注册表将域设置为此状态。域名可由注册者修改。该域可以续订。如果域至少有一个关联的名称服务器，则该域在此状态下应包含在区域文件中。
REGISTRY-LOCK: The registry sets the domain to this status. The domain cannot be modified or deleted by the registrar. The registry MUST remove the REGISTRY-LOCK status for the registrar to modify the domain. The domain can be renewed. The domain SHALL be included in the zone file when in this status if the domain has at least one associated name server.
注册表锁定：注册表将域设置为此状态。注册器无法修改或删除域。注册中心必须删除注册表锁定状态，注册中心才能修改域。该域可以续订。如果域至少有一个关联的名称服务器，则该域在此状态下应包含在区域文件中。
REGISTRY-HOLD: The registry sets the domain to this status. The domain cannot be modified or deleted by the registrar. The registry MUST remove the REGISTRY-HOLD status for the registrar to modify the domain. The domain can be renewed. The domain SHALL NOT be included in the zone file when in this status.
注册表保持：注册表将域设置为此状态。注册器无法修改或删除域。注册中心必须删除注册中心保留状态，注册中心才能修改域。该域可以续订。处于此状态时，域不应包含在区域文件中。
REGISTRAR-HOLD: The registrar of the domain sets the domain to this status. The domain can not be modified or deleted when in this status. The registrar MUST remove REGISTRAR-HOLD status to modify the domain. The domain can be renewed. The domain SHALL NOT be included in the zone file when in this status.
REGISTRAR-HOLD：域的注册器将域设置为此状态。处于此状态时，无法修改或删除域。注册者必须删除注册者保留状态才能修改域。该域可以续订。处于此状态时，域不应包含在区域文件中。
REGISTRAR-LOCK: The registrar of the domain sets the domain to this status. The domain cannot be modified or deleted when in this status. The registrar MUST remove REGISTRAR-LOCK status to modify the domain. The domain can be renewed. The domain SHALL be included in the zone file when in this status.
registrator-LOCK：域的注册器将域设置为此状态。处于此状态时，无法修改或删除域。注册器必须删除注册器锁定状态才能修改域。该域可以续订。处于此状态时，域应包含在区域文件中。
REGISTRY-DELETE-NOTIFY: A domain is set on this status if it has expired and has child name servers that are hosting other domains. Only the registry may set this status. The domain SHALL be included in the zone file when in this status if the domain has at least one associated name server.
REGISTRY-DELETE-NOTIFY：如果某个域已过期，并且具有承载其他域的子名称服务器，则该域将设置为此状态。只有注册表可以设置此状态。如果域至少有一个关联的名称服务器，则该域在此状态下应包含在区域文件中。
The following syntax specification uses the augmented Backus-Naur Form (BNF) as described in [ABNF].
以下语法规范使用[ABNF]中所述的增广巴科斯诺尔形式（BNF）。
; ABNF specification for Registry Registrar Protocol (RRP) v1.1.0 ; Note that character string literals are case insensitive.
; ABNF注册表注册器协议（RRP）规范v1.1.0；请注意，字符串文字不区分大小写。
; Lexical tokens
space = %x20 ; " "
dot = %x2E ; "."
dash = %x2D ; "-"
underscore = %x5F ; "_"
colon = %x3A ; ":"
cr = %x0D ; ASCII carriage return
lf = %x0A ; ASCII linefeed
crlf = cr lf
alpha = %x41-5A / %x61-7A ; A-Z / a-z
digit = %x30-39 ; 0-9
dns-char = alpha / digit / dash
id-char = alpha / digit / underscore / dash
id-prefix = alpha / digit
id-word = id-prefix *id-char
printable-char = %x20-7E ; ASCII " " - "~"
; Lexical tokens
space = %x20 ; " "
dot = %x2E ; "."
dash = %x2D ; "-"
underscore = %x5F ; "_"
colon = %x3A ; ":"
cr = %x0D ; ASCII carriage return
lf = %x0A ; ASCII linefeed
crlf = cr lf
alpha = %x41-5A / %x61-7A ; A-Z / a-z
digit = %x30-39 ; 0-9
dns-char = alpha / digit / dash
id-char = alpha / digit / underscore / dash
id-prefix = alpha / digit
id-word = id-prefix *id-char
printable-char = %x20-7E ; ASCII " " - "~"
; Start of basic grammar.
year = 4digit
month = 2digit
day = 2digit
ymd = year dash month dash day
hour = 2digit
minute = 2digit
second = 2digit
split-second = 1digit
hms = hour colon minute colon second dot split-second
time-stamp = ymd space hms
ip-address = 1*3digit dot 1*3digit dot 1*3digit dot 1*3digit
password = 4*16printable-char
option-name = 1*128id-word
option-tag = dash option-name
option-value = 1*128id-word
attribute-name = 1*128id-word
attribute-value = 1*128printable-char
attribute-line = attribute-name colon attribute-value crlf
response = 3digit space 1*printable-char crlf
version-number = "RRP" space 1*digit dot 1*digit dot 1*digit
label = id-prefix [*61dns-char id-prefix]
sldn = label dot label
servername = *(label dot) sldn
period = %x31-39 / (%x31-39 %x30-39) ; "1" - "9" or "10" - "99"
period-option = dash "Period" colon period crlf
yesno = "Yes" / "No"
domainstatus = "Active" / "Registry-Lock" / "Registry-Hold" /
"Registrar-Lock" / "Registrar-Hold" /
"Registry-Delete-Notify"
; Start of basic grammar.
year = 4digit
month = 2digit
day = 2digit
ymd = year dash month dash day
hour = 2digit
minute = 2digit
second = 2digit
split-second = 1digit
hms = hour colon minute colon second dot split-second
time-stamp = ymd space hms
ip-address = 1*3digit dot 1*3digit dot 1*3digit dot 1*3digit
password = 4*16printable-char
option-name = 1*128id-word
option-tag = dash option-name
option-value = 1*128id-word
attribute-name = 1*128id-word
attribute-value = 1*128printable-char
attribute-line = attribute-name colon attribute-value crlf
response = 3digit space 1*printable-char crlf
version-number = "RRP" space 1*digit dot 1*digit dot 1*digit
label = id-prefix [*61dns-char id-prefix]
sldn = label dot label
servername = *(label dot) sldn
period = %x31-39 / (%x31-39 %x30-39) ; "1" - "9" or "10" - "99"
period-option = dash "Period" colon period crlf
yesno = "Yes" / "No"
domainstatus = "Active" / "Registry-Lock" / "Registry-Hold" /
"Registrar-Lock" / "Registrar-Hold" /
"Registry-Delete-Notify"
; RRP commands and responses.
rrp = add / check / delete / describe / mod / quit / renew /
session / status / transfer
; RRP commands and responses.
rrp = add / check / delete / describe / mod / quit / renew /
session / status / transfer
add = add-request add-response check = check-request check-response delete = del-request del-response describe = describe-request describe-response mod = mod-request mod-response quit = quit-request quit-response renew = renew-request renew-response session = session-request session-response status = status-request status-response transfer = transfer-request transfer-response
添加=添加请求添加响应检查=检查请求检查响应删除=删除请求删除响应描述=描述请求描述响应mod=mod request mod response quit=退出请求退出响应续订=续订请求续订响应会话=会话请求会话响应状态=状态请求状态响应传输=传输请求传输响应
; ADD command. add-request = add-domain-request / add-nameserver-request add-response = add-domain-response / add-nameserver-response add-domain-request = "add" crlf "EntityName" colon "Domain" crlf "DomainName" colon sldn crlf [period-option] 0*13("NameServer" colon servername crlf) dot crlf add-nameserver-request = "add" crlf "EntityName" colon "NameServer" crlf "NameServer" colon servername crlf 1*("IPAddress" colon ip-address crlf) dot crlf add-domain-response = response "RegistrationExpirationDate" colon time-stamp crlf "status" colon domainstatus crlf dot crlf add-nameserver-response = response dot crlf
; 添加命令。add request=添加域请求/add nameserver request add response=添加域响应/add nameserver response add domain request=“add”crlf“EntityName”colon“domain”crlf“DomainName”colon sldn crlf[句点选项]0*13（“nameserver”colon servername crlf）dot crlf添加名称服务器请求=“add”crlf“EntityName”colon“nameserver”crlf“名称服务器”冒号服务器名称crlf 1*（“IPAddress”冒号ip地址crlf）点crlf添加域响应=响应“RegistrationExpirationDate”冒号时间戳crlf“状态”冒号域状态crlf点crlf添加名称服务器响应=响应点crlf
; CHECK command. check-request = check-domain-request / check-nameserver-request check-response = check-domain-response / check-nameserver-response check-domain-request = "check" crlf "EntityName" colon "Domain" crlf "DomainName" colon sldn crlf dot crlf check-nameserver-request = "check" crlf "EntityName" colon "NameServer" crlf "NameServer" colon servername crlf dot crlf check-domain-response = response
; 检查命令。检查请求=检查域请求/检查名称服务器请求检查响应=检查域响应/检查名称服务器响应检查域请求=“检查”crlf“EntityName”冒号“domain”crlf“DomainName”冒号sldn crlf点crlf检查名称服务器请求=“检查”crlf“EntityName”冒号“nameserver”crlf“nameserver”冒号服务器名crlf点crlf检查域响应=响应
dot crlf check-nameserver-response = available-check-nameserver-response / notavailable-check-nameserver-response available-check-nameserver-response = response dot crlf notavailable-check-nameserver-response = response 1*("IPAddress" colon ip-address crlf) dot crlf
点crlf检查名称服务器响应=可用检查名称服务器响应/不可用检查名称服务器响应可用检查名称服务器响应=响应点crlf不可用检查名称服务器响应=响应1*（“IPAddress”冒号ip地址crlf）点crlf
; DEL command. del-request = del-domain-request / del-nameserver-request del-response = response dot crlf del-domain-request = "del" crlf "EntityName" colon "Domain" crlf "DomainName" colon sldn crlf dot crlf del-nameserver-request = "del" crlf "EntityName" colon "NameServer" crlf "NameServer" colon servername crlf dot crlf
; DEL命令。del request=del domain request/del nameserver request del response=response dot crlf del domain request=“del”crlf”EntityName“冒号”domain“crlf”domain“域名”冒号sldn crlf dot crlf del nameserver request=“del”crlf”EntityName“冒号”nameserver“冒号服务器名crlf dot crlf”
; DESCRIBE command. describe-request = "describe" crlf [target-option] *(option-tag colon option-value crlf) dot crlf describe-response = response "Protocol" colon version-number crlf *attribute-line dot crlf target-option = dash "Target" colon "Protocol" crlf
; 描述命令。descripe request=“descripe”crlf[目标选项]*（选项标签冒号选项值crlf）dot crlf descripe response=响应“协议”冒号版本号crlf*属性行dot crlf目标选项=破折号“目标”冒号“协议”crlf
; MOD command. mod-request = mod-domain-request / mod-nameserver-request mod-response = response *attribute-line dot crlf mod-domain-request = "mod" crlf "EntityName" colon "Domain" crlf "DomainName" colon sldn crlf *(add-attribute-value-line / remove-attribute-value-line / replace-attribute-value-line)
; MOD命令。mod request=mod domain request/mod nameserver request mod response=response*属性行dot crlf mod domain request=“mod”crlf”EntityName“冒号”domain“crlf”domain“域名”冒号sldn crlf*（添加属性值行/删除属性值行/替换属性值行）
dot crlf mod-nameserver-request = "mod" crlf "EntityName" colon "NameServer" crlf "NameServer" colon servername crlf ["NewNameServer" colon attribute-value crlf] *(add-attribute-value-line / remove-attribute-value-line / replace-attribute-value-line) dot crlf add-attribute-value-line = attribute-name colon new-attribute-value remove-attribute-value-line = attribute-name colon old-attribute-value "=" replace-attribute-value-line = attribute-name colon old-attribute-value "=" new-attribute-value old-attribute-value = attribute-value new-attribute-value = attribute-value
dot crlf mod nameserver request=“mod”crlf”EntityName“colon”nameserver“crlf”nameserver“colon servername crlf[“NewNameServer”colon属性值crlf]*（添加属性值行/删除属性值行/替换属性值行）dot crlf添加属性值行=属性名称冒号新属性值删除属性值行=属性名称冒号旧属性值“=”替换属性值行=属性名称冒号旧属性值“=”新属性值旧属性值=属性值新属性值=属性值
; QUIT command. quit-request = "quit" crlf dot crlf quit-response = response dot crlf
; 退出命令。退出请求=“退出”crlf点crlf退出响应=响应点crlf
; RENEW command. renew-request = "renew" crlf "EntityName" colon "Domain" crlf "DomainName" colon sldn crlf [renew-period-option] dot crlf expiration-year-option = dash "CurrentExpirationYear" colon year crlf renew-period-option = period-option expiration-year-option / expiration-year-option period-option renew-response = response "RegistrationExpirationDate" colon time-stamp crlf dot crlf
; 更新命令。续订请求=“续订”crlf“EntityName”冒号“Domain”crlf“DomainName”冒号sldn crlf[续订期限选项]dot crlf到期年份选项=破折号“CurrentExpirationYear”冒号年份crlf续订期限选项=期限选项到期年份选项/到期年份选项期限选项续订响应=响应“RegistrationExpirationDate”冒号时间戳crlf点crlf
; SESSION command. session-request = "session" crlf registrar-id-option registrar-password-option [registrar-newpassword-option] dot crlf session-response = response dot crlf registrar-id-option = dash "Id" colon option-value crlf registrar-password-option =
; 会话命令。会话请求=“会话”crlf注册器id选项注册器密码选项[注册器新密码选项]dot crlf会话响应=响应dot crlf注册器id选项=破折号“id”冒号选项值crlf注册器密码选项=
dash "Password" colon password crlf registrar-newpassword-option = dash "NewPassword" colon password crlf
破折号“密码”冒号密码crlf注册器新密码选项=破折号“新密码”冒号密码crlf
; STATUS command. status-request = status-domain-request / status-nameserver-request status-response = response *attribute-line dot crlf status-domain-request = "status" crlf "EntityName" colon "Domain" crlf "DomainName" colon sldn crlf dot crlf status-nameserver-request = "status" crlf "EntityName" colon "NameServer" crlf "NameServer" colon servername crlf dot crlf
; 状态命令。状态请求=状态域请求/状态名称服务器请求状态响应=响应*属性行dot crlf status domain request=“status”crlf“EntityName”colon“domain”crlf“DomainName”colon sldn crlf dot crlf status nameserver request=“status”crlf“EntityName”colon“nameserver”crlf“nameserver”冒号服务器名crlf点crlf
; TRANSFER command. transfer-request = "transfer" crlf [approve-option] "EntityName" colon "Domain" crlf "DomainName" colon sldn crlf dot crlf transfer-response = response "RegistrationExpirationDate" colon time-stamp crlf dot crlf approve-option = dash "Approve" colon yesno crlf
; 转移命令。传输请求=“传输”crlf[批准选项]“实体名称”冒号“域”crlf“域名”冒号sldn crlf点crlf传输响应=响应“注册ExpirationDate”冒号时间戳crlf点crlf批准选项=破折号“批准”冒号是否crlf
; End of grammar.
; 语法结束。
RRP is defined using 7-bit US-ASCII characters. Other character sets and character codes are not currently supported.
RRP使用7位US-ASCII字符定义。当前不支持其他字符集和字符代码。
RRP was not designed to provide bulk data query features. The primary goal of the original protocol designers was to provide a fast, light weight transactional protocol that could be implemented with minimal need for database queries that would take a "long" time to complete or that would return a "large" amount of data. Implementers SHOULD consider developing offline reporting features to provide bulk data for registrar reporting in a fashion suitable for the given registry-registrar operating environment.
RRP不是为提供批量数据查询功能而设计的。原始协议设计者的主要目标是提供一个快速、轻量级的事务协议，该协议可以在不需要数据库查询的情况下实现，而数据库查询需要“很长”的时间才能完成，或者返回“大量”数据。实施者应考虑开发离线报告特征，以适合于给定注册表注册操作环境的方式为注册者报告提供大量数据。
This version of RRP does contain a few limitations noted over the course of several months of operational experience with live domain name registrars. Later versions of this protocol or its successors should strive to resolve or address each of the following issues:
这个版本的RRP确实包含几个限制，这些限制是在几个月的实时域名注册运营经验中注意到的。本议定书的后续版本或其后续版本应努力解决或解决以下每一个问题：
The DESCRIBE command should return information describing System-defined default implementation values.
descripe命令应返回描述系统定义的默认实现值的信息。
Use of the RENEW command without the "CurrentExpirationYear" and "Period" parameters does not provide idempotency. Repeated execution of a RENEW command without these parameters can result in multiple successful RENEW commands, which may not be the desired action if a registrar is retrying a RENEW command due to network connectivity problems.
使用不带“CurrentExpirationYear”和“Period”参数的RENEW命令不会提供幂等性。在没有这些参数的情况下重复执行续订命令可能会导致多个续订命令成功，如果注册器由于网络连接问题而重试续订命令，则这可能不是所需的操作。
Time stamps returned by RRP do not include time zone identifiers and SHOULD be interpreted as local registry time.
RRP返回的时间戳不包括时区标识符，应解释为本地注册表时间。
The protocol does not provide features for a registrar to become aware of domain transfer requests and responses. Systems must rely on means outside of the protocol, such as electronic mail and/or registry-provided reports, to inform registrars of transfer requests and responses.
该协议没有为注册者提供了解域传输请求和响应的功能。系统必须依靠议定书以外的手段，如电子邮件和/或登记处提供的报告，将转让请求和答复通知登记处。
The protocol does not provide features for a registrar to determine all of the domains served by a name server. Systems must provide this information using a method outside of the protocol, such as through periodic extracts from a System database.
该协议不提供注册器确定名称服务器服务的所有域的功能。系统必须使用协议之外的方法提供此信息，例如通过定期从系统数据库提取。
The protocol does not provide features to manage lame delegation of name servers. Any registrar may "use" name servers registered by another registrar. When a registrar tries to delete a domain or name server it is quite possible that name servers in the domain to be deleted or the name server to be deleted will be associated with other live domains, precluding immediate deletion. Systems must rely on means outside of the protocol to manage lame delegation of name servers.
该协议不提供管理名称服务器的lame委派的功能。任何注册商均可“使用”由另一注册商注册的名称服务器。当注册者试图删除域或名称服务器时，很可能要删除的域中的名称服务器或要删除的名称服务器将与其他活动域关联，从而无法立即删除。系统必须依靠协议之外的方法来管理名称服务器的lame委托。
The use of "=" within the MOD command to indicate a value to be removed is somewhat confusing. A more explicit means of identifying old and new attribute values within the protocol syntax could make this feature more obvious.
MOD命令中使用“=”表示要删除的值有点令人困惑。在协议语法中标识新旧属性值的更明确的方法可以使此功能更加明显。
The CHECK command also returns name server IP addresses when returning positive confirmation of the registration of a name server. This extra information may be useful, but it is inconsistent with the limited function of the command. The command should return a positive or negative response and nothing more.
当返回名称服务器注册的肯定确认时，CHECK命令还返回名称服务器IP地址。这些额外的信息可能有用，但与命令的有限功能不一致。该命令应返回肯定或否定响应，仅此而已。
The formal protocol syntax described in this document requires a specific order for the elements of a command entity block and command options. The NSI Registry's server-side implementation of the protocol provides the additional flexibility of allowing order independent specification of options and entity block elements. Client-side implementers are strongly urged to observe the order of command elements as specified here to ensure compliance if the more restricted form is enforced in the future.
本文档中描述的正式协议语法要求命令实体块和命令选项元素的特定顺序。NSI注册表的协议服务器端实现提供了额外的灵活性，允许对选项和实体块元素进行顺序无关的规范。强烈建议客户端实现人员遵守此处指定的命令元素顺序，以确保将来强制执行更严格的表单时的遵从性。
RRP does not return time stamps or transaction identifiers to track transactions. The NSI Registry provides registrars with daily and weekly reports that include time stamps in local registry time to document and synchronize data on a per-registrar basis.
RRP不会返回时间戳或事务标识符来跟踪事务。NSI注册中心为注册中心提供每日和每周报告，其中包括本地注册中心记录和同步每个注册中心数据的时间戳。
Misuse of the Registry Registrar Protocol can have catastrophic operational consequences for registrants, registrars, and registries. As such, all registrars must be authenticated prior to all interactions with the registry. In addition, all data exchanged between the registrar and the registry must be protected to avoid unintended disclosure of information.
滥用注册登记员协议可能会给注册人、注册人和注册处带来灾难性的运营后果。因此，在与注册中心进行所有交互之前，必须对所有注册中心进行身份验证。此外，书记官长和书记官处之间交换的所有数据都必须受到保护，以避免意外披露信息。
IANA assigned TCP port 648 for RRP use in November 1998. No other action is required of IANA to support operation of this protocol.
IANA于1998年11月将TCP端口648分配给RRP使用。IANA无需采取其他行动来支持本协议的运行。
IANA has reserved certain IPv4 address ranges as described in [ALLOCATION]. Implementers MUST ensure that name server IP addresses do not fall into one of the reserved address ranges to avoid operational DNS errors.
IANA保留了某些IPv4地址范围，如[ALLOCATION]中所述。实施者必须确保名称服务器IP地址不属于保留地址范围之一，以避免操作DNS错误。
[ABNF] Crocker, D. (Editor) and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[ABNF]Crocker，D.（编辑）和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。
[ALLOCATION] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D. and J. Postel, "Internet Registry IP Allocation Guidelines", BCP 12, RFC 2050, November 1996.
[分配]Hubbard，K.，Kosters，M.，Conrad，D.，Karrenberg，D.和J.Postel，“互联网注册IP分配指南”，BCP 12，RFC 2050，1996年11月。
[MUSTSHOULD] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[MUSTSHOULD]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[SSL] A. Frier, P. Karlton, and P. Kocher, "The SSL 3.0 Protocol", Netscape Communications Corp., November 18, 1996.
[SSL]A.Frier，P.Karlton和P.Kocher，“SSL 3.0协议”，网景通信公司，1996年11月18日。
[TLS] Dierks T. and C. Allen, "The TLS Protocol Version 1.0", RFC 2246, January 1999.
[TLS]Dierks T.和C.Allen，“TLS协议1.0版”，RFC 2246，1999年1月。
Many people have contributed significantly to this document and the protocol it describes. Brad McMillen and Neeran Saraf deserve special mention as co-authors of an earlier internal protocol specification. Other content contributors to the earlier internal specification include Aristotle Balogh, Chris Bason, Mark Kosters, Jasdip Singh, and Yibing Wu. Finally, significant contributors to the review of this document include Steve Mahlstedt and Chris Smith.
许多人对本文件及其描述的协议做出了重大贡献。Brad McMillen和Neeran Saraf作为早期内部协议规范的共同作者值得特别提及。早期内部规范的其他内容贡献者包括亚里士多德·巴洛格、克里斯·巴森、马克·科斯特斯、贾斯蒂普·辛格和吴一冰。最后，本文件审查的重要贡献者包括Steve Mahlstedt和Chris Smith。
Scott Hollenbeck Network Solutions, Inc. Registry 505 Huntmar Park Dr. Herndon, VA 20170 USA
Scott Hollenbeck Network Solutions，Inc.注册号505美国弗吉尼亚州亨特马公园Herndon博士，邮编20170
EMail: shollenb@netsol.com
EMail: shollenb@netsol.com
Manoj Srivastava Network Solutions, Inc. Registry 505 Huntmar Park Dr. Herndon, VA 20170 USA
Manoj Srivastava Network Solutions，Inc.注册号：美国弗吉尼亚州亨特马尔公园505 Herndon博士，邮编：20170
EMail: manojs@netsol.com
EMail: manojs@netsol.com
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编辑功能的资金目前由互联网协会提供。