I-D ACTION:draft-ietf-ids-dnsnames-02.txt

Internet-Drafts@ietf.org Mon, 03 February 1997 15:28 UTC

Received: from ietf.org by ietf.org id aa17413; 3 Feb 97 10:28 EST
Received: from ietf.ietf.org by ietf.org id aa15007; 3 Feb 97 9:56 EST
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
cc: ietf-ids@umich.edu
Sender: ietf-announce-request@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ids-dnsnames-02.txt
Date: Mon, 03 Feb 1997 09:56:21 -0500
X-Orig-Sender: cclark@ietf.org
Message-ID: <9702030956.aa15007@ietf.org>

 A Revised Internet-Draft is available from the on-line Internet-Drafts 
 directories. This draft is a work item of the Integrated Directory 
 Services Working Group of the IETF.                                       

       Title     : Use of DNS Aliases for Network Services                 
       Author(s) : M. Hamilton, R. Wright
       Filename  : draft-ietf-ids-dnsnames-02.txt
       Pages     : 9
       Date      : 01/31/1997

It has become a common practice to use symbolic names (usually CNAMEs) in 
the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer to network 
services such as anonymous FTP [RFC-959] servers, Gopher [RFC-1436] 
servers, and most notably World-Wide Web HTTP [RFC-1945] servers.  This is 
desirable for a number of reasons.  It provides a way of moving services 
from one machine to another transparently, and a mechanism by which people 
or agents may programatically discover that an organization runs, say, 
a World-Wide Web server.   

Although this approach has been almost universally adopted, there is 
no standards document or similar specification for these commonly 
used names.  This document seeks to rectify this situation by 
gathering together the extant "folklore" on naming conventions, and 
proposes a mechanism for accommodating new protocols.   

It is important to note that these naming conventions do not provide 
a complete long term solution to the problem of finding a 
particular network service for a site.  There are efforts in 
other IETF working groups to address the long term solution 
to this problem, such as the Server Location Resource 
Records (DNSSRV) [RFC-2052] work.                                                      

Internet-Drafts are 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-ietf-ids-dnsnames-02.txt".
A URL for the Internet-Draft is:
Internet-Drafts directories are located at:	
     o  Africa:  ftp.is.co.za                    
     o  Europe:  ftp.nordu.net            	
     o  Pacific Rim: munnari.oz.au               
     o  US East Coast: ds.internic.net           
     o  US West Coast: ftp.isi.edu               
Internet-Drafts are also available by mail.	
Send a message to:  mailserv@ds.internic.net. In the body type: 
     "FILE /internet-drafts/draft-ietf-ids-dnsnames-02.txt".
NOTE: The mail server at ds.internic.net 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.