From 918ede1d1e8d7d47e78ee4476db6386b4b026aee Mon Sep 17 00:00:00 2001 From: Tommy Pauly Date: Tue, 12 Sep 2023 09:08:21 -0700 Subject: [PATCH] Update draft-ietf-privacypass-auth-scheme.md Co-authored-by: Christopher Wood --- draft-ietf-privacypass-auth-scheme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-privacypass-auth-scheme.md b/draft-ietf-privacypass-auth-scheme.md index 99c53b41..15bfd976 100644 --- a/draft-ietf-privacypass-auth-scheme.md +++ b/draft-ietf-privacypass-auth-scheme.md @@ -217,7 +217,7 @@ that contain a hostname and optional port, where the port is implied to be "443" missing. The names use the format of the authority portion of a URI as defined in {{Section 3.2 of !URI=RFC3986}}. The names MUST NOT include a "userinfo" portion of an authority. For example, a server name used in one of these fields might be -"issuer.example.com" or "issuer.example.com:8443". +"issuer.example.com" or "issuer.example.com:8443", but not "issuer@example.com". When used in an authentication challenge, the "PrivateToken" scheme uses the following parameters: