Re: [TLS] ECH and resumption - what to put in SNI?

Ben Schwartz <> Fri, 25 June 2021 14:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AB8F53A1A98 for <>; Fri, 25 Jun 2021 07:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mku8PxH7M4w4 for <>; Fri, 25 Jun 2021 07:37:09 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 24F3E3A1A96 for <>; Fri, 25 Jun 2021 07:37:09 -0700 (PDT)
Received: by with SMTP id k30-20020a05600c1c9eb02901d4d33c5ca0so563730wms.3 for <>; Fri, 25 Jun 2021 07:37:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B4xyCiirE6GdBF7aBv+MkEhCWKyOWtnAZpTH/qTq8y0=; b=ZoEX57CjjfN2trycOO4t67H8Y7axBlkqNQPHkL6lvrx2FiPh1GIZYa2HURo8omLgho jiGNcf17vAbg++MqXPOjYLqon9mpii4PgBETtFT2vKtyxYfa5j1dl9NVvtPWy2Qaa3Sa 38hCq/lIN1/gNrfoeEapQu4S44fXEfsiERZFFtCThegVzxbj8yjlIBuCvm0Hli7QgB2h QWdAmNBofzfMGJvuQUczyPBPmIlFRQJDmIe/AZBLpNWUx1KwyMdyqCfKvh/0k6KmPBPR qC9bF8nVVs5OPu1+1fKxOsmKObwO6oaXcl9scf13OXKNI1IKPNo0akJPdFQH8JE4uHC9 upCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B4xyCiirE6GdBF7aBv+MkEhCWKyOWtnAZpTH/qTq8y0=; b=SwnW+K6K3sEeKuais/9sCqvo16OTWlJ9MIcfmx1MoIZR9Xajv1jG0++mUDDPzBymZ8 wdC4Kkwz0MKm0vfWBTyplfKyLIjItV5vPMb660emMsSpF04M8VKKKp/qrkuFrZtxy3Ib RJHewAvepYek3NHR/m/ixXKiJM0f1LlVcqUijsYMlIPm4AjHrgBggIbXKZ8M4FfhpyHe EpZeAQy2CxVxssErFo9vUfaXeJRUxPDUrq2WdRwqozyMieBlr1VGiQWT6oHG24SpqY6i gXteBpkGWrc0IVl0rgcUHwY+U35t1NTE25Hf0pG9lLp2SpLpgp7P1c4BvIRbyYNnVcsw LYKA==
X-Gm-Message-State: AOAM531b8RUkCTnZdhjfClzdvcXR8ckL5NmVvZNws1DzBNV1ButiZh2z t6XIvTH4lczU0Mabr5t4YOuyDljT5lPvisWkanpQMw==
X-Google-Smtp-Source: ABdhPJy76axXsIX80X84NWGnVBMmUsX/cOgq3WZd9ftbq11D4pZeFwcx5TnjEcvlpBESfodnCLYX3adwwQ31jDSWeeA=
X-Received: by 2002:a7b:c5d2:: with SMTP id n18mr11069212wmk.97.1624631826639; Fri, 25 Jun 2021 07:37:06 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Ben Schwartz <>
Date: Fri, 25 Jun 2021 10:36:54 -0400
Message-ID: <>
To: Stephen Farrell <>
Cc: "" <>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="000000000000f0f26305c598127e"
Archived-At: <>
Subject: Re: [TLS] ECH and resumption - what to put in SNI?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 25 Jun 2021 14:37:14 -0000

On Fri, Jun 25, 2021 at 10:21 AM Stephen Farrell <>

> Hiya,
> If a client established a session to
> using ECH with a public_name of, what ought
> the client put in the SNI when resuming?

> I guess the client could do ECH again

That's my expectation.


> might cause interesting failures for a library
> client that can't do fresh DNS queries from within the
> library (and might never see the TTL of the HTTPS/SVCB
> RR in any case).

I expect the application would pass an ECHConfigList to the TLS library
with each new connection request, and new requests might be resumed from a
ticket cache.  The TLS library doesn't need to know anything about the TTL,
because the ECHConfigList is single-use, and independent from whether the
resumption cache was used.