SET Token Delivery Using HTTP
draft-hunt-secevent-distribution-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Phil Hunt , Marius Scurtescu | ||
Last updated | 2017-03-09 | ||
Replaced by | draft-ietf-secevent-delivery, draft-hunt-secevent-stream-mgmt | ||
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-hunt-secevent-stream-mgmt, 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 over TLS. The specification defines the metadata the an Event Transmitter uses to describe the Event Receiver's HTTP endpoint and the SET token delivery configuration. The specification defines how the Event Receiver may check the current configuration metadata and delivery status using HTTP GET over TLS. The specification also defines how delivery can be assured subject to the SET Token Receiver's need for assurance.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)