[registrars] FYI: Daigle on 954

[Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>]

I haven't look to see if there is any similarity with an ID I published
on the subject last September.

------- Forwarded Message

To: IETF-Announce: ;
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-daigle-rfc954bis-00.txt
Date: Fri, 13 Jun 2003 07:52:08 -0400
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

- --NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: WHOIS Protocol Specification
	Author(s)	: L. Daigle
	Filename	: draft-daigle-rfc954bis-00.txt
	Pages		: 4
	Date		: 2003-6-12
	
This document updates the specification of the WHOIS protocol,
thereby obsoleting RFC954 [1].  The update is intended to remove the
material from RFC954 that does not have to do with the on-the-wire
protocol, and is no longer applicable in today's Internet.  This
document does not attempt to change or update the protocol per se, or
document other uses of the protocol that have come into existence
since the publication of RFC954.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-daigle-rfc954bis-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-daigle-rfc954bis-00.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-daigle-rfc954bis-00.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.

- --NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

- --OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-6-13080717.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-daigle-rfc954bis-00.txt

- --OtherAccess
Content-Type: Message/External-body;
	name="draft-daigle-rfc954bis-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-6-13080717.I-D@ietf.org>

- --OtherAccess--

- --NextPart--




------- End of Forwarded Message