The generic registry-registrar protocol requirements draft has been updated
to include comments received after last month's last call. This version
includes updates based on comments received from Marc Blanchet, Peter Chow,
Eric Schaetzlein, and Mike Lampson; please provide any final comments to the
RRP mailing list by midnight GMT Friday 29 September. Given that we did a
two-week last call last month, one additional week should be enough to get
this finished.
Scott Hollenbeck
VeriSign Global Registry Services
-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Friday, September 22, 2000 6:46 AM
Subject: I-D ACTION:draft-hollenbeck-grrp-reqs-04.txt
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
Title : Generic Registry Registrar Protocol (GRRP)
Requirements
Author(s) : S. Hollenbeck
Filename : draft-hollenbeck-grrp-reqs-04.txt
Pages : 23
Date : 21-Sep-00
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 Top Level Domain (TLD)
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.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hollenbeck-grrp-reqs-04.txt
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-hollenbeck-grrp-reqs-04.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv@ietf.org.
In the body type:
"FILE /internet-drafts/draft-hollenbeck-grrp-reqs-04.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
---------
See http://www.nsiregistry.com/maillist/rrp/
for message archives and subscription management information.
This archive was generated by hypermail 2b29 : Fri Sep 22 2000 - 08:55:32 EDT