RFC 3632 (rfc3632) - Page 2 of 8
VeriSign Registry Registrar Protocol (RRP) Version 2
Alternative Format: Original Text Document
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