Subject: [Privacy-pass] Fwd: New Version Notification for draft-privacypass-rate-limit-tokens-01.txt

From: Tommy Pauly <[email-masked]>
Date: Wed, 06 Apr 2022 09:13:45 -0700

Hello Privacy Pass,

We’ve published a revision of the rate-limited tokens issuance protocol. Notably, this version:

- Aligns with the latest revision of the auth scheme (origin info handling)
- Explains requirements to avoid allowing the attester to fingerprint origins (each issuer needs many origins, without unique rate-limits)
- Expands discussion of what compromised issuers and attesters could do
- Adds test vectors

Please take a look! Chairs, we’d also like to request an adoption call for this work.

Best,
Tommy (on behalf of the authors)

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-privacypass-rate-limit-tokens-01.txt
> Date: April 5, 2022 at 3:36:42 PM PDT
> To: "Christopher A. Wood" <[email-masked]>, Christopher Wood <[email-masked]>, Jana Iyengar <[email-masked]>, Scott Hendrickson <[email-masked]>, Steven Valdez <[email-masked]>, Tommy Pauly <[email-masked]>
> 
> 
> A new version of I-D, draft-privacypass-rate-limit-tokens-01.txt
> has been successfully submitted by Tommy Pauly and posted to the
> IETF repository.
> 
> Name:		draft-privacypass-rate-limit-tokens
> Revision:	01
> Title:		Rate-Limited Token Issuance Protocol
> Document date:	2022-04-05
> Group:		Individual Submission
> Pages:		37
> URL:            https://www.ietf.org/archive/id/draft-privacypass-rate-limit-tokens-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-privacypass-rate-limit-tokens/
> Html:           https://www.ietf.org/archive/id/draft-privacypass-rate-limit-tokens-01.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-privacypass-rate-limit-tokens
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-privacypass-rate-limit-tokens-01
> 
> Abstract:
>   This document specifies a variant of the Privacy Pass issuance
>   protocol that allows for tokens to be rate-limited on a per-origin
>   basis.  This enables origins to use tokens for use cases that need to
>   restrict access from anonymous clients.
> 
> Discussion Venues
> 
>   This note is to be removed before publishing as an RFC.
> 
>   Source for this draft and an issue tracker can be found at
>   https://github.com/tfpauly/privacy-proxy.
> 
> 
> 
> 
> The IETF Secretariat
> 
>