Multi-Push-Based Security Event Token (SET) Delivery Using HTTP
draft-deshpande-secevent-http-multi-push-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Apoorva Deshpande , Aaron Parecki | ||
| Last updated | 2025-03-29 (Latest revision 2024-09-25) | ||
| 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 how multiple Security Event Tokens (SETs) can be delivered to an intended recipient using HTTP POST over TLS. The SETs are transmitted in the body of an HTTP POST request to an endpoint operated by the recipient, and the recipient indicates successful or failed transmission via the HTTP response.
Authors
Apoorva Deshpande
Aaron Parecki
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)