Re: [quicwg/base-drafts] Possible ambiguity for Handling Reserved HTTP/2 Settings parameters type values (#4809)
kaduk <notifications@github.com> Sat, 23 January 2021 00:00 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 9AEE03A1597 for <quic-issues@ietfa.amsl.com>; Fri, 22 Jan 2021 16:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.258
X-Spam-Level:
X-Spam-Status: No, score=-2.258 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, 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 cPymLw_CeOMK for <quic-issues@ietfa.amsl.com>; Fri, 22 Jan 2021 16:00:16 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7847B3A1596 for <quic-issues@ietf.org>; Fri, 22 Jan 2021 16:00:16 -0800 (PST)
Received: from github.com (hubbernetes-node-fad2290.ac4-iad.github.net [10.52.118.55]) by smtp.github.com (Postfix) with ESMTPA id A145B60059D for <quic-issues@ietf.org>; Fri, 22 Jan 2021 16:00:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611360015; bh=ZTOzTBB7x4gmVpBOQ/CvxcocU+831FmOkhc+ORFAEBQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XmArOJ1vwkZ+mjzbj6ngXrtBNrnzVr90llJpLDBAmNrUiMFkd/arNeBSCAWlLdM+b H1eYRzxBLcNuupyp9sjTvnmiaIM5meQVLOIbP6qpA2G8ngBx1WFXQaA+nrIrFYnOHU ugwxOz922H2rLMTCcEaRhZMWotXqmhY+dyPXgFJs=
Date: Fri, 22 Jan 2021 16:00:15 -0800
From: kaduk <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK76CH2YA4WZFRICWK56C5EA7EVBNHHC6NZT7I@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4809/765783312@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4809@github.com>
References: <quicwg/base-drafts/issues/4809@github.com>
Subject: Re: [quicwg/base-drafts] Possible ambiguity for Handling Reserved HTTP/2 Settings parameters type values (#4809)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_600b670f9e7d9_601a041765bc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kaduk
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/BwaOLStWXCSPXTQUgSI3gy-xrGw>
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: Sat, 23 Jan 2021 00:00:18 -0000
I wonder if we should ask IANA if they can tell how it came to be that 0x0 was marked as reserved with 7540 as the reference even though we are failing to see what part of 7540 should be effectuating that. -- 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/4809#issuecomment-765783312
- [quicwg/base-drafts] Possible ambiguity for Handl… Lucas Pardue
- Re: [quicwg/base-drafts] Possible ambiguity for H… Lucas Pardue
- Re: [quicwg/base-drafts] Possible ambiguity for H… Mike Bishop
- Re: [quicwg/base-drafts] Possible ambiguity for H… Lucas Pardue
- Re: [quicwg/base-drafts] Possible ambiguity for H… kaduk
- Re: [quicwg/base-drafts] Possible ambiguity for H… Mike Bishop