Re: [quicwg/base-drafts] Why is SETTINGS parameter duplication a connection error? (#2663)

Mike Bishop <notifications@github.com> Wed, 01 May 2019 21:22 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 D0710120288 for <quic-issues@ietfa.amsl.com>; Wed, 1 May 2019 14:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 g6eLlp7OWmSl for <quic-issues@ietfa.amsl.com>; Wed, 1 May 2019 14:22:04 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 EC7D4120223 for <quic-issues@ietf.org>; Wed, 1 May 2019 14:22:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=F0uYN49KAYNEhjwAzpJa4FhElFU=; b=t9qQqI08irnNYgwR 5h7nyi8XAJOUzCS2UcRl6imbqGrheNawdBLk1v7+GawlnNbxk8H0tKx25Mb/jeN+ pShEzJ+OTG3XSXsjdHp16xuDiSkx081AV6Ml9yoKrNwUeR1rnHXx6JE68cUFt69r ykUYDgdxlWXPGsmkKy+OWRQe8k8=
Received: by filter0478p1iad2.sendgrid.net with SMTP id filter0478p1iad2-18364-5CCA0DFA-1B 2019-05-01 21:22:02.964493984 +0000 UTC m=+518728.634121458
Received: from github-lowworker-6313c1a.cp1-iad.github.net (unknown [140.82.115.2]) by ismtpd0001p1iad2.sendgrid.net (SG) with ESMTP id AbgrIybuSJiPxKMyHmQxyw for <quic-issues@ietf.org>; Wed, 01 May 2019 21:22:03.025 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-6313c1a.cp1-iad.github.net (Postfix) with ESMTP id D6990380073 for <quic-issues@ietf.org>; Wed, 1 May 2019 14:22:02 -0700 (PDT)
Date: Wed, 01 May 2019 21:22:02 +0000 (UTC)
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6BSLNCHGMMVCYKIIN225AHVEVBNHHBULJJJA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2663/488434554@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2663@github.com>
References: <quicwg/base-drafts/issues/2663@github.com>
Subject: Re: [quicwg/base-drafts] Why is SETTINGS parameter duplication a connection error? (#2663)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cca0dfad4e3b_5cf83fce080cd9681152b"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3q1UKaReC8LgpR/5tpiDGd6dSghpWXR3b7fS XEpuu4QSewf34ElOnT4/m5msxZpulhk4imPl+ToJ9W41BOQ8oYqt2Tc7Y6q86/D2xlM4+HNU+47mQu JLgAT0MXY1lj8TX/FX+pPajCb5eGTWvP5U4Qvc2gMACZ7mFFPL+RnBFdDeJnccLHNPGir6wa9E1MzW Y=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/KItttKD1QlV98WnIQ6rGjbLiH0E>
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: Wed, 01 May 2019 21:22:13 -0000

In HTTP/2, when SETTINGS can arrive at any time and update anything, the value of a particular setting evolves over time.  You have to be able to handle a setting wandering over the course of a connection, and so having it happen over the course of frame processing isn't actually any different.

In HTTP/3, settings have an initial value before SETTINGS is received, then they get a value once and it's permanent.  You can either mandate that senders construct a "proper" frame, or specify how receivers squash an improper frame; the end result has to be the same, that a setting gets a value once and can't change thereafter.

-- 
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/2663#issuecomment-488434554