From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: Add deadline awareness to QUIC
Date: Mon, 14 Nov 2022 15:18:49 -0800 [thread overview]
Message-ID: <CAA93jw4Mf9QOsW6v9MHveU+8Am7i_Nc_YtGFe3pT++w_yHu9ew@mail.gmail.com> (raw)
In-Reply-To: <CAAZo2nGK_HPbRKhW7fk8cBbZ5Y8HJOf737COKoFy=Xc6XHoL9g@mail.gmail.com>
---------- Forwarded message ---------
From: Chuan Ma <simonkorl0228@gmail.com>
Date: Mon, Nov 14, 2022 at 10:21 AM
Subject: Add deadline awareness to QUIC
To: <quic@ietf.org>
Cc: <cuiyong@tsinghua.edu.cn>
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
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
next parent reply other threads:[~2022-11-14 23:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAZo2nGK_HPbRKhW7fk8cBbZ5Y8HJOf737COKoFy=Xc6XHoL9g@mail.gmail.com>
2022-11-14 23:18 ` Dave Taht [this message]
2022-11-14 23:30 ` Dave Collier-Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4Mf9QOsW6v9MHveU+8Am7i_Nc_YtGFe3pT++w_yHu9ew@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox