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

Lucas Pardue <> Thu, 02 May 2019 10:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8AA25120322 for <>; Thu, 2 May 2019 03:02:41 -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 nFRYATCO-eAH for <>; Thu, 2 May 2019 03:02:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 897D812009C for <>; Thu, 2 May 2019 03:02:37 -0700 (PDT)
Date: Thu, 02 May 2019 03:02:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556791356; bh=QGyA1mH/9dWR28N8CMcdVR6H7e/bzOgWtD7vQLQ/Hvg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iRAB7+1bpb1BN+Pnv4PRf0j0Iu8SOsrysCHR/3+Pvk3lWJEGrIFDRJ+rXIYHiEDjR Zt1IgN7WwBv74a+R6UerozIUmo4WSdTThQipoCLE5VkEVMgJkyk6hivFFhlfTX2yO/ +JQJJZwap1kdDpOk08OqvxnsakPOrRKu/Zr5H+Yo=
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_5ccac03c98b2f_467d3ff427ecd9605792de"; 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, 02 May 2019 10:02:41 -0000

That's a great summary @MikeBishop. The slight grey area for me is the current text:

> A receiver MAY treat the presence of the same parameter more than once as a connection error

This leaves handling up to the receiver with no defined behaviour (which is a fine paradigm). I.e. right now, if you send me duplicate parameters, I pick the last one observed and don't send connection error.

I have no preference for any change to receiver requirement.

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