rfc2832.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   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>

4.3.4 DESCRIBE

   This command allows a registrar to obtain general information about
   an RRP implementation. The command MAY contain the following
   parameters:

   - The "Target" parameter set to value "Protocol".

   The implementation MUST return the protocol version number whether or
   not the request contains the "Target" parameter.

   Authorized User: All registrars MAY use the DESCRIBE command.

   Examples

   A registrar obtains general information about an RRP implementation:

   C:describe<crlf>
   C:-Target:Protocol<crlf>
   C:.<crlf>
   S:200 Command completed successfully<crlf>
   S:Protocol:RRP 1.1.0<crlf>
   S:.<crlf>

4.3.5 MOD

   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.



Hollenbeck & Srivastava      Informational                     [Page 14]

RFC 2832            NSI Registry Registrar Protocol             May 2000


4.3.5.1 Domain Modification

   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.

   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.

   Authorized User: The current registrar of a domain name MAY use the
   MOD command to modify the attributes of a domain name.

   Examples

   A registrar removes one name server (ns1) from a domain and adds a
   new name server (ns3) to the same domain:

   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>

4.3.5.2 Name Server Modification

   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.









Hollenbeck & Srivastava      Informational                     [Page 15]

RFC 2832            NSI Registry Registrar Protocol             May 2000


   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.

   Authorized User: The current registrar of a name server MAY use the
   MOD command to modify the attributes of a domain name.

   Examples

   A registrar changes the name and IP address of a name server:

   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>

4.3.6 QUIT

   This command allows a registrar to close an RRP connection. A
   response MUST be sent before closing the connection.

   Authorized User: All registrars MAY use the QUIT command.

   Examples

   A registrar ends an RRP session and closes an existing connection:

   C:quit<crlf>
   C:.<crlf>
   S:220 Command completed successfully. Server closing connection<crlf>
   S:.<crlf>










Hollenbeck & Srivastava      Informational                     [Page 16]

RFC 2832            NSI Registry Registrar Protocol             May 2000


4.3.7 RENEW

   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.

   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.

   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.

   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>



Hollenbeck & Srivastava      Informational                     [Page 17]

RFC 2832            NSI Registry Registrar Protocol             May 2000


4.3.8 SESSION

   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:

   - The "Id" parameter set to the registrar's System user ID.
   - The "Password" parameter set to the registrar's current System
     password.

   The request to establish an RRP session MAY contain a new password
   for the registrar in a single instance of the "NewPassword"
   parameter.

   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.

   Authorized User: All registrars MAY use the SESSION command.

   Examples

   A registrar establishes an RRP session:

   C:session<crlf>
   C:-Id:registrarA<crlf>
   C:-Password:i-am-registrarA<crlf>
   C:.<crlf>
   S:200 Command completed successfully<crlf>
   S:.<crlf>

4.3.9 STATUS

   This command allows a registrar to determine the current status of a
   domain name or name server.

4.3.9.1 Domain Status

   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.





Hollenbeck & Srivastava      Informational                     [Page 18]

RFC 2832            NSI Registry Registrar Protocol             May 2000


   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.

   Authorized User: The current registrar of a domain name MAY use the
   STATUS command to view current domain name attributes.

   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>







Hollenbeck & Srivastava      Informational                     [Page 19]

RFC 2832            NSI Registry Registrar Protocol             May 2000


   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>

4.3.9.2 Name Server Status

   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.

   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.