Admin Interface for the OSCORE Group Manager
draft-tiloca-ace-oscore-gm-admin-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

ACE Working Group                                              M. Tiloca
Internet-Draft                                               R. Hoeglund
Intended status: Experimental                                    RISE AB
Expires: May 7, 2020                                     P. van der Stok
                                                              Consultant
                                                            F. Palombini
                                                             Ericsson AB
                                                       November 04, 2019

              Admin Interface for the OSCORE Group Manager
                  draft-tiloca-ace-oscore-gm-admin-00

Abstract

   Group communication for CoAP can be secured using Group Object
   Security for Constrained RESTful Environments (Group OSCORE).  A
   Group Manager is responsible to handle the joining of new group
   members, as well as to manage and distribute the group key material.
   This document defines a RESTful admin interface at the Group Manager,
   that allows an Administrator entity to create and delete OSCORE
   groups, as well as to retrieve and update their configuration.  The
   ACE framework for Authentication and Authorization is used to enforce
   authentication and authorization of the Administrator at the Group
   Manager.  Protocol-specific transport profiles of ACE are used 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 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 May 7, 2020.

Tiloca, et al.             Expires May 7, 2020                  [Page 1]
Internet-Draft      Admin Interface for the OSCORE GM      November 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 . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Overview of the Admin Interface . . . . . . . . . . . . . . .   6
   4.  Group-collection Resource . . . . . . . . . . . . . . . . . .   7
     4.1.  GET . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  POST  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Group-configuration Resource  . . . . . . . . . . . . . . . .  12
     5.1.  GET . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.2.  POST  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.3.  DELETE  . . . . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  ACE Groupcomm Parameters Registry . . . . . . . . . . . .  15
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   The Constrained Application Protocol (CoAP) [RFC7252] can be used in
   group communication environments where messages are also exchanged
   over IP multicast [RFC7390][I-D.dijk-core-groupcomm-bis].
   Applications relying on CoAP can achieve end-to-end security at the
   application layer by using Object Security for Constrained RESTful
   Environments (OSCORE) [RFC8613], and especially Group OSCORE
   [I-D.ietf-core-oscore-groupcomm] in group communication scenarios.

Tiloca, et al.             Expires May 7, 2020                  [Page 2]