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

Internet-Drafts@ietf.org Thu, 08 August 1996 13:34 UTC

Received: from ietf.org by ietf.org id aa12545; 8 Aug 96 9:34 EDT
Received: from localhost by ietf.org id aa11944; 8 Aug 96 9:26 EDT
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-01.txt
Date: Thu, 08 Aug 1996 09:26:03 -0400
X-Orig-Sender: cclark@ietf.org
Message-ID: <9608080926.aa11944@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-01.txt
       Pages     : 10
       Date      : 08/07/1996

It has become a common practice to use symbolic names (usually CNAMEs) 
in the Domain Name Service (DNS - [1,2]) to refer to network services 
such as anonymous FTP [3] servers, Gopher [4] servers, and most 
notably World-Wide Web HTTP [5] 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 (DNS SRV) 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-01.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ietf-ids-dnsnames-01.txt
 
Internet-Drafts directories are located at:	
	                                                
     o  Africa                                   
        Address:  ftp.is.co.za (196.4.160.8)	
	                                                
     o  Europe                                   
        Address:  nic.nordu.net (192.36.148.17)	
        Address:  ftp.nis.garr.it (193.205.245.10)
	                                                
     o  Pacific Rim                              
        Address:  munnari.oz.au (128.250.1.21)	
	                                                
     o  US East Coast                            
        Address:  ds.internic.net (198.49.45.10)	
	                                                
     o  US West Coast                            
        Address:  ftp.isi.edu (128.9.0.32)  	
	                                                
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-01.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.
							
For questions, please mail to Internet-Drafts@ietf.org
							

Below is the data which will enable a MIME compliant mail reader 
implementation to automatically retrieve the ASCII version
of the Internet-Draft.
ftp://ds.internic.net/internet-drafts/draft-ietf-ids-dnsnames-01.txt"><ftp://ds.internic.net/internet-drafts/draft-ietf-ids-dnsnames-01.txt>