Secure group communication for CoAP
draft-tiloca-core-multicast-oscoap-02

Document Type Active Internet-Draft (individual)
Last updated 2017-07-01
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                             M. Tiloca
Internet-Draft                                              RISE SICS AB
Intended status: Standards Track                             G. Selander
Expires: January 2, 2018                                    F. Palombini
                                                             Ericsson AB
                                                           July 01, 2017

                  Secure group communication for CoAP
                 draft-tiloca-core-multicast-oscoap-02

Abstract

   This document describes a method for protecting group communication
   over the Constrained Application Protocol (CoAP).  The proposed
   approach relies on Object Security of CoAP (OSCOAP) and the CBOR
   Object Signing and Encryption (COSE) format.  All security
   requirements fulfilled by OSCOAP are maintained for multicast OSCOAP
   request messages and related unicast OSCOAP response messages.
   Source authentication of all messages exchanged within the group is
   ensured, by means of digital signatures produced through private keys
   of sender devices 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 http://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 January 2, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Tiloca, et al.           Expires January 2, 2018                [Page 1]
Internet-Draft     Secure group communication for CoAP         July 2017

   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.  Prerequisites and Requirements  . . . . . . . . . . . . . . .   4
   3.  Set-up Phase  . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Security Context  . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Message Processing  . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  Protecting the Request  . . . . . . . . . . . . . . . . .  10
     5.2.  Verifying the Request . . . . . . . . . . . . . . . . . .  10
     5.3.  Protecting the Response . . . . . . . . . . . . . . . . .  10
     5.4.  Verifying the Response  . . . . . . . . . . . . . . . . .  11
   6.  The COSE Object . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     7.1.  Group-level Security  . . . . . . . . . . . . . . . . . .  14
     7.2.  Management of Group Keying Material . . . . . . . . . . .  14
     7.3.  Synchronization of Sequence Numbers . . . . . . . . . . .  15
     7.4.  Provisioning of Public Keys . . . . . . . . . . . . . . .  16
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  17
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     10.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Appendix A.  Group Joining Based on the ACE Framework . . . . . .  20
   Appendix B.  List of Use Cases  . . . . . . . . . . . . . . . . .  20
   Appendix C.  No Source Authentication . . . . . . . . . . . . . .  22
   Appendix D.  Unicast OSCOAP Messages with Digital Signature . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  24

1.  Introduction

   The Constrained Application Protocol (CoAP) [RFC7252] is a web
   transfer protocol specifically designed for constrained devices and
Show full document text