Security Event Token (SET)
draft-backman-secevent-token-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Annabelle Backman , William Denniss , Morteza Ansari , Michael B. Jones | ||
| Last updated | 2018-06-03 (Latest revision 2017-11-30) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This specification defines the Security Event Token, which may be distributed via a protocol such as HTTP. The Security Event Token (SET) specification profiles the JSON Web Token (JWT), which can be optionally signed and/or encrypted. A SET describes a statement of fact from the perspective of an issuer that it intends to share with one or more receivers.
Authors
Annabelle Backman
William Denniss
Morteza Ansari
Michael B. Jones
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)