Re: [Webtransport] Protocol work (was [hybi] WebTransport Mailing List)
Bernard Aboba <bernard.aboba@gmail.com> Tue, 30 July 2019 20:47 UTC
Return-Path: <bernard.aboba@gmail.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 ABA4F12004D for <webtransport@ietfa.amsl.com>; Tue, 30 Jul 2019 13:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.737
X-Spam-Level:
X-Spam-Status: No, score=-1.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=gmail.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 0s51RE-VZsu1 for <webtransport@ietfa.amsl.com>; Tue, 30 Jul 2019 13:47:09 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02664120108 for <webtransport@ietf.org>; Tue, 30 Jul 2019 13:47:09 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id m8so29801243lji.7 for <webtransport@ietf.org>; Tue, 30 Jul 2019 13:47:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=JV2etadZpzeKgmnG0+ZDeF3m/UpaN6rSDoI4KBSYJ9U=; b=JLevsi9fPFwEwvvkLqRH4LEAr/oRgv+13FXzm5dpiGeLpuHZGQflvcAZffdZ7+qCGv WJctwRLGHdkWPInidoRRMyClXxaTKSTbha+QUQGQZWWOTFGso/RUBYNi9EaXnc8D5n8H zZBvOOYOEzE3rbgwG+2xl9bhhWxy6OFoUBGcrxU23bUloVilpsrLQJiHakxsndiRWQRn 4YCiZ+5fs6K9swg2V7uZ4EY58rfqLY7sYSDMnhAQo8MsT29c64zhKS7HnF0zQlDDSIxv BTso1snTaxCSwe4kuyzX8r5SFULUBlL4J8RfkCFb50UZPEEEugJSroVNoCjMydrhHUgR 0P5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=JV2etadZpzeKgmnG0+ZDeF3m/UpaN6rSDoI4KBSYJ9U=; b=Ktu6l2Y1Q3nHvINm5iicITXed9EQuO4Rib2sFw1Ze3gsef8rsT/Ww4fo27BJ44APqY uUvp4R9tYcAiXnOKHzIpOskCeaZY46Y6dhmUaFLxFElpbiviudMrEvNPl7o1/D0L55xj 03tEZxShmgH9mESWP+WL0OYGqQrF2idglQ7KuKKf7+aYJxgy5E0+Uw/m4/6LwDyTHs/7 PEfkdlO/EJIEgGaohrbInVgGtN3URH8tJN3o5CIT3zXOkKC/gAfIMDFXg4WM7MspXEU6 VLDbUGUkodB1RyMm2wQzXvHMhtmoAOgougI0TC31v4/EgjyxQz5jHgNo4voafrTLvxjy adcw==
X-Gm-Message-State: APjAAAX6pxJA9cbwZl1vUu6iA/J9Ya5X/tOKliTqrHJua4tXIfejmFO5 XtVZiDmp/JnGH6myRN3jZF2GB/vT9JbsUr5cB+p8Gfoz
X-Google-Smtp-Source: APXvYqwtr51lTNRxty/nZ/iTyQJVgE/3pSc0LqySMrKpSRsLmOQtQzEbhuWlgcF9LwE2wFGWxwiyOB0UvVleL7zes8c=
X-Received: by 2002:a2e:4e12:: with SMTP id c18mr11922215ljb.211.1564519626337; Tue, 30 Jul 2019 13:47:06 -0700 (PDT)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 30 Jul 2019 13:46:54 -0700
Message-ID: <CAOW+2ds5PsBKqni3Vyz3rx1CGbQD60FzkH0n85XD72mAvHz1=A@mail.gmail.com>
To: webtransport@ietf.org
Content-Type: multipart/alternative; boundary="000000000000926ff0058eec1c56"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/GQVMY8S_adMC0wHTP1f2-_0UtDk>
Subject: Re: [Webtransport] Protocol work (was [hybi] WebTransport Mailing List)
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, 30 Jul 2019 20:47:12 -0000
Lennart said: "W3C WebTransport API is a *framework* for all sorts of transports delivering streams or datagrams that may or may not be reliable/ordered on top of a transport that may or may not be reliable/ordered. So IMO, this mailing list or the perhaps upcoming IETF WG should not be limited to unreliable transports either. For example, it's very well possible to reuse RFC 6455 (WebSocket) and create a WebTransport-based API for it." [BA] As I understand it, the W3C Web Incubation Community Group (WICG) is handling the WebTransport API (see: https://github.com/WICG/web-transport ), so that the focus of the IETF would be on *new protocol development*. From that perspective, the following protocol documents seem potentially relevant: https://tools.ietf.org/html/draft-kinnear-httpbis-http2-transport (HTTP/2 Transport) https://tools.ietf.org/html/draft-vvv-webtransport-http3 (HTTP/3 Transport) https://tools.ietf.org/html/draft-vvv-webtransport-overview https://tools.ietf.org/html/draft-vvv-webtransport-quic (QuicTransport) During the discussion in DISPATCH there were some comments suggesting focus on the HTTP/3 (and perhaps HTTP/2) protocol work. While that seems like a natural extension to RFCs 6445 and 8441, QuicTransport does reduce the roundtrips needed when it is known that the server (and intervening network) support QUIC.
- Re: [Webtransport] Protocol work (was [hybi] WebT… Bernard Aboba