I-D ACTION:draft-ietf-dnsind-clarify-05.txt

Internet-Drafts@ietf.org Tue, 04 February 1997 14:46 UTC

Received: from ietf.org by ietf.org id aa03963; 4 Feb 97 9:46 EST
Received: from ietf.ietf.org by ietf.org id aa03158; 4 Feb 97 9:43 EST
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
cc: namedroppers@internic.net
Sender: ietf-announce-request@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dnsind-clarify-05.txt
Date: Tue, 04 Feb 1997 09:43:08 -0500
X-Orig-Sender: cclark@ietf.org
Message-ID: <9702040943.aa03158@ietf.org>

 A Revised Internet-Draft is available from the on-line Internet-Drafts 
 directories. This draft is a work item of the DNS IXFR, Notification, and 
 Dynamic Update Working Group of the IETF.                                 

Note: This revision reflects comments received during the last call period.

       Title     : Clarifications to the DNS Specification                 
       Author(s) : R. Elz, R. Bush
       Filename  : draft-ietf-dnsind-clarify-05.txt
       Pages     : 14
       Date      : 02/03/1997

This draft considers some areas that have been identified as problems with 
the specification of the Domain Name System, and proposes remedies for the 
defects identified.  Six separate issues are considered:    

+ IP packet header address usage from multi-homed servers,   
+ TTLs in sets of records with the same name, class, and type,  
+ correct handling of zone cuts,    
+ two minor issues concerning SOA records and their use,       
+ the issue of what is an authoritative, or canonical, name,   
+ and the issue of what makes a valid DNS label.  

The first four of these are areas where the correct behaviour 
has been somewhat unclear, we seek to rectify that.  The other 
two are already adequately specified, however the specifications 
seem to be sometimes ignored.  We seek to reinforce the 
existing specifications.

This version adds a brief discussion on the placement of an SOA record in 
the answer to an authoritative query, and the issue of TTLs on SOA records.
It also contains rather more discussion inspired by the oddities of some of
the new DNSSEC record types.  The ordered list of trustworthiness of 
various data types was revised by grouping the last three categories 
together, and adding a restriction on how such data should  be used.  
Many editorial changes were made.  This paragraph will be deleted 
from the final version of this document.
 
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-dnsind-clarify-05.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ietf-dnsind-clarify-05.txt
 
Internet-Drafts directories are located at:	
	                                                
     o  Africa:  ftp.is.co.za                    
	                                                
     o  Europe:  ftp.nordu.net            	
                 ftp.nis.garr.it                 
	                                                
     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-dnsind-clarify-05.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.
ftp://ds.internic.net/internet-drafts/draft-ietf-dnsind-clarify-05.txt"><ftp://ds.internic.net/internet-drafts/draft-ietf-dnsind-clarify-05.txt>