Re: Add deadline awareness to QUIC

Christian Huitema <huitema@huitema.net> Mon, 14 November 2022 19:05 UTC

Return-Path: <huitema@huitema.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 14006C14F742 for <quic@ietfa.amsl.com>; Mon, 14 Nov 2022 11:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ql_GjrRnD7F5 for <quic@ietfa.amsl.com>; Mon, 14 Nov 2022 11:05:05 -0800 (PST)
Received: from mx36-out21.antispamcloud.com (mx36-out21.antispamcloud.com [209.126.121.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA43EC14F736 for <quic@ietf.org>; Mon, 14 Nov 2022 11:05:05 -0800 (PST)
Received: from xse58.mail2web.com ([66.113.196.58] helo=xse.mail2web.com) by mx258.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1ouelS-0004wi-PA for quic@ietf.org; Mon, 14 Nov 2022 20:05:05 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4N9zJR644wz9bn for <quic@ietf.org>; Mon, 14 Nov 2022 11:04:39 -0800 (PST)
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1ouel5-0005pK-MM for quic@ietf.org; Mon, 14 Nov 2022 11:04:39 -0800
Received: (qmail 23283 invoked from network); 14 Nov 2022 19:04:39 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.58.46.132]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <simonkorl0228@gmail.com>; 14 Nov 2022 19:04:39 -0000
Message-ID: <797f896f-839b-3734-0c07-0465bfd7fe35@huitema.net>
Date: Mon, 14 Nov 2022 11:04:39 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Subject: Re: Add deadline awareness to QUIC
To: Chuan Ma <simonkorl0228@gmail.com>, quic@ietf.org
Cc: cuiyong@tsinghua.edu.cn
References: <CAAZo2nGK_HPbRKhW7fk8cBbZ5Y8HJOf737COKoFy=Xc6XHoL9g@mail.gmail.com>
Content-Language: en-US
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <CAAZo2nGK_HPbRKhW7fk8cBbZ5Y8HJOf737COKoFy=Xc6XHoL9g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: 66.113.196.58
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.52)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT+okj0gaqGgaJbrFub2joTuPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x6h2yQpzTslcOqazQkKtAFKj/EwzSHE5FGYwwjsNRPCF2e 4rgygFhl2pM2q7cTHC/mD6wdmZPcItWbGe10hXJtXL4FsauCVkDjmcYJdU3yWp7KuHNaaKdg7iBE ZefdsNUFWKwa/wzJUjmazeC7ImcaM05ne/b+IM64ThOgtGfoDxQ6V51u76v35b1wNe/MvdJPWWqi c9eoDWW+hxVOsiYx2+J9PgaoF8SQHto3le4zsHTaeQtlKubP6iUTjj6yPARK6buALVaA782LKxg6 vRmng8N1aLhXqdc+jC1RcnVud53D5caUhbVtvqItBqoizkEt9O20UjkwI0v+LOlw05G4BS+iyyNq bT8dUMXMJ4tUCMj6G37ZfAMLceP5aNHPt26RBupu5v1nytoNnc138GfEEIgtEXyXj6S3SDvReMcV 8TXUjLjYWQt1/5xnQymMoPsgr/U0flMcy2Vi/IcBgY4arPaiJ1W6hAyiRC61jekdwIcXNugoOEbH RyFULpSjm7hMIABpqqRGKyDs8xujM3cq7Rvkiy9CGpqIMbF0Ys3gbT4e+O1qgWYY9RCqk8Ds5BtE A3B3TZaXenH55k0fekmXEnFzsC48bTEFY06/YbB87aZA2T1TDpm1DkXX6Es5zXntCB3G1CwpaI3Z 4ESkMWDVEmlGVTLa11kLY1eVj2D9MClg0bX+hyQHjXZuP5+tl/TZcpPgEJKLbDyaC/LdLvvYAsTt NBxfGMrEQgjNlNVEYfpVB9v9zY0h8asEYmbGGsLRRrpb2yB+9SGl7QVSZMRQzaGa3FiXV2A9SrS+ Q7G2/h0sl4OFxBT1d23OUWLVuGpBtL9ewJnoHKUNLZpf7DfZK/JdWvgd2/FibEdMM0Jnxu/VcARR JJg0CPVGXFYA7xCx7SWZBpdAUArn/St00aGa08t44IPL25P8DLNzMDIRDLdvK/cKOEqlCIPGIfYQ DNLcNVwigJ23suxKKQl6t4RW
X-Report-Abuse-To: spam@quarantine14.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/x0sRO-jL9SFc5HYSpjnn2Da7vtk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
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, 14 Nov 2022 19:05:10 -0000

Hello Chuan Ma,

Your draft aligns very much with some of the options investigated for 
"media over QUIC". Have you considered participating in that working group?

-- Christian Huitema

On 11/14/2022 10:20 AM, Chuan Ma wrote:
> Dear all:
> 
> I'm Chuan Ma from Tsinghua University. I want to discuss the deadline
> awareness of the current application and whether we should add it to the
> QUIC protocol.
> 
> Applications may have specific deadline requirements for data transmission.
> For instance, a video conference application may require sending the data
> with a deadline of 200ms to enable live interaction. The application may
> drop the data that misses the deadline, even if the data has already
> reached the other end. In this case, it is possible to drop the data after
> the given deadline from the sender to save bandwidth and decrease queuing
> time. Deadline requirement is also helpful to offer deadline-aware
> scheduling combined with QUIC stream priority. Such scheduling methods can
> increase the punctuality of QUIC and allow more data to arrive on time. It
> is possible to extend QUIC and offer deadline-aware transport as a service.
> 
> Nowadays, deadline-aware data transmission is getting more and more
> popular. Applications that emphasize real-time interaction, such as VR/AR,
> gaming, and video conference, are drawing more and more attention. So
> deadline-aware transport has a lot of use cases. However, currently, it is
> the application that is responsible for realizing deadline-aware transport.
> This transport service should be offered by the transport protocol but not
> be left to the application. It is reasonable to provide such transport
> service in a new transport protocol, and QUIC is a good base.
> 
> We wrote a draft to show this idea in
> https://datatracker.ietf.org/doc/draft-shi-quic-dtp/ and implemented a
> protocol based on QUIC called DTP (Deadline-aware Transport Protocol) in
> https://github.com/STAR-Tsinghua/DTP.git. We also built a live stream
> prototype application to compare the performance between DTP and QUIC (
> https://github.com/STAR-Tsinghua/LiveEvaluationSystem.git). We found that
> DTP outperformed QUIC in improving data transmission punctuality and saving
> bandwidth resources. We published the paper in ICNP22 and built several
> systems like proxy and tunnel based on DTP. It would be a good idea to give
> this method a try.
> 
> We'd like to know what you think about this topic. Please let us know if
> you have any comments.
> 
> Best regards.
> 
> Chuan Ma
>