RFC 3375 on Generic Registry-Registrar Protocol Requirements
rfc-editor@rfc-editor.org Tue, 17 September 2002 00:39 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21004; Mon, 16 Sep 2002 20:39:52 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA26341 for ietf-123-outbound.10@ietf.org; Mon, 16 Sep 2002 20:35:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA26089 for <all-ietf@loki.ietf.org>; Mon, 16 Sep 2002 19:59:24 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20187 for <all-ietf@ietf.org>; Mon, 16 Sep 2002 19:57:38 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNxMD22367; Mon, 16 Sep 2002 16:59:22 -0700 (PDT)
Message-Id: <200209162359.g8GNxMD22367@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3375 on Generic Registry-Registrar Protocol Requirements
Cc: rfc-editor@rfc-editor.org, ietf-provreg@CAFAX.SE
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 16 Sep 2002 16:59:22 -0700
Sender: rfc-ed@ISI.EDU
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.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.