Subject Identifiers for Security Event Tokens
draft-backman-secevent-subject-identifiers-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Annabelle Backman , Marius Scurtescu | ||
| Last updated | 2018-06-04 | ||
| Replaced by | draft-ietf-secevent-subject-identifiers | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-secevent-subject-identifiers | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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) [JWT] or Security Event Token (SET) [SET], and a registry for defining and allocating names for these claim sets.
Authors
Annabelle Backman
Marius Scurtescu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)