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

Mike Bishop <> Tue, 27 August 2019 18:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B805E1208AC for <>; Tue, 27 Aug 2019 11:40:49 -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 D_5LI-YGwohq for <>; Tue, 27 Aug 2019 11:40: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 0DF6312088E for <>; Tue, 27 Aug 2019 11:40:47 -0700 (PDT)
Date: Tue, 27 Aug 2019 11:40:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1566931246; bh=imH/GXKh+EtYTzKLj4wvep84zpZz2POoLuNvb19Zqko=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WIQ21LkW1uDY11Dnt7As0H/BmivzYSrH4vMdTv5GdEc8nQJK+6mS6ZxNSaGSWHFY5 Sho8rmk1w0IOpHwYQm9e1kt8hPNGy8opawdYdcQ8+XDfvx2Tsu4PSzA+jEwcamOk7j t6Rg6lBMnL2plg9xXeDzQJ1MXfKoK8mfvsrabAkA=
From: Mike Bishop <>
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_5d65792e48de5_10a03ffb646cd960801e8"; 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: Tue, 27 Aug 2019 18:40:59 -0000

MikeBishop commented on this pull request.

 A server MAY accept 0-RTT and subsequently provide different settings in its
 SETTINGS frame. If 0-RTT data is accepted by the server, its SETTINGS frame MUST
 NOT reduce any limits or alter any values that might be violated by the client
-with its 0-RTT data.  The server MAY omit settings from its SETTINGS frame which
-are unchanged from the initial value.
+with its 0-RTT data.  The server MUST include all settings which differ from
+their default values.  If a server accepts 0-RTT, but then sends a SETTINGS
+frame which reduces a setting the client understands or omits a value that was
+previously specified to have a non-default value, this MUST be treated as a
+connection error of type HTTP_SETTINGS_ERROR.

Honestly, that description looks a little overlong and overspecific anyway.  How about I just drop the examples and leave it as "An endpoint detected an error in the payload of a SETTINGS frame."?

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