IETF Logo Mail Archive

Re: [quicwg/base-drafts] Consider making h3 frame types varint (#2253)

Kazuho Oku <notifications@github.com> Mon, 31 December 2018 02: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 2E3CA12008A for <quic-issues@ietfa.amsl.com>; Sun, 30 Dec 2018 18:00:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 DDN9nyDwQeuB for <quic-issues@ietfa.amsl.com>; Sun, 30 Dec 2018 18:00:05 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A16E9127598 for <quic-issues@ietf.org>; Sun, 30 Dec 2018 18:00:05 -0800 (PST)
Date: Sun, 30 Dec 2018 18:00:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546221604; bh=Xbj6ZQaoIA9ndK4tPO34ewDpSMmqlitk8yn9ObpbIM0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PLcRc072HQ2l63XF4d2vieLgUj8R39WRIpvmob5eR+HCLHoXH8hEaIUZLwe+Bzk4e yRO9cMjFU9ktS06AfvJp5XV4gYslBo4ihR+nxlpAdjleXf68qJEFL/F7+sGjaIkPxw LHJVzautPgmH24bme3KiNmQZpqHMTSniCIWTl4kw=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abddb9668a9d0ece0330c3f04f6ef236c8ac2f0a4b92cf0000000118413a2492a169ce17792cde@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2253/450600968@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2253@github.com>
References: <quicwg/base-drafts/issues/2253@github.com>
Subject: Re: [quicwg/base-drafts] Consider making h3 frame types varint (#2253)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c297824ba740_4dcc3fa3326d45c415123c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/T1vD1O90dneylLg9txl7NhOsUZA>
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, 31 Dec 2018 02:00:08 -0000

@martinthomson While I agree to the fact that it is impossible with the 8-bit design to send new frame types in 0-RTT, I am not sure if I am convinced with the argument that it represents the necessity to use varint frame types.

Consider the 0-RTT context-free push case. We not only need to have new frame types but change the semantics of push. The request headers of a context-push cannot be sent in a way that a client that do not understand the extension can ignore.

Therefore, to me it seems that anything to be sent from the server in 0-RTT needs to have a different unidirectional stream type. Therefore I think #2275 is the way to go, but that having varint frames types is not.

-- 
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/2253#issuecomment-450600968

v2.23.0 | Report a Bug | By Email