Re: [Webtransport] Magnus Westerlund's Block on charter-ietf-webtrans-00-00: (with BLOCK and COMMENT)

Mirja Kuehlewind <ietf@kuehlewind.net> Mon, 03 February 2020 10:52 UTC

Return-Path: <ietf@kuehlewind.net>
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 B9CD412009E; Mon, 3 Feb 2020 02:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 eym6NwziNvyU; Mon, 3 Feb 2020 02:52:54 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 846CF120096; Mon, 3 Feb 2020 02:52:54 -0800 (PST)
Received: from [2a00:79e1:abc:301:58f1:e777:f42a:c01e]; authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1iyZLY-00068B-OS; Mon, 03 Feb 2020 11:52:52 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <CABcZeBP5QN3OjMS+x4vkHnBc42=DhTunX+6GhCvEWjqGdmPc_Q@mail.gmail.com>
Date: Mon, 03 Feb 2020 11:52:52 +0100
Cc: Martin Thomson <mt@lowentropy.net>, webtrans-chairs@ietf.org, Magnus Westerlund <magnus.westerlund@ericsson.com>, webtransport@ietf.org, Bernard Aboba <bernard.aboba@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF92F26A-9913-49CA-A3DF-39C8515D6846@kuehlewind.net>
References: <158048874973.21096.7146214036477975185.idtracker@ietfa.amsl.com> <D48C1258-E534-43A8-8BD1-73F7AE99D9B2@gmail.com> <fabe0d9c-6278-43e9-a401-bef30804107b@www.fastmail.com> <CABcZeBOQ4Uv+c_zmPKv7+st-at=uTE3UukfU05p_rFQs5iCh3Q@mail.gmail.com> <CAF9D01C-A167-4B6E-BBAD-969B3878FA30@kuehlewind.net> <CABcZeBP5QN3OjMS+x4vkHnBc42=DhTunX+6GhCvEWjqGdmPc_Q@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1580727174;e27da53b;
X-HE-SMSGID: 1iyZLY-00068B-OS
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/41AnkZpiNjvFkemA6YsWdPuIQ64>
Subject: Re: [Webtransport] Magnus Westerlund's Block on charter-ietf-webtrans-00-00: (with BLOCK and COMMENT)
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, 03 Feb 2020 10:52:57 -0000

Yes, totally understood that you don’t want to put any specific protocol suggestions in the charter but right now it seem a bit too loose (from a transport point of view). So if you don’t want what is proposed currently, do you have another proposal? 

If you are working on a draft yourself, I think it would actually be nice to have a first version of this draft out before the groups is fully started to people discussion the charter right now, would actually better understand what the discussion is about.

Mirja



> On 3. Feb 2020, at 11:44, Eric Rescorla <ekr@rtfm.com> wrote:
> 
> Well, I certainly don't think we should build a new version of QUIC, and it seems likely that QUIC will be involved somehow, but Victor had some quite specific protocol suggestions which might or might not be what we want. In addition we need to ensure that there's some parity via a TCP-based mechanism.
> 
> -Ekr
> 
> 
> 
> On Mon, Feb 3, 2020 at 2:42 AM Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
> Hi Ekr, hi Martin,
> 
> I thought that building something on top of QUIC or H3 are preconditions for any solution. If that is the case I would also prefer to put this in the charter (to exclude it clearly from the scope of this group to rebuild a new QUIC or a new version of quic or something like that which should be done in the quic group; similar for http which should be done in the httpbis in future). If you think that is somehow too restrictive what are the option open, you would want to work on in this new group?
> 
> Mirja
> 
> 
> 
> > On 3. Feb 2020, at 11:23, Eric Rescorla <ekr@rtfm.com> wrote:
> > 
> > As MT says, I would not be comfortable if the charter defined the specific protocol starting points, given the uncertainty about exactly which pieces we will do.
> > 
> > -Ekr
> > 
> > 
> > On Sat, Feb 1, 2020 at 11:53 AM Martin Thomson <mt@lowentropy.net> wrote:
> > On Sat, Feb 1, 2020, at 04:09, Bernard Aboba wrote:
> > > [BA] Would it be sufficient to add this clarification to the existing 
> > > sentence? The result would look like this.
> > > 
> > > The WebTransport working group will define new client-server protocols 
> > > or protocol extensions using QUIC or HTTP3 in order to support the 
> > 
> > I would instead say "building on existing protocol work" and then point out separately that this will definitely not define a new transport (or lower) layer protocol.
> > 
> > At Mozilla we are still uncertain about the set of protocols as currently proposed, and would feel uncomfortable limiting this to just those two *in the charter*.
> > 
> > -- 
> > Webtransport mailing list
> > Webtransport@ietf.org
> > https://www.ietf.org/mailman/listinfo/webtransport
> > -- 
> > Webtransport mailing list
> > Webtransport@ietf.org
> > https://www.ietf.org/mailman/listinfo/webtransport
>