Ephemeral Diffie-Hellman Over COSE (EDHOC)
draft-selander-ace-cose-ecdhe-13
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-03-11
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
ACE Working Group G. Selander
Internet-Draft J. Mattsson
Intended status: Standards Track F. Palombini
Expires: September 12, 2019 Ericsson AB
March 11, 2019
Ephemeral Diffie-Hellman Over COSE (EDHOC)
draft-selander-ace-cose-ecdhe-13
Abstract
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,
perfect forward secrecy, and identity protection. EDHOC is intended
for usage in constrained scenarios and a main use case is to
establish an OSCORE security context. By reusing COSE for
cryptography, CBOR for encoding, and CoAP for transport, the
additional code footprint can be kept very low.
Status of This Memo
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 September 12, 2019.
Copyright Notice
Copyright (c) 2019 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
Selander, et al. Expires September 12, 2019 [Page 1]
Internet-Draft Ephemeral Diffie-Hellman Over COSE (EDHOC) March 2019
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Rationale for EDHOC . . . . . . . . . . . . . . . . . . . 4
1.2. Terminology and Requirements Language . . . . . . . . . . 5
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. EDHOC Overview . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Cipher Suites . . . . . . . . . . . . . . . . . . . . . . 8
3.2. Ephemeral Public Keys . . . . . . . . . . . . . . . . . . 9
3.3. Key Derivation . . . . . . . . . . . . . . . . . . . . . 9
4. EDHOC Authenticated with Asymmetric Keys . . . . . . . . . . 11
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2. EDHOC Message 1 . . . . . . . . . . . . . . . . . . . . . 13
4.3. EDHOC Message 2 . . . . . . . . . . . . . . . . . . . . . 15
4.4. EDHOC Message 3 . . . . . . . . . . . . . . . . . . . . . 18
5. EDHOC Authenticated with Symmetric Keys . . . . . . . . . . . 20
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2. EDHOC Message 1 . . . . . . . . . . . . . . . . . . . . . 21
5.3. EDHOC Message 2 . . . . . . . . . . . . . . . . . . . . . 21
5.4. EDHOC Message 3 . . . . . . . . . . . . . . . . . . . . . 22
6. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. EDHOC Error Message . . . . . . . . . . . . . . . . . . . 22
7. Transferring EDHOC and Deriving Application Keys . . . . . . 24
7.1. Transferring EDHOC in CoAP . . . . . . . . . . . . . . . 24
7.2. Transferring EDHOC over Other Protocols . . . . . . . . . 27
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
8.1. EDHOC Cipher Suites Registry . . . . . . . . . . . . . . 27
8.2. EDHOC Method Type Registry . . . . . . . . . . . . . . . 27
8.3. The Well-Known URI Registry . . . . . . . . . . . . . . . 27
8.4. Media Types Registry . . . . . . . . . . . . . . . . . . 27
8.5. CoAP Content-Formats Registry . . . . . . . . . . . . . . 28
9. Security Considerations . . . . . . . . . . . . . . . . . . . 29
9.1. Security Properties . . . . . . . . . . . . . . . . . . . 29
9.2. Cryptographic Considerations . . . . . . . . . . . . . . 30
9.3. Mandatory to Implement Cipher Suite . . . . . . . . . . . 30
Show full document text