Check Point Software Technologies Ltd.

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

SJD AB

simon@josefsson.org

Security Area Internet-Draft This document describes the use of Curve25519 and Curve448 for ephemeral key exchange in the Internet Key Exchange (IKEv2) protocol.

The "Elliptic Curves for Security" document describes two elliptic curves: Curve25519 and Curve448, as well as the X25519 and X448 functions for performing key agreement (Diffie-Hellman) operations with these curves. The curves and functions are designed for both performance and security. Almost ten years ago the "ECP Groups for IKE and IKEv2" document specified the first elliptic curve Diffie-Hellman groups for the Internet Key Exchange protocol (IKEv2 - ). These were the so-called NIST curves. The state of the art has advanced since then. More modern curves allow faster implementations while making it much easier to write constant-time implementations free from time-based side-channel attacks. This document defines two such curves for use in IKE. See for details about the speed and security of the Curve25519 function.

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 .

All cryptographic computations are done using the X25519 and X448 functions defined in . All related parameters (for example, the base point) and the encoding (in particular, pruning the least/most significant bits and use of little-endian encoding) are inherited from . An ephemeral Diffie-Hellman key exchange using Curve25519 or Curve448 goes as follows: Each party picks a secret key d uniformly at random and computes the corresponding public key. "X" is used below to denote either X25519 or X448, and "G" is used to denote the corresponding base point:

Parties exchange their public keys (see ) and compute a shared secret:

This shared secret is used directly as the value denoted g^ir in section 2.14 of RFC 7296. It is 32 octets when Curve25519 is used, and 56 octets when Curve448 is used.

The use of Curve25519 and Curve448 in IKEv2 is negotiated using a Transform Type 4 (Diffie-Hellman group) in the SA payload of either an IKE_SA_INIT or a CREATE_CHILD_SA exchange. The value TBA1 is used for the group defined by Curve25519 and the value TBA2 is used for the group defined by Curve448.

The diagram for the Key Exchange Payload from section 3.4 of RFC 7296 is copied below for convenience:

Payload Length - For Curve25519 the public key is 32 octets, so the Payload Length field will be 40, and for Curve448 the public key is 56 octets, so the Payload Length field will be 64. The Diffie-Hellman Group Num is TBA1 for Curve25519, or TBA2 for Curve448. The Key Exchange Data is the 32 or 56 octets as described in section 6 of

This document matches the discussion in related to receiving and accepting incompatible point formats. In particular, receiving entities MUST mask the most-significant bit in the final byte for X25519 (but not X448), and implementations MUST accept non-canonical values. See section 5 of for further discussion.

Curve25519 and Curve448 are designed to facilitate the production of high-performance constant-time implementations. Implementors are encouraged to use a constant-time implementation of the functions. This point is of crucial importance if the implementation chooses to reuse its supposedly ephemeral key pair for many key exchanges, which some implementations do in order to improve performance. Curve25519 is intended for the ~128-bit security level, comparable to the 256-bit random ECP group (group 19) defined in RFC 4753, also known as NIST P-256 or secp256r1. Curve448 is intended for the ~224-bit security level. While the NIST curves are advertised as being chosen verifiably at random, there is no explanation for the seeds used to generate them. In contrast, the process used to pick these curves is fully documented and rigid enough so that independent verification has been done. This is widely seen as a security advantage, since it prevents the generating party from maliciously manipulating the parameters. Another family of curves available in IKE, generated in a fully verifiable way, is the Brainpool curves . For example, brainpoolP256 (group 28) is expected to provide a level of security comparable to Curve25519 and NIST P-256. However, due to the use of pseudo-random prime, it is significantly slower than NIST P-256, which is itself slower than Curve25519.

IANA is requested to assign two values from the IKEv2 "Transform Type 4 - Diffie-Hellman Group Transform IDs" registry, with names "Curve25519" and "Curve448" and this document as reference. The Recipient Tests field should also point to this document: Number Name Recipient Tests Reference TBA1Curve25519RFCxxxx RFCxxxx TBA2Curve448RFCxxxx RFCxxxx

Curve25519 was designed by D. J. Bernstein and the parameters for Curve448 ("Goldilocks") is by Mike Hamburg. The specification of algorithms, wire format and other considerations are in RFC 7748 by Adam Langley, Mike Hamburg, and Sean Turner. The example in was calculated using the master version of OpenSSL, retrieved on August 4th, 2016.

Harvard University

1350 Mass. Ave. Cambridge MA 02138 - +1 617 495 3864 sob@harvard.edu

General keyword

Suppose we have both the initiator and the responder generating private keys by generating 32 random octets. As usual in IKEv2 and its extension, we will denote Initiator values with the suffix _i and responder values with the suffix _r:

These numbers need to be fixed by unsetting some bits as described in section 5 of RFC 7748. This affects only the first and last octets of each value:

The actual private keys are considered to be encoded in little-endian format:

The public keys are generated from this using the formula in :

And this is the value of the Key Exchange Data field in the key exchange payload described in . The shared value is calculated as in :