Re: Call for Adoption: Private State Tokens/Private Tokens Work Stream

Thanks. We should just be careful to refer to WGLC documents accurately,
just like we're careful not to characterize CG documents as if they'd been
adopted by a chartered WG.

On Thu, Dec 8, 2022 at 11:04 AM Tommy Pauly <tpauly@apple.com> wrote:

> Hi Jeffrey,
>
> They’re not RFCs yet, but as I mentioned, they’re “quite mature”, as in
> they’re already through most of the working group last call process. There
> likely won’t be any inter op-breaking changes at this point, and even if
> there are, they’ll be through the IETF process pretty soon, so that the W3C
> conversations can build on them.
>
> The architecture document has completed working group last call:
>
> https://datatracker.ietf.org/doc/draft-ietf-privacypass-architecture/
>
> And the auth scheme and protocol documents are in / completing working
> group last call:
>
> https://datatracker.ietf.org/doc/draft-ietf-privacypass-auth-scheme/
> https://datatracker.ietf.org/doc/draft-ietf-privacypass-protocol/
>
> Thanks,
> Tommy
>
>
> On Dec 8, 2022, at 11:00 AM, 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.
>
> Thanks,
> Jeffrey
>
>
>