Browse Prior Art Database

NSI Registry Registrar Protocol (RRP) Version 1.1.0 (RFC2832)

IP.com Disclosure Number: IPCOM000003431D
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 32 page(s) / 71K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Hollenbeck: AUTHOR [+2]

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.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 4% of the total text.

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

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.

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.

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.

This document is being discussed on the "rrp" mailing list. To join

the list, send a message to with the

words "subscribe rrp" in the body of the message. There is also a web

site for the mailing list archives at

.

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.

In examples, "C:" represents lines sent by the registrar client and

"S:" represents lines sent by the registry server.

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