Updated DATAGRAM -03 draft

Tommy Pauly <tpauly@apple.com> Mon, 08 July 2019 15:20 UTC

Return-Path: <tpauly@apple.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 F191612018A for <quic@ietfa.amsl.com>; Mon, 8 Jul 2019 08:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=apple.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 MTlYekEguJml for <quic@ietfa.amsl.com>; Mon, 8 Jul 2019 08:20:21 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED07912003E for <quic@ietf.org>; Mon, 8 Jul 2019 08:20:20 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x68FGRil055250 for <quic@ietf.org>; Mon, 8 Jul 2019 08:20:19 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : content-type : mime-version : subject : message-id : references : to : date; s=20180706; bh=eb9hoFR3pvbAhDAxX+rtu0JOFE+NPO/uxlyM6f/XD7w=; b=Q1Xg2qafLPXxrfYI96ke849OdUfyV/yTX0vlwVS7+49l27KG+cPOCkaETPORG1Sz3NHR KX7FNYQqFWIZzqx+0kCveFx8T78gQVmzAXQzXcDrkjDiqdGBeBw5oy6HfD0SGNawJxRF 3DJrJCMuDJ2i8pv0QfmA7DeKYPU0wxEHihQdxIoUjH2oP/8YM6OBAoIhXSfwJR02JLbo Y0OxDXwQ8gBVlLiAd7EaZSfePej89YGX8IYpqMZb/qrEwm8mrezyPiFc6yYX13xLiuHV J4nU8CM4BmekqhNEYiAIYtgoJwEhXxYJLLys1tIJaoybrpu//q8Bj6A7G2zHu2zndSxl zA==
Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2tjrav190y-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <quic@ietf.org>; Mon, 08 Jul 2019 08:20:19 -0700
Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0PUB00C9UX9VOT10@mr2-mtap-s01.rno.apple.com> for quic@ietf.org; Mon, 08 Jul 2019 08:20:19 -0700 (PDT)
Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0PUB00L00X9MX000@nwk-mmpp-sz13.apple.com> for quic@ietf.org; Mon, 08 Jul 2019 08:20:19 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 4fc7fc2a6ed6f60e40832e4273217f25
X-Va-E-CD: 7c5eb70ef839e2d282b24ab0108b9d75
X-Va-R-CD: 4a14aac1a9a68c8ee8f6a97913d9d135
X-Va-CD: 0
X-Va-ID: 98ad2448-ac73-4f54-9668-fd8bd5e90d6c
X-V-A:
X-V-T-CD: 4fc7fc2a6ed6f60e40832e4273217f25
X-V-E-CD: 7c5eb70ef839e2d282b24ab0108b9d75
X-V-R-CD: 4a14aac1a9a68c8ee8f6a97913d9d135
X-V-CD: 0
X-V-ID: 99b20f44-2eec-423f-8b10-521b739f068d
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-07-08_05:,, signatures=0
Received: from tpauly.scv.apple.com (tpauly.scv.apple.com [17.192.171.37]) by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0PUB0056KX9M2DA0@nwk-mmpp-sz13.apple.com> for quic@ietf.org; Mon, 08 Jul 2019 08:20:10 -0700 (PDT)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_6B39B886-8D39-41F6-A323-780AEB1C13D6"
MIME-version: 1.0 (Mac OS X Mail 13.0 \(3560.7\))
Subject: Updated DATAGRAM -03 draft
Message-id: <FAEF650D-5C03-4CD3-8178-873A0969F230@apple.com>
References: <156246300105.3401.11374988947164402300.idtracker@ietfa.amsl.com>
To: QUIC WG <quic@ietf.org>
Date: Mon, 08 Jul 2019 08:20:09 -0700
X-Mailer: Apple Mail (2.3560.7)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-08_05:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nOug5EfOjt9VTMi68FrvppUowjc>
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: Mon, 08 Jul 2019 15:20:24 -0000

Hello all,

We’ve updated the QUIC DATAGRAM draft to incorporate some of the feedback we received at the side meeting in Prague. Notably, it clarifies:

- Guidance around datagram acknowledgements
- Datagrams do not participate in any flow control
- Datagrams do participate in congestion control

The remaining area of open discussion is around the newly re-named optional “flow identifiers”. The primary argument for removing these is that applications can add identifiers onto datagrams themselves, and the transport should not transmit a field that it does not do anything with. We did add some text clarifying that these identifiers are essentially like UDP ports for demultiplexing, and pointed out some *minimal* things the transport can do to help batch transmission of datagrams in the same flow and promote fate-sharing within a flow. There’s been some discussion on Slack of other approaches that would make these flow IDs more first-class citizens—adding reliable signaling for opening and closing flows, as many applications would also generally need some similar sort of control channel—but these seem a bit heavy-weight. Either way, this is an area where discussion is welcome and I expect the document to change.

Best,
Tommy

> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-pauly-quic-datagram-03.txt
> Date: July 6, 2019 at 6:30:01 PM PDT
> To: Eric Kinnear <ekinnear@apple.com>, David Schinazi <dschinazi.ietf@gmail.com>, Tommy Pauly <tpauly@apple.com>
> 
> 
> A new version of I-D, draft-pauly-quic-datagram-03.txt
> has been successfully submitted by Tommy Pauly and posted to the
> IETF repository.
> 
> Name:		draft-pauly-quic-datagram
> Revision:	03
> Title:		An Unreliable Datagram Extension to QUIC
> Document date:	2019-07-06
> Group:		Individual Submission
> Pages:		8
> URL:            https://www.ietf.org/internet-drafts/draft-pauly-quic-datagram-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-pauly-quic-datagram/
> Htmlized:       https://tools.ietf.org/html/draft-pauly-quic-datagram-03
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-pauly-quic-datagram
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-pauly-quic-datagram-03
> 
> Abstract:
>   This document defines an extension to the QUIC transport protocol to
>   add support for sending and receiving unreliable datagrams over a
>   QUIC connection.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>