draft-ietf-dnsext-ds-sha256-05.txt

来自「非常好的dns解析软件」· 文本 代码 · 共 505 行 · 第 1/2 页

Network Working Group                                        W. Hardaker
Internet-Draft                                                    Sparta
Expires: August 25, 2006                               February 21, 2006


 Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)
                   draft-ietf-dnsext-ds-sha256-05.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on August 25, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This document specifies how to use the SHA-256 digest type in DNS
   Delegation Signer (DS) Resource Records (RRs).  DS records, when
   stored in a parent zone, point to key signing DNSKEY key(s) in a
   child zone.








Hardaker                 Expires August 25, 2006                [Page 1]

Internet-Draft       Use of SHA-256 in DNSSEC DS RRs       February 2006


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Implementing the SHA-256 algorithm for DS record support  . . . 3
     2.1.  DS record field values  . . . . . . . . . . . . . . . . . . 3
     2.2.  DS Record with SHA-256 Wire Format  . . . . . . . . . . . . 3
     2.3.  Example DS Record Using SHA-256 . . . . . . . . . . . . . . 4
   3.  Implementation Requirements . . . . . . . . . . . . . . . . . . 4
   4.  Deployment Considerations . . . . . . . . . . . . . . . . . . . 4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
     6.1.  Potential Digest Type Downgrade Attacks . . . . . . . . . . 5
     6.2.  SHA-1 vs SHA-256 Considerations for DS Records  . . . . . . 6
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 8
   Intellectual Property and Copyright Statements  . . . . . . . . . . 9
































Hardaker                 Expires August 25, 2006                [Page 2]

Internet-Draft       Use of SHA-256 in DNSSEC DS RRs       February 2006


1.  Introduction

   The DNSSEC [RFC4033] [RFC4034] [RFC4035] DS RR is published in parent
   zones to distribute a cryptographic digest of a child's Key Signing
   Key (KSK) DNSKEY RR.  The DS RRset is signed by at least one of the
   parent zone's private zone data signing keys for each algorithm in
   use by the parent.  Each signature is published in an RRSIG resource
   record, owned by the same domain as the DS RRset and with a type
   covered of DS.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].


2.  Implementing the SHA-256 algorithm for DS record support

   This document specifies that the digest type code [XXX: To be
   assigned by IANA; likely 2] is to be assigned to SHA-256 [SHA256]
   [SHA256CODE] for use within DS records.  The results of the digest
   algorithm MUST NOT be truncated and the entire 32 byte digest result
   is to be published in the DS record.

2.1.  DS record field values

   Using the SHA-256 digest algorithm within a DS record will make use
   of the following DS-record fields:

   Digest type: [XXX: To be assigned by IANA; likely 2]

   Digest: A SHA-256 bit digest value calculated by using the following
      formula ("|" denotes concatenation).  The resulting value is not
      truncated and the entire 32 byte result is to used in the
      resulting DS record and related calculations.

        digest = SHA_256(DNSKEY owner name | DNSKEY RDATA)

      where DNSKEY RDATA is defined by [RFC4034] as:

        DNSKEY RDATA = Flags | Protocol | Algorithm | Public Key

   The Key Tag field and Algorithm fields remain unchanged by this
   document and are specified in the [RFC4034] specification.

2.2.  DS Record with SHA-256 Wire Format

   The resulting on-the-wire format for the resulting DS record will be
   [XXX: IANA assignment should replace the 2 below]:



Hardaker                 Expires August 25, 2006                [Page 3]

Internet-Draft       Use of SHA-256 in DNSSEC DS RRs       February 2006


                           1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           Key Tag             |  Algorithm    | DigestType=2  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      /                                                               /
      /            Digest  (length for SHA-256 is 32 bytes)           /
      /                                                               /
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|

2.3.  Example DS Record Using SHA-256

   The following is an example DNSKEY and matching DS record.  This
   DNSKEY record comes from the example DNSKEY/DS records found in
   section 5.4 of [RFC4034].

   The DNSKEY record:

   dskey.example.com. 86400 IN DNSKEY 256 3 5 ( AQOeiiR0GOMYkDshWoSKz9Xz
                                                fwJr1AYtsmx3TGkJaNXVbfi/
                                                2pHm822aJ5iI9BMzNXxeYCmZ
                                                DRD99WYwYqUSdjMmmAphXdvx
                                                egXd/M5+X7OrzKBaMbCVdFLU
                                                Uh6DhweJBjEVv5f2wwjM9Xzc
                                                nOf+EPbtG9DMBmADjFDc2w/r
                                                ljwvFw==
                                                ) ;  key id = 60485

   The resulting DS record covering the above DNSKEY record using a SHA-
   256 digest: [RFC Editor: please replace XXX with the assigned digest
   type (likely 2):]

   dskey.example.com. 86400 IN DS 60485 5 XXX ( D4B7D520E7BB5F0F67674A0C
                                                CEB1E3E0614B93C4F9E99B83
                                                83F6A1E4469DA50A )


3.  Implementation Requirements

   Implementations MUST support the use of the SHA-256 algorithm in DS
   RRs.  Validator implementations SHOULD ignore DS RRs containing SHA-1
   digests if DS RRs with SHA-256 digests are present in the DS RRset.


4.  Deployment Considerations

   If a validator does not support the SHA-256 digest type and no other
   DS RR exists in a zone's DS RRset with a supported digest type, then



Hardaker                 Expires August 25, 2006                [Page 4]

Internet-Draft       Use of SHA-256 in DNSSEC DS RRs       February 2006


   the validator has no supported authentication path leading from the
   parent to the child.  The resolver should treat this case as it would
   the case of an authenticated NSEC RRset proving that no DS RRset
   exists, as described in [RFC4035], section 5.2.

   Because zone administrators can not control the deployment speed of
   support for SHA-256 in validators that may be referencing any of
   their zones, zone operators should consider deploying both SHA-1 and
   SHA-256 based DS records.  This should be done for every DNSKEY for
   which DS records are being generated.  Whether to make use of both
   digest types and for how long is a policy decision that extends
   beyond the scope of this document.


5.  IANA Considerations

   Only one IANA action is required by this document:

   The Digest Type to be used for supporting SHA-256 within DS records
   needs to be assigned by IANA.  This document requests that the Digest
   Type value of 2 be assigned to the SHA-256 digest algorithm.

   At the time of this writing, the current digest types assigned for
   use in DS records are as follows:

      VALUE     Digest Type          Status