Browse Prior Art Database

VeriSign Registry Registrar Protocol (RRP) Version 2.0.0 (RFC3632)

IP.com Disclosure Number: IPCOM000020552D
Original Publication Date: 2003-Nov-01
Included in the Prior Art Database: 2003-Nov-27
Document File: 9 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Hollenbeck: AUTHOR [+3]

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 26% of the total text.

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 inval...