Re: [quicwg/base-drafts] Why is SETTINGS parameter duplication a connection error? (#2663)
Lucas Pardue <notifications@github.com> Thu, 02 May 2019 10:02 UTC
Return-Path: <noreply@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 8AA25120322 for <quic-issues@ietfa.amsl.com>; Thu, 2 May 2019 03:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
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: 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 nFRYATCO-eAH for <quic-issues@ietfa.amsl.com>; Thu, 2 May 2019 03:02:37 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 897D812009C for <quic-issues@ietf.org>; 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; d=github.com; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2BJYIKMDEZ5HLOAFN227ZLZEVBNHHBULJJJA@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/488617998@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_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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Wpyls0XFAQT3PrQtaqJb2Io0KVE>
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, 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: https://github.com/quicwg/base-drafts/issues/2663#issuecomment-488617998
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Mike Bishop
- [quicwg/base-drafts] Why is SETTINGS parameter du… Lucas Pardue
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… ianswett
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Lucas Pardue
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Lucas Pardue
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Lucas Pardue
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Mike Bishop
- Re: [quicwg/base-drafts] Why is SETTINGS paramete… Martin Thomson