IETF Logo Mail Archive

Re: [Webtransport] A comment on draft-kinnear-httpbis-http2-transport-02

Eric Kinnear <ekinnear@apple.com> Tue, 19 November 2019 10:31 UTC

Return-Path: <ekinnear@apple.com>
X-Original-To: webtransport@ietfa.amsl.com
Delivered-To: webtransport@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89A041200C7 for <webtransport@ietfa.amsl.com>; Tue, 19 Nov 2019 02:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 kqueqw8m0uVf for <webtransport@ietfa.amsl.com>; Tue, 19 Nov 2019 02:31:23 -0800 (PST)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E1D61208F6 for <webtransport@ietf.org>; Tue, 19 Nov 2019 02:31:23 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id xAJAROfR058837; Tue, 19 Nov 2019 02:31:15 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=/C/ptVBbzu4WJLVXw8Z0ZDyyeZfWJua/ec5nD2Z/hDs=; b=FLzq7FlYcU1/1tRb4rlz5fvyHch+Ypgi1m/XBQqGd8/LNw7Zq5nOHKAgS+dzqhzQ70Nn cuaU27HO7zxiRZRodPGT4jXyPOJjsRcBTZ8vsJrUXfckpa5sdKRJt0aJz5E4lc1gw/kr +VlEjYVd13nY6z5c6/4VJjpZHKeRNgKdA4cXl7j7mqcRPhs5A0GTt/otmAj8WUlZbIBR UFRnI69b2C5bP7mHUnUO/9wNf6rDd7VX6HkPEMIQ4yLLwAq+hySNa8tp9b747cQp9UGI YS1bUlt/WwjKayOXn1p4nP82XhAuwbdv3PohmNKKlIGC6TONTwWnQSOm7/mvLFX/tqn2 Pg==
Received: from sng-mtap-sz02.asia.apple.com (sng-mtap-sz02.asia.apple.com [17.84.80.84]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2waenwr6xg-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 19 Nov 2019 02:31:15 -0800
Received: from sng-mmpp-sz01.asia.apple.com (sng-mmpp-sz01.asia.apple.com [17.84.80.62]) by sng-mtap-sz02.asia.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0Q1700NGHP812V00@sng-mtap-sz02.asia.apple.com>; Tue, 19 Nov 2019 18:31:13 +0800 (+08)
Received: from process_milters-daemon.sng-mmpp-sz01.asia.apple.com by sng-mmpp-sz01.asia.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0Q1700700N5KCD00@sng-mmpp-sz01.asia.apple.com>; Tue, 19 Nov 2019 18:31:13 +0800 (+08)
X-Va-A:
X-Va-T-CD: 998a9864e8b92da9dad0a458e77c5f05
X-Va-E-CD: ec73a80d9bb32e8686f4a7d26871f899
X-Va-R-CD: b879d5d6a960c316f46e8ba8837b4386
X-Va-CD: 0
X-Va-ID: 549e459b-39d0-4488-a123-4435bc086a00
X-V-A:
X-V-T-CD: 998a9864e8b92da9dad0a458e77c5f05
X-V-E-CD: ec73a80d9bb32e8686f4a7d26871f899
X-V-R-CD: b879d5d6a960c316f46e8ba8837b4386
X-V-CD: 0
X-V-ID: 87bcac4b-6c00-485d-8ac8-d822877a7ceb
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-11-19_03:,, signatures=0
Received: from [17.235.145.241] (unknown [17.235.145.241]) by sng-mmpp-sz01.asia.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0Q1700C42P7XR860@sng-mmpp-sz01.asia.apple.com>; Tue, 19 Nov 2019 18:31:10 +0800 (+08)
Sender: ekinnear@apple.com
From: Eric Kinnear <ekinnear@apple.com>
Message-id: <C16AD68E-9A0C-4249-8BFF-A7DBD601DD69@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_0FA3D4A9-4E92-45F3-849B-1457EF7E6AED"
MIME-version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
Date: Tue, 19 Nov 2019 18:31:09 +0800
In-reply-to: <CAAZdMadWee99BsnNrAfYFfhwGCwCBka-7oFPeaY2yPAfWamNQw@mail.gmail.com>
Cc: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, "webtransport@ietf.org" <webtransport@ietf.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, Bernard Aboba <bernard.aboba@gmail.com>
To: Victor Vasiliev <vasilvv=40google.com@dmarc.ietf.org>
References: <CAOW+2dssuXQGnRTcq77Az_vQGDv0tm5cdd+TWPf0p_Q3mD9Dag@mail.gmail.com> <714de35c-15b0-9f01-ab36-ef62dfffe259@it.aoyama.ac.jp> <CAAZdMadWee99BsnNrAfYFfhwGCwCBka-7oFPeaY2yPAfWamNQw@mail.gmail.com>
X-Mailer: Apple Mail (2.3594.4.19)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-19_03:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/Qo3Z1wg1UIl1Vuqk0UkiszCEiPg>
Subject: Re: [Webtransport] A comment on draft-kinnear-httpbis-http2-transport-02
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <webtransport.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webtransport>, <mailto:webtransport-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webtransport/>
List-Post: <mailto:webtransport@ietf.org>
List-Help: <mailto:webtransport-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webtransport>, <mailto:webtransport-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2019 10:31:28 -0000

Agreed, I think these are somewhat separate concepts. I think draft-kinnear-httpbis-http2-transport is working towards extending HTTP/2 for bidirectional transport *beyond* WebSockets, if you’re intending to send WebSocket data on a stream, you’d use “websocket”, not “bytestream”, and you really probably should register another :protocol value to use for your protocol. The latest rev of the draft here indicates that if you’re going to use “bytestream” you must have negotiated what’s on the bytestream in a different manner. 

Lots more to unpack here, and always happy to chat, but that’s the short version of “bytestream” =/= “websocket”.

Thanks,
Eric


> On Nov 19, 2019, at 1:56 PM, Victor Vasiliev <vasilvv=40google.com@dmarc.ietf.org> wrote:
> 
> On Tue, Nov 19, 2019 at 12:54 PM Martin J.. Dürst <duerst@it.aoyama..ac.jp <mailto:duerst@it.aoyama.ac.jp>> wrote:
> The distinction between binary and text datagrams, and the limitation of 
> text datagrams to UTF-8, considerably simplifies the creation of 
> datagram-based protocols and increases interoperability.
> 
> I wonder why this wasn't included in the Webtransport draft, and hope 
> that it can be added.
> 
> Hello Martin,
> 
> WebTransport does not make any assumptions about the nature of the payload it transmits, that is to say, all of the payload is assumed to be binary.  That is consistent with the general way the similar recent API has handled this (e.g. streaming fetch), as well as the design of underlying protocols.  TextEncoderStream/TextDecoderStream can be used to easily transform one into the other.
> 
> I'm especially confused about this being related to the datagrams; almost all datagram protocols I've seen are binary-based, since ~1200 bytes is typically too small for text-based protocols.
> 
>   -- Victor.
> -- 
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport

v2.23.0 | Report a Bug | By Email