Subject Identifiers for Security Event Tokens
draft-ietf-secevent-subject-identifiers-08
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Annabelle Backman , Marius Scurtescu | ||
| Last updated | 2021-11-25 (Latest revision 2021-05-24) | ||
| Replaces | draft-backman-secevent-subject-identifiers | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Yes | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | Benjamin Kaduk | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-secevent-subject-identifiers-08.txt
Abstract
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.
Authors
Annabelle Backman
Marius Scurtescu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)