Checking Resource Consistency with HTTP Mirrors
draft-group-privacypass-consistency-mirror-01
| Document | Type |
Replaced Internet-Draft
(privacypass WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Benjamin Beurdouche , Matthew Finkel , Steven Valdez , Christopher A. Wood , Tommy Pauly | ||
| Last updated | 2024-01-10 (Latest revision 2023-10-23) | ||
| Replaces | draft-group-privacypass-k-check | ||
| Replaced by | draft-ietf-privacypass-consistency-mirror | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-privacypass-consistency-mirror | |
| 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 the mirror protocol, an HTTP-based protocol for fetching mirrored HTTP resources. The primary use case for the mirror protocol is to support HTTP resource consistency checks in protocols that require clients have a consistent view of some protocol-specific resource (typically, a public key) for security or privacy reasons, including Privacy Pass and Oblivious HTTP. To that end, this document also describes how to use the mirror protocol to implement these consistency checks.
Authors
Benjamin Beurdouche
Matthew Finkel
Steven Valdez
Christopher A. Wood
Tommy Pauly
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)