Skip to main content

EdDSA for DNSSEC
draft-ietf-curdle-dnskey-eddsa-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 8080.
Authors Ondřej Surý , Robert Edmonds
Last updated 2016-04-18
Replaces draft-ietf-curdle-dnskey-ed25519, draft-ietf-curdle-dnskey-ed448
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 8080 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-curdle-dnskey-eddsa-00
Internet Engineering Task Force                                  O. Sury
Internet-Draft                                                    CZ.NIC
Intended status: Standards Track                              R. Edmonds
Expires: October 20, 2016                        Farsight Security, Inc.
                                                          April 18, 2016

                            EdDSA for DNSSEC
                   draft-ietf-curdle-dnskey-eddsa-00

Abstract

   This document describes how to specify EdDSA keys and signatures in
   DNS Security (DNSSEC).  It uses the Edwards-curve Digital Security
   Algorithm (EdDSA) with the choice of two curves, Ed25519 and Ed448.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on October 20, 2016.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Sury & Edmonds          Expires October 20, 2016                [Page 1]
Internet-Draft              EdDSA for DNSSEC                  April 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  DNSKEY Resource Records . . . . . . . . . . . . . . . . . . .   2
   4.  RRSIG Resource Records  . . . . . . . . . . . . . . . . . . .   3
   5.  Algorithm Number for DS, DNSKEY and RRSIG Resource Records  .   3
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     6.1.  Ed25519 Examples  . . . . . . . . . . . . . . . . . . . .   3
     6.2.  Ed448 Example . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  Implementation Status . . . . . . . . . . . . . . . . . . . .   6
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   6
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   DNSSEC, which is broadly defined in [RFC4033], [RFC4034], and
   [RFC4035], uses cryptographic keys and digital signatures to provide
   authentication of DNS data.  Currently, the most popular signature
   algorithm in use is RSA.  GOST ([RFC5933]) and NIST-specified
   elliptic curve cryptography ([RFC6605]) are also standardized.

   [I-D.irtf-cfrg-eddsa] describes the elliptic curve signature system
   EdDSA and recommends two curves, Ed25519 and Ed448.

   This document defines the use of DNSSEC's DS, DNSKEY, and RRSIG
   resource records (RRs) with a new signing algorithm, Edwards-curve
   Digital Signature Algorithm (EdDSA) using a choice of two curves,
   Ed25519 and Ed448.

2.  Requirements Language

   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].

3.  DNSKEY Resource Records

   An Ed25519 public key consists of a 32-octet value, which is encoded
   into the Public Key field of a DNSKEY resource record as a simple bit
   string.  The generation of a public key is defined in Chapter 5.1.5
   in [I-D.irtf-cfrg-eddsa].

Sury & Edmonds          Expires October 20, 2016                [Page 2]
Internet-Draft              EdDSA for DNSSEC                  April 2016

   An Ed448 public key consists of a 57-octet value, which is encoded
   into the Public Key field of a DNSKEY resource record as a simple bit
   string.  The generation of a public key is defined in Chapter 5.2.5
   in [I-D.irtf-cfrg-eddsa].

4.  RRSIG Resource Records

   In Chapter 10.3 in [I-D.irtf-cfrg-eddsa], the use of a context label
   is described.  EdDSA signatures in this scheme use the 17-octet
   context label 'DNSSEC SIGNATURE\0' (where \0 represents a zero-valued
   octet).

   (Note: Only Ed448 has the Context specified.  Before publishing the
   final draft we need to specify what to do with Ed25519 Context.)

   An Ed25519 signature consists of a 64-octet value, which is encoded
   into the Signature field of an RRSIG resource record as a simple bit
   string.  The Ed25519 signature algorithm is described in Chapter
   5.1.6 in [I-D.irtf-cfrg-eddsa].

   An Ed448 signature consists of a 114-octet value, which is encoded
   into the Signature field of an RRSIG resource record as a simple bit
   string.  The Ed448 signature algorithm is described in Chapter 5.2.6
   and verification of the Ed448 signature is described in Chapter 5.2.7
   in [I-D.irtf-cfrg-eddsa].

5.  Algorithm Number for DS, DNSKEY and RRSIG Resource Records

   The algorithm number associated with the use of Ed25519 in DS, DNSKEY
   and RRSIG resource records is TBD.  The algorithm number associated
   with the use of Ed448 in DS, DNSKEY and RRSIG resource records is
   TBD.  This registration is fully defined in the IANA Considerations
   section.

