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

Lucas Pardue <> Wed, 01 May 2019 13:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 95BF01200CE for <>; Wed, 1 May 2019 06:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_HI=-5, 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 lZhwxphrTsYq for <>; Wed, 1 May 2019 06:58:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5D93612016B for <>; Wed, 1 May 2019 06:58:21 -0700 (PDT)
Date: Wed, 01 May 2019 06:58:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556719100; bh=Jbv80la6CtWXc3t6ipSjOdb17Ovl2ud4rG4G3PBHADY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pOrVQoD7dJj98HRLT6JWHaG3Aol0+gxXKtRT9LAGujiXEnVKYtuskguQsEO6oyd7A 5swrxrfwLE7HAD1/xWlYY8KUDaS3h6QHi8wU9uz2oeCz9iGB5NrVlX9LimAYrqtzK5 44Z+ySPFcpIXs7QpdLeV6eyHFEF5USxjOYhxe9wY=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2663/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Why is SETTINGS parameter duplication a connection error? (#2663)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cc9a5fc12db5_32213faf508cd9641309f0"; 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: Wed, 01 May 2019 13:58:24 -0000

> I'm happy with the current text, because I don't see a valid use case for sending the same SETTING twice.

aha right, so because it is only permitted to send one SETTINGS frame, HTTP/3 doesn't need the means to ever handle more than one instance of a parameter.

> The text is MUST NOT send and MAY treat as an error, so as @dtikhonov said, you don't have to keep extra state on the parsing side.

I can live with the MAY. Closing issue.

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