Privacy Pass: HTTP API
draft-svaldez-pp-http-api-01
| Document | Type |
Replaced Internet-Draft
(privacypass WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Steven Valdez | ||
| Last updated | 2020-10-07 (Latest revision 2020-07-13) | ||
| Replaced by | draft-ietf-privacypass-http-api | ||
| 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-http-api | |
| 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 specifies an integration for Privacy Pass over an HTTP API, along with recommendations on how key commitments are stored and accessed by HTTP-based consumers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)