Re: [AVTCORE] Call for Adoption: Multiplexing Scheme Updates for QUIC

Martin Thomson <mt@lowentropy.net> Fri, 31 July 2020 04:49 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 073FD3A0D90 for <avt@ietfa.amsl.com>; Thu, 30 Jul 2020 21:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level:
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=Lv0eiW47; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QMlV/Up7
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 3WPLO4YWrFPR for <avt@ietfa.amsl.com>; Thu, 30 Jul 2020 21:49:08 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FAD33A0D81 for <avt@ietf.org>; Thu, 30 Jul 2020 21:49:08 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 681295C016A for <avt@ietf.org>; Fri, 31 Jul 2020 00:49:07 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Fri, 31 Jul 2020 00:49:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm2; bh=/1Kzk oFkzmHDtSSr/GJ+XtsitafK7eaOmLiEwykB68Q=; b=Lv0eiW47VMEgIpQB3aqjR 1aQ4Zxx0FV+p3MZNHL27oYo476QNQ0o6nE2GY+kqwmElmczW7vfs0a02Sz1L25sq xz/M3u6rQAiWwadDM4uSQsDlMPHnxVdJdO1yE8p7nwM8Qkyk2TkViNDUPT1cz5hR GI0Bsjkq9kOg6G5E/YE3le5WLXaCDyyHiUO4iBoxEi/zdU2NMsqsi511Tgu1HUzj WrmjkFAamFYiZ6yFkYH3yHsyqjhSGGoEifsQOxlS2Czv7guoK2ZAjntw9LKu2/tk k8HTQhn3k0q0cDv2mmyIQO+vqsiID3Dg7ynXpzoAYF2lEN8+cGwvXGKXtyRnjvL+ w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=/1KzkoFkzmHDtSSr/GJ+XtsitafK7eaOmLiEwykB6 8Q=; b=QMlV/Up77M/o/1zsM0+MWmE5mBYo1E8qTFlR3G0rpOHIBDqo8ugCTzvTc Yx4CBZIKOjYovlsFH8geOZCWtO6tLKuLrv8J8+cdpUbBX+5xW27VJcbYu/1lIhPl J38Ac6ShfuQ26thheM/eWUnQMO3Yl7iAq6JH2aEkhXh86doY2SC8RGjOKmQleAlj fmC5tNegcGKBlnpg3I0tNw35rJCjinrw7WP5//wEP2/CmupZNfph8RbPazIS9BZT eyXyKQyIW7mK+aNDzjmLbtOm5Ogp4iKlKJ54lwNXimpLbjIXQY1OQT6OMrGMNAIE CrLeN2MeegPLZNzd6zW2RAwaXjpSg==
X-ME-Sender: <xms:w6IjX81b769l1oAN2wYQ9Z0PSCMJF_Dgmk0dUjV70UAT35e8EESyjw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrieejgdekkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpefftefgvedvhfdtffehje dufefhhfevhedufefhgfelleetieefgeefgffgleehgfenucffohhmrghinhepihgvthhf rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:w6IjX3FgVqTz-E69c5uCB75bVLbCn3gZCO7dnDUG2R1rf4qern2PZQ> <xmx:w6IjX07u-HA6m8wZ28Hxlad1TpJhHCh9nKfTaoQIZZKo6SEpz4Js3Q> <xmx:w6IjX1334liiGNV57FmUtKFJ9oC8947uBbVJoxKjmp0gVoowDTzzFg> <xmx:w6IjX_GaBusiRE_J5heTaW6lriXXExNBR6ZgCdALlm9LK3lbH7GAfA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0C714E00CE; Fri, 31 Jul 2020 00:49:07 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-128-gd51a832-fm-20200728.001-gd51a8328
Mime-Version: 1.0
Message-Id: <9daf531b-a377-4473-9d09-0919ec39fcc1@www.fastmail.com>
In-Reply-To: <C9AA3682-17B8-43EC-BC22-58F37904AD23@8x8.com>
References: <C9AA3682-17B8-43EC-BC22-58F37904AD23@8x8.com>
Date: Fri, 31 Jul 2020 14:48:46 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: avt@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/i06QGgekGurl8lBgrBozrMrc_Mw>
Subject: Re: [AVTCORE] Call for Adoption: Multiplexing Scheme Updates for QUIC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2020 04:49:10 -0000

Hi Jonathan,

The draft makes some claims that are not clearly true about QUIC.  In particular:

   As noted in [I-D.aboba-avtcore-quic-multiplexing], the first octet of
   a QUIC short header packet falls in the range 64 to 127, thereby
   overlapping with the allocated range for TURN channels of 64 to 79.

It's important to distinguish between QUIC as defined in draft-ietf-quic-transport and QUIC as defined in draft-ietf-quic-invariants.  The draft is correct in that it cites the former and relies on properties of the former.  However, it is very easy to misinterpret this statement as applying more broadly.

To add spice to this, the claims here are invalid if you consider draft-thomson-quic-bit-grease, which allows long and short headers to take 128-255 and 0-127 respectively.

It would be most unfortunate if an IETF RFC were to so directly encourage protocol ossification.  This draft needs a more careful treatment of this problem.

Other than that fairly serious shortcoming, this is a worthwhile update that is worth doing.

p.s., I don't know if the approach suggested for TURN channels is appropriate, but I trust that AVTCore are competent to decide that.

On Fri, Jul 31, 2020, at 00:18, Jonathan Lennox wrote:
> (Note this mail is Cc’d to quic@ietf.org; please keep discussion on 
> avt@ietf.org.)
> 
> This is a call for adoption in the AVTCore working group of the 
> document “Multiplexing Scheme Updates for QUIC”, 
> https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00 , as the 
> basis for a working group item, along with an appropriate milestone.
> 
> As a summary for those unfamiliar with the document, it updates RFC 
> 7983 to document how QUIC can be demultiplexed from STUN, DTLS, RTP, 
> and other protocols common in WebRTC and WebRTC-like systems.
> 
> If you have opinions on whether this document should be adopted, please 
> respond to the AVTCore mailing list by Friday, August 14th.
> 
> Technical comments on the document itself are also always welcome, of course!
> 
> Thanks,
> 
> Jonathan Lennox
> AVTCore co-chair
>