IETF Logo Mail Archive

[quicwg/base-drafts] http3: Are reserved frames allowed before SETTINGS? (#2693)

Lucas Pardue <notifications@github.com> Sun, 12 May 2019 18:46 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 85A56120071 for <quic-issues@ietfa.amsl.com>; Sun, 12 May 2019 11:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Level:
X-Spam-Status: No, score=-6.464 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_20=1.546, 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 OuIUDSLyOsEG for <quic-issues@ietfa.amsl.com>; Sun, 12 May 2019 11:46:02 -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 DAA5A120020 for <quic-issues@ietf.org>; Sun, 12 May 2019 11:46:01 -0700 (PDT)
Date: Sun, 12 May 2019 11:46:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557686760; bh=p5ltsqb+0K/kPLxrp4++xVudg5nPDHQETSflDjQ/Ygs=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=jeZyouE9deFUHBKH9MlV3Z0Konf5zNLqKDxfsN/aogJOlenFcweqoHgSskkmAMCG9 TNxQeo4Gp2nUvakXwXuN/TJ62J73OGp3kvMOs/un/Gp3cWUDVXHF/ZbVtYmL3FOM3H aiRc30N/UZuUKkq4cYAt+FsOtSyknEFFw7aZc86Y=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7Y6CLHNHFWAXDAAL524WOGREVBNHHBU2NSLQ@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@github.com>
Subject: [quicwg/base-drafts] http3: Are reserved frames allowed before SETTINGS? (#2693)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd869e8a5b63_17453fb5daecd9643703c0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/cx0Nw5lgkWB9P778X78aGsKvMdw>
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: Sun, 12 May 2019 18:46:04 -0000

We've had a long standing requirement that

> A SETTINGS frame MUST be sent as the first frame of each control
   stream (see Section 3.2.1) by each peer

By the way I interpret this, I put a check in my implementation that doesn't permit any frame until SETTINGS is received. Am I interpreting things correctly?

It would be more consistent to allow reserved frame types to appear at any point on any stream that carries frames. However, I'm fine with this requirement as is but it means there is a little more effort needed to handle reserved frame types across streams. 

-- 
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

v2.23.0 | Report a Bug | By Email