Generic Registry-Registrar Protocol Requirements
draft-ietf-provreg-grrp-reqs-06

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3375.
Author Scott Hollenbeck
Last updated 2015-10-14 (Latest revision 2002-02-25)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
txt htmlized bibtex bibxml
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3375 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Patrik Fältström
IESG note
Send notices to (None)
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-provreg-grrp-reqs-06 
A new Request for Comments is now available in online RFC libraries.

        RFC 3375

        Title:      Generic Registry-Registrar Protocol Requirements
        Author(s):  S. Hollenbeck
        Status:     Informational
        Date:       September 2002
        Mailbox:    shollenbeck@verisign.com
        Pages:      21
        Characters: 46022
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-grrp-reqs-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3375.txt

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 document is a product of the Provisioning Registry Protocl
Working Group. 

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.