Pub-Sub Profile for Authentication and Authorization for Constrained Environments (ACE)
draft-ietf-ace-pubsub-profile-02
ACE Working Group F. Palombini
Internet-Draft Ericsson
Intended status: Standards Track C. Sengul
Expires: 7 July 2021 Brunel University
3 January 2021
Pub-Sub Profile for Authentication and Authorization for Constrained
Environments (ACE)
draft-ietf-ace-pubsub-profile-02
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.
Note to Readers
Source for this draft and an issue tracker can be found at
https://github.com/ace-wg/pubsub-profile (https://github.com/ace-wg/
pubsub-profile).
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 7 July 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
Palombini & Sengul Expires 7 July 2021 [Page 1]
Internet-Draft pubsub-profile January 2021
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. Application Profile Overview . . . . . . . . . . . . . . . . 3
3. PubSub Application Profiles . . . . . . . . . . . . . . . . . 5
3.1. Retrieval of COSE Key for protection of content . . . . . 6
3.2. coap_pubsub_app Application Profile . . . . . . . . . . . 9
3.3. mqtt_pubsub_app Application Profile . . . . . . . . . . . 9
4. Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. CoAP Publisher . . . . . . . . . . . . . . . . . . . . . 11
4.2. MQTT Publisher . . . . . . . . . . . . . . . . . . . . . 11
5. Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. CoAP Subscriber . . . . . . . . . . . . . . . . . . . . . 12
5.2. MQTT Subscriber . . . . . . . . . . . . . . . . . . . . . 13
6. Pub-Sub Protected Communication . . . . . . . . . . . . . . . 13
6.1. Using COSE Objects To Protect The Resource
Representation . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8.1. ACE Groupcomm Profile Registry . . . . . . . . . . . . . 16
8.1.1. CoAP Profile Registration . . . . . . . . . . . . . . 17
8.1.2. CoAP Profile Registration . . . . . . . . . . . . . . 17
8.2. ACE Groupcomm Key Registry . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Requirements on Application Profiles . . . . . . . . 19
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
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
Show full document text