Requirements for a Lightweight AKE for OSCORE
draft-ietf-lake-reqs-03
Network Working Group M. Vucinic
Internet-Draft Inria
Intended status: Informational G. Selander
Expires: 31 October 2020 J. Mattsson
Ericsson AB
D. Garcia
Odin Solutions S.L.
29 April 2020
Requirements for a Lightweight AKE for OSCORE
draft-ietf-lake-reqs-03
Abstract
This document compiles the requirements for a lightweight
authenticated key exchange protocol for OSCORE. This draft is in a
working group last call (WGLC) in the LAKE working group. Post-WGLC,
the requirements will be considered sufficiently stable for the
working group to proceed with its work. It is not currently planned
to publish this draft as an RFC.
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 31 October 2020.
Copyright Notice
Copyright (c) 2020 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
Vucinic, et al. Expires 31 October 2020 [Page 1]
Internet-Draft Reqs-LAKE-for-OSCORE April 2020
and restrictions with respect 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Problem description . . . . . . . . . . . . . . . . . . . . . 3
2.1. AKE for OSCORE . . . . . . . . . . . . . . . . . . . . . 3
2.2. Credentials . . . . . . . . . . . . . . . . . . . . . . . 5
2.2.1. Initial Focus . . . . . . . . . . . . . . . . . . . . 6
2.3. Mutual Authentication . . . . . . . . . . . . . . . . . . 7
2.4. Confidentiality . . . . . . . . . . . . . . . . . . . . . 7
2.5. Cryptographic Agility and Negotiation Integrity . . . . . 8
2.6. Cryptographic Strength . . . . . . . . . . . . . . . . . 9
2.7. Identity Protection . . . . . . . . . . . . . . . . . . . 9
2.8. Auxiliary Data . . . . . . . . . . . . . . . . . . . . . 10
2.9. Extensibility . . . . . . . . . . . . . . . . . . . . . . 11
2.10. Availability . . . . . . . . . . . . . . . . . . . . . . 11
2.11. Lightweight . . . . . . . . . . . . . . . . . . . . . . . 11
2.11.1. LoRaWAN . . . . . . . . . . . . . . . . . . . . . . 13
2.11.2. 6TiSCH . . . . . . . . . . . . . . . . . . . . . . . 15
2.11.3. NB-IoT . . . . . . . . . . . . . . . . . . . . . . . 16
2.11.4. Discussion and Summary of Benchmarks . . . . . . . . 18
2.11.5. AKE frequency . . . . . . . . . . . . . . . . . . . 20
3. Security Considerations . . . . . . . . . . . . . . . . . . . 21
4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 21
Informative References . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction
OSCORE [RFC8613] is a lightweight communication security protocol
providing end-to-end security on application layer for constrained
IoT settings (cf. [RFC7228]). OSCORE lacks a matching authenticated
key exchange protocol (AKE). The intention with the LAKE WG
[LAKE-WG] is to create a simple yet secure AKE for implementation in
embedded devices supporting OSCORE.
To ensure that the AKE is efficient for the expected applications of
OSCORE, we list the relevant public specifications of technologies
Show full document text