Discovery of OSCORE Groups with the CoRE Resource Directory
draft-tiloca-core-oscore-discovery-03

Document Type Active Internet-Draft (individual)
Last updated 2019-07-05
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: January 6, 2020
                                                         P. van der Stok
                                                              Consultant
                                                           July 05, 2019

      Discovery of OSCORE Groups with the CoRE Resource Directory
                 draft-tiloca-core-oscore-discovery-03

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 a CoAP endpoint can use the CoRE Resource Directory to
   discover OSCORE groups and acquire information to join them through
   the respective Group Manager.  A given OSCORE group may protect
   multiple application groups, which are separately announced in the
   Resource Directory as sets of endpoints sharing a pool of resources.
   This approach is consistent with, but not limited to, the joining of
   OSCORE groups based on the ACE framework for Authentication and
   Authorization in constrained environments.

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 January 6, 2020.

Tiloca, et al.           Expires January 6, 2020                [Page 1]
Internet-Draft   OSCORE group discovery with the CoRE RD       July 2019

Copyright Notice

   Copyright (c) 2019 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
   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 . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Registration Resource for Group Managers  . . . . . . . . . .   5
   3.  Registration of Group Manager Endpoints . . . . . . . . . . .   6
   4.  Addition and Update of OSCORE Groups  . . . . . . . . . . . .   8
   5.  Discovery of OSCORE Groups  . . . . . . . . . . . . . . . . .   9
     5.1.  Discovery Example #1  . . . . . . . . . . . . . . . . . .  10
     5.2.  Discovery Example #2  . . . . . . . . . . . . . . . . . .  11
   6.  Use Case Example With Full Discovery  . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Resource Types  . . . . . . . . . . . . . . . . . . . . .  17
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  17
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  18
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   A set of CoAP endpoints constitutes an application group by sharing a
   common pool of resources.  The members of an application group may be
   members of a given security group, by sharing a common set of keying
   material to secure group communication.

   The Constrained Application Protocol (CoAP) [RFC7252] supports group
   communication over IP multicast
   [RFC7390][I-D.dijk-core-groupcomm-bis] to improve efficiency and
   latency of communication and reduce bandwidth requirements.  The
   document Object Security for Constrained RESTful Environments
   (OSCORE) [I-D.ietf-core-object-security] describes how to achieve

Tiloca, et al.           Expires January 6, 2020                [Page 2]
Show full document text