idnits 2.17.1 draft-sury-dnskey-ed25519-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (September 8, 2015) is 3153 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational draft: draft-josefsson-eddsa-ed25519 (ref. 'I-D.josefsson-eddsa-ed25519') -- Obsolete informational reference (is this intentional?): RFC 6982 (Obsoleted by RFC 7942) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force O. Sury 3 Internet-Draft CZ.NIC 4 Intended status: Standards Track R. Edmonds 5 Expires: March 11, 2016 Farsight Security, Inc. 6 September 8, 2015 8 Ed25519 for DNSSEC 9 draft-sury-dnskey-ed25519-03 11 Abstract 13 This document describes how to specify Ed25519 keys and signatures in 14 DNS Security (DNSSEC). It uses the Ed25519 instance of the Edwards- 15 curve Digital Signature Algorithm (EdDSA) with the SHA-512 hash 16 algorithm. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on March 11, 2016. 35 Copyright Notice 37 Copyright (c) 2015 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 54 3. DNSKEY and RRSIG Resource Records for Ed25519 . . . . . . . . 3 55 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 57 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 58 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 5 59 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 60 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 9.1. Normative References . . . . . . . . . . . . . . . . . . 6 62 9.2. Informative References . . . . . . . . . . . . . . . . . 6 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 65 1. Introduction 67 DNSSEC, which is broadly defined in [RFC4033], [RFC4034], and 68 [RFC4035], uses cryptographic keys and digital signatures to provide 69 authentication of DNS data. Currently, the most popular signature 70 algorithm in use is RSA. [RFC5933] and [RFC6605] later defined the 71 use of GOST and NIST specified elliptic curve cryptography in DNSSEC. 73 This document defines the use of DNSSEC's DS, DNSKEY, and RRSIG 74 resource records (RRs) with a new signing algorithm: the Ed25519 75 instance of the Edwards-curve Digital Signature Algorithm (EdDSA) 76 used with the SHA-512 hash algorithm. A more thorough description of 77 Ed25519 can be found in [I-D.josefsson-eddsa-ed25519]. 79 Ed25519 has a 128-bit security target, which is considered to be 80 equivalent in strength to RSA with ~3000-bit keys. Ed25519 public 81 keys are 256 bits (32 bytes) long while signatures are 512 bits (64 82 bytes) long. 84 The usage of the Ed25519 algorithm in DNSSEC has advantages and 85 disadvantages relative to RSA. Ed25519 keys are much shorter than 86 RSA keys. At comparable strengths, Ed25519 keys are 352 bytes 87 smaller than RSA-3072 keys. Similarly, an Ed25519 signature saves 88 320 bytes over an RSA-3072 signature. 90 However, DNSSEC with RSA is not commonly deployed on the Internet 91 with signatures as large as 3072 bits. [RFC6781] contemplates the 92 routine use of RSA-1024 and RSA-2048 in DNSSEC. Even when compared 93 to the use of RSA at reduced strengths, Ed25519 still provides 94 substantially smaller keys and signatures. 96 Signing with Ed25519 is significantly faster than signing with 97 equivalently strong RSA, and it is also faster than signing with the 98 existing ECDSA algorithms defined in [RFC6605]. However, the 99 validation of RSA signatures is significantly faster than the 100 validation of Ed25519 signatures. 102 2. Requirements Language 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 106 document are to be interpreted as described in [RFC2119]. 108 3. DNSKEY and RRSIG Resource Records for Ed25519 110 An Ed25519 public key consists of a 32-byte value that represents the 111 compressed encoding of the curve point, which is encoded into the 112 Public Key field of a DNSKEY resource record as a simple bit string. 113 The generation of a public key is defined in Chapter 5.5 in 114 [I-D.josefsson-eddsa-ed25519]. 116 An Ed25519 signature consists of a 64-byte value, which is encoded 117 into the Signature field of an RRSIG resource record as a simple bit 118 string. The Ed25519 signature algorithm is described in Chapter 5.6 119 in [I-D.josefsson-eddsa-ed25519]. 121 The algorithm number associated with the use of Ed25519 with SHA-512 122 in DS, DNSKEY and RRSIG resource records is TBD. This registration 123 is fully defined in the IANA Considerations section. 125 4. Examples 126 This section needs an update after the algorithm for Ed25519 is 127 assigned. 129 Private-key-format: v1.2 130 Algorithm: TBD (ED25519SHA512) 131 PrivateKey: ODIyNjAzODQ2MjgwODAxMjI2NDUxOTAyMDQxNDIyNjI= 132 # corresponding to 82260384628080122645190204142262 INT 134 example.com. 3600 IN DNSKEY 257 3 TBD ( 135 l02Woi0iS8Aa25FQkUd9RMzZHJpBoRQwAQEX1SxZJA4= ) 137 example.com. 3600 IN DS 3613 TBD 2 ( 138 3aa5ab37efce57f737fc1627013fee07bdf241bd10f3 139 b1964ab55c78e79a304b ) 141 www.example.com. 3600 IN A 192.0.2.1 142 www.example.com. 3600 IN RRSIG A TBD 3 3600 ( 143 20150820000000 20150730000000 3613 example.com. 144 cvTRVrU7dwnemQuBq9/E4tlIiRpvWcEmYdzqs6SCQxw6 145 qmczBBQGldssMx1TCJnwsEs9ZuA2phPzuJNoon9BCA== ) 147 Private-key-format: v1.2 148 Algorithm: TBD (ED25519SHA512) 149 PrivateKey: DSSF3o0s0f+ElWzj9E/Osxw8hLpk55chkmx0LYN5WiY= 151 example.com. 3600 IN DNSKEY 257 3 TBD ( 152 zPnZ/QwEe7S8C5SPz2OfS5RR40ATk2/rYnE9xHIEijs= ) 154 example.com. 3600 IN DS 55648 TBD 2 ( 155 96401675bc7ecdd541ec0f70d69238c7b95d3bd4de1e 156 231a068ceb214d02a4ed ) 158 www.example.com. 3600 IN A 192.0.2.1 159 www.example.com. 3600 IN RRSIG A TBD 3 3600 ( 160 20150820000000 20150730000000 35452 example.com. 161 yuGb9rCNIuhDaRJbuhYHj89Y/3Pi8KWUm7lOt00ivVRGvgulmVX8DgpE 162 AFyMP2MKXJrqYJr+ViiCIDwcOIbPAQ==) 164 5. Acknowledgements 166 Some of the material in this document is copied liberally from 167 [RFC6605]. 169 The authors of this document wish to thank Jan Vcelak, Pieter Lexis 170 and Kees Monshouwer for a review of this document. 172 6. IANA Considerations 174 This document updates the IANA registry "Domain Name System Security 175 (DNSSEC) Algorithm Numbers". The following entry has been added to 176 the registry: 178 +--------------+----------------------+ 179 | Number | TBD | 180 | Description | Ed25519 with SHA-512 | 181 | Mnemonic | ED25519SHA512 | 182 | Zone Signing | Y | 183 | Trans. Sec. | * | 184 | Reference | This document | 185 +--------------+----------------------+ 187 * There has been no determination of standardization of the use of 188 this algorithm with Transaction Security. 190 7. Implementation Status 192 (Note to the RFC Editor: please remove this entire section as well as 193 the reference to RFC 6982 before publication.) 195 This section records the status of known implementations of the 196 protocol defined by this specification at the time of posting of this 197 Internet-Draft, and is based on a proposal described in [RFC6982]. 198 The description of implementations in this section is intended to 199 assist the IETF in its decision processes in progressing drafts to 200 RFCs. Please note that the listing of any individual implementation 201 here does not imply endorsement by the IETF. Furthermore, no effort 202 has been spent to verify the information presented here that was 203 supplied by IETF contributors. This is not intended as, and must not 204 be construed to be, a catalog of available implementations or their 205 features. Readers are advised to note that other implementations may 206 exist. 208 According to [RFC6982], "this will allow reviewers and working groups 209 to assign due consideration to documents that have the benefit of 210 running code, which may serve as evidence of valuable experimentation 211 and feedback that have made the implemented protocols more mature. 212 It is up to the individual working groups to use this information as 213 they see fit". 215 TODO: Fill out this section. 217 8. Security Considerations 219 Ed25519 is targeted to provide attack resistance comparable to 220 quality 128-bit symmetric ciphers. Such an assessment could, of 221 course, change in the future if new attacks that work better than the 222 ones known today are found. 224 9. References 226 9.1. Normative References 228 [I-D.josefsson-eddsa-ed25519] 229 Josefsson, S. and N. Moller, "EdDSA and Ed25519", draft- 230 josefsson-eddsa-ed25519-03 (work in progress), May 2015. 232 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 233 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 234 RFC2119, March 1997, 235 . 237 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 238 Rose, "DNS Security Introduction and Requirements", RFC 239 4033, DOI 10.17487/RFC4033, March 2005, 240 . 242 [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. 243 Rose, "Resource Records for the DNS Security Extensions", 244 RFC 4034, DOI 10.17487/RFC4034, March 2005, 245 . 247 [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. 248 Rose, "Protocol Modifications for the DNS Security 249 Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005, 250 . 252 9.2. Informative References 254 [RFC5933] Dolmatov, V., Ed., Chuprina, A., and I. Ustinov, "Use of 255 GOST Signature Algorithms in DNSKEY and RRSIG Resource 256 Records for DNSSEC", RFC 5933, DOI 10.17487/RFC5933, July 257 2010, . 259 [RFC6605] Hoffman, P. and W. Wijngaards, "Elliptic Curve Digital 260 Signature Algorithm (DSA) for DNSSEC", RFC 6605, DOI 261 10.17487/RFC6605, April 2012, 262 . 264 [RFC6781] Kolkman, O., Mekking, W., and R. Gieben, "DNSSEC 265 Operational Practices, Version 2", RFC 6781, DOI 10.17487/ 266 RFC6781, December 2012, 267 . 269 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 270 Code: The Implementation Status Section", RFC 6982, DOI 271 10.17487/RFC6982, July 2013, 272 . 274 Authors' Addresses 276 Ondrej Sury 277 CZ.NIC 278 Milesovska 1136/5 279 Praha 130 00 280 CZ 282 Phone: +420 222 745 111 283 Email: ondrej.sury@nic.cz 285 Robert Edmonds 286 Farsight Security, Inc. 287 155 Bovet Rd #476 288 San Mateo, California 94402 289 US 291 Phone: +1 650 489 7919 292 Email: edmonds@fsi.io