Re: [quicwg/base-drafts] Clarify HTTP/2 setting parameter reservation (#3955)
David Schinazi <notifications@github.com> Fri, 24 July 2020 18:58 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 4E3143A08FA for <quic-issues@ietfa.amsl.com>; Fri, 24 Jul 2020 11:58:50 -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 W26kBIjielLk for <quic-issues@ietfa.amsl.com>; Fri, 24 Jul 2020 11:58:49 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10A1B3A08F5 for <quic-issues@ietf.org>; Fri, 24 Jul 2020 11:58:48 -0700 (PDT)
Received: from github-lowworker-d93c4b6.va3-iad.github.net (github-lowworker-d93c4b6.va3-iad.github.net [10.48.17.47]) by smtp.github.com (Postfix) with ESMTP id C3A1CE1E15 for <quic-issues@ietf.org>; Fri, 24 Jul 2020 11:58:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595617127; bh=8HzhWPtO7XWNI5jA+Cj1tOY1dVgure4+yV6SUU+Iy3c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zoIj5j18tEbSpDwbm+JKpW1uNJCIHTI7oylHooMrQjWTPAsF6uW1f9Oc3IMj7DXye q7O5/1H3h7QuatAiWx7JYzCuImeS/qQno/J4CzmHKO6J9mqd7F35yeo+VznrJUzF66 MY8yi6fuK/rR7TxnVEurC15jqL63px/K1kVDCOeY=
Date: Fri, 24 Jul 2020 11:58:47 -0700
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7666P46XN2D2ZOBZ55E4IGPEVBNHHCPHGA74@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/review/455117253@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_5f1b2f67b2052_2ff63fd7ccacd968184130"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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/97Gw1ejHX2mUizzNN1_JYaTHbQw>
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: Fri, 24 Jul 2020 18:58:50 -0000
@DavidSchinazi commented on this pull request. > @@ -2316,20 +2320,26 @@ SETTINGS_HEADER_TABLE_SIZE: SETTINGS_ENABLE_PUSH: : This is removed in favor of the MAX_PUSH_ID which provides a more granular - control over server push. + control over server push. Specifying a setting with the identifier 0x2 A reference to the prohibition works for me, I just want to make sure we have text somewhere clearly stating that endpoints MUST NOT send those -- 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#discussion_r460233601
- [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