Re: Call for Adoption: draft-pauly-quic-datagram
Lucas Pardue <lucaspardue.24.7@gmail.com> Thu, 12 December 2019 01:07 UTC
Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9962112018D for <quic@ietfa.amsl.com>; Wed, 11 Dec 2019 17:07:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 uXmuCB5ouKsi for <quic@ietfa.amsl.com>; Wed, 11 Dec 2019 17:07:17 -0800 (PST)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (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 16743120132 for <quic@ietf.org>; Wed, 11 Dec 2019 17:07:17 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id i31so205627uae.13 for <quic@ietf.org>; Wed, 11 Dec 2019 17:07:17 -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 :cc; bh=/TFzTGewT8Gf8ENHXzKlyp6GNZs0aAw6zAFV2MYCekw=; b=JsOH+LsJzXg8Mf2o43PUHGBH1cbgqmlJN/ktqFovC3En2KnT9bi2AaPmGd4V32lO9s yExYS8bFePFAuolRXpW3Z2QsD3sgXfKwijEP9dpflfw83wVo3qynTASC9mpQVbaFSr8Q SBA5iUbV25JBCtBys7TXSzUx1mW+w+1nTxwfatp5GK3WH8DFXQkLIHyS+hjCUsfRqqD6 6+Wtt/CnJ0VAF3OLU3WTTYTMd0VezW9AmN7W/u+krRNsUuerglhKfF0wJvwNNexjJihk yTTt0D43GArredXDkygHKcD7P+6z+sSwH44Mub7NTkseC8PTMRNxRy/YXM0WIjxc/8+k QnYQ==
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=/TFzTGewT8Gf8ENHXzKlyp6GNZs0aAw6zAFV2MYCekw=; b=t8YbX1yWzfr3+pes5PFHBbg3n5PV4KQbDEuijIG2v+3qXvtfZWr8gKu9IKCu1aLZU6 J+f6uFyTN5xV856QbIk24DTCFfsLB2n5EGme6v9vn8FrKuog/UYkR3vVMNzyQ/vKDDck al50YVMi6Op4MoTN20+JQ0h1t8AaR41rWlai5J92nT7+Ch+eB0pt+ClQn1MTuTkpRGtr MiCFixb4dHk6wKWi5HUpRWU7tj6024onMLjq0WA2C3H8giqGD9+Kxr5KfcLJSNT5IFDx LDugwr+PaMf39QBZOS++6ggKH38epQ/vz5nFXQDKaJ/sybFqJG5MMJjlry3aS2vIuOTB cseQ==
X-Gm-Message-State: APjAAAW+VtG+wz/H3zRX0ddri2mE03gQd8ZeAyRpLo4UWdeSleZiiiLq jcePc4rC04oeNScg5oW2TNT7QZ1Evj4JGdSTDXk=
X-Google-Smtp-Source: APXvYqx5l2AcW/IpBLMNroSCOA8dOb9CdRy3bIWppf1BHSqjqjJG+cnoP5P9eJYejUiu5pnloqTbGQ/g35gkx4Vz8rM=
X-Received: by 2002:ab0:3415:: with SMTP id z21mr6273652uap.9.1576112835911; Wed, 11 Dec 2019 17:07:15 -0800 (PST)
MIME-Version: 1.0
References: <5A21DBF8-996D-410D-A868-95D640C39298@mnot.net> <CAAZdMadqbTKGOLq6CGuTGVZ3V6JFxvTSHAZHLYhe=MbisHA-yg@mail.gmail.com> <CAN1APddrBOQqLz1L8Jn+WNLqHC_1XwnnoBH7zqYRoHYsPnQBYA@mail.gmail.com> <CACpbDccJqKKniABZeVbU8c1evgJdAV+S9tXtoqQo6KeO=0QMGQ@mail.gmail.com>
In-Reply-To: <CACpbDccJqKKniABZeVbU8c1evgJdAV+S9tXtoqQo6KeO=0QMGQ@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 12 Dec 2019 01:07:23 +0000
Message-ID: <CALGR9oYaQL4VfmpMaNu9P5+cKJcghxD-acPFtJr3owQhLnBP6w@mail.gmail.com>
Subject: Re: Call for Adoption: draft-pauly-quic-datagram
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>, Victor Vasiliev <vasilvv=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b5e5c60599775dde"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2XhutFEpoBdxVmnCOkgnuyhBLeg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2019 01:07:19 -0000
I support adoption of this draft but will note that in the abstract sense it is hard to reason about the design of DATAGRAM and hard to interop without an application of it. Since the round of call for adoption does not incorporate an application, I have concern about the scope. I wrote up SiDUCK [1] as means to an end, there are probably better ways to make us comfortable as a WG. [1] - https://tools.ietf.org/html/draft-pardue-quic-siduck-0 On Wed, Dec 11, 2019 at 11:03 PM Jana Iyengar <jri.ietf@gmail.com> wrote: > I support adoption of this document. > > This is a natural extension to QUIC and there are multiple implementations > and side-conversations happening already, and as I understand it, there is > some deployment experience. > > One note however. Per my read, this is the first extension that extends > the functionality of QUIC beyond the charter's original conception of it > for HTTP. Many things are possible with QUIC, but the things we want to > standardize are the things that are likely to be used. There's no better > argument for useful extensions than a discussion of actual deployment where > it exists.. It enables others to use it similarly, and importantly, it > informs why the mechanism is designed so. I would have hoped for more > active discussions around current uses of this extension where it exists, > including deployment experience where it exists. Perhaps the authors can > take this as feedback going forward. > > - jana > > On Wed, Dec 11, 2019 at 2:00 PM Mikkel Fahnøe Jørgensen < > mikkelfj@gmail.com> wrote: > >> Yes, datagrams are important for custom protocols. >> >> >> On 11 December 2019 at 22.49.23, Victor Vasiliev ( >> vasilvv=40google.com@dmarc.ietf.org) wrote: >> >> I support adoption of this draft. We already support a version of this >> in gQUIC and I am willing to work on making sure it's interoperable with >> other implementations. >> >> On Wed, Dec 11, 2019, 13:36 Mark Nottingham <mnot@mnot..net >> <mnot@mnot.net>> wrote: >> >>> This is a Call for Adoption of the following document: >>> https://tools.ietf.org/html/draft-pauly-quic-datagram-05 >>> >>> The Working Group has discussed this document for some time, most >>> recently in Singapore. >>> >>> Please state whether you support adoption of the document by the Working >>> Group, and any additional information that you feel may be helpful. >>> >>> This call will end on 15 January 2020. >>> >>> Regards, >>> >>> -- >>> Mark Nottingham https://www.mnot.net/ >>> >>>
- Call for Adoption: draft-pauly-quic-datagram Mark Nottingham
- Re: Call for Adoption: draft-pauly-quic-datagram Victor Vasiliev
- Re: Call for Adoption: draft-pauly-quic-datagram Mikkel Fahnøe Jørgensen
- Re: Call for Adoption: draft-pauly-quic-datagram Jana Iyengar
- Re: Call for Adoption: draft-pauly-quic-datagram Christopher Wood
- RE: Call for Adoption: draft-pauly-quic-datagram Lubashev, Igor
- Re: Call for Adoption: draft-pauly-quic-datagram Ian Swett
- Re: Call for Adoption: draft-pauly-quic-datagram Martin Thomson
- Re: Call for Adoption: draft-pauly-quic-datagram Lucas Pardue
- Re: Call for Adoption: draft-pauly-quic-datagram Kazuho Oku
- RE: Call for Adoption: draft-pauly-quic-datagram Roni Even (A)
- Re: Call for Adoption: draft-pauly-quic-datagram Jiuhai Zhang
- Re: Call for Adoption: draft-pauly-quic-datagram Christian Huitema
- Re: Call for Adoption: draft-pauly-quic-datagram Mirja Kuehlewind
- Re: Call for Adoption: draft-pauly-quic-datagram Brian Trammell (IETF)
- Re: Call for Adoption: draft-pauly-quic-datagram Christian Huitema
- Re: Call for Adoption: draft-pauly-quic-datagram Roberto Peon
- Re: Call for Adoption: draft-pauly-quic-datagram Mikkel Fahnøe Jørgensen
- Re: Call for Adoption: draft-pauly-quic-datagram Mike Coleman
- Re: Call for Adoption: draft-pauly-quic-datagram Rui Paulo
- Re: Call for Adoption: draft-pauly-quic-datagram Marten Seemann
- Re: Call for Adoption: draft-pauly-quic-datagram Patrick McManus
- Re: Call for Adoption: draft-pauly-quic-datagram Vidhi Goel
- RE: Call for Adoption: draft-pauly-quic-datagram Mike Bishop
- RE: Call for Adoption: draft-pauly-quic-datagram Florin Baboescu
- Re: Call for Adoption: draft-pauly-quic-datagram Thomas Fossati
- Re: Call for Adoption: draft-pauly-quic-datagram Eric Rescorla
- Re: Call for Adoption: draft-pauly-quic-datagram Gyan Mishra
- Re: Call for Adoption: draft-pauly-quic-datagram Phillip Hallam-Baker
- Re: Call for Adoption: draft-pauly-quic-datagram Bernard Aboba
- Re: Call for Adoption: draft-pauly-quic-datagram Sean Turner
- Re: Call for Adoption: draft-pauly-quic-datagram Tal Mizrahi
- RE: Call for Adoption: draft-pauly-quic-datagram Ingemar Johansson S