Key Provisioning for Group Communication using ACE
draft-palombini-ace-key-groupcomm-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-03-01
|
|
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 F. Palombini
Internet-Draft Ericsson AB
Intended status: Standards Track M. Tiloca
Expires: September 2, 2018 RISE SICS AB
March 01, 2018
Key Provisioning for Group Communication using ACE
draft-palombini-ace-key-groupcomm-00
Abstract
This document defines a message format for distributing keying
material in group communication scenarios (such as based on multicast
or publisher-subscriber model) using the ACE framework.
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 September 2, 2018.
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
(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.
Palombini & Tiloca Expires September 2, 2018 [Page 1]
Internet-Draft Key Prov Group Comm March 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Addition to the Group . . . . . . . . . . . . . . . . . . . . 4
3.1. Authorization Request . . . . . . . . . . . . . . . . . . 4
3.2. Authorization Response . . . . . . . . . . . . . . . . . 5
3.3. Token Post . . . . . . . . . . . . . . . . . . . . . . . 6
4. Key Distribution . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Key Distribution Request . . . . . . . . . . . . . . . . 6
4.2. Key Distribution Response . . . . . . . . . . . . . . . . 7
5. Remove a Node from the Group . . . . . . . . . . . . . . . . 8
5.1. Not authorized anymore . . . . . . . . . . . . . . . . . 8
5.2. Request to Leave the Group . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This document expands the ACE framework [I-D.ietf-ace-oauth-authz] to
define the format of messages used to distribute the keying material
in a group communication scenario. Profiles that use group
communication can build on this document to specify exactly which of
the message parameters defined in this documents are used, and what
are their values. Known applications that can benefit from this
document would be, for example, profiles addressing group
communication based on multicast [RFC7390] or publishing/subscribing
[I-D.ietf-core-coap-pubsub] in ACE.
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. These
words may also appear in this document in lowercase, absent their
normative meanings.
Readers are expected to be familiar with the terms and concepts
described in [I-D.ietf-ace-oauth-authz] and [RFC8152].
Palombini & Tiloca Expires September 2, 2018 [Page 2]
Internet-Draft Key Prov Group Comm March 2018
2. Overview
+-----------+ +-----------+
Show full document text