Object Security for Constrained RESTful Environments (OSCORE)
draft-ietf-core-object-security-15

Document Type Active Internet-Draft (core WG)
Last updated 2018-09-20 (latest revision 2018-08-31)
Replaces draft-selander-ace-object-security
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Dec 2017 - Object Security for ... )
Document shepherd Carsten Bormann
Shepherd write-up Show (last changed 2018-03-07)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has a DISCUSS. Needs one more YES or NO OBJECTION position to pass.
Responsible AD Alexey Melnikov
Send notices to Carsten Bormann <cabo@tzi.org>, jaime.jimenez@ericsson.com
IANA IANA review state Version Changed - Review Needed
IANA action state None
CoRE Working Group                                           G. Selander
Internet-Draft                                               J. Mattsson
Intended status: Standards Track                            F. Palombini
Expires: March 4, 2019                                       Ericsson AB
                                                                L. Seitz
                                                               RISE SICS
                                                         August 31, 2018

     Object Security for Constrained RESTful Environments (OSCORE)
                   draft-ietf-core-object-security-15

Abstract

   This document defines Object Security for Constrained RESTful
   Environments (OSCORE), a method for application-layer protection of
   the Constrained Application Protocol (CoAP), using CBOR Object
   Signing and Encryption (COSE).  OSCORE provides end-to-end protection
   between endpoints communicating using CoAP or CoAP-mappable HTTP.
   OSCORE is designed for constrained nodes and networks supporting a
   range of proxy operations, including translation between different
   transport protocols.

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 March 4, 2019.

Copyright Notice

   Copyright (c) 2018 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

Selander, et al.          Expires March 4, 2019                 [Page 1]
Internet-Draft                   OSCORE                      August 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   6
   2.  The OSCORE Option . . . . . . . . . . . . . . . . . . . . . .   7
   3.  The Security Context  . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Security Context Definition . . . . . . . . . . . . . . .   8
     3.2.  Establishment of Security Context Parameters  . . . . . .  10
     3.3.  Requirements on the Security Context Parameters . . . . .  13
   4.  Protected Message Fields  . . . . . . . . . . . . . . . . . .  14
     4.1.  CoAP Options  . . . . . . . . . . . . . . . . . . . . . .  15
     4.2.  CoAP Header Fields and Payload  . . . . . . . . . . . . .  23
     4.3.  Signaling Messages  . . . . . . . . . . . . . . . . . . .  24
   5.  The COSE Object . . . . . . . . . . . . . . . . . . . . . . .  24
     5.1.  Kid Context . . . . . . . . . . . . . . . . . . . . . . .  26
     5.2.  AEAD Nonce  . . . . . . . . . . . . . . . . . . . . . . .  26
     5.3.  Plaintext . . . . . . . . . . . . . . . . . . . . . . . .  27
     5.4.  Additional Authenticated Data . . . . . . . . . . . . . .  28
   6.  OSCORE Header Compression . . . . . . . . . . . . . . . . . .  29
     6.1.  Encoding of the OSCORE Option Value . . . . . . . . . . .  30
     6.2.  Encoding of the OSCORE Payload  . . . . . . . . . . . . .  31
     6.3.  Examples of Compressed COSE Objects . . . . . . . . . . .  31
   7.  Message Binding, Sequence Numbers, Freshness and Replay
       Protection  . . . . . . . . . . . . . . . . . . . . . . . . .  34
     7.1.  Message Binding . . . . . . . . . . . . . . . . . . . . .  34
     7.2.  Sequence Numbers  . . . . . . . . . . . . . . . . . . . .  34
     7.3.  Freshness . . . . . . . . . . . . . . . . . . . . . . . .  34
     7.4.  Replay Protection . . . . . . . . . . . . . . . . . . . .  35
     7.5.  Losing Part of the Context State  . . . . . . . . . . . .  36
   8.  Processing  . . . . . . . . . . . . . . . . . . . . . . . . .  37
     8.1.  Protecting the Request  . . . . . . . . . . . . . . . . .  37
     8.2.  Verifying the Request . . . . . . . . . . . . . . . . . .  38
     8.3.  Protecting the Response . . . . . . . . . . . . . . . . .  39
     8.4.  Verifying the Response  . . . . . . . . . . . . . . . . .  40
Show full document text