Hello ace,
In the new version, we have updated the following:
   *  More details on the scope format.
   *  More details in the encoding of the 'key' parameter in the Join
Response.
   *  More details on exchanges between group members and KDC.
   *  More details on the rekeying process and rekeying messages.
   *  Defined replay checks at the Subscriber.
   *  Improved examples.
   *  Improved security considerations.
   *  Revised IANA considerations.
   *  Aligned the list of profile requirements with
draft-ietf-ace-key-groupcomm.
   *  Clarifications and editorial improvements.

Kind regards,
--Cigdem

On Sun, 7 Jul 2024 at 22:24, <internet-dra...@ietf.org> wrote:

> Internet-Draft draft-ietf-ace-pubsub-profile-10.txt is now available. It
> is a
> work item of the Authentication and Authorization for Constrained
> Environments
> (ACE) WG of the IETF.
>
>    Title:   Publish-Subscribe Profile for Authentication and Authorization
> for Constrained Environments (ACE)
>    Authors: Francesca Palombini
>             Cigdem Sengul
>             Marco Tiloca
>    Name:    draft-ietf-ace-pubsub-profile-10.txt
>    Pages:   56
>    Dates:   2024-07-07
>
> 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 datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ace-pubsub-profile/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-ace-pubsub-profile-10.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ace-pubsub-profile-10
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> Ace mailing list -- ace@ietf.org
> To unsubscribe send an email to ace-le...@ietf.org
>
_______________________________________________
Ace mailing list -- ace@ietf.org
To unsubscribe send an email to ace-le...@ietf.org

Reply via email to