6.  Examples

6.1.  Ed25519 Examples

Sury & Edmonds          Expires October 20, 2016                [Page 3]
Internet-Draft              EdDSA for DNSSEC                  April 2016

      This section needs an update after the algorithm for Ed25519 is
                                 assigned.

    Private-key-format: v1.2
    Algorithm: TBD (ED25519)
    PrivateKey: ODIyNjAzODQ2MjgwODAxMjI2NDUxOTAyMDQxNDIyNjI=
    # corresponding to 82260384628080122645190204142262 INT

    example.com. 3600 IN DNSKEY 257 3 TBD (
            l02Woi0iS8Aa25FQkUd9RMzZHJpBoRQwAQEX1SxZJA4= )

    example.com. 3600 IN DS 3613 TBD 2 (
            3aa5ab37efce57f737fc1627013fee07bdf241bd10f3
            b1964ab55c78e79a304b )

    www.example.com. 3600 IN A 192.0.2.1
    www.example.com. 3600 IN RRSIG A TBD 3 3600 (
            20150820000000 20150730000000 3613 example.com.
            cvTRVrU7dwnemQuBq9/E4tlIiRpvWcEmYdzqs6SCQxw6
            qmczBBQGldssMx1TCJnwsEs9ZuA2phPzuJNoon9BCA== )

    Private-key-format: v1.2
    Algorithm: TBD (ED25519)
    PrivateKey: DSSF3o0s0f+ElWzj9E/Osxw8hLpk55chkmx0LYN5WiY=

    example.com. 3600 IN DNSKEY 257 3 TBD (
            zPnZ/QwEe7S8C5SPz2OfS5RR40ATk2/rYnE9xHIEijs= )

    example.com. 3600 IN DS 55648 TBD 2 (
            96401675bc7ecdd541ec0f70d69238c7b95d3bd4de1e
            231a068ceb214d02a4ed )

    www.example.com. 3600 IN A 192.0.2.1
    www.example.com. 3600 IN RRSIG A TBD 3 3600 (
            20150820000000 20150730000000 35452 example.com.
            yuGb9rCNIuhDaRJbuhYHj89Y/3Pi8KWUm7lOt00ivVRGvgulmVX8DgpE
            AFyMP2MKXJrqYJr+ViiCIDwcOIbPAQ==)

6.2.  Ed448 Example

Sury & Edmonds          Expires October 20, 2016                [Page 4]
Internet-Draft              EdDSA for DNSSEC                  April 2016

       This section needs an update after the algorithm for Ed448 is
                                 assigned.

    Private-key-format: v1.2
    Algorithm: TBD (ED448)
    PrivateKey: TBD

    example.com. 3600 IN DNSKEY 257 3 TBD (
            TBD )

    example.com. 3600 IN DS 3613 TBD 2 (
            TBD )

    www.example.com. 3600 IN A 192.0.2.1
    www.example.com. 3600 IN RRSIG A TBD 3 3600 (
            20150820000000 20150730000000 3613 example.com.
            TBD )

    Private-key-format: v1.2
    Algorithm: TBD (ED448)
    PrivateKey: TBD

    example.com. 3600 IN DNSKEY 257 3 TBD (
            TBD )

    example.com. 3600 IN DS 55648 TBD 2 (
            TBD )

    www.example.com. 3600 IN A 192.0.2.1
    www.example.com. 3600 IN RRSIG A TBD 3 3600 (
            20150820000000 20150730000000 35452 example.com.
            TBD )

7.  Acknowledgements

   Some of the material in this document is copied liberally from
   [RFC6605].

   The authors of this document wish to thank Jan Vcelak, Pieter Lexis
   and Kees Monshouwer for a review of this document.

8.  IANA Considerations

   This document updates the IANA registry "Domain Name System Security
   (DNSSEC) Algorithm Numbers".  The following entry has been added to
   the registry:

Sury & Edmonds          Expires October 20, 2016                [Page 5]
Internet-Draft              EdDSA for DNSSEC                  April 2016

             +--------------+---------------+---------------+
             | Number       | TBD           | TBD           |
             | Description  | Ed25519       | Ed448         |
             | Mnemonic     | ED25519       | Ed448         |
             | Zone Signing | Y             | Y             |
             | Trans. Sec.  | *             | *             |
             | Reference    | This document | This document |
             +--------------+---------------+---------------+

    * There has been no determination of standardization of the use of
                 this algorithm with Transaction Security.

