IETF Logo Mail Archive

Re: [Webtransport] Confirming Consensus on WebTransport protocols

Jana Iyengar <jri.ietf@gmail.com> Wed, 13 January 2021 19:24 UTC

Return-Path: <jri.ietf@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 432A83A1057 for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 11:24:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 dSTJbuSMhQBQ for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 11:24:47 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 5C3E83A104D for <webtransport@ietf.org>; Wed, 13 Jan 2021 11:24:47 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id b10so3828235ljp.6 for <webtransport@ietf.org>; Wed, 13 Jan 2021 11:24:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ApMbNEyOnUcMEJtdep6nVV7mmwYu4nbSDpvcM8Widno=; b=QLk3QGx1Hm5MrgbTd29g+36PEM1pF5+QhNtmO6nMuSyWyjyLFejSoc0tpzl5R8RcPj 9gjNRjPrLZm7RxZiOIYD7euTMed8INiOYJaLHDMMQ/T2g3yLy5G0tzgBBYH4pBgd1weS IfsjmFL9HX7xvTrOX9czW40nrbS8RnTgA39CqY79y85V85fWrgM1cEIwtDeDsZCmIVzK g8HZfGqxJqkR6L/a7agn1OZhhZFZ11o9Y29fg7DX7n+n6AYrhNmEz+tsbBPz+hpzIyJF q0fQmcFHH0DjNd9upzkdxZpmmC4JUdY08bvxoqyx7T2VaSi3RpMj8smhpy6T2bIIXJ1u Dm0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ApMbNEyOnUcMEJtdep6nVV7mmwYu4nbSDpvcM8Widno=; b=pg8DZxRXQXSzZyDkh6CsccG5Mp0+qYMGcPGmODBCjKdAEt/ghRMEHBiIxUc4J/CR4S DsATzbHxbc33goeWatHbNpNTDxn6FLM+xN0NRWOm2mRWJAs3ez/L9GrFeB48omnumgqF A8PdgSNey7ETFpST5hGwLS1KV7t5bVydeBqKpJFdosq8hHSfJiiTAWKaGD9XND7F7Ylr pxA3THLWURkjOdy9v09lDLyFnUQdAG7y0IcDNF51p4q9kS3uuksSVZa8BalXK/3evmwc OSnItiMS0fzE0iCFF/Au447jAY0BbIwqknzMUubSWTKrPO6vhZUtTsIit01eToNbfSoN Tn5g==
X-Gm-Message-State: AOAM532waG+oxKEzF+Sc9m2yyf4hwvBi6K/ah5mm4Fxe161NBHshramu UWhHj/1WP5wg/ApNWTo4DUsPcUbqskqrxN7TEcrqvL9Y
X-Google-Smtp-Source: ABdhPJyAdj12CEOoln9fa5VltxwQzMP60fVKwLZFkIgWEDNFr6NBvBK1TgVZJoLHKhbBpeBWEhL+uG8Z6tRGGNOK6O0=
X-Received: by 2002:a2e:6c03:: with SMTP id h3mr1596881ljc.360.1610565884833; Wed, 13 Jan 2021 11:24:44 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com> <C3FE8766-978C-413B-B4AC-F21DFE842F46@fb.com>
In-Reply-To: <C3FE8766-978C-413B-B4AC-F21DFE842F46@fb.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 13 Jan 2021 11:24:33 -0800
Message-ID: <CACpbDcfx0j5XDjvefgri=jBUum6vsjOBtKiGOrLz6x2PfJTV3g@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000073f45e05b8cd1774"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/nMw6YI5MwnLeQ2GxMG_1jc0SSZ4>
Subject: Re: [Webtransport] Confirming Consensus on WebTransport protocols
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: Wed, 13 Jan 2021 19:24:50 -0000

I support the consensus of 1A and 2A.

On Wed, Jan 13, 2021 at 9:16 AM Alan Frindell <afrind=
40fb.com@dmarc.ietf.org> wrote:

> > I'd like to call out that there are two things which could be referred
> to as 'pooling'.  One is using a single connection for HTTP/3 and
> WebTransport at the same time.  The other is support for multiple
> WebTransport sessions inside a single connection.
>
>
>
> Absolutely.  QuicTransport prevents even the possibility of pooling HTTP
> and WebTransport on the same connection, as is done with H2 and WebSockets.
>
>
>
> > This latter type of 'pooling' is part of what makes Http3Transport more
> complex than QuicTransport.  Was there ever an explicit question about
> whether multiple sessions on a single connection are necessary or even
> useful?
>
>
>
> We have use cases for pooling multiple sessions on the same connection
> which I described during IETF 109.  I don’t want to completely hijack this
> thread to discuss them, however.  I’d prefer to wait until we finish
> confirming consensus on questions 1 and 2 before diving deep into pooling.
>
>
>
> -Alan
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

v2.23.0 | Report a Bug | By Email