Re: [quicwg/base-drafts] Binding settings into session tickets (#2790)

Nick Harper <> Thu, 01 August 2019 21:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E0569120253 for <>; Thu, 1 Aug 2019 14:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, 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 vyCMfd7TXQ_7 for <>; Thu, 1 Aug 2019 14:32: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 1BC21120165 for <>; Thu, 1 Aug 2019 14:32:47 -0700 (PDT)
Date: Thu, 01 Aug 2019 14:32:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1564695166; bh=3fS/bX1Eg7S33L4STR8EMMsP4g9iJaZS1xekczDOVts=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Wjg1g5Z35v3W0ZfhMjJ94+Tfvz+HqaxhOp7Bpjl7gCaLmH2QJ1Ar8ahyZd+2bA6WY zxWwKD1YDvacLzsPxLNrm3yTHmvTh1zmoGuhiw/QffArm5udkORwABehrOU5maKI+q DA7g9a7TA97e8BowlgttTTxFHhhc5Fe9oc9OUfW4=
From: Nick Harper <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2790/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Binding settings into session tickets (#2790)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d435a7e60c3c_62763fa9212cd9683346b1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nharper
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, 01 Aug 2019 21:32:49 -0000

There are a few more options here:

* When sending SETTINGS, send all values, not just the ones changed from the previous connection (i.e. don't send a delta). Once the client receives that SETTINGS frame, both sides agree on that state for the rest of the connection, but they might not agree on the SETTINGS for early data (it could be the default settings, or it could be the SETTINGS from any previous connection).
* Use the default settings for early data. Both peers will always agree on the settings state and there aren't any ordering concerns between SETTINGS and NST. However, this prevents using anything that depends on SETTINGS in early data, e.g. QPACK or future extensions. (Unless QPACK or a future extension defines some way to remember a value for early data on the next connection.)

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