Management API for SET Event Streams
draft-scurtescu-secevent-event-stream-mgmt-api-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marius Scurtescu , Annabelle Backman | ||
| Last updated | 2018-04-19 (Latest revision 2017-08-10) | ||
| Replaces | draft-scurtescu-secevent-simple-control-plane | ||
| 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
Security Event Token (SET) delivery requires event receivers to indicate to event transmitters the subjects about which they wish to receive events, and how they wish to receive them. This specification defines an HTTP API for a basic control plane that event transmitters can implement and event receivers may use to manage the flow of events from one to the other.
Authors
Marius Scurtescu
Annabelle Backman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)