The K-Check Protocol for HTTP Resource Consistency
draft-group-privacypass-k-check-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Benjamin Beurdouche , Matthew Finkel , Steven Valdez , Christopher A. Wood | ||
| Last updated | 2023-07-10 | ||
| Replaced by | draft-group-privacypass-consistency-mirror | ||
| 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-group-privacypass-consistency-mirror | |
| 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 protocol called K-Check for implementing HTTP resource consistency checks. The primary use case for K-Check is for deployments of protocols such as Privacy Pass and Oblivious HTTP in which privacy goals require that clients have a consistent view of some protocol-specific resource (typically, a public key).
Authors
Benjamin Beurdouche
Matthew Finkel
Steven Valdez
Christopher A. Wood
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)