Key Management for OSCORE Groups in ACE
draft-ietf-ace-key-groupcomm-oscore-00
ACE Working Group M. Tiloca
Internet-Draft RISE AB
Intended status: Standards Track J. Park
Expires: June 23, 2019 Universitaet Duisburg-Essen
F. Palombini
Ericsson AB
December 20, 2018
Key Management for OSCORE Groups in ACE
draft-ietf-ace-key-groupcomm-oscore-00
Abstract
This document describes a method to request and provision keying
material in group communication scenarios 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 new client nodes that join an
OSCORE 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 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 June 23, 2019.
Copyright Notice
Copyright (c) 2018 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
Tiloca, et al. Expires June 23, 2019 [Page 1]
Internet-Draft Key Management for OSCORE Groups in ACE December 2018
(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
1.2. Relation to Other Documents . . . . . . . . . . . . . . . 5
2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Overview of the Join Process . . . . . . . . . . . . . . 7
2.2. Overview of the Group Rekeying Process . . . . . . . . . 7
3. Joining Node to Authorization Server . . . . . . . . . . . . 8
3.1. Authorization Request . . . . . . . . . . . . . . . . . . 8
3.2. Authorization Response . . . . . . . . . . . . . . . . . 9
4. Joining Node to Group Manager . . . . . . . . . . . . . . . . 10
4.1. Join Request . . . . . . . . . . . . . . . . . . . . . . 10
4.2. Join Response . . . . . . . . . . . . . . . . . . . . . . 10
5. Leaving of a Group Member . . . . . . . . . . . . . . . . . . 12
6. Public Keys of Joining Nodes . . . . . . . . . . . . . . . . 12
7. Group Rekeying Process . . . . . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 16
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
Object Security for Constrained RESTful Environments (OSCORE)
[I-D.ietf-core-object-security] is a method for application-layer
protection of the Constrained Application Protocol (CoAP) [RFC7252],
using CBOR Object Signing and Encryption (COSE) [RFC8152] and
enabling end-to-end security of CoAP payload and options.
As described in [I-D.ietf-core-oscore-groupcomm], OSCORE may be used
to protect CoAP group communication over IP multicast [RFC7390].
This relies on a Group Manager, which is responsible for managing an
Show full document text