Re: [tcpm] question regarding draft-gomez-tcpm-delack-suppr-reqs

Carles Gomez Montenegro <carlesgo@entel.upc.edu> Sat, 02 May 2020 08:34 UTC

Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 119C33A0ADA for <tcpm@ietfa.amsl.com>; Sat, 2 May 2020 01:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 KHyKguWIfXWf for <tcpm@ietfa.amsl.com>; Sat, 2 May 2020 01:34:24 -0700 (PDT)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79C6A3A0AD8 for <tcpm@ietf.org>; Sat, 2 May 2020 01:34:23 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by violet.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id 0428YFLo055372; Sat, 2 May 2020 10:34:15 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 21BBB1D53C1; Sat, 2 May 2020 10:34:14 +0200 (CEST)
Received: from 83.53.208.128 by webmail.entel.upc.edu with HTTP; Sat, 2 May 2020 10:34:15 +0200
Message-ID: <6b11e0a37698146c8e2bad6052634452.squirrel@webmail.entel.upc.edu>
In-Reply-To: <CAK6E8=ficYMU-r25fNLawPZ++fn6NQaa8kAznR7iCo9n0GNmPQ@mail.gmail.com>
References: <CAK6E8=dpmjf9MDQQVSkURcxnFrB3ZK_zqUDyoKs=MJgeLCeqvQ@mail.gmail.com> <23157b5e4063646449099e97eccde0f3.squirrel@webmail.entel.upc.edu> <CAK6E8=ficYMU-r25fNLawPZ++fn6NQaa8kAznR7iCo9n0GNmPQ@mail.gmail.com>
Date: Sat, 02 May 2020 10:34:15 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: Yuchung Cheng <ycheng@google.com>
Cc: jon.crowcroft@cl.cam.ac.uk, "tcpm@ietf.org Extensions" <tcpm@ietf.org>, Neal Cardwell <ncardwell@google.com>
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.100.3 at violet
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Sat, 02 May 2020 10:34:16 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/UCvEYwyRDezRHmeIot5p_1hnRH0>
Subject: Re: [tcpm] question regarding draft-gomez-tcpm-delack-suppr-reqs
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 May 2020 08:34:31 -0000

Hi Yuchung,

<snip>

>> Note that the problem pointed out is that, as stated in the RFC 5681
>> text
>> above:
>>
>>    "During slow start, a TCP increments cwnd by at most SMSS bytes for
>>     each ACK received that cumulatively acknowledges new data"
>>
>> It may be desirable to support, during slow start, a cwnd increase by
>> more
>> than SMSS per each ACK acknowledging new data.
> I agree. We in fact implemented Linux to increase cwnd by the exact
> amount sequence (in unit of packets) so slow-start increase function is
> regardless of ack-thinning effect but purely based on amount
> delivered. This has an important effect on
> Wireless as the other ack talk mentions. It also helps in case of ACK
> losses or reordering.

Agreed!

By the way, in the next draft update, we will add that, despite its
"Experimental" status, ABC is supported in many implementations.

<snip>

Thanks,

Carles