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

ianswett <notifications@github.com> Wed, 01 May 2019 13:48 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 9D146120128 for <quic-issues@ietfa.amsl.com>; Wed, 1 May 2019 06:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 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_28=1.404, 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 LDrQALpcelm4 for <quic-issues@ietfa.amsl.com>; Wed, 1 May 2019 06:48:35 -0700 (PDT)
Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3326912004B for <quic-issues@ietf.org>; Wed, 1 May 2019 06:48:35 -0700 (PDT)
Date: Wed, 01 May 2019 06:48:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1556718514; bh=iI2RO0P+up+pTwr85xlXn7Gefqgk7zQv5pQOFZqFh8g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NkqaG9LrGZgB4daKs3ed4YRVJZ6MAQ9O03gLfxTqLkzt7qL2xfCOOqfnfNrueZmPQ QkRDxcQiTh74OPE69Wp+9GnR9xmmMoVtE0mEqDuYiFGKCoyQhyU1Csra906FF6kXdQ vNFSzWXvxOU9+nyn3i6F9gRk7pg3FdDFOAtEi4y0=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2TXSVQ4JIN2M34FP5223LDFEVBNHHBULJJJA@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/488286777@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_5cc9a3b276586_66b03f8ecb8cd96495753"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/hG2qQH1M8rr37NARPoyn1vGOv98>
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 13:48:37 -0000

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'm happy with the current text, because I don't see a valid use case for sending the same SETTING twice.

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