From e66f64c7dc928d81ad10a5339ae79a1a2ae2d5f2 Mon Sep 17 00:00:00 2001 From: Eric Rescorla Date: Mon, 27 May 2024 07:56:07 -0700 Subject: [PATCH] Update draft-ietf-tls-esni.md Co-authored-by: Benjamin M. Schwartz --- draft-ietf-tls-esni.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/draft-ietf-tls-esni.md b/draft-ietf-tls-esni.md index 01ff7c9a..4e4b29da 100644 --- a/draft-ietf-tls-esni.md +++ b/draft-ietf-tls-esni.md @@ -931,7 +931,8 @@ connection. Otherwise, it might become possible for the client to have the wrong public name for the server, thus making recovery impossible. ECHConfigs learned from ECH rejection can be used as a tracking -vector. Clients SHOULD give them the same lifetime as other server-based +vector. Clients SHOULD impose the same lifetime and scope restrictions +that they apply to other server-based tracking vectors such as PSKs. In general, it is safest to try to retrieve a new ECHConfig unless