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

Jana Iyengar <> Wed, 11 December 2019 23:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E3CD31201C6 for <>; Wed, 11 Dec 2019 15:03:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jyfHyQGK36N1 for <>; Wed, 11 Dec 2019 15:03:37 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9C01412012A for <>; Wed, 11 Dec 2019 15:03:36 -0800 (PST)
Received: by with SMTP id u17so43051lja.4 for <>; Wed, 11 Dec 2019 15:03:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ElifU0kCQZDGu5EtDXYhOXG7uSPcd4A04p/mjQUx7S0=; b=Xcr127m/H8hIugT9aRCGP9H8h2AQFqCc/F7C3xfugxZwrlksDtp/N7Y55hMJWEJHty XXQiQMZWVcliIRi7Sx1wFYgzhsFHJE3+NuVFAeKkSuNHvO6kqUbzOsN0DJV4RGMX7a++ CtZo/53M8a/pYIofi/DVnY0G36pWmigJ81Dsc/+Ws2s9a6vwy9aWgCI6KKm0O/j1bAxu HVMkAGvpmluVfPrKpkwhAs1uhlnC8sy23zNvzqlXDGwH9ZHKEhksbpZRiCDK6iNPcZCu A9TCiNc1zLC8qNvaIrAxgISocb4he3i+JV2cD+bqNoDVDOblFujNErlUCY+iEjS9t0aG okNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ElifU0kCQZDGu5EtDXYhOXG7uSPcd4A04p/mjQUx7S0=; b=da9TBDjNiKnHTDvgg8jj4hBjHOM41NlTs4hfvgVdQKdzZbetQf+7NmHFHDlVwS4ypj m4QxFBMj2wTzPkqqqQDs8yXbwv+uombdHewXeoBw4NWzlfs5dEIJ8EVTo49GveEQOVwO fp/h5R+QPA6qt+29w6nig+C7RFfBRoFEVbwKd917qeWUyg4hkrTp1+td5LwtZFI5nSqu wUDpNeBu6fdfyGXp2m99jslvTo9hnBrvj/pRiBuo/oD3/EyhTbcP03pVXSqJwCR1exLO 3L17PbZ2siVDCNJ8SFjfrPizxbr3d10jEvICrMqkgj4gghKUvYQ554Q/koJpO2twJR6B p1ww==
X-Gm-Message-State: APjAAAWxl0nPX3UVraYiywSlQv0n9M4JVX8OkGUWRWOzNJ95inLEf2Ex v/4rAmMmSwnZfYQTF1xPimNeY287axJSyOaq6vU=
X-Google-Smtp-Source: APXvYqy0eA8yJtNSndoM6FuadswlxktU3lLOZVxrfOD0VQcO3Arulzch6RrFuSdO5InMxKIjwWjXuL2Ha7dj4l2UyjI=
X-Received: by 2002:a2e:9b58:: with SMTP id o24mr3862487ljj.197.1576105414912; Wed, 11 Dec 2019 15:03:34 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Jana Iyengar <>
Date: Wed, 11 Dec 2019 15:03:23 -0800
Message-ID: <>
Subject: Re: Call for Adoption: draft-pauly-quic-datagram
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <>
Cc: Mark Nottingham <>, Victor Vasiliev <>, Lars Eggert <>, IETF QUIC WG <>
Content-Type: multipart/alternative; boundary="000000000000626d64059975a3e9"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Dec 2019 23:03:39 -0000

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 <>

> Yes, datagrams are important for custom protocols.
> On 11 December 2019 at 22.49.23, Victor Vasiliev (
> 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 <> wrote:
>> This is a Call for Adoption of the following document:
>> 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