VeriSign Registry Registrar Protocol (RRP) Version 2.0.0
RFC 3632

Document Type RFC - Informational (December 2003; No errata)
Updates RFC 2832
Last updated 2015-10-14
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3632 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      S. Hollenbeck
Request for Comments: 3632                             S. Veeramachaneni
Updates: 2832                                           S. Yalamanchilli
Category: Informational                                   VeriSign, Inc.
                                                           November 2003

        VeriSign Registry Registrar Protocol (RRP) Version 2.0.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 (2003).  All Rights Reserved.

Abstract

   This document updates version 1.1.0 of the Network Solutions Inc.
   (NSI) Registry Registrar Protocol (RRP) specified in RFC 2832.  The
   changes described in this document combined with the base
   specification documented in RFC 2832 specify version 2.0.0 of the
   VeriSign Registry Registrar Protocol.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Protocol Updates . . . . . . . . . . . . . . . . . . . . . . .  2
       2.1.  Response Codes . . . . . . . . . . . . . . . . . . . . .  2
       2.2.  TRANSFER Command Update  . . . . . . . . . . . . . . . .  3
       2.3.  IPv6 Name Server Addresses . . . . . . . . . . . . . . .  4
   3.  Internationalization Considerations  . . . . . . . . . . . . .  6
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  6
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  6
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  6
   7.  Normative References . . . . . . . . . . . . . . . . . . . . .  6
   8.  Authors' Addresses . . . . . . . . . . . . . . . . . . . . . .  7
   9.  Full Copyright Statement . . . . . . . . . . . . . . . . . . .  8

Hollenbeck, et al.           Informational                      [Page 1]
RFC 3632                  VeriSign RRP v2.0.0              November 2003

1.  Introduction

   The Network Solutions, Inc. (NSI) Registry Registrar Protocol (RRP)
   was developed by NSI in 1998 and 1999 to allow multiple registrars to
   provide second level Internet domain name registration services in
   the top level domains (TLDs) administered by the NSI TLD registry.
   Version 1.1.0 of the NSI RRP was published as Informational RFC 2832
   [2] in May 2000.  This document describes changes to RFC 2832 that
   specify version 2.0.0 of the protocol.

   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 BCP 14, RFC
      2119 [1].

      In examples, "C:" represents lines sent by a protocol client and
      "S:"  represents lines returned by a protocol server.

2.  Protocol Updates

   This specification describes several modifications to RFC 2832 [2]:
   two new response codes have been added, domain TRANSFER command
   processing has been updated to allow a client to cancel a requested
   domain transfer, and support for IPv6 name server addresses has been
   added.

2.1.  Response Codes

   Section 5.1 of RFC 2832 [2] has been updated to include two
   additional error response codes.

   510 Invalid encoding

   The value of a domain name or name server entity contains invalid
   ASCII compatible encoding used to represent an internationalized
   domain or host name.  The encoding is checked and verified in two
   situations: when registering an internationalized domain name or name
   server name, and when changing the name of a name server and the new
   name of the server is internationalized.

Hollenbeck, et al.           Informational                      [Page 2]
RFC 3632                  VeriSign RRP v2.0.0              November 2003

   Section 5.2 of RFC 2832 [2] has been updated to include response code
   510 as a possible error value returned from the ADD command:

   Command: ADD
   Success: 200, 220
   Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 510, 520, 531,
   535, 540, 541, 545, 546, 547, 549, 550, 554

   557 Name server locked

   An attempt has been made to modify or delete a name server that is
   hosting a TLD in the root zone.  Modifications to the root zone can
   only be made with the approval of the U.S. Department of Commerce and
   IANA, so if the registrar absolutely needs to modify or delete such a
   name server, the action needs to be coordinated through the registry
   operator using an out-of-band communications channel.

   Section 5.2 of RFC 2832 [2] has been updated to include response code
   557 as a possible error value returned from the DEL and MOD commands:

   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, 557
Show full document text