[tcpm] rfc8312bis: use of the term 'AIMD'

Bob Briscoe <ietf@bobbriscoe.net> Wed, 15 September 2021 13:17 UTC

Return-Path: <ietf@bobbriscoe.net>
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 9DB7C3A187A; Wed, 15 Sep 2021 06:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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=bobbriscoe.net
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 R3WIJ095gQpS; Wed, 15 Sep 2021 06:17:46 -0700 (PDT)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (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 C3B043A187E; Wed, 15 Sep 2021 06:17:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:MIME-Version:Date:Message-ID:Cc: Subject:From:To:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=CHTTJLG0nj2vIl2l2kJ0VFe6u4dxP5tZqeXhAIWN4WM=; b=QmU2cJ8gxuYDyZHJtytoC58g26 YwtNLWL1TNK7LdQ9usrzJoWgeoAyyhI71odcA63iTsmj4B7IFu68n35BcTyIjdytl1Fd0WHlxkn2p WFJHjrp501oCoISeNPCW4UzGKxcRCZs+680RF7VHEF7LJG1vDxuX7pFczP6Z32eXaI0AoRV5ZmYZu uFiBiCtqVyPesiehPc0AD82VkKhKP29d02Cyfr1Pmc20Cp4q4MBaBGS+6tIhuKJXSbJQ3npVlPScW Vm+ksXxGCKVa+iV4cydT+e6EmtlMBDo5cHvVHvj7VyuFS3BwZLlSvj9rqYllTZrcmEjIVJIUkpcFu G3l5Zw5w==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:57384 helo=[192.168.1.13]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <ietf@bobbriscoe.net>) id 1mQUnN-0061o8-1q; Wed, 15 Sep 2021 14:17:43 +0100
To: "EGGERT, Lars" <lars@netapp.com>, Vidhi Goel <vidhi_goel@apple.com>, Lisong Xu <xu@unl.edu>
From: Bob Briscoe <ietf@bobbriscoe.net>
Cc: tcpm IETF list <tcpm@ietf.org>, "draft-ietf-tcpm-rfc8312bis@ietf.org" <draft-ietf-tcpm-rfc8312bis@ietf.org>
Message-ID: <854defe0-a49b-d6ad-c242-934e5bf913b8@bobbriscoe.net>
Date: Wed, 15 Sep 2021 14:17:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------EA7364F01545D00962F72063"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/AYcFztqVPqZHj5s4UNIZmC-uAUI>
Subject: [tcpm] rfc8312bis: use of the term 'AIMD'
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: Wed, 15 Sep 2021 13:17:54 -0000

Lars, Lisong, Vidhi and co-authors,

Sorry. in the process of trying to close off the recent github issues, I 
noticed one editorial point that is prevalent throughout the document:
I think the terms 'AIMD TCP' and AIMD-friendly are inappropriate and 
would be better replaced with just 'Reno' and 'Reno-friendly', for these 
reasons:

  * AIMD describes a broad class of CC algorithms with any α and β, but
    in the Cubic draft it is always used to describe (α=1, β=0.5), which
    would surely be more specifically described as just 'Reno'.{Note 1}
  * Although Reno was only defined within the TCP wire protocol, the
    core of the algorithm is agnostic to the wire protocol, as witnessed
    by the brevity of the diffs for the variants in SCTP, etc.
  * 'Reno' would be a better (at least adequate) word to describe the
    variants in SCTP, TFRC, QUIC etc, while avoiding unnecessarily
    confusing use of the word 'TCP'.
  * On the current Internet, Cubic is very often in its 'TCP-friendly'
    mode {2}. So Cubic is very often running as an AIMD algorithm.
    Therefore I find it *really* confusing when Cubic is described as if
    it is 'other than AIMD'. People really should not think of the Cubic
    algorithm as pure Cubic mode - that creates really really bad
    intuition about how the Internet is working.


{1}: New Reno is primarily about retransmission, and only peripherally a 
congestion control difference.
{2}: See https://arxiv.org/pdf/2107.01003.pdf#page.4 for data by country 
between RIPE Atlas probes and the main global CDNs. Note however that 
the purpose of that study was to set the parameters of an AQM, so it 
assumes AQM-like queue delay. For tail-drop buffers (still unfortunately 
widespread), Cubic will more often get into true Cubic mode, at least 
for long flows. But for short and medium flows that do not have time to 
fill tail-drop buffers, this data is still likely to be relevant.

Sorry again for raising an issue after WGLC. But this terminology is 
definitely wrong, and I definitely wouldn't want it to set a precedent.


Bob


-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/