| Internet-Draft | DKIM Signing Algorithm AdaEd25519-SHA256 | October 2024 |
| Nurpmeso | Expires 8 April 2025 | [Page] |
This memo adds the DKIM (RFC 6376) signing algorithm AdaEd25519-SHA256. It is identical to Ed25519-SHA256 (RFC 8463) except for its use of DKIM hash algorithm adaptivity (draft-nurpmeso-dkim-hash-adaptivity-00). Private and public keys are identical, and can be used interchangeably.¶
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 https://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 8 April 2025.¶
Copyright (c) 2024 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 (https://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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Ed25519-SHA256[RFC8463], which defines a DKIM key type for Ed25519[RFC8032], became standardized in 2018, but has not gained much traction in the six years since its introduction. A survey of DKIM implementations revealed necessity for error prone extra code paths to implement it with existing APIs. In addition the DKIM[RFC6376] algorithm of how "Computing the Message Hashes" for IMF[RFC5322] messages causes Ed25519-SHA256 to create a 64-byte SHA-256[RFC6234] "data-hash" input for Ed25519, which is then "prehashed" with the stronger SHA-512[RFC6234] that expands to 128 bytes. AdaEd25519-SHA256 bases upon DKIM Hash Algorithm Adaptivity[I-D.nurpmeso-dkim-hash-adaptivity] that takes advantage of algorithm progress and digital signature API reality.¶
AdaEd25519-SHA256 is identical to Ed25519-SHA256[RFC8463] except that it uses DKIM Hash Algorithm Adaptivity[I-D.nurpmeso-dkim-hash-adaptivity]: the DKIM[RFC6376] (section 3.7) "hash-alg" SHA-256[RFC6234] is only used to produce the "body-hash", and "sig-alg" is fed in all the input used to create the "data-hash". Private and public keys are identical, and can be used interchangeably.¶
INFORMATIVE NOTE: Even though [RFC8410] defined ASN.1 Object Identifiers (OIDs) for Ed25519, it was considered more important to keep compatibility with actively used Ed25519-SHA256 keys, than to support ASN.1 standard means of inspecting key data blobs.¶
The "sig-a-tag-k" ABNF definition of DKIM[RFC6376] (section 3.5), as well as the "key-k-tag-type" ABNF definition of DKIM[RFC6376] (section 3.6.1) are both extended by an entry "adaed25519".¶
This memo requests adding the new key type "adaed25519" to the "DKIM Key Type" registry.¶
This specification should reduce implementation burden and complexity, aids hash hardening of affected algorithms to a certain extend, and potentially increases, dependent upon algorithm, data volume and API optimization efforts, processing performance.¶