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

Christian Huitema <huitema@huitema.net> Mon, 06 July 2020 21:07 UTC

Return-Path: <huitema@huitema.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 EA3FF3A0AD9 for <quic@ietfa.amsl.com>; Mon, 6 Jul 2020 14:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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 JjsCMWSfriuQ for <quic@ietfa.amsl.com>; Mon, 6 Jul 2020 14:07:57 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 EF9CB3A0AD8 for <quic@ietf.org>; Mon, 6 Jul 2020 14:07:56 -0700 (PDT)
Received: from xse371.mail2web.com ([66.113.197.117] helo=xse.mail2web.com) by mx36.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jsYKu-00074b-86 for quic@ietf.org; Mon, 06 Jul 2020 23:07:51 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4B0ynH2rD8z6FB2 for <quic@ietf.org>; Mon, 6 Jul 2020 14:07:15 -0700 (PDT)
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jsYKZ-0008EO-8z for quic@ietf.org; Mon, 06 Jul 2020 14:07:15 -0700
Received: (qmail 22268 invoked from network); 6 Jul 2020 21:07:15 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.46.187]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 6 Jul 2020 21:07:14 -0000
To: Kangjiao <kangjiao@huawei.com>, Martin Thomson <mt@lowentropy.net>
Cc: "quic@ietf.org" <quic@ietf.org>
References: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com> <cd99a66b-6478-4b15-b6fc-0c512e92e118@www.fastmail.com> <719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFD@dggemm534-mbs.china.huawei.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Subject: Re: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Message-ID: <98c0a7a0-2dfa-a327-33d3-5c337c390fd2@huitema.net>
Date: Mon, 06 Jul 2020 14:07:14 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFD@dggemm534-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------9DAEB3FD897038C12194E73F"
Content-Language: en-US
X-Originating-IP: 66.113.197.117
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0f6LF1GdvkEexklpcFpSF5apSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59ftlPGAYnoChmvr7MHhb7Z5TU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+7KJix/R2qbtdH2ZflMjNgfX2XX9bIsGDSYq5OAASmskY6jSvfpO+1kZkomjtjB6X5Q5Q9f RUeIpTIC2ySfqvnqLwoxlgatmaBb0rBiK9xbkDrUqzcKIief90MVLZY9LbIZh9+IQ1oS9LBn3VIP 95Jz7ujRlJ9wSMlhvaudJXZ9EIBG/qaR+8r9SKFMmPJLf850OvZYsmoVQuOIhwKLK6IKBNB4LZ0v UHHKTzJX7b1JhLSQQ4vSj0QEim26t/Moy0UPX5E73H1QfrH/5kkrV/Cr0bm2vWdo8usP65i82q1C dZgGrpL44wdx9eXqjQjbvUopOMQJvQ/Ck3iiU+4DQAj3fuQgzT3K9JUHTNiGwfwAmxx/Wk8McinP JEkgAVrOMpYt4o3CgqJq+7GLH3LDcCCXn4KxIMmLKkg5fu+h86FP7+F98Qs+KGQ0tfoeDSAfzCMv UwPy3x0FYtCNEb10sHyQCLHEvD1OqP6bgZ4L66GcgBg66gs5OuzYxJgw5atIxeNDvjI/CYe5WPy0 +t1RP0azWadFjuzwPVVLsuYPIFYAx5xMPnetLBJMh51NiRRoHICAC6iPKDrKIWN2yNyuqa9KmiK7 x42VjdzChZMe6O/Did+/hGXTmfhE+Dx2/NyzMXo75ntICbS+BvGEZ0Xy7wYWvOnCUbNPgcPcQwzM gKHyQxUo+ql2ySTkvEFH/23XMww2BnTTFGX5/yI4Ky+1ZJcbGqc5H4PEZHeoI/d6LWFf332z7LMw LGdoi9FMQ5j9dQUvMi1YKAun15JQSJLyCT5k+MTObVKxHy/dols381l9r9ft9daDonlwd6LnuX+J u10=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iEeZvuJjUgi637WI9hS-E82vs3M>
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 21:08:00 -0000

Hello Jiao,

Your draft is motivated by specific data about running high bandwidth
applications over wireless local area network. It would be interesting
to compare behavior of these applications using different
acknowledgement policies, probably using simulations. Do you have
definitions of the application and of the WLAN that we could enter in
simulations?

