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

Document Type Active Internet-Draft (core WG)
Authors Francesca Palombini  , Marco Tiloca  , Rikard Höglund  , Stefan Hristozov  , Göran Selander 
Last updated 2021-04-01
Replaces draft-palombini-core-oscore-edhoc
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) 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)
CoRE Working Group                                          F. Palombini
Internet-Draft                                                  Ericsson
Intended status: Standards Track                               M. Tiloca
Expires: 3 October 2021                                      R. Hoeglund
                                                                 RISE AB
                                                            S. Hristozov
                                                        Fraunhofer AISEC
                                                             G. Selander
                                                                Ericsson
                                                            1 April 2021

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

Abstract

   This document defines an optimization approach 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 to complete an OSCORE transaction using that
   Security Context.

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 3 October 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Palombini, et al.        Expires 3 October 2021                 [Page 1]
Internet-Draft               EDHOC + OSCORE                   April 2021

   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 Option  . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  EDHOC Combined with OSCORE  . . . . . . . . . . . . . . . . .   6
     4.1.  Client Processing . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Server Processing . . . . . . . . . . . . . . . . . . . .   7
   5.  Example of EDHOC + OSCORE Request . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  CoAP Option Numbers Registry  . . . . . . . . . . . . . .  10
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   This document defines an optimization approach 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.

   This optimization is desirable, since the number of protocol round
   trips impacts the minimum number of flights, which in turn can have a
   substantial impact on the latency of conveying the first OSCORE
   request, when using certain radio technologies.

Palombini, et al.        Expires 3 October 2021                 [Page 2]
Internet-Draft               EDHOC + OSCORE                   April 2021

   Without this optimization, it is not possible, not even in theory, to
   achieve the minimum number of flights.  This optimization makes it
   possible also in practice, since the last message of the EDHOC
   protocol can be made relatively small (see Section 1 of
   [I-D.ietf-lake-edhoc]), thus allowing additional OSCORE protected
Show full document text