Hello everyone,
We have uploaded a new version with minor modifications before the document
expiration date:
Version -10 to -11
* Recommended /ps/TOPICNAME as path ot topic resources at the Broker.
* The request for a new Sender ID uses the method POST.
* Fixed description of ACE Group Error with identifier 4.
* Aligned requirement formulation with that in RFC 9594.
* Updated references.
* Clarifications and editorial improvements.
Kind regards,
--Cigdem
---------- Forwarded message ---------
From: <internet-dra...@ietf.org>
Date: Tue, 7 Jan 2025 at 19:15
Subject: New Version Notification for draft-ietf-ace-pubsub-profile-11.txt
To: Cigdem Sengul <csen...@acm.org>, Francesca Palombini <
francesca.palomb...@ericsson.com>, Marco Tiloca <marco.til...@ri.se>
A new version of Internet-Draft draft-ietf-ace-pubsub-profile-11.txt has
been
successfully submitted by Cigdem Sengul and posted to the
IETF repository.
Name: draft-ietf-ace-pubsub-profile
Revision: 11
Title: Publish-Subscribe Profile for Authentication and Authorization
for Constrained Environments (ACE)
Date: 2025-01-07
Group: ace
Pages: 57
URL:
https://www.ietf.org/archive/id/draft-ietf-ace-pubsub-profile-11.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-ace-pubsub-profile/
HTML:
https://www.ietf.org/archive/id/draft-ietf-ace-pubsub-profile-11.html
HTMLized:
https://datatracker.ietf.org/doc/html/draft-ietf-ace-pubsub-profile
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-pubsub-profile-11
Abstract:
This document defines an application profile of the Authentication
and Authorization for Constrained Environments (ACE) framework, to
enable secure group communication in the Publish-Subscribe (Pub-Sub)
architecture for the Constrained Application Protocol (CoAP) [draft-
ietf-core-coap-pubsub], where Publishers and Subscribers communicate
through a Broker. This profile relies on protocol-specific transport
profiles of ACE to achieve communication security, server
authentication, and proof-of-possession for a key owned by the Client
and bound to an OAuth 2.0 access token. This document specifies the
provisioning and enforcement of authorization information for Clients
to act as Publishers and/or Subscribers, as well as the provisioning
of keying material and security parameters that Clients use for
protecting their communications end-to-end through the Broker.
Note to RFC Editor: Please replace "[draft-ietf-core-coap-pubsub]"
with the RFC number of that document and delete this paragraph.
The IETF Secretariat
_______________________________________________
Ace mailing list -- ace@ietf.org
To unsubscribe send an email to ace-le...@ietf.org
