Privacy Pass HTTP API
draft-ietf-privacypass-http-api-00
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Steven Valdez | ||
| Last updated | 2021-07-09 (Latest revision 2021-01-05) | ||
| Replaces | draft-svaldez-pp-http-api | ||
| Replaced by | draft-ietf-privacypass-auth-scheme | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| 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 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.)