new draft

diff --git a/doc/draft/draft-ietf-dnsext-dnssec-2535typecode-change-00.txt b/doc/draft/draft-ietf-dnsext-dnssec-2535typecode-change-01.txt
similarity index 95%
rename from doc/draft/draft-ietf-dnsext-dnssec-2535typecode-change-00.txt
rename to doc/draft/draft-ietf-dnsext-dnssec-2535typecode-change-01.txt
index aa014d876dd0d10dfce29dc3a90b6348617ffbeb..a28552912b611996a9ee29b7f8c6348b8bbc3b9a 100644 (file)
--- a/doc/draft/draft-ietf-dnsext-dnssec-2535typecode-change-00.txt
+++ b/doc/draft/draft-ietf-dnsext-dnssec-2535typecode-change-01.txt
@@ -1,12 +1,9 @@
-
-
-
 INTERNET-DRAFT                                             Samuel Weiler
-Expires: November 2003                                      May 12, 2003
+Expires: November 2003                                      May 22, 2003
 
 
         Legacy Resolver Compatibility for Delegation Signer
-        draft-ietf-dnsext-dnssec-2535typecode-change-00.txt
+        draft-ietf-dnsext-dnssec-2535typecode-change-01.txt
 
 Status of this Memo
 
@@ -202,11 +199,14 @@ Abstract
    NOT receive special treatment.  As an example, if a SIG is included
    in a signed zone, there MUST be an RRSIG for it.
 
-   As a clarification to previous documents, NSEC can appear in the
-   authority section of an answer at any time, not just in negative
-   answers.  The mere presence of an NSEC record in the answer or
-   authority section of an answer with RCODE=NOERROR, MUST NOT be
-   interpreted as a negative answer.  The NSEC must be validated.
+   As a clarification to previous documents, many positive responses,
+   including wildcard proofs and insecure referrals, will contain NSEC
+   RRs.  As a result, resolvers MUST NOT treat answers with NSEC RRs
+   as negative answers merely because they contain an NSEC.  A
+   resolver SHOULD either ignore the NSEC, as a DNSSEC-unaware (or
+   2535-aware) resolver would, or validate the NSEC and check its
+   applicability and interpretation as described in [RFC2535] and
+   [DS].
    
 4. IANA Considerations
 
@@ -284,6 +284,3 @@ Abstract
    weiler@tislabs.com
 
 
-
-
-

diff --git a/doc/draft/draft-ietf-dnsext-rfc1886bis-02.txt b/doc/draft/draft-ietf-dnsext-rfc1886bis-03.txt
similarity index 89%
rename from doc/draft/draft-ietf-dnsext-rfc1886bis-02.txt
rename to doc/draft/draft-ietf-dnsext-rfc1886bis-03.txt
index 52c8333ce06deb359f88bd14b9714e68ba9af538..f1cccf241cf789cb67bdae1d67ed532e964d41ca 100644 (file)
--- a/doc/draft/draft-ietf-dnsext-rfc1886bis-02.txt
+++ b/doc/draft/draft-ietf-dnsext-rfc1886bis-03.txt
@@ -1,14 +1,14 @@
 Internet Engineering Task Force                        S. Thomson, Cisco
 INTERNET-DRAFT                                     C. Huitema, Microsoft
-February 28, 2003                                      V. Ksinant, 6WIND
-Expires August 28, 2003                                M. Souissi, AFNIC
+May 12, 2003                                           V. Ksinant, 6WIND
+Expires November 12, 2003                              M. Souissi, AFNIC
 
 
 
 
 
                 DNS Extensions to support IP version 6
-                <draft-ietf-dnsext-rfc1886bis-02.txt>
+                <draft-ietf-dnsext-rfc1886bis-03.txt>
 
 
 Status of this Memo
@@ -30,7 +30,7 @@ Status of this Memo
    To view the list Internet-Draft Shadow Directories, see
    http://www.ietf.org/shadow.html.
 
-   This Internet Draft expires August 28, 2003.
+   This Internet Draft expires November 12, 2003.
 
 
 
@@ -54,9 +54,9 @@ Abstract
 
 
 
-draft-ietf-dnsext-rfc1886bis-02.txt                             [Page 1]
+draft-ietf-dnsext-rfc1886bis-03.txt                             [Page 1]
 \f
-INTERNET-DRAFT    DNS Extensions to support IP version 6   February 2003
+INTERNET-DRAFT    DNS Extensions to support IP version 6        May 2003
 
 
 Table of Contents
