[Webtransport] Http3Transport pooling/sharing
Bernard Aboba <bernard.aboba@gmail.com> Mon, 09 November 2020 18:32 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 BCF1E3A12B9 for <webtransport@ietfa.amsl.com>; Mon, 9 Nov 2020 10:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 vHvOnsY-XP1m for <webtransport@ietfa.amsl.com>; Mon, 9 Nov 2020 10:32:51 -0800 (PST)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 50FB03A12B8 for <webtransport@ietf.org>; Mon, 9 Nov 2020 10:32:51 -0800 (PST)
Received: by mail-lf1-x12c.google.com with SMTP id j205so6470449lfj.6 for <webtransport@ietf.org>; Mon, 09 Nov 2020 10:32:51 -0800 (PST)
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=90vq9jeEaso4rA/kh9k9WxJrynU8ccY0wxZv4ci++hk=; b=IlPBDufF+5DygJpUW1e2DWyPqNHVjEDzdXl10f26Gu3mU2wLajWYtus7LfUEp89QEV CtfWDgo2r9XJSt5MLLDypPca+rjp77JQrJ8NzVOuUbKTf0kWAAF/cE3IhuxBBKeEueMB HXUaIpj3Uc7RlJbGmiys0oeoXQOAGi0QcoNGZtxIoqry2FShAmoAGWLHfonvl3kS9xSv z4K3pAHNWck40vkx31peLQMvxiAjwYN2uTepjETyfHvoOE2UZTASYWQdaQXSEI0zJ9Iv NW+WYps2IWNgCmuxJkbIpkmM0Y6/tDbsOojtletc74GMvNRZrCdTW7iHi0hV4NVMiBBU OviA==
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=90vq9jeEaso4rA/kh9k9WxJrynU8ccY0wxZv4ci++hk=; b=ekoovcD2fM+5P9vUQNmxo9ecKJVL/3ofRzLn3t6zkXMMgRG+7ykYlCxjokt8CXeRIF qvImV7j1y8QCbnyWGmX6hynfiPyJarAQUEp19keLulINdSILAMobzbz/ZIqTNBVNrgjc MyYNvhE/vMy4ivVa5tnx+93mzkp1X3b84FztFlfySCMc8Ivkg1CQlTfOIwR/J9MKBREu gp9VTdcmDhkN7h+8fqvFSklHpw//VBoXbDx9AuUEQprreOSGsy7O+ihKsjl+SxVvPZ8o 7pLXEdz+1DsvwOEHCIyd/Tla3GGku7c+iPW0kEvtDRYXY0cHoRZalOVd8Pd7auXi5fmi bU0g==
X-Gm-Message-State: AOAM533AhmSBJpGgUHonsPhBAlPk+2bN96huhhaX10jl+dGtGIWm95aV OPvUl0ZUD28od+rDJ3PQKeRuIcnjnLJxu3Q9BQJvcI/v+tOThQ==
X-Google-Smtp-Source: ABdhPJzx8t300apWTpJ14Ycng+2+H4PxfYg9/9EojRZcuDFmnup7xU/TwX2gfmaHJnMEVebMA8Zr5/fctGo/OEEiBaw=
X-Received: by 2002:ac2:53ad:: with SMTP id j13mr3762577lfh.177.1604946769178; Mon, 09 Nov 2020 10:32:49 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 09 Nov 2020 10:32:38 -0800
Message-ID: <CAOW+2duHJTByX_E2jrQMuapKm=cxVwiZKUYWtpz-K-nw9SWQiw@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000f793e05b3b0caf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/wT-LsZUci-KU_QNTU90oYqllj0I>
Subject: [Webtransport] Http3Transport pooling/sharing
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: Mon, 09 Nov 2020 18:32:53 -0000
One of the use cases that has been described in the recent W3C WebTransport WG meeting was sharing of an HTTP/3 QUIC connection between HTTP/3 Request/Response and WebTransport. In looking into how this would work in practice, it appears that there are some complications. Http3Transport requires support for HTTP/3 Datagrams. draft-vvv-webtransport-http3 Section 4.1 says: "If "http3_transport_support" is negotiated, support for the QUIC DATAGRAM extension MUST be negotiated." What happens if there is an existing HTTP/3 connection to the same Origin but that connection did not negotiate support for QUIC DATAGRAMS?
- [Webtransport] Http3Transport pooling/sharing Bernard Aboba
- Re: [Webtransport] Http3Transport pooling/sharing Martin Thomson
- Re: [Webtransport] Http3Transport pooling/sharing Lucas Pardue
- Re: [Webtransport] Http3Transport pooling/sharing Bernard Aboba
- Re: [Webtransport] Http3Transport pooling/sharing Luke Curley