Re: [quicwg/base-drafts] Text on session resumption (#3566)

Mike Bishop <> Thu, 09 April 2020 18:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 625BC3A0C24 for <>; Thu, 9 Apr 2020 11:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.863
X-Spam-Status: No, score=-6.863 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8Q3b-ja3eJs1 for <>; Thu, 9 Apr 2020 11:58:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DACE33A0C23 for <>; Thu, 9 Apr 2020 11:58:46 -0700 (PDT)
Date: Thu, 09 Apr 2020 11:58:45 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1586458726; bh=jHX/wQsMB+fvlA93qIfs3dkj8hrAAb/stHLM+G621CM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=j0xPG1mfhmfMjK9T/cwTIr8HNQ4ikWJvlzyb5VGBvKS9dvu+u5VBgV3WaM9i73aL5 eePkbWB3NS5VQk37WRqOT6pvtI/6MhK8ALm8rAdEn8GEsVpuJd1L3jOBLWwG/3AC85 QGLmzdQt0T/sbQKyFPZ7KjBDJD13jfYFPl5fat5M=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3566/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Text on session resumption (#3566)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e8f7065ed5ac_2ddd3fd3b1ecd960152637"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Apr 2020 18:58:48 -0000

@MikeBishop approved this pull request.

> +Endpoints that use session resumption might need to remember some information
+about the current connection when creating a resumed connection. TLS requires
+that some information be retained; see Section 4.6.1 of {{!TLS13}}. QUIC itself
+does not depend on any state being retained when resuming a connection, unless
+0-RTT is also used; see {{enable-0rtt}} and Section 7.3.1 of
+{{QUIC-TRANSPORT}}. Application protocols could depend on state that is
+retained between resumed connections.
+Clients can store any state required for resumption along with the session
+ticket. Servers can use the session ticket to help carry state.
+Session resumption allows servers to link activity on the original connection
+with the resumed connection, which might be a privacy issue for clients.
+Clients can choose not to enable resumption to avoid creating this correlation.
+Client SHOULD NOT reuse tickets as that allows entities other than the server
+to correlate connection; see Section C.4 of {{!TLS13}}.

to correlate connections; see Section C.4 of {{!TLS13}}.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: