Discovery of OSCORE groups with the CoRE Resource Directory
draft-tiloca-core-oscore-discovery-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-09
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 AB
Intended status: Standards Track                              C. Amsuess
Expires: April 12, 2019
                                                         P. van der Stok
                                                              Consultant
                                                        October 09, 2018

      Discovery of OSCORE groups with the CoRE Resource Directory
                 draft-tiloca-core-oscore-discovery-00

Abstract

   Group communication over the Constrained Application Protocol (CoAP)
   can be secured by means of Object Security for Constrained RESTful
   Environments (OSCORE).  At deployment time, devices may not know the
   exact OSCORE groups to join, the respective Group Manager, or other
   information required to perform the joining process.  This document
   describes how CoAP endpoints can use the CoRE Resource Directory to
   discover OSCORE groups and acquire information to join them through
   their respective Group Manager.  This approach is consistent with,
   but not limited to, the joining of OSCORE groups based on the ACE
   framework for Authentication and Authorization.

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 April 12, 2019.

Copyright Notice

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

Tiloca, et al.           Expires April 12, 2019                 [Page 1]
Internet-Draft   OSCORE group discovery with the CoRE RD    October 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Registration Resource for Group Managers  . . . . . . . . . .   4
   3.  Registration of Group Manager Endpoints . . . . . . . . . . .   4
   4.  Addition and Update of OSCORE Groups  . . . . . . . . . . . .   5
   5.  Discovery of OSCORE Groups  . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Resource Types  . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The Constrained Application Protocol (CoAP) [RFC7252] supports group
   communication over IP multicast [RFC7390] to improve efficiency and
   latency of communication and reduce bandwidth requirements.  The
   method Object Security for Constrained RESTful Environments (OSCORE)
   [I-D.ietf-core-object-security] enables end-to-end security of CoAP
   payload and options through CBOR Object Signing and Encryption (COSE)
   [RFC8152].  In addition, [I-D.ietf-core-oscore-groupcomm] specifies
   how OSCORE protects CoAP messages in group communication contexts.

   A CoAP endpoint joins an OSCORE group by interacting with the
   responsible Group Manager (GM) to get the required keying material.
   As described in [I-D.tiloca-ace-oscoap-joining], the joining process
   can be based on the ACE framework for Authentication and
   Authorization in constrained environments [I-D.ietf-ace-oauth-authz],
   with the joining endpoint and the GM as ACE Client and ACE Resource
   Server, respectively.  That is, the joining endpoint accesses the
   join resource associated to the OSCORE group of interest and exported
Show full document text