Re: [quicwg/base-drafts] http3: Are reserved and non-core frames allowed before SETTINGS? (#2693)
Mike Bishop <notifications@github.com> Mon, 13 May 2019 18:01 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 5464E1200B5 for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 11:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level:
X-Spam-Status: No, score=-6.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 q0JNCeda2L0g for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 11:01:09 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76535120021 for <quic-issues@ietf.org>; Mon, 13 May 2019 11:01:09 -0700 (PDT)
Date: Mon, 13 May 2019 11:01:08 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557770468; bh=HTEkuwmbeiCGKMqdRy9f5q3DaxRWJnqJFunmUC93hW4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tBqcDYhdsvJ15gYuieOUbZS+SpeoW/QfeK1Odb0hRV83Y6mSgBOIQMC1ht4Hd3p/y x9UqRYU71h9Hu5GCE7UBEr2lCanr7quS2Z7eCnlozoHPz+Rbih3obOpBmxIaxaHdK4 vCxn6YD8a+dEupxKLAIcVAusCl2r0aydkU/AcXvo=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5TSAXHGDFDVTD4O65243RWJEVBNHHBU2NSLQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2693/491924995@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2693@github.com>
References: <quicwg/base-drafts/issues/2693@github.com>
Subject: Re: [quicwg/base-drafts] http3: Are reserved and non-core frames allowed before SETTINGS? (#2693)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd9b0e4ad07a_4b853ff1890cd9644105df"; 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/F4yV0tXdbfnsheO990eUO2Fbqe8>
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: Mon, 13 May 2019 18:01:11 -0000
On receipt, reserved is irrelevant -- it's just an unknown frame type. The reservation is simply to permit senders to generate unknown frame types without accidental collision to a real extension the client might support. So the question is whether "ignoring" unknown frame types means pretending that they weren't even there, and therefore the subsequent frame might still be the first frame on the stream. I'm inclined to say no -- you take no action on a frame you don't recognize, but that doesn't mean that the next frame was the first frame. -- 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/2693#issuecomment-491924995
- [quicwg/base-drafts] http3: Are reserved frames a… Lucas Pardue
- Re: [quicwg/base-drafts] http3: Are reserved fram… Luca Niccolini
- Re: [quicwg/base-drafts] http3: Are reserved and … Lucas Pardue
- Re: [quicwg/base-drafts] http3: Are reserved and … Kazuho Oku
- Re: [quicwg/base-drafts] http3: Are reserved and … Lucas Pardue
- Re: [quicwg/base-drafts] http3: Are reserved and … Mike Bishop
- Re: [quicwg/base-drafts] http3: Are reserved and … Mike Bishop