[Privacy-pass] Re: WG Last Call: draft-ietf-privacypass-batched-tokens-05 (Ends 2025-09-21)

[Ben Schwartz <[e-mail]>]

Thanks for the comment, Thibault!

Thibault is the only person who has commented on this Last Call.   This makes it difficult for the chairs to assess the working group's consensus on this draft.

If you have reviewed this draft, please comment on the list to indicate whether it is ready for publication.  If you haven't reviewed this draft, now would be a good time!

Thanks,
Ben Schwartz
________________________________
From: Thibault Meunier <[e-mail]>
Sent: Tuesday, September 16, 2025 10:02 AM
To: Joseph Salowey <[e-mail]>
Cc: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Subject: Re: [Privacy-pass] WG Last Call: draft-ietf-privacypass-batched-tokens-05 (Ends 2025-09-21)

Hi privacypass,

(Disclosure: I am an author of the draft.)

I support adoption of this draft. Implementations exist in Go [1], Rust [2], and TypeScript [3]. These are now interoperable, and test vectors have been generated [4] from the Go and Rust implementations.

To the best of my knowledge:

1. The generic token batch mechanism is implemented and deployed by Cloudflare.
2. The amortized tokens are in use at Kagi, and in deployment by Phoenix R&D.

[1] https://github.com/cloudflare/pat-go/
[2] https://github.com/raphaelrobert/privacypass
[3] https://github.com/cloudflare/privacypass-ts/
[4] https://github.com/raphaelrobert/privacypass/wiki/Interop

Best,
Thibault

On Sunday, September 7th, 2025 at 10:24 PM, Joseph Salowey via Datatracker <[e-mail]> wrote:

>
>
>
> Subject: WG Last Call: draft-ietf-privacypass-batched-tokens-05 (Ends
> 2025-09-21)
>
> This message starts a 2-week WG Last Call for this document.
>
> Abstract:
> This document specifies two variants of the Privacy Pass issuance
> protocol that allow for batched issuance of tokens. These allow
> clients to request more than one token at a time and for issuers to
> issue more than one token at a time.
>
> File can be retrieved from:
> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-privacypass-batched-tokens/__;!!Bt8RZUm9aw!_xmPZOpXyLkiRW6OdJh6CvzLPAummNdkLSqZNjFIRND8tdb9mkV1Z8IRSUusveu0Z9PvdKqcUAxtWHyv$
>
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping
> [e-mail] in copy. Objections should be motivated and suggestions
> to resolve them are highly appreciated.
>
> Authors, and WG participants in general, are reminded again of the
> Intellectual Property Rights (IPR) disclosure obligations described in BCP 79
> [1]. Appropriate IPR disclosures required for full conformance with the
> provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
> any. Sanctions available for application to violators of IETF IPR Policy can
> be found at [3].
>
> Thank you.
>
> [1] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!Bt8RZUm9aw!_xmPZOpXyLkiRW6OdJh6CvzLPAummNdkLSqZNjFIRND8tdb9mkV1Z8IRSUusveu0Z9PvdKqcUMyKDbuX$
> [2] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!Bt8RZUm9aw!_xmPZOpXyLkiRW6OdJh6CvzLPAummNdkLSqZNjFIRND8tdb9mkV1Z8IRSUusveu0Z9PvdKqcUKg1f8g6$
> [3] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!Bt8RZUm9aw!_xmPZOpXyLkiRW6OdJh6CvzLPAummNdkLSqZNjFIRND8tdb9mkV1Z8IRSUusveu0Z9PvdKqcUHHYx7YT$
>
>
>
> --
> Privacy-pass mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]