[tsvwg] Takeaways for HPCC++

"Rui, Miao" <miao.rui@alibaba-inc.com> Sun, 02 August 2020 18:21 UTC

Return-Path: <miao.rui@alibaba-inc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CAB63A0A96; Sun, 2 Aug 2020 11:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.196
X-Spam-Level:
X-Spam-Status: No, score=-0.196 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_EXCESS_BASE64=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alibaba-inc.com
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 gUycK7g91jGR; Sun, 2 Aug 2020 11:21:15 -0700 (PDT)
Received: from out0-148.mail.aliyun.com (out0-148.mail.aliyun.com [140.205.0.148]) (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 E15A33A0A94; Sun, 2 Aug 2020 11:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1596392471; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=1rjd4uS3vj1trKrGQptw56Q/yxShBuC7bG9i6hzOzaM=; b=C4/C5W1uMOHSqG95RBQAGrkcdwtoEdW/+7hxcD3XZb1pE1kafVhMrNg7cwiQz2TBlZNH7U+z4zIMi6SKgMmxeyDUnsVE1aj6cgeGh88Z8J0ngsQoD70CQAdKtTa10c0V/+gOiTD+5Zu+2Eh2RdIymy9fO26xT7xs1WBGdU7hRJI=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R781e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e01a16378; MF=miao.rui@alibaba-inc.com; NM=1; PH=DW; RN=5; SR=0; TI=W4_5948689_v5ForWebDing_0A9326C9_1596391887685_o7001c172n;
Received: from WS-web (miao.rui@alibaba-inc.com[W4_5948689_v5ForWebDing_0A9326C9_1596391887685_o7001c172n]) by e01l10414.eu6 at Mon, 03 Aug 2020 02:21:09 +0800
Date: Mon, 03 Aug 2020 02:21:09 +0800
From: "=?UTF-8?B?UnVpLCBNaWFv?=" <miao.rui@alibaba-inc.com>
To: "tsvwg" <tsvwg@ietf.org>
Cc: "tsvwg-chairs" <tsvwg-chairs@ietf.org>, "Wesley Eddy" <wes@mti-systems.com>, "=?UTF-8?B?UGFuLCBSb25n?=" <rong.pan@intel.com>, "Barak Gafni" <gbarak@mellanox.com>
Reply-To: "=?UTF-8?B?UnVpLCBNaWFv?=" <miao.rui@alibaba-inc.com>
Message-ID: <725865b7-b8a5-4099-8019-e8c43c84f9b4.miao.rui@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent][W4_5948689][v5ForWebDing][Chrome]
MIME-Version: 1.0
x-aliyun-mail-creator: W4_5948689_v5ForWebDing_NTMTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzg0LjAuNDE0Ny44OSBTYWZhcmkvNTM3LjM2XQ
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_3058_45f00940_5f270415_537d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/XIfDHgAXqOP3nxlDirUKJbSvahg>
Subject: [tsvwg] =?utf-8?q?Takeaways_for_HPCC++?=
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Aug 2020 18:21:17 -0000

Hello TSVWG members,

It was our pleasure to present HPCC++ in the IETF-108 meeting this week. We appreciate your valuable feedback. Our current draft is located at https://tools.ietf.org/html/draft-pan-tsvwg-hpccplus-01.
Here, we have summarized a list of takeaways to further improve the draft. 

1. HPCC++ is a generic congestion control scheme that works for high-speed networks. It requires to have window limit and ACK self-clocking, which is out of the definition of RoCEv2 but should instead work well for TCP/iWRAP. In addition, HPCC++ conforms to the paradigm of existing TCP congestion control, such as switch marking, receiver feedback, and sender enforcement. The major changes are using inband telemetry as the congestion feedback and it is incremental. In the next revision, we describe clearly how it works for TCP/UDP and related protocols.

2. HPCC++ works for both data centers and the Internet. We will add descriptions and results for the Internet-scale size and latency in the next revision.

Thanks again for the comments. Please feel free to let us know if you have more thoughts.

All the best,
Rui, Rong, Barak