[registrars] Fwd: RFC 3912 on WHOIS Protocol Specification]

[Tim Ruiz <tim@xxxxxxxxxxx>]

FYI<BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT:
blue 2px solid"><BR>Date: Fri, 24 Sep 2004 09:37:39 -0700<BR>From:
rfc-editor@xxxxxxxxxxxxxx<BR>To: ietf-announce@xxxxxxxx<BR>Cc:
rfc-editor@xxxxxxxxxxxxxx<BR>Subject: RFC 3912 on WHOIS Protocol
Specification<BR><BR><BR><BR>A new Request for Comments is now
available in online RFC libraries.<BR><BR><BR>&nbsp; &nbsp; &nbsp;
&nbsp;RFC 3912<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;Title: &nbsp; &nbsp;
&nbsp;WHOIS Protocol Specification<BR>&nbsp; &nbsp; &nbsp;
&nbsp;Author(s): &nbsp;L. Daigle<BR>&nbsp; &nbsp; &nbsp; &nbsp;Status:
&nbsp; &nbsp; Standards Track<BR>&nbsp; &nbsp; &nbsp; &nbsp;Date:
&nbsp; &nbsp; &nbsp; September 2004<BR>&nbsp; &nbsp; &nbsp;
&nbsp;Mailbox: &nbsp; &nbsp;leslie@xxxxxxxxxxxxxxxx<BR>&nbsp; &nbsp;
&nbsp; &nbsp;Pages: &nbsp; &nbsp; &nbsp;4<BR>&nbsp; &nbsp; &nbsp;
&nbsp;Characters: 7770<BR>&nbsp; &nbsp; &nbsp; &nbsp;Obsoletes:
&nbsp;954, 812<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;I-D Tag: &nbsp;
&nbsp;draft-daigle-rfc954bis-01.txt<BR><BR>&nbsp; &nbsp; &nbsp;
&nbsp;URL: &nbsp; &nbsp; &nbsp;
&nbsp;ftp://ftp.rfc-editor.org/in-notes/rfc3912.txt<BR><BR><BR>This
document updates the specification of the WHOIS protocol,<BR>thereby
obsoleting RFC 954. &nbsp;The update is intended to remove
the<BR>material from RFC 954 that does not have to do with the
on-the-wire<BR>protocol, and is no longer applicable in today's
Internet. &nbsp;This<BR>document does not attempt to change or update
the protocol per se, or<BR>document other uses of the protocol that
have come into existence<BR>since the publication of RFC
954.<BR><BR>This is now a Draft Standard Protocol.<BR><BR>This document
specifies an Internet standards track protocol for<BR>the Internet
community, and requests discussion and suggestions<BR>for improvements.
&nbsp;Please refer to the current edition of the<BR>"Internet Official
Protocol Standards" (STD 1) for the<BR>standardization state and status
of this protocol. &nbsp;Distribution<BR>of this memo is
unlimited.<BR><BR>This announcement is sent to the IETF list and the
RFC-DIST list.<BR>Requests to be added to or deleted from the IETF
distribution list<BR>should be sent to IETF-REQUEST@xxxxxxxx.
&nbsp;Requests to be<BR>added to or deleted from the RFC-DIST
distribution list should<BR>be sent to
RFC-DIST-REQUEST@xxxxxxxxxxxxxx.<BR><BR>Details on obtaining RFCs via
FTP or EMAIL may be obtained by sending<BR>an EMAIL message to
rfc-info@xxxxxxxxxxxxxx with the message body <BR>help:
ways_to_get_rfcs. &nbsp;For example:<BR><BR>&nbsp; &nbsp; &nbsp;
&nbsp;To: rfc-info@xxxxxxxxxxxxxx<BR>&nbsp; &nbsp; &nbsp;
&nbsp;Subject: getting rfcs<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;help:
ways_to_get_rfcs<BR><BR>Requests for special distribution should be
addressed to either the<BR>author of the RFC in question, or to
RFC-Manager@xxxxxxxxxxxxxx. &nbsp;Unless<BR>specifically noted
otherwise on the RFC itself, all RFCs are for<BR>unlimited
distribution.<BR><BR>Submissions for Requests for Comments should be
sent to<BR>RFC-EDITOR@xxxxxxxxxxxxxx. &nbsp;Please consult RFC 2223,
Instructions to RFC<BR>Authors, for further
information.<BR><BR><BR>Joyce K. Reynolds and Sandy
Ginoza<BR>USC/Information Sciences Institute<BR><BR></BLOCKQUOTE>