rfc3375.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 1,180 行 · 第 1/4 页

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 ................................. 15
   7.1 Reliability ........................................ 15
   7.2 Availability ....................................... 15
   7.3 Scalability ........................................ 16
   7.4 Maintainability .................................... 16
   7.5 Extensibility ...................................... 16
   7.6 Security ........................................... 16
   8.  Other Requirements ................................. 17
   8.1 Database Requirements .............................. 17
   8.2 Operational Requirements ........................... 17
   8.3 Site Adaptation Requirements ....................... 17
   8.4 Data Collection Requirements ....................... 17
   9.  Internationalization Requirements .................. 18
   10. IANA Considerations ................................ 18
   11. Security Considerations ............................ 18
   12. Acknowledgements ................................... 19
   13. References ......................................... 19
   14. Editor's Address ................................... 20
   15. Full Copyright Statement ........................... 21

1. Introduction

   The advent of shared domain name registration systems illustrates the
   utility of a common, generic protocol for registry-registrar
   interaction.  A standard generic protocol will allow registrars to
   communicate with multiple registries through a common interface,
   reducing operational complexity.  This document describes high level
   functional and interface requirements for a generic provisioning
   protocol suitable for registry-registrar operations.  Detailed
   technical requirements are not addressed in this document.

1.1 Definitions, Acronyms, and Abbreviations

   ccTLD: Country Code Top Level Domain.  ".us" is an example of a
   ccTLD.

   DNS: Domain Name System

   gTLD: Generic Top Level Domain.  ".com" is an example of a gTLD.




Hollenbeck                   Informational                      [Page 2]

RFC 3375                Generic RRP Requirements          September 2002


   IANA: Internet Assigned Numbers Authority

   IETF: Internet Engineering Task Force

   IP Address: Either or both IPv4 or IPv6 address.

   IPv4: Internet Protocol version 4

   IPv6: Internet Protocol version 6

   RRP: Registry-Registrar Protocol

   TLD: Top Level Domain.  A generic term used to describe both gTLDs
   and ccTLDs that exist under the top-level root of the domain name
   hierarchy.

   Exclusive Registration System: A domain name registration system in
   which registry services are limited to a single registrar.  Exclusive
   Registration Systems are either loosely coupled (in which case the
   separation between registry and registrar systems is readily
   evident), or tightly coupled (in which case the separation between
   registry and registrar systems is obscure).

   Name Space: The range of values that can be assigned within a
   particular node of the domain name hierarchy.

   Object: A generic term used to describe entities that are created,
   updated, deleted, and otherwise managed by a generic registry-
   registrar protocol.

   Registrant: An entity that registers domain names in a registry
   through the services provided by a registrar.  Registrants include
   individuals, organizations, and corporations.

   Registrar: An entity that provides front-end domain name registration
   services to registrants, providing a public interface to registry
   services.

   Registry: An entity that provides back-end domain name registration
   services to registrars, managing a central repository of information
   associated with domain name delegations.  A registry is typically
   responsible for publication and distribution of zone files used by
   the Domain Name System.

   Shared Registration System: A domain name registration system in
   which registry services are shared among multiple independent
   registrars.  Shared Registration Systems require a loose coupling
   between registrars and a registry.



Hollenbeck                   Informational                      [Page 3]

RFC 3375                Generic RRP Requirements          September 2002


   Thick Registry: A registry in which all of the information associated
   with registered entities, including both technical information
   (information needed to produce zone files) and social information
   (information needed to implement operational, business, or legal
   practices), is stored within the registry repository.

   Thin Registry: A registry in which all elements of the social
   information associated with registered entities is distributed
   between a shared registry and the registrars served by the registry.

   Zone: The complete set of information for a particular "pruned"
   subtree of the domain space.  The zone concept is described fully in
   [RFC1035].

2. General Description

   A basic understanding of domain name registration systems provides
   focus for the enumeration of functional and interface requirements of
   a protocol to serve those systems.  This section provides a high-
   level description of domain name registration systems to provide
   context for the requirements identified later in this document.

2.1 System Perspective

   A domain name registration system consists of a protocol and
   associated software and hardware that permits registrars to provide
   Internet domain name registration services within the name spaces
   administered by a registry.  A registration system can be shared
   among multiple competing registrars, or it can be served by a single
   registrar that is either tightly or loosely coupled with back-end
   registry services.  The system providing registration services for
   the .com, .net, and .org gTLDs is an example of a shared registration
   system serving multiple competing registrars.  The systems providing
   registration services for some ccTLDs and the .gov and .mil gTLDs are
   examples of registration systems served by a single registrar.

2.2 System Functions

   Registrars access a registry through a protocol to register objects
   and perform object management functions.  Required functions include
   session management; object creation, update, renewal, and deletion;
   object query; and object transfer.

   A registry generates DNS zone files for the name spaces it serves.
   Zone files are created and distributed to a series of name servers
   that provide the foundation for the domain name system.





Hollenbeck                   Informational                      [Page 4]

RFC 3375                Generic RRP Requirements          September 2002


2.3 User Characteristics

   Protocol users fall into two broad categories: entities that use
   protocol client implementations and entities that use protocol server
   implementations, though an entity can provide both client and server
   services if it provides intermediate services.  A protocol provides a
   loose coupling between these communicating entities.

2.4 Assumptions

   There is one and only one registry that is authoritative for a given
   name space and zone.

   A registry can be authoritative for more than one name space and
   zone.  Some registry operations can be billable.  The impact of a
   billable operation can be mitigated through the specification of
   non-billable operations that allow a registrar to make informed
   decisions before executing billable operations.

   A registry can choose to implement a subset of the features provided
   by a generic registry-registrar protocol.  A thin registry, for
   example, might not provide services to register social information.
   Specification of minimal implementation compliance requirements is
   thus an exercise left for a formal protocol definition document that
   addresses the functional requirements specified here.

   A protocol that meets the requirements described here can be called
   something other than "Generic Registry Registrar Protocol".

   The requirements described in this document are not intended to limit
   the set of objects that can be managed by a generic registry-
   registrar protocol.

3. Functional Requirements

   This section describes functional requirements for a registry-
   registrar protocol.  Technical requirements that describe how these
   requirements are to be met are out of scope for this document.













Hollenbeck                   Informational                      [Page 5]

RFC 3375                Generic RRP Requirements          September 2002


3.1 Session Management

   [1] The protocol MUST provide services to explicitly establish a
   client session with a registry server.

   [2] In a connection-oriented environment, a server MUST respond to
   connection attempts with information that identifies the server and
   the default server protocol version.