The draft draft-iyengar-quic-delayed-ack-00 provides a way for senders
to specify both the maximum delay between acknowledgements and the
maximum number of packets between acknowledgement, with receivers
sending acknowledgements when one of the conditions is true. Several
servers set the delay to a fraction of the RTT, and the number of
packets to a corresponding fraction of the number of packets per
congestion window -- RTT/8 is often suggested. How is that different
from setting the "ACK intensity" suggested in
draft-li-quic-optimizing-ack-in-wlan-00?

The draft draft-li-quic-optimizing-ack-in-wlan-00 mentions using one way
delay measurements. Is that a reference to draft-huitema-quic-ts-00 ?

-- Christian Huitema

On 7/6/2020 7:35 AM, Kangjiao wrote:
>
> Dear Martin,
>
>  
>
> Here are the two drafts:
>
> draft-li-quic-optimizing-ack-in-wlan-00:
> https://tools.ietf.org/html/draft-li-quic-optimizing-ack-in-wlan-00  
>
> draft-iyengar-quic-delayed-ack-00:
> https://tools.ietf.org/html/draft-iyengar-quic-delayed-ack-00
>
>  
>
> I have outlined some distinction and connection between these two drafts:
>
>  
>
> a)       Both draft-li-quic-optimizing-ack-in-wlan-00 and
> draft-iyengar-quic-delayed-ack-00 propose a solution to reduce the ACK
> frequency for QUIC. draft-iyengar-quic-delayed-ack-00 makes the two
> parameters in delayed ACK, i.e., "Packet Tolerance" and "Max Ack
> Delay", be tunable by the sender. These two tunable parameters do not
> include RTT as a factor. Sara Landstrom et al. [1] has demonstrated
> that, in theory, the endpoint should acknowledge data at least twice
> per send window (RTT) to ensure utilization. In this case, reducing
> ACK frequency without considering the RTT as a factor of Max Ack
> Delay, might cause performance issues. On the other hand, the purpose
> in draft-li-quic-optimizing-ack-in-wlan-00 is to minimize the ACK
> frequency required by the transport, thus the ACK frequency is
> computed as *MIN*{bw/(packet_tolerance *max_packet_size), beta/RTTmin}
> (beta indicates the number of ACKs per RTT). While
> draft-iyengar-quic-delayed-ack-00 adopts the extended delayed ACK as
> specified in the legacy TCP, whose ACK frequency is computed as
> *MAX*{bw/( packet_tolerance *max_packet_size), 1/ max_ack_delay}. A
> paper [2] (to be appeared in SIGCOMM2020) has demonstrated that using
> a *MIN* instead of a *MAX* can also achieve equally good performance.
>
>  
>
> b)       draft-iyengar-quic-delayed-ack-00 provides a way for the
> sender to customize the ACK frequency. This means the ACKs might be
> excessively delayed when the Max Ack Delay is large. When sending
> fewer ACK frames, many data packets might be received during the ACK
> interval, generating only one RTT sample among multiple packets is
> likely to result in biases. For example, a larger minimum RTT
> estimate. In draft-li-quic-optimizing-ack-in-wlan-00, we propose a
> one-way-delay-based method to compute the minimum RTT more accurately.
> Apart from the ACK scheme, this is another point that we would like to
> discuss and get feedback from QUIC WG.
>
>  
>
> c)       With some minor extensions such as adding one more field of
> ACK-INTENSITY, the proposed ACK scheme in
> draft-li-quic-optimizing-ack-in-wlan-00 may be able to reuse the
> ACK-FEQUENCY frame specified in draft-iyengar-quic-delayed-ack-00 to
> sync the ACK intensity between sender and receiver.
>
>  
>
> Some reference mentioned above:
>
> [1] Sara Landstrom and Lars-Ake Larzon. 2007. Reducing the TCP
> acknowledgment frequency. ACM SIGCOMM CCR 37, 3 (2007), 5–16.
>
> [2] Tong Li, Kai Zheng, Ke Xu, Rahul Arvind Jadhav, Tao Xiong, Keith
> Winstein, Kun Tan. "TACK: Improving Wireless Transport Performance by
> Taming Acknowledgments", ACM SIGCOMM, 2020. (
> http://www.thucsnet.org/uploads/2/5/2/8/25289795/tong_sigcomm20.pdf )
>
>  
>
> Best Regards,
>
> Jiao
>
>  
>
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Martin Thomson
> Sent: Monday, July 6, 2020 8:41 AM
> To: quic@ietf.org
> Subject: Re: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
>
>  
>
> 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
>
> > 
>
>  
>