SET Token Delivery Using HTTP
draft-hunt-secevent-delivery-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Phil Hunt , Marius Scurtescu , Morteza Ansari , Anthony Nadalin , Annabelle Backman | ||
| Last updated | 2017-07-02 | ||
| Replaced by | draft-ietf-secevent-delivery | ||
| 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-delivery | |
| 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 how a series of security event tokens (SETs) may be delivered to a previously registered receiver using HTTP POST over TLS initiated as a push to the receiver, or as a poll by the receiver. The specification also defines how delivery can be assured subject to the SET Token Receiver's need for assurance.
Authors
Phil Hunt
Marius Scurtescu
Morteza Ansari
Anthony Nadalin
Annabelle Backman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)