9.  Implementation Status

   (Note to the RFC Editor: please remove this entire section as well as
   the reference to RFC 6982 before publication.)

   This section records the status of known implementations of the
   protocol defined by this specification at the time of posting of this
   Internet-Draft, and is based on a proposal described in [RFC6982].
   The description of implementations in this section is intended to
   assist the IETF in its decision processes in progressing drafts to
   RFCs.  Please note that the listing of any individual implementation
   here does not imply endorsement by the IETF.  Furthermore, no effort
   has been spent to verify the information presented here that was
   supplied by IETF contributors.  This is not intended as, and must not
   be construed to be, a catalog of available implementations or their
   features.  Readers are advised to note that other implementations may
   exist.

   According to [RFC6982], "this will allow reviewers and working groups
   to assign due consideration to documents that have the benefit of
   running code, which may serve as evidence of valuable experimentation
   and feedback that have made the implemented protocols more mature.
   It is up to the individual working groups to use this information as
   they see fit".

10.  Security Considerations

   The security level of Ed25519 is slightly under the standard 128-bit
   level and the security level of Ed448 is slightly under the standard
   224-bit level ([RFC7748]).  Security considerations listed in
   [RFC7748] also apply to the usage of Ed25519 and Ed448 in DNSSEC.
   Such an assessment could, of course, change in the future if new
   attacks that work better than the ones known today are found.

Sury & Edmonds          Expires October 20, 2016                [Page 6]
Internet-Draft              EdDSA for DNSSEC                  April 2016

11.  References

11.1.  Normative References

   [I-D.irtf-cfrg-eddsa]
              Josefsson, S. and I. Liusvaara, "Edwards-curve Digital
              Signature Algorithm (EdDSA)", draft-irtf-cfrg-eddsa-05
              (work in progress), March 2016.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC4033]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "DNS Security Introduction and Requirements",
              RFC 4033, DOI 10.17487/RFC4033, March 2005,
              <http://www.rfc-editor.org/info/rfc4033>.

   [RFC4034]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "Resource Records for the DNS Security Extensions",
              RFC 4034, DOI 10.17487/RFC4034, March 2005,
              <http://www.rfc-editor.org/info/rfc4034>.

   [RFC4035]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "Protocol Modifications for the DNS Security
              Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005,
              <http://www.rfc-editor.org/info/rfc4035>.

   [RFC7748]  Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves
              for Security", RFC 7748, DOI 10.17487/RFC7748, January
              2016, <http://www.rfc-editor.org/info/rfc7748>.

11.2.  Informative References

   [RFC5933]  Dolmatov, V., Ed., Chuprina, A., and I. Ustinov, "Use of
              GOST Signature Algorithms in DNSKEY and RRSIG Resource
              Records for DNSSEC", RFC 5933, DOI 10.17487/RFC5933, July
              2010, <http://www.rfc-editor.org/info/rfc5933>.

   [RFC6605]  Hoffman, P. and W. Wijngaards, "Elliptic Curve Digital
              Signature Algorithm (DSA) for DNSSEC", RFC 6605,
              DOI 10.17487/RFC6605, April 2012,
              <http://www.rfc-editor.org/info/rfc6605>.

Sury & Edmonds          Expires October 20, 2016                [Page 7]
Internet-Draft              EdDSA for DNSSEC                  April 2016

   [RFC6982]  Sheffer, Y. and A. Farrel, "Improving Awareness of Running
              Code: The Implementation Status Section", RFC 6982,
              DOI 10.17487/RFC6982, July 2013,
              <http://www.rfc-editor.org/info/rfc6982>.

Authors' Addresses

   Ondrej Sury
   CZ.NIC
   Milesovska 1136/5
   Praha  130 00
   CZ

   Phone: +420 222 745 111
   Email: ondrej.sury@nic.cz

   Robert Edmonds
   Farsight Security, Inc.
   177 Bovet Rd #180
   San Mateo, California  94402
   US

   Phone: +1 650 489 7919
   Email: edmonds@fsi.io

Sury & Edmonds          Expires October 20, 2016                [Page 8]