Browse Prior Art Database

Generic Registry-Registrar Protocol Requirements (RFC3375)

IP.com Disclosure Number: IPCOM000009755D
Original Publication Date: 2002-Sep-01
Included in the Prior Art Database: 2002-Sep-17
Document File: 22 page(s) / 46K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Hollenbeck: AUTHOR

Abstract

This document describes high-level functional and interface requirements for a client-server protocol for the registration and management of Internet domain names in shared registries. Specific technical requirements detailed for protocol design are not presented here. Instead, this document focuses on the basic functions and interfaces required of a protocol to support multiple registry and registrar operational models.

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

Network Working Group                                      S. Hollenbeck

Request for Comments: 3375                                Verisign, Inc.

Category: Informational                                   September 2002

            Generic Registry-Registrar Protocol Requirements

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 (2002).  All Rights Reserved.

Abstract

   This document describes high-level functional and interface

   requirements for a client-server protocol for the registration and

   management of Internet domain names in shared registries.  Specific

   technical requirements detailed for protocol design are not presented

   here.  Instead, this document focuses on the basic functions and

   interfaces required of a protocol to support multiple registry and

   registrar operational models.

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 [RFC2119].

Table of Contents

   1.  Introduction .......................................  2

   1.1 Definitions, Acronyms, and Abbreviations ...........  2

   2.  General Description ................................  4

   2.1 System Perspective .................................  4

   2.2 System Functions ...................................  4

   2.3 User Characteristics ...............................  5

   2.4 Assumptions ........................................  5

   3.  Functional Requirements ............................  5

   3.1 Session Management .................................  6

   3.2 Identification and Authentication ..................  6

   3.3 Transaction Identification .........................  7

   3.4 Object Management ..................................  7

   3.5 Domain Status Indicators ........................... 13

Hollenbeck                   Informational                      [Page 1]

RFC 3375                Generic RRP Requirements          September 2002

   3.6 Transaction Completion Status ...................... 13

   4.  External Interface Requirements .................... 14

   4.1 User, Hardware, and Software Interfaces ............ 14

   4.2 Communications Interfaces .......................... 14

   5.  Performance Requirements ........................... 14

   6.  Design Constraints ................................. 14

   6.1 Standards Compliance ............................... 14

   6.2 Hardware Limitations ............................... 15

   7.  Service Attributes ................................. 1...