From b58dda567f5cd5844ad8104efebc51f5cf6283b4 Mon Sep 17 00:00:00 2001 From: Christopher Wood Date: Thu, 21 Sep 2023 19:17:49 -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 d4293a5c..b640a388 100644 --- a/draft-ietf-privacypass-architecture.md +++ b/draft-ietf-privacypass-architecture.md @@ -1047,7 +1047,7 @@ of information that Issuers may learn about Clients otherwise. Since this metadata may be useful for practical deployments of Privacy Pass, Issuers must balance this against the reduction in Client privacy. -The number of permitted metadata values often depends on deployment specific +The number of permitted metadata values often depends on deployment-specific details. In general, limiting the amount of metadata permitted helps limit the extent to which metadata can uniquely identify individual Clients. Failure to bound the number of possible metadata values can therefore lead to reduction in