Re: [quicwg/base-drafts] Clarify HTTP/2 setting parameter reservation (#3955)
Mike Bishop <notifications@github.com> Tue, 28 July 2020 18:40 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 38C673A0B85 for <quic-issues@ietfa.amsl.com>; Tue, 28 Jul 2020 11:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 iHehcSQO9c37 for <quic-issues@ietfa.amsl.com>; Tue, 28 Jul 2020 11:40:21 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E54F53A0B40 for <quic-issues@ietf.org>; Tue, 28 Jul 2020 11:40:20 -0700 (PDT)
Received: from github-lowworker-cf59896.ash1-iad.github.net (github-lowworker-cf59896.ash1-iad.github.net [10.56.112.26]) by smtp.github.com (Postfix) with ESMTP id 2AE9F520F33 for <quic-issues@ietf.org>; Tue, 28 Jul 2020 11:40:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595961620; bh=gRQYX6IYLY6t/W3N2fxozsNfW3qJ9NXNy6nrCTgxS9Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u2RBoTxnH7zAOe8mTqiTLWnCf731ClFTP+JVRAPEGCLR0sSgU11n54aRv4xc8KYWf dTSkVpECaDeSsu1b+L3qYpwGw4skBR9arX2ww+KLc1dNKeWFTrSG2QMyM2pHnntZop 1P2Ka8nCN8WmbF9/XyvufHYKxGJwIeMfA1epwRqA=
Date: Tue, 28 Jul 2020 11:40:20 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7LAJZO6QMMTDC2VP55FRJBJEVBNHHCPHGA74@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3955/c665209707@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3955@github.com>
References: <quicwg/base-drafts/pull/3955@github.com>
Subject: Re: [quicwg/base-drafts] Clarify HTTP/2 setting parameter reservation (#3955)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f2071141c4c0_4bd716f849367"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/0NWeHltfz62iGI3bGgdrwHZ0AqI>
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, 28 Jul 2020 18:40:22 -0000
@LPardue points out that SETTINGS and frames are different, because of tunneling intermediaries. The intermediary need not check every received frame for validity if they're not processing the frames. SETTINGS, on the other hand, have to be checked because they're inherently hop-by-hop. While I'm not crazy about having SETTINGS and frames be different, there is at least a justification for it. -- 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/pull/3955#issuecomment-665209707
- [quicwg/base-drafts] Clarify HTTP/2 setting param… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… ianswett
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Bence Béky
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… David Schinazi
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… David Schinazi
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Martin Thomson
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… David Schinazi
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Jana Iyengar
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Martin Thomson
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Jana Iyengar
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… David Schinazi
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Jana Iyengar
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Martin Thomson
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Mike Bishop
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Kazuho Oku
- Re: [quicwg/base-drafts] Clarify HTTP/2 setting p… Jana Iyengar