From 8f3d7ab5f25d319542f6e23e1e5eb5d7270399a2 Mon Sep 17 00:00:00 2001 From: Christopher Wood Date: Thu, 21 Sep 2023 19:17:44 -0400 Subject: [PATCH] Update draft-ietf-privacypass-architecture.md Co-authored-by: Tommy Pauly --- draft-ietf-privacypass-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-privacypass-architecture.md b/draft-ietf-privacypass-architecture.md index b7660699..d4293a5c 100644 --- a/draft-ietf-privacypass-architecture.md +++ b/draft-ietf-privacypass-architecture.md @@ -1041,7 +1041,7 @@ the tracked Client it would set the bit to `1`, and `0` otherwise. Adding additional bits provides an exponential increase in tracking granularity similarly to introducing more Issuers (though with more potential targeting). -For this reason, deployments should take amount of metadata used by an Issuer +For this reason, deployments should take the amount of metadata used by an Issuer in creating redemption tokens must into account -- together with the bits of information that Issuers may learn about Clients otherwise. Since this metadata may be useful for practical deployments of Privacy Pass, Issuers