Re: [Webtransport] [Masque] WGLC for draft-ietf-masque-h3-datagram

David Schinazi <dschinazi.ietf@gmail.com> Wed, 23 March 2022 09:42 UTC

Return-Path: <dschinazi.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 E6F693A150D for <webtransport@ietfa.amsl.com>; Wed, 23 Mar 2022 02:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 6wAyN_jHCLHO for <webtransport@ietfa.amsl.com>; Wed, 23 Mar 2022 02:42:05 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 8B4EE3A152D for <webtransport@ietf.org>; Wed, 23 Mar 2022 02:42:05 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id n18so1001512plg.5 for <webtransport@ietf.org>; Wed, 23 Mar 2022 02:42:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VIvHCtMPbMj8D/N+ye3KKSmoqQmrEnlK+nC8sXLah0M=; b=cSl6MRJMHRtQjQ6mDfTFWm/AMlYd8RO4ZNOTi5WR3sjhflMAhk05BR27156XH6XrFz oCgiDmZGnUmS5QqdF+ZMWMEwvg0xCPlSwSJY2sNUqpHPez9L3J6oyx5NWFIGTDxVfI6e 6uYvNC1b7/fB9duyf28OsGCLzuglisw/F9/o1Iyai7+lvOYN3XvNYo+lQ/SIZ+lhyms0 gPRWfTGDMPNy0aA0PMfnFtKGbdnkaOoct1kiudQhXEIzYexwId8vifz/cK+1q/LM225c yRogVBINv51v6f1GWCsgep0fH2mU+s6TdApgOys34LyJlKESH8LtHy6z36HvzpMCKKzk MxmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VIvHCtMPbMj8D/N+ye3KKSmoqQmrEnlK+nC8sXLah0M=; b=Ddb4fVCuOTwT6xdiAjta8FUJiFjoT0yrg0oA7jXr1K8lx21KQNlIHqd1Pomk92h5by gJTW+zpiaHK3Adu7oE/NDdx2/SduPvm4GURnDdKQiJcRK9xXXp0wSdYe72aWoby/21yH lhBYL4mvxWn9p36hx/592nQR/XyAuITsqKTtrdq2OasGTpTzG1dzwO714YAhKOqvuM/u 4+mSPdslsCcL0jYZK1RclQpIg1ej1KdM+LI0c1sSfM51+EqmpoPZqBVzZzrudjxYzJjf TT8Ur/wBftmiCakOwbGksF+Ahma4EwessFE6ZXMjCy0HNvAYt8Xn3Cn4foAfIQQQCGx+ yEfQ==
X-Gm-Message-State: AOAM532BjUBbczdfVK7CtRmkAIEhQ/yp1e3p7vsIVahnCejdDFJWimLQ 8i5aC8FE3tfFObsf18KDg7KKBqqrQqjLo5Oy9W0=
X-Google-Smtp-Source: ABdhPJyjIPTCFk/Gjw8lOs8K8PMX8PdYgAXJhc6o8U4P2LTQrpgjXuaKOrLxwgMSUopasgvFTkiUwxcoe8tXN0WFLy4=
X-Received: by 2002:a17:902:7802:b0:150:baa:bc1a with SMTP id p2-20020a170902780200b001500baabc1amr22852089pll.110.1648028524323; Wed, 23 Mar 2022 02:42:04 -0700 (PDT)
MIME-Version: 1.0
References: <8428BD40-8BE1-4C61-8547-203EFCBCD3DF@heapingbits.net> <345300A7-256B-4524-8CBD-16629951C837@mnot.net> <BA7FC1A8-9668-470A-B58B-38A16EE7B725@mnot.net>
In-Reply-To: <BA7FC1A8-9668-470A-B58B-38A16EE7B725@mnot.net>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 23 Mar 2022 10:41:53 +0100
Message-ID: <CAPDSy+4Vgz2xDZrxA=-QS196MqzxgZF7aZEnPg6tL9DMh36=aA@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: MASQUE <masque@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c5a61005dadf8aaa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/f-2UqZBTZ31DpH_dzw1Ka4MVqbY>
X-Mailman-Approved-At: Wed, 23 Mar 2022 02:47:53 -0700
Subject: Re: [Webtransport] [Masque] WGLC for draft-ietf-masque-h3-datagram
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: WebTransport WG <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, 23 Mar 2022 09:42:11 -0000

