Joining of OSCORE multicast groups in ACE
draft-tiloca-ace-oscoap-joining-02

Document Type Active Internet-Draft (individual)
Last updated 2017-10-29
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)
ACE Working Group                                              M. Tiloca
Internet-Draft                                              RISE SICS AB
Intended status: Standards Track                                 J. Park
Expires: May 2, 2018                         Universitaet Duisburg-Essen
                                                        October 29, 2017

               Joining of OSCORE multicast groups in ACE
                   draft-tiloca-ace-oscoap-joining-02

Abstract

   This document describes a method to join a multicast group where
   communications are based on CoAP and secured with Object Security for
   Constrained RESTful Environments (OSCORE).  The proposed method
   delegates the authentication and authorization of client nodes that
   join an OSCORE multicast group through a Group Manager server.  This
   approach builds on the ACE framework for Authentication and
   Authorization, and leverages protocol-specific profiles of ACE to
   achieve communication security, proof-of-possession and server
   authentication.

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 May 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
   publication of this document.  Please review these documents

Tiloca & Park              Expires May 2, 2018                  [Page 1]
Internet-Draft         OSCORE group joining in ACE          October 2017

   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.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Joining Node to Authorization Server  . . . . . . . . . . . .   6
   4.  Joining Node to Group Manager . . . . . . . . . . . . . . . .   7
   5.  Public Keys of Joining Nodes  . . . . . . . . . . . . . . . .   8
   6.  Updating Authorization Information  . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Object Security for Constrained RESTful Environments (OSCORE)
   [I-D.ietf-core-object-security] is a method for application layer
   protection of CoAP messages, using the CBOR Object Signing and
   Encryption (COSE) [RFC8152], and enabling end-to-end security of CoAP
   payload and options.

   OSCORE may also be used to protect group communication for CoAP over
   IP multicast, as described in [I-D.tiloca-core-multicast-oscoap].
   This relies on a Group Manager entity, which is responsible for
   managing a multicast group where members exchange CoAP messages
   secured with OSCORE.  In particular, the Group Manager coordinates
   the join process of new group members and can be responsible for
   multiple groups.

   This document builds on the ACE framework for Authentication and
   Authorization [I-D.ietf-ace-oauth-authz] and specifies how a client
   joins an OSCORE multicast group through a resource server acting as
   Group Manager.  The client acting as joining node relies on an Access
   Token, which is bound to a proof-of-possession key and authorizes the
   access to a specific join resource at the Group Manager.

   In order to achieve communication security, proof-of-possession and
   server authentication, the client and the Group Manager leverage

Tiloca & Park              Expires May 2, 2018                  [Page 2]
Show full document text