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

Martin Thomson <mt@lowentropy.net> Mon, 06 July 2020 00:41 UTC

Return-Path: <mt@lowentropy.net>
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 E40E83A0C7D for <quic@ietfa.amsl.com>; Sun, 5 Jul 2020 17:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=WVK4RKQQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=O0lZz68S
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 L54Tcg-gWIx5 for <quic@ietfa.amsl.com>; Sun, 5 Jul 2020 17:41:06 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AC543A0C7C for <quic@ietf.org>; Sun, 5 Jul 2020 17:41:06 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 28C22453 for <quic@ietf.org>; Sun, 5 Jul 2020 20:41:05 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Sun, 05 Jul 2020 20:41:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm2; bh=UbOD8 D6gN8g769mJxHqg94qciIPVB+Wkf40vinZGbGI=; b=WVK4RKQQ1RdWOSU7THgO0 yyJgJPW9rYe1jOIZL9J4kaPyUmyU68TiFr/mpmxMl6GL3V7rXXISxr39maTvChUH k3zO8dYflZMGV9cTAz93znfBQsU7Ag30OD1/G4wNEOd4L4bBL3STWCUSkWkFpUYE kT6i99PojFx83ntCLp991LpXzskg/vKbzmGuMbfQWNsnff8oEN2PUM03PTvqJHTv kC/6FapTXs8Vf4Pwe4lpOSus1LohQIjnYh2GoEiyxXG6MyaGjPO2l42rkVqz7DrO d6P2ZcDkMkuyLnGzEqZUjbUqzMSRvaY9Zmb0XniLqp66xYlcCEFBz/2JmfwuuA38 Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=UbOD8D6gN8g769mJxHqg94qciIPVB+Wkf40vinZGb GI=; b=O0lZz68SjWx03IGMdvmICIvo1i37ycgUxFC2xTJO7WEHxNdCm4v/UwJYk bCQDXVmJ6shvYvGt2VptByQM/ciiBLFSJHq18YMCOf51PdX5lV7RhwmrcdExYr7d U9+yQOqZSlDDBaw1lwhFT++SvY0bOo63uMR+DdDVMA91/gM1C0vTjCj2BeBhqYm9 +VL57Sfxw6u/+4qD5QoGph3EhX6V9y+R+3ryCI7wjq8j+WxQKLQSlS8U6BHbYGFN V1GG9T+SAMuJdWGk1EApF/0JcVoAt1Ky7gk2rLy09ShQf2/l+hdtZgBbakSe5Akl iUzbkM5zjsNsuAB18ShrQ98mSVk6Q==
X-ME-Sender: <xms:IHMCXxb6Sr0HE1tifmZ0ieI-R0Ishm8oPBdCM_h2GawQ7y68zj2Tjg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddvgdefgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpefftefgvedvhfdtffehje dufefhhfevhedufefhgfelleetieefgeefgffgleehgfenucffohhmrghinhepihgvthhf rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:IHMCX4Zb2t2ZK0hd2Y-84FT5RajuLi35J8qZ9cIOxBTux1GYJaou1g> <xmx:IHMCXz-0Gy9iO-g73bWtQbElYiQUFX2FuUEocFjqoEzc4qFJuMUCHw> <xmx:IHMCX_rEswNTFjMri2Fiw-7FkN1grHTB6Doz8pO796k0LCQoet8iCQ> <xmx:IHMCX16FLRFnPTjr1VZ8MbB_0p49Zz-ZQjyXiMwBIZna2ZjamJapRQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 68BB4E00AA; Sun, 5 Jul 2020 20:41:04 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-Id: <cd99a66b-6478-4b15-b6fc-0c512e92e118@www.fastmail.com>
In-Reply-To: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com>
References: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com>
Date: Mon, 06 Jul 2020 10:40:44 +1000
From: Martin Thomson <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7hSt5o7ZH7s5TQXhhyX2U24JguM>
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: Mon, 06 Jul 2020 00:41:08 -0000

Can you speak a little about the relationship with draft-iyengar-quic-delayed-ack ?

On Sat, Jul 4, 2020, at 16:05, Kangjiao wrote:
>  
> 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
>