IETF Logo Mail Archive

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

Nick Harper <notifications@github.com> Thu, 17 October 2019 16:49 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0483F120AD2 for <quic-issues@ietfa.amsl.com>; Thu, 17 Oct 2019 09:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.454
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YjmZgSZCJv34 for <quic-issues@ietfa.amsl.com>; Thu, 17 Oct 2019 09:49:15 -0700 (PDT)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C87B6120ADA for <quic-issues@ietf.org>; Thu, 17 Oct 2019 09:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=7sic+fzhJy9Sba/AmsF69qFlugg=; b=JiRe4d3E1kGhUt1p f24+d3qYP+3LQjo/DK9VkLdJ6Twf15Gee8lQTsKd79g8iCXp6qLImylHLNNoNbgM CG5xtMIWA2mfJkcJdsYojdNimf9KYbIstefrInAxt9FOEWXCWiGCr8gdNrENYpXx AZWbxskQ5kvSUVOrbzOSsu0OCk8=
Received: by filter0127p1iad2.sendgrid.net with SMTP id filter0127p1iad2-22855-5DA89B88-34 2019-10-17 16:49:12.837359778 +0000 UTC m=+2122.773055138
Received: from github-lowworker-39b4a70.va3-iad.github.net (unknown [140.82.115.11]) by ismtpd0024p1mdw1.sendgrid.net (SG) with ESMTP id WlW6uyKsR-ifT2OQnQzCKQ for <quic-issues@ietf.org>; Thu, 17 Oct 2019 16:49:12.693 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-39b4a70.va3-iad.github.net (Postfix) with ESMTP id 721F77C008C for <quic-issues@ietf.org>; Thu, 17 Oct 2019 09:49:12 -0700 (PDT)
Date: Thu, 17 Oct 2019 16:49:12 +0000
From: Nick Harper <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK75UFXOO2DTAJFP4ZF3WXOBREVBNHHB4UEZZA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3110@github.com>
Subject: [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_5da89b8870a70_68a53fc5e7acd9642868f6"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0Cek/SexcWeUKnni/6NE/9RsByxtyPg3O8CC +PyIQ5nVNyB3NKIVkTWqdw/XYUGz4vVoaAvCM//2ck52YYsPxU+kvGUK/0ziXacSrrCRHHPeq0WC/z IlyXfeJzBG1u/zycXbBNQC1st8HY0wDiAhfCNBHjkCczDv7LqDHkVU1DI9XOos/aiQ3uI3dfJCDXWt 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/CpBu_4QGjMRclN4S6RMXf_qY83k>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2019 16:49:23 -0000

The HTTP draft currently specifies

>  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.

Is it intentional that a client MUST remember SETTINGS values that it doesn't support (to check that the server didn't omit a setting)?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3110

v2.23.0 | Report a Bug | By Email