The Privacy Pass HTTP Authentication Scheme
draft-ietf-privacypass-auth-scheme-15

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-privacypass-auth-scheme@ietf.org, ietf@bemasc.net, paul.wouters@aiven.io, privacy-pass@ietf.org, privacypass-chairs@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'The Privacy Pass HTTP Authentication Scheme' to Proposed Standard (draft-ietf-privacypass-auth-scheme-15.txt)

The IESG has approved the following document:
- 'The Privacy Pass HTTP Authentication Scheme'
  (draft-ietf-privacypass-auth-scheme-15.txt) as Proposed Standard

This document is the product of the Privacy Pass Working Group.

The IESG contact persons are Paul Wouters and Roman Danyliw.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-privacypass-auth-scheme/

Ballot Text

Technical Summary

   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.

Working Group Summary

The document is intended to address a specific charter point for the PRIVACYPASS
working group: to "specify a HTTP-layer API for the protocol".  Initial proposals
defined a REST API, but the proposal was ultimately streamlined to this form. The
working group has a clear consensus that this is the right approach and adequately
addresses the need for an "HTTP-layer API". The AD was consulted to see if this was
considered in charter.
 

Document Quality

A number of vendors are implementing or planning to implement.

Personnel

   The Document Shepherd for this document is Benjamin M. Schwartz. The
   Responsible Area Director is Paul Wouters.

RFC Editor Note