Re: [quicwg/base-drafts] Does a client need to remember SETTINGS it doesn't understand when doing 0-RTT resumption? (#3110)

Lucas Pardue <> Thu, 17 October 2019 17:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3143F120B39 for <>; Thu, 17 Oct 2019 10:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 S-HIAXy1b6GK for <>; Thu, 17 Oct 2019 10:12:31 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5A59F120B2C for <>; Thu, 17 Oct 2019 10:12:31 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 989086E14D9 for <>; Thu, 17 Oct 2019 10:12:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571332350; bh=q6oAIcvWXUzPifHX0aWW1uKLz1kZdxi5J3plHSxBKeo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z6UOSaWxlVbENNfXbYnWBf9RUOyeYOwsm5fXibM+GaDmOaPVqD+YO20WyWrOPK9Hb QgSI7x3RHbF1JGcWEePcVU4kcuB50OxmsRphfGF4EnjWP6nzW8aAQyUmUPXsCpTYxg ddDd57tj1Th1MZRjHOcyg0jCeNRoJmHmH0NJlzXg=
Date: Thu, 17 Oct 2019 10:12:30 -0700
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3110/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Does a client need to remember SETTINGS it doesn't understand when doing 0-RTT resumption? (#3110)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da8a0fe8a436_61c43fd487acd9601789f0"; 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: Thu, 17 Oct 2019 17:12:33 -0000

I think this could affect reserved settings (aka grease) too, just in a slightly different way. Some editorial tweak to address the problem would be good.

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