Re: [Id-event] RFC 9493 on Subject Identifiers for Security Event Tokens

[Prachi Jain <[e-mail]>]

Thanks Yaron. Truly appreciate the guidance and support in getting this
past the finish line.

On Thu, Dec 7, 2023 at 5:04 AM Yaron Sheffer <[e-mail]> wrote:

> Congratulations on this last deliverable of the Security Events working
> group. Thanks to Annabelle and Prachi who drove this document to completion!
>
>         Yaron
>
> On 07/12/2023, 3:06, "[e-mail] <mailto:
> [e-mail]> on behalf of [e-mail] <mailto:
> [e-mail]>" <[e-mail] <mailto:
> [e-mail]> on behalf of [e-mail] <mailto:
> [e-mail]>> wrote:
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>
>
> RFC 9493
>
>
> Title: Subject Identifiers for Security Event Tokens
> Author: A. Backman, Ed.,
> M. Scurtescu,
> P. Jain
> Status: Standards Track
> Stream: IETF
> Date: December 2023
> Mailbox: [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>
> Pages: 18
> Updates/Obsoletes/SeeAlso: None
>
>
> I-D Tag: draft-ietf-secevent-subject-identifiers-18.txt
>
>
> URL: https://www.rfc-editor.org/info/rfc9493 <
> https://www.rfc-editor.org/info/rfc9493>
>
>
> DOI: 10.17487/RFC9493
>
>
> Security events communicated within Security Event Tokens may support
> a variety of identifiers to identify subjects related to the event.
> This specification formalizes the notion of Subject Identifiers as
> structured information that describes a subject and named formats
> that define the syntax and semantics for encoding Subject Identifiers
> as JSON objects. It also establishes a registry for defining and
> allocating names for such formats as well as the JSON Web Token (JWT)
> "sub_id" Claim.
>
>
> This document is a product of the Security Events Working Group of the
> IETF.
>
>
> This is now a Proposed Standard.
>
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions
> for improvements. Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards <
> https://www.rfc-editor.org/standards>) for the
> standardization state and status of this protocol. Distribution of this
> memo is unlimited.
>
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
> https://www.ietf.org/mailman/listinfo/ietf-announce <
> https://www.ietf.org/mailman/listinfo/ietf-announce>
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist <
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>
>
>
> For searching the RFC series, see https://www.rfc-editor.org/search <
> https://www.rfc-editor.org/search>
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk <
> https://www.rfc-editor.org/retrieve/bulk>
>
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [e-mail] <mailto:
> [e-mail]>. Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> _______________________________________________
> Id-event mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/id-event <
> https://www.ietf.org/mailman/listinfo/id-event>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/id-event
>