draft-ietf-dnsext-ad-is-secure-01.txt   draft-ietf-dnsext-ad-is-secure-02.txt 
DNSEXT Working Group Brian Wellington (Nominum) DNSEXT Working Group Brian Wellington
INTERNET-DRAFT Olafur Gudmundsson (NAI Labs) INTERNET-DRAFT Olafur Gudmundsson
<draft-ietf-dnsext-ad-is-secure-01.txt> January 2001 <draft-ietf-dnsext-ad-is-secure-02.txt> June 2001
Updates: RFC 2535 Updates: RFC 2535
Redefinition of DNS AD bit Redefinition of DNS AD bit
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Comments should be sent to the authors or the DNSEXT WG mailing list Comments should be sent to the authors or the DNSEXT WG mailing list
namedroppers@ops.ietf.org namedroppers@ops.ietf.org
This draft expires on July 19, 2001. This draft expires on December 18, 2001.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All rights reserved. Copyright (C) The Internet Society (2001). All rights reserved.
Abstract Abstract
Based on implementation experience, the current definition of the AD Based on implementation experience, the current definition of the AD
bit in the DNS header is not useful. This draft changes the bit in the DNS header is not useful. This draft changes the
specification so that the AD bit is only set on answers where specification so that the AD bit is only set on answers where
skipping to change at page 3, line 4 skipping to change at page 3, line 4
the answer and authority sections of the response are either the answer and authority sections of the response are either
Authenticated or Insecure." Authenticated or Insecure."
The changes are to delete the words "either" and "or Insecure" from The changes are to delete the words "either" and "or Insecure" from
the sentence. the sentence.
The replacement text reads: The replacement text reads:
"The AD bit MUST NOT be set on a response unless all of the RRsets in "The AD bit MUST NOT be set on a response unless all of the RRsets in
the answer and authority sections of the response are Authenticated." the answer and authority sections of the response are Authenticated."
If the answer section contains any data, the server MUST NOT include AD should be set if and only if all RRs in the answer section, and
data in the authority section that would cause the AD bit to be any relevant negative response RRs in the authority section are
unset. Authenticated.
The AD bit MUST NOT be set on a response unless all of the RRsets in The AD bit MUST NOT be set on a response unless all of the RRsets in
the answer and authority sections are Authenticated. the answer and authority sections are Authenticated.
A resolver MUST NOT blindly trust the AD bit unless it communicates A resolver MUST NOT blindly trust the AD bit unless it communicates
with the server over secure transport mechanism or using message with the server over secure transport mechanism or using message
authentication such as TSIG[RFC2845] or SIG(0)[RFC2931], and the authentication such as TSIG[RFC2845] or SIG(0)[RFC2931], and the
resolver policy is that it can trust the server. resolver policy is that it can trust the server.
A DNS server following this modified specification will only set the A DNS server following this modified specification will only set the
AD bit when it has cryptographically verified the data in the answer. AD bit when it has cryptographically verified the data in the answer.
skipping to change at page 4, line 15 skipping to change at page 4, line 15
[RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, B. Wellington, [RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, B. Wellington,
``Secret Key Transaction Authentication for DNS (TSIG)'', RFC ``Secret Key Transaction Authentication for DNS (TSIG)'', RFC
2845, May 2000. 2845, May 2000.
[RFC2931] D. Eastlake, ``DNS Request and Transaction Signatures [RFC2931] D. Eastlake, ``DNS Request and Transaction Signatures
(SIG(0))'', RFC 2931, September 2000. (SIG(0))'', RFC 2931, September 2000.
Authors Addresses Authors Addresses
Brian Wellington Olafur Gudmundsson Brian Wellington Olafur Gudmundsson
Nominum Inc. NAI Labs Nominum Inc.
950 Charter Street 3060 Washington Road (Rt. 97) 950 Charter Street 3826 Legation Street, NW
Redwood City, CA, 94063 Glenwood, MD, 21738 Redwood City, CA, 94063 Washington, DC, 20015
USA USA USA USA
+1 650 381 6022 +1 443 259 2389 <Brian.Wellington@nominum.com> <ogud@ogud.com>
<Brian.Wellington@nominum.com> <ogud@tislabs.com>
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/