Requirements for a Lightweight AKE for OSCORE
draft-ietf-lake-reqs-01

Document Type Active Internet-Draft (lake WG)
Last updated 2020-02-19
Replaces draft-selander-lake-reqs
Stream IETF
Intended RFC status (None)
Formats plain text html xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         M. Vucinic
Internet-Draft                                                     Inria
Intended status: Informational                               G. Selander
Expires: 22 August 2020                                      J. Mattsson
                                                             Ericsson AB
                                                               D. Garcia
                                                     Odin Solutions S.L.
                                                        19 February 2020

             Requirements for a Lightweight AKE for OSCORE
                        draft-ietf-lake-reqs-01

Abstract

   This document compiles the requirements for a lightweight
   authenticated key exchange protocol for OSCORE.

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 22 August 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
   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.

Vucinic, et al.          Expires 22 August 2020                 [Page 1]
Internet-Draft            Reqs-LAKE-for-OSCORE             February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Problem description . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  AKE for OSCORE  . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Credentials . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Mutual Authentication . . . . . . . . . . . . . . . . . .   6
     2.4.  Confidentiality . . . . . . . . . . . . . . . . . . . . .   7
     2.5.  Cryptographic Agility and Negotiation Integrity . . . . .   7
     2.6.  Identity Protection . . . . . . . . . . . . . . . . . . .   8
     2.7.  Auxiliary Data  . . . . . . . . . . . . . . . . . . . . .   9
     2.8.  Extensibility . . . . . . . . . . . . . . . . . . . . . .   9
     2.9.  Denial of Service . . . . . . . . . . . . . . . . . . . .  10
     2.10. Lightweight . . . . . . . . . . . . . . . . . . . . . . .  10
       2.10.1.  LoRaWAN  . . . . . . . . . . . . . . . . . . . . . .  12
       2.10.2.  6TiSCH . . . . . . . . . . . . . . . . . . . . . . .  13
       2.10.3.  NB-IoT . . . . . . . . . . . . . . . . . . . . . . .  14
       2.10.4.  Discussion . . . . . . . . . . . . . . . . . . . . .  16
       2.10.5.  AKE frequency  . . . . . . . . . . . . . . . . . . .  17
   3.  Requirements Summary  . . . . . . . . . . . . . . . . . . . .  17
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Informative References  . . . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

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 LAKE 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
   where OSCORE is included:

   *  The IETF 6TiSCH WG charter (-02) identifies the need to "secur[e]
      the join process and mak[e] that fit within the constraints of
      high latency, low throughput and small frame sizes that
      characterize IEEE802.15.4 TSCH".  OSCORE protects the join
      protocol as described in 6TiSCH Minimal Security
      [I-D.ietf-6tisch-minimal-security].
Show full document text