Re: Call for Adoption: Private State Tokens/Private Tokens Work Stream from Chris Wood on 2022-12-08 (public-antifraud@w3.org from December 2022)

From: Chris Wood <chriswood@cloudflare.com>
Date: Thu, 8 Dec 2022 14:03:12 -0500
To: Jeffrey Yasskin <jyasskin@google.com>
Cc: Tommy Pauly <tpauly@apple.com>, "Zucker-Scharff, Aram" <Aram.Zucker-Scharff@washpost.com>, "public-antifraud@w3.org" <public-antifraud@w3.org>, Brian May <bmay@dstillery.com>, Chris Wilson <cwilso@google.com>, Sofía Celi <cherenkov@riseup.net>, Steven Valdez <svaldez@google.com>
Message-ID: <CAHOm9wdoODr1qn748omvFYJ8BSn__ydnMgex5ShU_tWn8DwjhA@mail.gmail.com>

On Thu, Dec 8, 2022 at 2:00 PM Jeffrey Yasskin <jyasskin@google.com> wrote:

> On Thu, Dec 8, 2022 at 9:51 AM Tommy Pauly <tpauly@apple.com> wrote:
>
>> ... we do have a solid basis and architecture for algorithms and an
>> extensible architecture for token types that’s quite mature in the IETF
>> PrivacyPass WG. That standardized version of privacy pass ...
>>
>
> Tommy, where is the standardized version of privacy pass? The latest I see
> is https://datatracker.ietf.org/doc/draft-ietf-privacypass-protocol/07/,
> which is not standardized.
>

This is in WGLC now and likely on its way to moving through the process. It
also has codepoints locked in and real world versions of it deployed. All
that remains is some of the IETF process.

Best,
Chris

>
> Thanks,
> Jeffrey
>

Received on Thursday, 8 December 2022 19:03:36 UTC