IETF Logo Mail Archive

Re: [Webtransport] Confirming Consensus on WebTransport protocols

Yutaka Hirano <yhirano@google.com> Thu, 14 January 2021 09:15 UTC

Return-Path: <yhirano@google.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 8BB153A1372 for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 01:15:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level:
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 SHfnCWfgBvDh for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 01:15:57 -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 A71E63A10E8 for <webtransport@ietf.org>; Thu, 14 Jan 2021 01:15:56 -0800 (PST)
Received: by mail-lf1-x12c.google.com with SMTP id v24so372598lfr.7 for <webtransport@ietf.org>; Thu, 14 Jan 2021 01:15:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+jPCcl8Zo0MN+NiY+Z4NBQ97PnG2dP2X7Ftf8PTq1vk=; b=eo0mHyVWx8O7IsyIejH+yyKKIcdkj+wJGev4noQVhSdyJm7gaSk1d5t73i5knToZoE XAeDrVIrF0u+Upm8+uozuSK9iwbrjv3vFopQ0mx0gfoWOes+IC4Z/5u+LH0pKxTemv4r 0OHcct1fON7aHlahClQi8LFtnEuo2HiG5l0wAUwYVWFkI/w+QpR4l2/a2LnKC+fwVpFh EQVWxHFhibd3hwNPZFrztd1fM31MnujJp+pIc7aBiDaOfvXnRnlvn/eVuV94JoEFU392 Jhpa5SMFYTkMzp+3XvC3a6luhS6PH+Ujq60fq16vvYgvgmt8lfoWm+Zyw9ESPDsvEgF4 yVzw==
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:cc; bh=+jPCcl8Zo0MN+NiY+Z4NBQ97PnG2dP2X7Ftf8PTq1vk=; b=P21YF9rgCquxlzVE7wNWKhnuxlITFmY5z7YlxtnDDXg682rPpj96DCErKdj6GXEqc3 i8H1lIvnsQ2Ifj+ZuNqYqYEJUKI6KVZJM3GWfEPQUgIBpAF+CMFPc1KKPKwj6qTjm7aQ 3OfWZvFD9kE7p82yfZjs2KK+S6H0UdpjeUBTiay17r0hF/1PJpLjVHGCp734+uvFupdN JjbUZRch25RrDgfTKuwYSNbWsEhIHztXf6031swkplrBcO9+WUGNZtWPQVsdtm+yuURY 2AcIbtcAgRsYulTa1DnpZrtCDf8eUgfVKY9HJeN7iKNpdTdVfdFMz/UK8wrwAR/MBrDd 4h9w==
X-Gm-Message-State: AOAM533kv/8ELTFhKKQiKTao2q3eGA9CFqIZCYDSyZvK9EfHM4hnc7Kq DLSS6E4bVzK6Yit+76t2W395HfnRZ1AijOfFSv06qg==
X-Google-Smtp-Source: ABdhPJxIsYR7ImAWfDnqUQ6iAbIYhvZFYrdJJ34XQp5ZaQDrkv1mfzLGjhxZ1Ct9NfwOWATXr2PpyvuiDhhzTRUDb/g=
X-Received: by 2002:a19:a06:: with SMTP id 6mr2781542lfk.624.1610615754756; Thu, 14 Jan 2021 01:15:54 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAAZdMafTH73XmtKnr7ZpScT4aL2OvfjcKy1mEEXBSMDQBqAxCg@mail.gmail.com>
In-Reply-To: <CAAZdMafTH73XmtKnr7ZpScT4aL2OvfjcKy1mEEXBSMDQBqAxCg@mail.gmail.com>
From: Yutaka Hirano <yhirano@google.com>
Date: Thu, 14 Jan 2021 18:15:42 +0900
Message-ID: <CABihn6GJrKjaPZfpdLZ_JW4x5H2imaR4ZTUs0jgwMchJQYmNGg@mail.gmail.com>
To: Victor Vasiliev <vasilvv=40google.com@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eee01a05b8d8b3cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/Yy-zbCxffsUZJs-1E1T1raiMzP8>
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: Thu, 14 Jan 2021 09:15:59 -0000

I support the consensus.

On Thu, Jan 14, 2021 at 6:02 PM Victor Vasiliev <vasilvv=
40google.com@dmarc.ietf.org> wrote:

> On Tue, Jan 12, 2021 at 7:02 PM Martin Thomson <mt@lowentropy.net> wrote:
>
>> On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
>> > The consensus was option 1A.
>>
>> Great!
>>
>> > The consensus was option 2A.
>>
>> I can live with that.  Can I request a brief summary of the reasons?
>>
>
> From my perspective, it's mostly because QuicTransport has been just an
> incremental reinvention of HTTP from scratch.
>
>
>> > Additionally, we discussed pooling and decided that we would
>> > not allow pooling in WebTransport over HTTP/3 for now, due
>> > to the complexities of pooling.
>>
>> I don't think that this group gets to say that.  If we are using HTTP,
>> then we are using HTTP.  We might decide that in browsers we want to keep
>> the connections separate for $reasons, but I am opposed to saying that.
>>
>> Unless of course I'm missing context in the same way I missed the meeting.
>>
>
> HTTP pooling is an optimization, so I don't believe it is ever actively
> required.
>
> Most of the objections to using HTTP as a transport come from a perceived
> requirement to support pooling.  Even outside of design complexity related
> to flow control and prioritization, there are cases where web developers
> actively benefit from not using pooling (using connection-level stats or
> congestion control state for things like ABR).  I believe that it should be
> possible to enable/disable pooling WebTransport as a part of settings
> negotiation, and I am currently trying to figure out the details of how to
> do that.
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

v2.23.0 | Report a Bug | By Email