Secure group communication for CoAP
draft-ietf-core-oscore-groupcomm-02

Document Type Active Internet-Draft (core WG)
Last updated 2018-06-28
Replaces draft-tiloca-core-multicast-oscoap
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html 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                                             M. Tiloca
Internet-Draft                                                 RISE SICS
Intended status: Standards Track                             G. Selander
Expires: December 30, 2018                                  F. Palombini
                                                             Ericsson AB
                                                                 J. Park
                                             Universitaet Duisburg-Essen
                                                           June 28, 2018

                  Secure group communication for CoAP
                  draft-ietf-core-oscore-groupcomm-02

Abstract

   This document describes a mode for protecting group communication
   over the Constrained Application Protocol (CoAP).  The proposed mode
   relies on Object Security for Constrained RESTful Environments
   (OSCORE) and the CBOR Object Signing and Encryption (COSE) format.
   In particular, it is defined how OSCORE should be used in a group
   communication setting, while fulfilling the same security
   requirements for request messages and related response messages.
   Source authentication of all messages exchanged within the group is
   ensured, by means of digital signatures produced through private keys
   of sender endpoints and embedded in the protected CoAP messages.

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 December 30, 2018.

Copyright Notice

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

Tiloca, et al.          Expires December 30, 2018               [Page 1]
Internet-Draft     Secure group communication for CoAP         June 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  OSCORE Security Context . . . . . . . . . . . . . . . . . . .   5
     2.1.  Management of Group Keying Material . . . . . . . . . . .   7
   3.  The COSE Object . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Example: Request  . . . . . . . . . . . . . . . . . . . .   9
     3.2.  Example: Response . . . . . . . . . . . . . . . . . . . .  10
   4.  Message Processing  . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Protecting the Request  . . . . . . . . . . . . . . . . .  10
     4.2.  Verifying the Request . . . . . . . . . . . . . . . . . .  11
     4.3.  Protecting the Response . . . . . . . . . . . . . . . . .  11
     4.4.  Verifying the Response  . . . . . . . . . . . . . . . . .  11
   5.  Synchronization of Sequence Numbers . . . . . . . . . . . . .  12
   6.  Responsibilities of the Group Manager . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
     7.1.  Group-level Security  . . . . . . . . . . . . . . . . . .  14
     7.2.  Uniqueness of (key, nonce)  . . . . . . . . . . . . . . .  14
     7.3.  Collision of Group Identifiers  . . . . . . . . . . . . .  14
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Appendix A.  Assumptions and Security Objectives  . . . . . . . .  18
     A.1.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .  18
     A.2.  Security Objectives . . . . . . . . . . . . . . . . . . .  20
   Appendix B.  List of Use Cases  . . . . . . . . . . . . . . . . .  21
   Appendix C.  Example of Group Identifier Format . . . . . . . . .  23
Show full document text