Re: [quicwg/base-drafts] Send complete SETTINGS (#2972)

Lucas Pardue <> Fri, 16 August 2019 18:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 46A871200D5 for <>; Fri, 16 Aug 2019 11:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_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 EvZGImYmpJOU for <>; Fri, 16 Aug 2019 11:02:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 976241200CD for <>; Fri, 16 Aug 2019 11:02:37 -0700 (PDT)
Date: Fri, 16 Aug 2019 11:02:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1565978556; bh=mgKE6ftQfwl4gnCDX7PezSnvIURDwb4NNYugHZcMvsk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rFHCsFZMNH2eLLKV64s7+SkjPS3xoKkVM5K274Kxl62ETsqV9LwdidGVMQ6uWRZKv crh6FEfnB6h2uIW0Vc7dt0n8iLOc9g8OVY1zW1QPEB0+0UInTHjHL3cSR4rBzuIKpj yGqyZ9atktBFqdoa/BPDIYNYu5Bj0NAkWz3UL9uI=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2972/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Send complete SETTINGS (#2972)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d56efbce30f3_18553ff0aaccd96047065b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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: Fri, 16 Aug 2019 18:02:39 -0000

LPardue commented on this pull request.

>  server's SETTINGS frame has arrived.  This removes the need for a client to wait
 for the SETTINGS frame before sending requests.
 A server can remember the settings that it advertised, or store an
 integrity-protected copy of the values in the ticket and recover the information
 when accepting 0-RTT data. A server uses the HTTP/3 settings values in
-determining whether to accept 0-RTT data.
+determining whether to accept 0-RTT data.  If the server cannot recover the
+settings from a session being resumed, it MUST NOT accept 0-RTT data.

by my reading, the paragraph describes to methods: remember or recover. This new clause seems to imply if you can't recover, then remember is not allowed.

Is it more aligned with the intent to say that when a server chooses the recover method, and encodes the data in a ticket, and a client presents a ticket, then the server MUST recover the settings or else reject 0-RTT?

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