Combining EDHOC and OSCORE
draft-palombini-core-oscore-edhoc-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized 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)
CoRE Working Group                                          F. Palombini
Internet-Draft                                                  Ericsson
Intended status: Standards Track                               M. Tiloca
Expires: 14 January 2021                                     R. Hoeglund
                                                                 RISE AB
                                                            S. Hristozov
                                                        Fraunhofer AISEC
                                                             G. Selander
                                                                Ericsson
                                                            13 July 2020

                       Combining EDHOC and OSCORE
                  draft-palombini-core-oscore-edhoc-00

Abstract

   This document defines possible optimization approaches for combining
   the lightweight authenticated key exchange protocol EDHOC run over
   CoAP with the first subsequent OSCORE transaction.  This combination
   reduces the number of round trips required to set up an OSCORE
   Security Context and complete an OSCORE transaction using that
   context.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/EricssonResearch/oscore-edhoc
   (https://github.com/EricssonResearch/oscore-edhoc).

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 14 January 2021.

Palombini, et al.        Expires 14 January 2021                [Page 1]
Internet-Draft               EDHOC + OSCORE                    July 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  EDHOC in OSCORE . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Signalling in a New EDHOC Option  . . . . . . . . . . . .   6
     3.2.  Signalling in the OSCORE Option . . . . . . . . . . . . .   6
   4.  OSCORE in EDHOC . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Signalling in a New EDHOC+OSCORE Option . . . . . . . . .   8
     4.2.  Signalling Based on the Number of Elements in the
           Payload . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This document presents possible optimization approaches to combine
   the lightweight authenticated key exchange protocol EDHOC
   [I-D.ietf-lake-edhoc], when running over CoAP [RFC7252], with the
   first subsequent OSCORE [RFC8613] transaction.

   This allows for a minimum number of round trips necessary to setup
   the OSCORE Security Context and complete an OSCORE transaction, for
   example when an IoT device gets configured in a network for the first
   time.

   The number of protocol round trips impacts the minimum number of
   flights, which can have a substantial impact on performance with
   certain radio technologies as discussed in Section 2.11 of
   [I-D.ietf-lake-reqs].

Palombini, et al.        Expires 14 January 2021                [Page 2]
Internet-Draft               EDHOC + OSCORE                    July 2020

   Without this optimization, it is not possible, not even in theory, to
Show full document text