@@ -109,9 +109,9 @@ Table of Contents
    that has more than one IPv6 address must have more than one such
    record.
 
-draft-ietf-dnsext-rfc1886bis-02.txt                             [Page 2]
+draft-ietf-dnsext-rfc1886bis-03.txt                             [Page 2]
 \f
-INTERNET-DRAFT    DNS Extensions to support IP version 6   February 2003
+INTERNET-DRAFT    DNS Extensions to support IP version 6        May 2003
 
 2.1 AAAA record type
 
@@ -165,9 +165,9 @@ INTERNET-DRAFT    DNS Extensions to support IP version 6   February 2003
 b.a.9.8.7.6.5.0.4.0.0.0.3.0.0.0.2.0.0.0.1.0.0.0.0.0.0.0.1.2.3.4.IP6.
                                                                ARPA.
 
-draft-ietf-dnsext-rfc1886bis-02.txt                             [Page 3]
+draft-ietf-dnsext-rfc1886bis-03.txt                             [Page 3]
 \f
-INTERNET-DRAFT    DNS Extensions to support IP version 6   February 2003
+INTERNET-DRAFT    DNS Extensions to support IP version 6        May 2003
 
 3. MODIFICATIONS TO EXISTING QUERY TYPES
 
@@ -204,7 +204,7 @@ APPENDIX A: Changes from RFC 1886
         EXISTING QUERY TYPES"
       - Added security considerations.
       - Updated references :
-        * From RFC 1884 to RFC 2373 (IP Version 6 Addressing 
+        * From RFC 1884 to RFC 3513 (IP Version 6 Addressing 
           Architecture).
         * From "work in progress" to RFC 2893 (Transition Mechanisms for
           IPv6 Hosts and Routers).
@@ -219,9 +219,9 @@ APPENDIX A: Changes from RFC 1886
 
 
 
-draft-ietf-dnsext-rfc1886bis-02.txt                             [Page 4]
+draft-ietf-dnsext-rfc1886bis-03.txt                             [Page 4]
 \f
-INTERNET-DRAFT    DNS Extensions to support IP version 6   February 2003
+INTERNET-DRAFT    DNS Extensions to support IP version 6        May 2003
 
 Acknowledgements
 
@@ -244,16 +244,13 @@ Normative References
         tion", STD 13, RFC 1035, USC/Information Sciences Institute,
         November 1987.
 
-   [3]  Hinden, R., and S. Deering, "IP Version 6 Addressing 
-        Architecture", RFC 2373, Nokia, Cisco, July 1998.
-        This RFC is being updated. The current draft is
-        "draft-ietf-ipngwg-addr-arch-v3-11.txt", Hinden, R., and 
-        S. Deering, October 25, 2002
-
 
 
 Informative References
 
+   [3]  Hinden, R., and S. Deering, "Internet Protocol Version 6 (IPv6)
+        Addressing Architecture", RFC 3513, Nokia, Cisco, April 2003.
+
    [4]  Gilligan, R., and E. Nordmark, "Transition Mechanisms for IPv6
         Hosts and Routers", RFC 2893, FreeGate Corp., Sun Microsystems
        Inc., August 2000.
@@ -275,9 +272,12 @@ Informative References
         RFC 2845, ISC, NAI Labs, Motorola, Nominum, May 2000.
 
 
-draft-ietf-dnsext-rfc1886bis-02.txt                             [Page 5]
+
+
+
+draft-ietf-dnsext-rfc1886bis-03.txt                             [Page 5]
 \f
-INTERNET-DRAFT    DNS Extensions to support IP version 6   February 2003
+INTERNET-DRAFT    DNS Extensions to support IP version 6        May 2003
 
 
 Authors' Addresses
@@ -329,9 +329,9 @@ Authors' Addresses
 
 
 
-draft-ietf-dnsext-rfc1886bis-02.txt                             [Page 6]
+draft-ietf-dnsext-rfc1886bis-03.txt                             [Page 6]
 \f
-INTERNET-DRAFT    DNS Extensions to support IP version 6   February 2003
+INTERNET-DRAFT    DNS Extensions to support IP version 6        May 2003
 
 Full Copyright Statement
 
@@ -387,4 +387,4 @@ Full Copyright Statement
          information to the IETF Executive Director.
 
 
-draft-ietf-dnsext-rfc1886bis-02.txt                             [Page 7]
+draft-ietf-dnsext-rfc1886bis-03.txt                             [Page 7]