Re: Add deadline awareness to QUIC

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 14 November 2022 23:12 UTC

Return-Path: <sarikaya2012@gmail.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 8FBA6C14CE20 for <quic@ietfa.amsl.com>; Mon, 14 Nov 2022 15:12:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.845
X-Spam-Level:
X-Spam-Status: No, score=-1.845 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mGI3Bf4vEN4z for <quic@ietfa.amsl.com>; Mon, 14 Nov 2022 15:12:04 -0800 (PST)
Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com [IPv6:2607:f8b0:4864:20::a31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 C789FC14F730 for <quic@ietf.org>; Mon, 14 Nov 2022 15:12:04 -0800 (PST)
Received: by mail-vk1-xa31.google.com with SMTP id b81so5768257vkf.1 for <quic@ietf.org>; Mon, 14 Nov 2022 15:12:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YJVBqt6ZOsdk9SrxDm1p7qD0dvLg/ELRUKn7wbXUt7M=; b=MtG1e0MbKZXH6xVB7L7dwwRsxJTUEQ9gE0i7sKx5pD9KzugyklmOw7kDn2xycxEM0w i7EkEiKi5zDDo3FOpmSUevbaMGYGj4wE7D8Fb0aqwDbthFpFaiEiL5ES6M3NpB32q/ZW jIy/It84uYrPJwSK0MFBH9fss0QFlcCpBFGuqIkSsevl9Cr54q/WIWpW+nixzBYMswcH K60M9aisf/UyLobRvF0zn5ZooZ6EVTes6/zQzUs57VQk8YzD99HJG5NwNPdi3NVcmaKn edNh2DSiuUGspTycX71K+bLUkl6e+jFjwCy0ob0hpqUfqzSWkEsf4nTADcV1C66fiqoB o7Hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YJVBqt6ZOsdk9SrxDm1p7qD0dvLg/ELRUKn7wbXUt7M=; b=6rgYD+pRih5LoPC9ZqWVadulSo3uB29m6k+dty1gluuyHhIIXhRaq+e+/ahbkjPz5l NFwi8uw79H8DjBkbaGJT0mwFsylcC1H5Ts6WQMVgHHYf2+sDORtpq3y/ngM/PPVb7u9o CuyPf/FfF+tjn0dxZyu3czICNC+QIsi/Yph+2y2fynwo15HPGxHQZ0zfxNVKgW+b88dS bVTvxPJ6vcWxt+LrQs1We3PJUyHYe/jJ2cnnDdHF90/h50XVPALloCupDk6ta6y8jv4v 6tkBE0TJgbx+BDF7jNJ6lDVpyUtRN5+58qGr1ZOuEuW7StV4cNRbnll9GKo0m17uQzie cG+A==
X-Gm-Message-State: ANoB5plok9RtZ4Rrwsb+vjglpdGjLYIO+1wf7lI9Z4xnB5fCrvOlq5H8 zIerKitB7vXynbu/wqYGNSU4mWPu787g0yAxG0E=
X-Google-Smtp-Source: AA0mqf4PRq2WBvn6qdxlcZi4Xr4gG+x41OD5pTyayqvh3Jv6G3O4qhkR48jOy0BM3EoDHPyqX/O+GaO9G0MbRqF8ejs=
X-Received: by 2002:a1f:30d1:0:b0:3b8:3b0b:2238 with SMTP id w200-20020a1f30d1000000b003b83b0b2238mr7657596vkw.23.1668467523568; Mon, 14 Nov 2022 15:12:03 -0800 (PST)
MIME-Version: 1.0
References: <CAAZo2nGK_HPbRKhW7fk8cBbZ5Y8HJOf737COKoFy=Xc6XHoL9g@mail.gmail.com> <797f896f-839b-3734-0c07-0465bfd7fe35@huitema.net>
In-Reply-To: <797f896f-839b-3734-0c07-0465bfd7fe35@huitema.net>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 14 Nov 2022 17:11:52 -0600
Message-ID: <CAC8QAcdeUvkGpoR4-dQp05cjW8QnHRVAvUkV5ASCZ=xpYG7Tfw@mail.gmail.com>
Subject: Re: Add deadline awareness to QUIC
To: Christian Huitema <huitema@huitema.net>
Cc: Chuan Ma <simonkorl0228@gmail.com>, quic@ietf.org, cuiyong@tsinghua.edu.cn
Content-Type: multipart/alternative; boundary="0000000000000fcbd205ed765e67"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kKhZRiRKTqWYIlngJqvnKeaURcQ>
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 23:12:08 -0000

On Mon, Nov 14, 2022 at 1:05 PM Christian Huitema <huitema@huitema.net>
wrote:

> 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?
>
>
I agree, this looks very much like media transmission material.

Behcet

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