From 0402c071f0420c88a888e5e4516d23e4a8aac24e Mon Sep 17 00:00:00 2001 From: Eric Rescorla Date: Sat, 27 Jul 2024 15:13:13 -0700 Subject: [PATCH] Update draft-ietf-tls-esni.md Co-authored-by: Benjamin M. Schwartz --- draft-ietf-tls-esni.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-tls-esni.md b/draft-ietf-tls-esni.md index b1f33788..4fee21a6 100644 --- a/draft-ietf-tls-esni.md +++ b/draft-ietf-tls-esni.md @@ -940,7 +940,7 @@ used to bootstrap the connection, such as a DNS SVCB ServiceMode record {{ECH-IN-DNS}}. Clients MUST limit any sharing of persisted ECH-related state to connections that use the same ECHConfig source. Otherwise, it might become possible for the client to have the wrong public name for -the server, thus making recovery impossible. +the server, making recovery impossible. ECHConfigs learned from ECH rejection can be used as a tracking vector. Clients SHOULD impose the same lifetime and scope restrictions