Add deadline awareness to QUIC
Chuan Ma <simonkorl0228@gmail.com> Mon, 14 November 2022 18:20 UTC
Return-Path: <simonkorl0228@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 46BF5C14F721 for <quic@ietfa.amsl.com>; Mon, 14 Nov 2022 10:20:54 -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 28fuZPJAlDYg for <quic@ietfa.amsl.com>; Mon, 14 Nov 2022 10:20:51 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 EF35CC14F692 for <quic@ietf.org>; Mon, 14 Nov 2022 10:20:51 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id p184so8801539iof.11 for <quic@ietf.org>; Mon, 14 Nov 2022 10:20:51 -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:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=eZ9Ne4WEhDut14IzqnpryD8BunTPTjQwlwS70600jTI=; b=hXAiHYF4i2nKHCLEeBqqEWtuk3QDU9087bZ4Slo5+Csgs1ARwi1Em2n1VCSOa1QV+7 56LCnoRKafg+Z6kBHUqTKbS+KpvEzW8kjw1vchYI2xY2kIdAWhqoi+LzNPTW2Bgjxp5K aJ+2HoZyrbRJ4Me0c0Thw8Qt0D5xNoldQIAgscHfBnMnfsnAYEOB6hTtVWH+jsICwrkN 2ntTtSUQxneF/YLb7Va6gZxar2kgV2oMx4Yqki+3n87pHXbi6QyrqKTx9jTniiOy1V/B oUYc0qYrW8wpEEOviyRYsemKOwFDYafneLMqO142SokAlruJiXVGF9QVmkHF3w61G9q1 ZQtg==
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:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=eZ9Ne4WEhDut14IzqnpryD8BunTPTjQwlwS70600jTI=; b=Efnww+3J66FdI2YXstx5Kpo1x5Of84f3wvnyr7jtCvgYw74tLIVvLvkF2BIw+Putl0 oQymKNk28YPyWOqqFaYcSRWRbxq0m7NqhPbiykC0s8bSL5lAP2WFBEEfkAnrT8zFTcZt N/WI5F8ddKtlv1uHUFDpLgXcYmfv4goVkpSmqvghiWfpN0gI4wKPURhLatXRSs/lSMXy kONsztnQGVjhXoxvfYyIftG1cwb1vdU5KqeCylzZ77qSmn26NEamDpgNJpi+dlKJufd1 HHyzsvmza74vwSbw3vq10yipMx6AmFDwB37EhN5GO8o13cBvBWkA/Se8149jQd6veR0P htXg==
X-Gm-Message-State: ANoB5pl7kDkzr+W3yz/mB0bdOwjIgoidteqiCjOaQE1kcjOwxj3O9dtc Jlm+ExE0cMkoeJP1v+ZKjwL+qfHgXbzvKJl5q9HLL6mS+HK+rQ==
X-Google-Smtp-Source: AA0mqf7fsnDtvWJf2T3h5HFJSnTvad39IdVsSCrICsDn9MsZ+CwihgDC+7eRSjcZdJT1Rh8MhC3khLELtCsNt3EL0OE=
X-Received: by 2002:a6b:3c0f:0:b0:6cc:a195:ce8f with SMTP id k15-20020a6b3c0f000000b006cca195ce8fmr5913286iob.18.1668450050800; Mon, 14 Nov 2022 10:20:50 -0800 (PST)
MIME-Version: 1.0
From: Chuan Ma <simonkorl0228@gmail.com>
Date: Tue, 15 Nov 2022 02:20:41 +0800
Message-ID: <CAAZo2nGK_HPbRKhW7fk8cBbZ5Y8HJOf737COKoFy=Xc6XHoL9g@mail.gmail.com>
Subject: Add deadline awareness to QUIC
To: quic@ietf.org
Cc: cuiyong@tsinghua.edu.cn
Content-Type: multipart/alternative; boundary="0000000000009a85b805ed724c5b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ie6Ju6cNCocNNktldJJrvZfsXQ8>
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 18:20:54 -0000
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
- Add deadline awareness to QUIC Chuan Ma
- Re: Add deadline awareness to QUIC Christian Huitema
- Re: Add deadline awareness to QUIC Behcet Sarikaya
- Re: Add deadline awareness to QUIC Chuan Ma
- Re: Add deadline awareness to QUIC Ian Swett
- RE: Add deadline awareness to QUIC Shihang(Vincent)
- Re: Add deadline awareness to QUIC Ian Swett
- Re: Add deadline awareness to QUIC François Michel
- Re: Add deadline awareness to QUIC Michael Welzl
- RE: Add deadline awareness to QUIC Shihang(Vincent)
- RE: Add deadline awareness to QUIC Shihang(Vincent)
- RE: Add deadline awareness to QUIC Shihang(Vincent)
- Re: Add deadline awareness to QUIC Michael Welzl