From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 38DC13CB42 for ; Mon, 14 Nov 2022 18:19:03 -0500 (EST) Received: by mail-wm1-x336.google.com with SMTP id 5so8565166wmo.1 for ; Mon, 14 Nov 2022 15:19:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=/9bqbscKZq/AM9N+F4e4nXyRftA/1H+4ctQuWkSpbCs=; b=Z1dHXAaLIqGIG2U3ZCskheCQb2RCgh4lzHozZVW1F5t90Gd3EI8d/i3f3hxXLX1JK4 B9FJXkRPaPUoPECvrm61uXNm0i8Qz/2RGLr8CH17OSqqqfcrydvGjA19pwBuDChGN5OM 84p9NzXda25eBd28XExqRyuEO8sjqnkF60+92V98y6Ob2jsM2GxRTLCXrje+K0Ks2Lqm +rIcvja48FKnAC4Hl5A+/GQ52fxP42s+lnonL2PiGwTIcApqYlP/fKLzKVL8WHdNvHIm GQHdJPAQM8h0zv+Vu59I3NURB1et49lYoh2kPT4tFMutFSS+zFS7f1vi7hYfCd1TIdN3 a4Ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=/9bqbscKZq/AM9N+F4e4nXyRftA/1H+4ctQuWkSpbCs=; b=24GnlTPtoi83wpcyrlaAN0Ec8whjv7WgvNu+eyZVt8A90dxJls+4SxAgtA5j0KKQXC O0uMBCLEhOuzIP89vHx9lzAnin2r5eZ24gQeEI2ms5S9n+5SpXoT4/zbnoZP7bG97G47 li37bf1KDHYckLSISdDcodSj/GWmb2km7X+5iq5sTfjKMAyBdVf/XvvubTCHHmc/uV2F La/2BrG8fme8Tj9hd16QevLr7GxoPKMxLCyOQYPZGeL6kIF18xhWydrsUzn8j8h2CWFC PMAQ/6/Ml+6usmrAzZlCRdtsGMPuIiKT/p3ZJ+AkNOWNJ+VkDt/Qw4pMs1T3uid5UY3Y vzag== X-Gm-Message-State: ANoB5plsHETOqc4DX+bnTJIL89zNgcUtHdOFlZo50nqRAoJfhuRx51/1 0nIQ0d17+dSy+v1la4GK5fO4DPC7FU8/kw2ejVgz8tI18c4= X-Google-Smtp-Source: AA0mqf53mFU6VaqcZEfE92GkzsCzKd/824tL5LtDTPTPuQExzpGaHeDS5qU9Nqtac9tRX4iTA6Nl6eo0cPZCupii/8g= X-Received: by 2002:a7b:cd82:0:b0:3cf:a6e8:b59b with SMTP id y2-20020a7bcd82000000b003cfa6e8b59bmr9437760wmj.128.1668467941526; Mon, 14 Nov 2022 15:19:01 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dave Taht Date: Mon, 14 Nov 2022 15:18:49 -0800 Message-ID: To: bloat Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [Bloat] Fwd: Add deadline awareness to QUIC X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2022 23:19:03 -0000 ---------- Forwarded message --------- From: Chuan Ma Date: Mon, Nov 14, 2022 at 10:21 AM Subject: Add deadline awareness to QUIC To: Cc: 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 --=20 This song goes out to all the folk that thought Stadia would work: https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666656= 07352320-FXtz Dave T=C3=A4ht CEO, TekLibre, LLC