IETF Logo Mail Archive

Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00

Kangjiao <kangjiao@huawei.com> Sat, 04 July 2020 06:05 UTC

Return-Path: <kangjiao@huawei.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 6428E3A0BCE; Fri, 3 Jul 2020 23:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQOZiDBoCDNw; Fri, 3 Jul 2020 23:05:41 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B6B03A0BCB; Fri, 3 Jul 2020 23:05:41 -0700 (PDT)
Received: from lhreml737-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E5A914C82814C1684A53; Sat, 4 Jul 2020 07:05:38 +0100 (IST)
Received: from lhreml737-chm.china.huawei.com (10.201.108.187) by lhreml737-chm.china.huawei.com (10.201.108.187) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Sat, 4 Jul 2020 07:05:38 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml737-chm.china.huawei.com (10.201.108.187) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Sat, 4 Jul 2020 07:05:38 +0100
Received: from DGGEMM534-MBS.china.huawei.com ([169.254.7.44]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0487.000; Sat, 4 Jul 2020 14:05:28 +0800
From: Kangjiao <kangjiao@huawei.com>
To: "quic@ietf.org" <quic@ietf.org>
CC: "quic-chairs@ietf.org" <quic-chairs@ietf.org>, "Litong (2012 Labs)" <li.tong@huawei.com>
Subject: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Topic: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Index: AdZRyGcTBCKzXYE+TnatOw5glQUhXg==
Date: Sat, 04 Jul 2020 06:05:28 +0000
Message-ID: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.86.35]
Content-Type: multipart/alternative; boundary="_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04dggemm534mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zCVg5eySzaXajO5O-JEbpO4ZGSA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 04 Jul 2020 06:05:44 -0000

Dear QUIC WG members,


We uploaded a draft describing a mechanism for ACK optimization to QUIC group. The link is https://datatracker.ietf.org/doc/draft-li-quic-optimizing-ack-in-wlan/. This solution comes from our practice and the results show it is a good replacement of the traditional ACK mechanism to compensate for scenarios where the acknowledgement overhead is non-negligible (i.e., wireless scenarios).



The key points for this solution can be:



1. We conclude the formula of the minimum ACK intensity required for QUIC transport.



2. In order to alleviate the error in RTT estimation, we use protocol extensions and a one-way delay factor. We think this round-trip timing method can also be applicable for the ack thinning mechanisms (such as "Changing the Default QUIC ACK Policy" #3529) that have been discussed in QUIC group.



3. For implementation and interoperability, we define a new ACK-INTENSITY Frame in which ACK Intensity is set. ACK Intensity is a variable-length integer indicating the updated intensity of QUIC ACK Frame calculated by our formula.



We look forward to your valuable comments and suggestions. Thanks.

Sincerely,
Jiao

v2.23.0 | Report a Bug | By Email