From 80e53ae89c516d27491834360387a76df9a0c33c Mon Sep 17 00:00:00 2001 From: Christopher Wood Date: Thu, 21 Sep 2023 11:33:57 -0400 Subject: [PATCH] Address Rob's architecture review --- 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 78f87b32..9b960531 100644 --- a/draft-ietf-privacypass-architecture.md +++ b/draft-ietf-privacypass-architecture.md @@ -313,7 +313,7 @@ are deployment specific. For example, in settings where Clients interact with Issuers through an Attester, Attesters and Issuers might use mutually authenticated TLS to authenticate one another. In settings where Clients do not communicate with Issuers through an Attester, the Attesters -might convey this trust via a digital signature over that Issuers can verify. +might convey this trust via a digital signature that Issuers can verify. Clients explicitly trust Attesters to perform attestation correctly and in a way that does not violate their privacy. In particular, this means that Attesters