[Openid-specs-risc] FW: [Id-event] Protocol Action: 'Subject Identifiers for Security Event Tokens' to Proposed Standard (draft-ietf-secevent-subject-identifiers-18.txt)

[Tim Cappalli]

From: Id-event <id-event-bounces at ietf.org> on behalf of The IESG <iesg-secretary at ietf.org>
Date: Monday, June 26, 2023 at 14:09
To: IETF-Announce <ietf-announce at ietf.org>
Cc: The IESG <iesg at ietf.org>, draft-ietf-secevent-subject-identifiers at ietf.org <draft-ietf-secevent-subject-identifiers at ietf.org>, id-event at ietf.org <id-event at ietf.org>, rdd at cert.org <rdd at cert.org>, rfc-editor at rfc-editor.org <rfc-editor at rfc-editor.org>, secevent-chairs at ietf.org <secevent-chairs at ietf.org>, yaronf.ietf at gmail.com <yaronf.ietf at gmail.com>
Subject: [Id-event] Protocol Action: 'Subject Identifiers for Security Event Tokens' to Proposed Standard (draft-ietf-secevent-subject-identifiers-18.txt)
The IESG has approved the following document:
- 'Subject Identifiers for Security Event Tokens'
  (draft-ietf-secevent-subject-identifiers-18.txt) as Proposed Standard

This document is the product of the Security Events Working Group.

The IESG contact persons are Paul Wouters and Roman Danyliw.

A URL of this Internet-Draft is:
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-secevent-subject-identifiers%2F&data=05%7C01%7Ctim.cappalli%40microsoft.com%7Cad3ecee1f52342465c9e08db76706ff6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638233997536089185%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YvcWWpHru4ZFhCQm00s4nrkMumuPUs0fN%2BOuwcOdIVg%3D&reserved=0<https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/>





Technical Summary

   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 describe a subject, and named formats
   that define the syntax and semantics for encoding subject identifiers
   as JSON objects.  It also defines a registry for defining and
   allocating names for such formats, as well as the sub_id JSON Web
   Token (JWT) claim.

Working Group Summary

There was nothing notable in the WG process beyond the long dormancy this document had.

Document Quality

This is a dependency of the GNAP WG, and GNAP participants have been involved in the later development stages of this draft.

Personnel

- Document Shepherd:  Yaron Sheffer
- Responsible AD: Roman Danyliw

_______________________________________________
Id-event mailing list
Id-event at ietf.org
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fid-event&data=05%7C01%7Ctim.cappalli%40microsoft.com%7Cad3ecee1f52342465c9e08db76706ff6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638233997536089185%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9soZHMjmsCNsWZoAyI30XSXBJhNLsCuZ6NPC8TbkTc8%3D&reserved=0<https://www.ietf.org/mailman/listinfo/id-event>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20230627/e0c075ec/attachment.html>