idnits 2.17.1 draft-ietf-provreg-grrp-reqs-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3375 5 Title: Generic Registry-Registrar Protocol Requirements 6 Author(s): S. Hollenbeck 7 Status: Informational 8 Date: September 2002 9 Mailbox: shollenbeck@verisign.com 10 Pages: 21 11 Characters: 46022 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-provreg-grrp-reqs-06.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3375.txt 18 This document describes high-level functional and interface 19 requirements for a client-server protocol for the registration and 20 management of Internet domain names in shared registries. Specific 21 technical requirements detailed for protocol design are not presented 22 here. Instead, this document focuses on the basic functions and 23 interfaces required of a protocol to support multiple registry and 24 registrar operational models. 26 This document is a product of the Provisioning Registry Protocl 27 Working Group. 29 This memo provides information for the Internet community. It does 30 not specify an Internet standard of any kind. Distribution of this 31 memo is unlimited. 33 This announcement is sent to the IETF list and the RFC-DIST list. 34 Requests to be added to or deleted from the IETF distribution list 35 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 36 added to or deleted from the RFC-DIST distribution list should 37 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 39 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 40 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 41 help: ways_to_get_rfcs. For example: 43 To: rfc-info@RFC-EDITOR.ORG 44 Subject: getting rfcs 46 help: ways_to_get_rfcs 48 Requests for special distribution should be addressed to either the 49 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 50 specifically noted otherwise on the RFC itself, all RFCs are for 51 unlimited distribution.echo 52 Submissions for Requests for Comments should be sent to 53 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 54 Authors, for further information.