Skip to main content

Privacy Pass Issuance Protocol
draft-ietf-privacypass-protocol-16

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-protocol@ietf.org, jsalowey@gmail.com, paul.wouters@aiven.io, privacy-pass@ietf.org, privacypass-chairs@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Privacy Pass Issuance Protocol' to Proposed Standard (draft-ietf-privacypass-protocol-16.txt)

The IESG has approved the following document:
- 'Privacy Pass Issuance Protocol'
  (draft-ietf-privacypass-protocol-16.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-protocol/


Ballot Text

Technical Summary

   This document specifies two variants of the two-message issuance
   protocol for Privacy Pass tokens: one that produces tokens that are
   privately verifiable using the issuance private key, and another that
   produces tokens that are publicly verifiable using the issuance
   public key.

Working Group Summary

   Strong consensus (although the WG is relatively small)

Document Quality

There are deployed examples of the privacy pass protocol.  References to
these implementations are included in the architecture document. This includes
two open source implementations that implement pieces of the architecture and vendor
products including private access tokens implemented by Apple, Cloudflare and
Fastly. These implementations communicate using the auth scheme defined in
this document (see e.g. https://developer.apple.com/news/?id=huqjyh7k,
https://www.fastly.com/blog/private-access-tokens-stepping-into-the-privacy-respecting-captcha-less).

A number of issues were addressed after various directorate reviews (esp the HTTPDIR review)

The 3 Media Types were approved by the Expert.

Personnel

   The Document Shepherd for this document is Joseph A. Salowey. The
   Responsible Area Director is Paul Wouters.

RFC Editor Note