RFC 9528: Ephemeral Diffie-Hellman Over COSE (EDHOC)
In plain English — editorial summary, not part of the RFC
This document specifies Ephemeral Diffie-Hellman Over COSE (EDHOC), a very compact and lightweight authenticated Diffie-Hellman key exchange with ephemeral keys. EDHOC provides mutual authentication, forward secrecy, and identity protection. EDHOC is intended for usage in constrained scenarios, and a main use case is to establish an Object Security for Constrained RESTful Environments (OSCORE) security context. By reusing CBOR Object Signing and Encryption (COSE) for cryptography, Concise Binary Object Representation (CBOR) for encoding, and Constrained Application Protocol (CoAP) for transport, the additional code size can be kept very low.
Document record
- Document ID
- RFC9528
- Published
- March 2024
- Authors
- G. Selander; J. Preuß Mattsson; F. Palombini
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 82
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9668Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)Current
November 2024
- RFC 9529Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 9597CBOR Web Token (CWT) Claims in COSE HeadersCurrent
June 2024
- RFC 9140Nimble Out-of-Band Authentication for EAP (EAP-NOOB)Updated
December 2021
- RFC 9942CBOR Object Signing and Encryption (COSE) ReceiptsCurrent
June 2026
- RFC 9943An Architecture for Trustworthy and Transparent Digital Supply ChainsCurrent
June 2026
- RFC 9964ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)Current
May 2026
- RFC 9053CBOR Object Signing and Encryption (COSE): Initial AlgorithmsUpdated
August 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?