]> Check Point Software Technologies Ltd.

5 Hasolelim st. Tel Aviv 6789735 Israel ynir.ietf@gmail.com

Security IPSecME Working Group Internet-Draft This document describes the use of the Edwards-curve digital signature algorithm in the IKEv2 protocol.

The Internet Key Exchange protocol can use arbitrary signature algorithms as described in . The latter RFC defines the SIGNATURE_HASH_ALGORITHMS notification where each side of the IKE negotiation lists its supported hash algorithms. This assumes that all signature schemes involve a hashing phase followed by a signature phase. This made sense because most signature algorithms either cannot sign messages bigger than their key or truncate messages bigger than their key. EdDSA () defines signature methods that do not require pre-hashing of the message. Unlike other methods, these accept arbitrary-sized messages, so no pre-hashing is required. These methods are called Ed25519 and Ed448, which respectively use the Edwards 25519 and the Edwards 448 ("Goldilocks") curves. Although that document also defines pre-hashed versions of these algorithm, those versions are not recommended for protocols where the entire to-be-signed message is available at once. See section 8.5 or RFC 8032 for that recommendation. EdDSA defines the binary format of the signatures that should be used in the "Signature Value" field of the Authentication Data Format in section 3. The CURDLE PKIX document () defines the object identifiers (OIDs) for these signature methods. For convenience, these OIDs are repeated in . In order to signal within IKE that no hashing needs to be done, we define a new value has in the SIGNATURE_HASH_ALGORITHMS notification, one that indicates that no hashing is performed.

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 .

This document defines a new value called "Identity" (value is 5) in the hash algorithm registry for use in the SIGNATURE_HASH_ALGORITHMS notification. Inserting this new value into the notification indicates that the receiver supports at least one signature algorithm that accepts arbitrary-sized messages such as Ed25519 and Ed448. Ed25519 and Ed448 are only defined with the Identity hash, and MUST NOT be sent to a receiver that has not indicated support for the "Identity" hash. The pre-hashed versions of Ed25519 and Ed448 (Ed25519ph and Ed448ph respectively) SHOULD NOT be used in IKE.

The new "Identity" value is needed only for signature algorithms that accept an arbitrary-sized input. It MUST NOT be used if none of the supported and configured algorithms have this property. On the other hand there is no good reason to pre-hash the inputs where the signature algorithm has that property. For this reason implementations MUST have the "Identity" value in the SIGNATURE_HASH_ALGORITHMS notification when EdDSA is supported and configured. Implementations SHOULD NOT have other hash algorithms in the notification if all supported and configured signature algorithms have this property.

IANA has assigned the value 5 for the algorithm with the name "Identity" in the "IKEv2 Hash Algorithms" registry with this draft as reference. Upon publication of this document IANA is requested to update the entry with this document as reference.

&rfc2119; &rfc7296; &rfc7427; &rfc8032;

The normative reference for the ASN.1 objects for Ed25519 and Ed448 is in . They are repeated below for convenience.

id-Ed25519 OBJECT IDENTIFIER ::= { 1.3.101.112 } Parameters are absent. Length is 7 bytes. Binary encoding: 3005 0603 2B65 70

id-Ed448 OBJECT IDENTIFIER ::= { 1.3.101.113 } Parameters are absent. Length is 7 bytes. Binary encoding: 3005 0603 2B65 71