Pub-Sub Profile for Authentication and Authorization for Constrained Environments (ACE)
draft-ietf-ace-pubsub-profile-00
ACE Working Group F. Palombini
Internet-Draft Ericsson
Intended status: Standards Track January 04, 2020
Expires: July 7, 2020
Pub-Sub Profile for Authentication and Authorization for Constrained
Environments (ACE)
draft-ietf-ace-pubsub-profile-00
Abstract
This specification defines an application profile for authentication
and authorization for publishers and subscribers in a pub-sub setting
scenario in a constrained environment, using the ACE framework. This
profile relies on transport layer or application layer security to
authorize the publisher to the broker. Moreover, it relies on
application layer security for publisher-broker and subscriber-broker
communication.
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 July 7, 2020.
Copyright Notice
Copyright (c) 2020 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
Palombini Expires July 7, 2020 [Page 1]
Internet-Draft pubsub-profile January 2020
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 . . . . . . . . . . . . . . . . . . . . . . . 2
2. Application Profile Overview . . . . . . . . . . . . . . . . 3
3. coap_pubsub_app Application Profile . . . . . . . . . . . . . 5
3.1. Retrieval of COSE Key for protection of content . . . . . 5
4. Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Pub-Sub Protected Communication . . . . . . . . . . . . . . . 12
6.1. Using COSE Objects To Protect The Resource Representation 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8.1. ACE Groupcomm Profile Registry . . . . . . . . . . . . . 15
8.2. ACE Groupcomm Key Registry . . . . . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.1. Normative References . . . . . . . . . . . . . . . . . . 16
9.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Requirements on Application Profiles . . . . . . . . 17
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction
The publisher-subscriber setting allows for devices with limited
reachability to communicate via a broker that enables store-and-
forward messaging between the devices. The pub-sub scenario using
the Constrained Application Protocol (CoAP) is specified in
[I-D.ietf-core-coap-pubsub]. This document defines a way to
authorize nodes in a CoAP pub-sub type of setting, using the ACE
framework [I-D.ietf-ace-oauth-authz], and to provide the keys for
protecting the communication between these nodes.
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 RFC 2119 [RFC2119].
Readers are expected to be familiar with the terms and concepts
described in [I-D.ietf-ace-oauth-authz], [I-D.ietf-ace-key-groupcomm]
and [I-D.ietf-core-coap-pubsub]. In particular, analogously to
[I-D.ietf-ace-oauth-authz], terminology for entities in the
architecture such as Client (C), Resource Server (RS), and
Palombini Expires July 7, 2020 [Page 2]
Show full document text