Security Event Token (SET)
draft-hunt-idevent-token-08
| Document | Type |
Replaced Internet-Draft
(secevent WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Phil Hunt , William Denniss , Morteza Ansari , Michael B. Jones | ||
| Last updated | 2017-01-09 | ||
| Replaced by | RFC 8417 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-secevent-token | |
| Consensus boilerplate | Unknown | ||
| 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) and may be optionally signed and/or encrypted. A SET describes a statement of fact that may be shared by an event publisher with event subscribers.
Authors
Phil Hunt
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.)