Re: [quicwg/base-drafts] HTTP SETTINGS: why reuse codepoint 0x3? (#1847)

Dmitri Tikhonov <notifications@github.com> Tue, 09 October 2018 19:07 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 63DEE12D7F8 for <quic-issues@ietfa.amsl.com>; Tue, 9 Oct 2018 12:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 9N7G7hWSY9jG for <quic-issues@ietfa.amsl.com>; Tue, 9 Oct 2018 12:07:37 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ED98129BBF for <quic-issues@ietf.org>; Tue, 9 Oct 2018 12:07:37 -0700 (PDT)
Date: Tue, 09 Oct 2018 12:07:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1539112055; bh=syVpjzYmpk1mdw12k5n9dXVbT8kjy0Oc5m8vgN8+GbQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UD+MlH2rlxCqpr93KBhdI9Y6X56zgZHsNdwGU8Qosa+hoWDTbQE1eDMpr+1IHvx+h tW6+YVzj2RzNaul5OYD6HCl/NAhkA9iajO/Fsti9UmplJjAinrbuaIhYQQcX9mBIbS yF22wNyas7mW/cDCMIDWaH4RQCKTFCcuOgYCeqVY=
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6dcc08a8b9a7bf0045ae2c7d938f3b4f881fec9192cf0000000117d4be7792a169ce15f37541@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1847/428313332@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1847@github.com>
References: <quicwg/base-drafts/issues/1847@github.com>
Subject: Re: [quicwg/base-drafts] HTTP SETTINGS: why reuse codepoint 0x3? (#1847)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bbcfc77227bb_ee73fe59e6d45c01501a8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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/Y9YeOYMyzPuSnU4fx89WS04twWQ>
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: Tue, 09 Oct 2018 19:07:39 -0000

We explicitly forbid other HTTP settings because (presumably?) we want to catch bugs.  By reusing 0x3, we allow for a potential bug when one side uses HTTP2 semantics -- likely due to some code reuse -- instead of HQ.

There are two consistent choices: either use another value instead of 0x3, or renumber HQ settings and not care about forbidding HTTP2 setting values.

-- 
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/1847#issuecomment-428313332