IETF Logo Mail Archive

Re: Call for Adoption: draft-pauly-quic-datagram

"Christopher Wood" <caw@heapingbits.net> Wed, 11 December 2019 23:06 UTC

Return-Path: <caw@heapingbits.net>
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 4E1A11201C6 for <quic@ietfa.amsl.com>; Wed, 11 Dec 2019 15:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=heapingbits.net header.b=cI1o0E8P; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=vdSopQWB
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 7VHR_JvIBusU for <quic@ietfa.amsl.com>; Wed, 11 Dec 2019 15:06:10 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89521120178 for <quic@ietf.org>; Wed, 11 Dec 2019 15:06:10 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D350621FBF for <quic@ietf.org>; Wed, 11 Dec 2019 18:06:09 -0500 (EST)
Received: from imap4 ([10.202.2.54]) by compute6.internal (MEProxy); Wed, 11 Dec 2019 18:06:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm3; bh=BXEth Gg+1qgyEJtS1YwcMGL/szLxqaehsmhWjyBREIk=; b=cI1o0E8PI7mZu7XEzslsI aTP5muy8oUuJbok79HhpTCgaHU4S+1i23UmONv3o1ExqL9qqHceczQ17NmuAxgYF +C6sc0IlX/nM0vkPG1JM3WXbcjbZ7W0jOFGF6gKlnL3J0DBuCxgCTkz7ZGdl4Y2G s70dpm2sLQx5h2a7uKXXgEDzAAeomuhSX0W4t9VrHhL9LYsF8EK2sNMZ3NBOXquk PK3TpGO+4DSIMiXIEuNat/90N9UFW+go7cpnRFW/s8c8s6TomRhryeqqCaBKkYLf QhGO/lKcRjLcb8vt5TWienW4tuiosc36zr3ndpRZSKcmWu3zInVnOGvsxthtxHTF w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=BXEthGg+1qgyEJtS1YwcMGL/szLxqaehsmhWjyBRE Ik=; b=vdSopQWBHL8Qi8tWBHJjBa7PCRGVUNoyZNPlleH8EYqFLYz3I4uKuLdxj LnEsDsWNyOfYDeCGYydSTJlIPeCyhJhtnDoHrwx2+sZxPyGajgyiUY652tQRWZ/1 arjfxKrGcqYdkDVIHj85MMMXi4PhB6mZ1NSaW7a1VrfZ4EvCtYMBe0f0XI/dq05W NDNsSSDDOnlHzAyJgEuqFjgBMZUP/vefe1LCd1Loq8cYyQltP2tzdEcu8vI//YHi p6nvNXfUD/j46Cl0WezRviD0hIHUcEdwC9q1q52dfN8IyKakDEcS80nnJKp/EOqS WIWhpc6hB5Jn7KQ1eBxzgk5HUbsnA==
X-ME-Sender: <xms:YXbxXQgKF4T85V3ml8WKTnb2L6ybseVRYb5dEWv6GcUqyBdWNfxroQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeliedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdevhhhrihhsthhophhhvghrucghohhougdfuceotggr fieshhgvrghpihhnghgsihhtshdrnhgvtheqnecuffhomhgrihhnpehivghtfhdrohhrgh dpmhhnohhtrdhnvghtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegtrgifsehhvggrphhi nhhgsghithhsrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:YXbxXbabpAPwNzpW2X-N2qM-qTQxUZ5zQ7jCLI0rpN_3vlpMj2Uxow> <xmx:YXbxXRXSVso8j3sfRlvJEdUbAk4ZRO9KIPecOrfQ5IX_fNiDpCvhFg> <xmx:YXbxXUb80pT5ddGt2DKgFaaYaQGvanvsR6eAs3HwkqgFMcLYp__Ayg> <xmx:YXbxXexiiU_XRStEaUlBVkCHfZzBNn8h6rZSjpyREYN7cbDQ2suXzg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 96FFB3C00A1; Wed, 11 Dec 2019 18:06:09 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-679-g1f7ccac-fmstable-20191210v1
Mime-Version: 1.0
Message-Id: <73106ed4-bb04-4410-9976-3f70bd837c70@www.fastmail.com>
In-Reply-To: <CACpbDccJqKKniABZeVbU8c1evgJdAV+S9tXtoqQo6KeO=0QMGQ@mail.gmail.com>
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>
Date: Wed, 11 Dec 2019 15:05:49 -0800
From: Christopher Wood <caw@heapingbits.net>
To: quic@ietf.org
Subject: Re: Call for Adoption: draft-pauly-quic-datagram
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/BsVrrleUp7O9vJBuwquo9wabtwU>
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: Wed, 11 Dec 2019 23:06:12 -0000

I support adoption. 

Best,
Chris

On Wed, Dec 11, 2019, at 3:03 PM, Jana Iyengar 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 <mailto: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/
> >>>

v2.23.0 | Report a Bug | By Email