[ HTTP and WebTransport lists to BCC to avoid further cross-posting ]

Hi Mark,

Thank you for reviewing the document, and for spending the time to write
this PR. The editors really appreciate it. You're absolutely right that the
draft was written focusing on HTTP/3 -- that's because we initially started
with only supporting HTTP/3 a few years back, but now that we're defining
something more generic over HTTP, I agree that some editorial changes are
needed. Having looked at your PR, I think it definitely helps -- Lucas and
I will sit down and review it together in detail, I suspect we'll end up
cherry-picking most of it into the document.

To respond to your question about the history of the Capsule Protocol,
there was interest from the MASQUE WG to create this generic messaging
system beyond only sending datagrams over h2 and h1. In particular,
CONNECT-IP relies on it to exchange IP configuration, and WebTransport
relies on it to exchange session close messages.

Since the MASQUE WG has been using GitHub, could we ask you to send your
issues/questions there please?
https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/issues
We're also happy to take feedback on the list but GitHub is preferred.

Thanks!
David


On Wed, Mar 23, 2022 at 5:22 AM Mark Nottingham <mnot@mnot.net> wrote:

> OK, I've done a rough run at a PR; see:
>   https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/pull/152
>
> The HTML is waiting on someone to press the button on the Action, so I've
> attached my locally generated copy.
>
> Personally, I think this is a significant improvement, and I don't believe
> I've changed anything normative.* While I'd be happy to see it merged
> (perhaps after some more work), I'd be equally pleased if it were
> cherry-picked from.
>
> Even if nothing from it is incorporated, the exercise has helped me
> understand the document better, and I've got a few issues/questions as a
> result. The previous e-mail asked for feedback on-list; is that still
> preferred?
>
> Cheers,
>
>
> * If folks do find normative differences, I'd be interested to hear about
> it; it might indicate misunderstanding on my part, or lack of clarity in
> the source document. Either way, it'd be good to clear up.
>
>
>
>
> > On 23 Mar 2022, at 12:49 pm, Mark Nottingham <mnot@mnot.net> wrote:
> >
> > Hi Chris et al,
> >
> > I've had a read-through of the document, thanks.
> >
> > The first thing that I noticed is that the specification is very
> obviously written from the perspective of someone who's very deep into the
> details of HTTP/3 and QUIC, and is either confusing or silent about how
> this relates to HTTP as a protocol overall. If this is going to be a new,
> version-independent feature of HTTP, I think we should specify it as one in
> the first instance -- especially given how poorly past attempts have failed
> when they weren't well-integrated (e.g., push).
> >
> > So, I think it needs a non-trivial rewrite that shouldn't affect
> implementations, but unfortunately will affect the editors. I'm willing to
> work on a PR if that'd be helpful -- but it may take a bit of time to get
> right. Would that work for you/them?
> >
> > Once that happens, I think it'll be easier to evaluate the technical
> content. If I understand it correctly, I have no problem with the
> on-the-wire details, although the capsule protocol feels like premature
> abstraction at this point. Could someone speak to the thinking behind it?
> >
> > Cheers,
> >
> >
> >> On 22 Mar 2022, at 4:38 am, Christopher Wood <caw@heapingbits.net>
> wrote:
> >>
> >> (Cross-posting to MASQUE, HTTPBIS, and WebTransport)
> >>
> >> This email initiates the WGLC for draft-ietf-masque-h3-datagram,
> located here:
> >>
> >> https://datatracker.ietf.org/doc/draft-ietf-masque-h3-datagram/
> >>
> >> Please review the document and send any comments to the MASQUE mailing
> list. HTTPBIS and WebTransport are cc'd given the overlap in technology.
> >>
> >> This call will conclude on April 8.
> >>
> >> Best,
> >> Chris and Eric
> >
> > --
> > Mark Nottingham https://www.mnot.net/
> >
> > --
> > Masque mailing list
> > Masque@ietf.org
> > https://www.ietf.org/mailman/listinfo/masque
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>