The Privacy Pass HTTP Authentication Scheme
draft-pauly-privacypass-auth-scheme-00
| Document | Type |
Replaced Internet-Draft
(privacypass WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tommy Pauly , Steven Valdez , Christopher A. Wood | ||
| Last updated | 2022-03-02 (Latest revision 2022-01-31) | ||
| Replaced by | draft-ietf-privacypass-auth-scheme | ||
| 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-auth-scheme | |
| 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 defines an HTTP authentication scheme that can be used by clients to redeem Privacy Pass tokens with an origin. It can also be used by origins to challenge clients to present an acceptable Privacy Pass token. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/tfpauly/privacy-proxy.
Authors
Tommy Pauly
Steven Valdez
Christopher A. Wood
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)