Signing HTTP Messages
draft-ietf-httpbis-message-signatures-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Annabelle Backman , Justin Richer , Manu Sporny | ||
| Last updated | 2020-10-12 (Latest revision 2020-04-10) | ||
| Replaces | draft-richanna-http-message-signatures, draft-cavage-http-signatures | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
ARTART Telechat review
(of
-17)
by Harald Alvestrand
Ready w/issues
GENART Last Call review
(of
-16)
by Dan Romascanu
Ready w/nits
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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 document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over content within an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer, and where the message may be transformed (e.g., by intermediaries) before reaching the verifier.
Authors
Annabelle Backman
Justin Richer
Manu Sporny
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)