Re: [quicwg/base-drafts] HTTP/3 settings frames and prioritization (#2772)

"Tom D." <> Fri, 07 June 2019 19:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 44FD4120161 for <>; Fri, 7 Jun 2019 12:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.02
X-Spam-Status: No, score=-7.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, RCVD_IN_MSPIKE_H2=-0.415, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 xhHZV76u3fjN for <>; Fri, 7 Jun 2019 12:15:24 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 34B03120018 for <>; Fri, 7 Jun 2019 12:15:24 -0700 (PDT)
Date: Fri, 07 Jun 2019 12:15:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1559934922; bh=NN823/2f9j8O/h+th3t76BbU1lN/wrDQpKeobTjs07E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TekCxZBl6E8Pnu67sPhUH252Lb4QbsvcMm7+LcN8Yj3Y+rLqbgWJ5n4iYbpWCWWH6 lUUTBs7Sj1VA+eeoFgsiJIOxwe47ZNjBwH2Qbm/9XPkBNsx+kGmFr6d4UXw5JpL23g tLKT81+oqCtDUJ/mwDPYawWhVgSfCL/3ITC+yae4=
From: "Tom D." <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2772/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP/3 settings frames and prioritization (#2772)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cfab7cad37b3_1f353ff2af0cd9601149be"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: tomdedecker
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, 07 Jun 2019 19:15:27 -0000

In my opinion, adding something like you just said to the specifications would be perfect. Given that section already mentions default settings values, it might not be bad to just expand it there. For example:

For clients using a 1-RTT QUIC connection, the initial value of each server setting is the default value. When a 0-RTT QUIC connection is being used, the initial value of each server setting is the value used in the previous session. 
Clients MUST store the settings the server provided in the session being resumed and MUST comply with stored settings until the current server settings are received.

could be appended with something along the lines of:

These values can be used by a client in a situation where it wants to send requests before the server's settings frame has arrived. 
This removes the need for a client to block and wait before sending its first request.

I think the most important part here is being a little more verbose about the edge case instead of just implying its existence by mentioning the default values for settings. 
If anyone has any other thoughts about it I'd love to hear them.

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