Generic Registry-Registrar Protocol Requirements
RFC 3375
|
Document |
Type |
|
RFC - Informational
(September 2002; No errata)
|
|
Author |
|
Scott Hollenbeck
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 3375 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Patrik Fältström
|
|
IESG note |
|
Responsible: RFC Editor
|
|
Send notices to |
|
(None)
|
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.
Show full document text