![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
A new Request for Comments is now available in online RFC libraries.
RFC 2345:
Title: Domain Names and Company Name Retrieval
Author(s): J. Klensin, T. Wolf, G. Oglesby
Status: Experimental
Date: May 1998
Mailbox: klensin at mci.net, ted at usa.net, gary at mci.net
Pages: 14
Characters: 29707
Updates/Obsoletes: None
URL: ftp://ftp.isi.edu/in-notes/rfc2345.txt
This document proposes a company name to URL mapping service based
on the oldest and least complex of Internet directory protocols,
whois, in order to explore whether an extremely simple and
widely-deployed protocol can succeed where more complex and
powerful options have failed or been excessively delayed.
This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind. Discussion and
suggestions for improvement are requested. 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at ISI.EDU
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 at ISI.EDU. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR at ISI.EDU. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Alegre Ramos
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.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.