What it is
RFC 7748, Elliptic Curves for Security, specifies the X25519 and X448 functions and explains their use for Diffie–Hellman key agreement. Two endpoints combine their own private information with the other endpoint’s public information to calculate a shared secret.
That secret becomes an input to the surrounding protocol’s key derivation. Key agreement alone does not establish who the other endpoint is; authentication must come from the protocol using it.
Although often grouped with IETF specifications, RFC 7748 is an Informational publication from the Internet Research Task Force’s Crypto Forum Research Group. Its publication category does not prevent another specification or a project contract from requiring its algorithms.
Who it applies to
The document is relevant to developers and integrators whose selected communication protocol or security profile uses X25519 or X448. In an automotive project, this could include a team integrating secure communications between a vehicle and a backend, or between computing platforms.
It does not impose a general legal obligation on vehicle manufacturers or require every ECU to implement these functions. Applicability comes from the chosen protocol, customer requirements, and system security design.
Cybersecurity engineers define the security requirements, while software and cryptographic-platform teams implement them. Hardware and network engineers contribute compatibility and resource assessments.
What it covers
The RFC defines curve parameters, byte representations, the mathematical operations, and examples for checking implementations.
| Function | Underlying curve | Purpose |
|---|---|---|
| X25519 | Curve25519 | Diffie–Hellman key agreement |
| X448 | Curve448 | Diffie–Hellman key agreement |
It also discusses implementation concerns, including operations whose timing could reveal private information, and provides test vectors. A mathematically correct result is only part of a secure implementation: the treatment of secrets during execution matters too.
The function names identify particular operations and encodings. A library advertising generic elliptic-curve cryptography may still lack the required function or expose an incompatible interface.
How it fits with other documents
RFC 7748 supplies a cryptographic building block. A protocol specification determines how endpoints exchange public values, authenticate the exchange, derive traffic keys, and respond to errors. TLS is one example of a protocol family that can use these functions.
X25519 and X448 perform key agreement. Ed25519 and Ed448 are signature algorithms specified separately in RFC 8032; their names do not make their keys or interfaces interchangeable.
Automotive cybersecurity requirements provide the wider engineering context. Selecting an RFC 7748 function does not by itself demonstrate compliance with a vehicle cybersecurity process or establish the security of an update system.
In practice
Start with the communication profile required by both endpoints. Confirm the selected function is supported by the actual library, cryptographic provider, and target platform configuration.
Use a maintained implementation and verify it against the RFC’s test vectors. Then test the complete handshake between the intended endpoints, including error paths and the surrounding protocol’s required handling of an all-zero shared result.
For an ECU integration, assess execution time, memory use, random-number generation, and handling of private material. Record the algorithm, provider version, configuration, and interoperability evidence so later platform changes can be reviewed against a clear baseline.