Subject Identifiers for Security Event Tokens
draft-ietf-secevent-subject-identifiers-05

Document Type Expired Internet-Draft (individual)
Last updated 2020-01-25 (latest revision 2019-07-24)
Replaces draft-backman-secevent-subject-identifiers
Stream (None)
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Yes
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD Benjamin Kaduk
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-secevent-subject-identifiers-05.txt

Abstract

Security events communicated within Security Event Tokens may support a variety of identifiers to identify the subject and/or other principals related to the event. This specification formalizes the notion of subject identifiers as named sets of well-defined claims describing the subject, a mechanism for representing subject identifiers within a [JSON] object such as a JSON Web Token [JWT] or Security Event Token [SET], and a registry for defining and allocating names for these claim sets.

Authors

Annabelle Backman (richanna@amazon.com)
Marius Scurtescu (marius.scurtescu@coinbase.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)