[iccrg] introducing draft-even-iccrg-dc-fast-congestion

"Roni Even (A)" <roni.even@huawei.com> Tue, 29 October 2019 06:34 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA4B71200B8 for <iccrg@ietfa.amsl.com>; Mon, 28 Oct 2019 23:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 0_MxQSZCc-HA for <iccrg@ietfa.amsl.com>; Mon, 28 Oct 2019 23:34:46 -0700 (PDT)
Received: from huawei.com (szxga08-in.huawei.com [45.249.212.255]) (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 53947120020 for <iccrg@irtf.org>; Mon, 28 Oct 2019 23:34:46 -0700 (PDT)
Received: from DGGEMM403-HUB.china.huawei.com (unknown [172.30.72.57]) by Forcepoint Email with ESMTP id 4ABEA89C33DA0094FE7B for <iccrg@irtf.org>; Tue, 29 Oct 2019 14:34:40 +0800 (CST)
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.58]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0439.000; Tue, 29 Oct 2019 14:34:37 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: iccrg IRTF list <iccrg@irtf.org>
Thread-Topic: introducing draft-even-iccrg-dc-fast-congestion
Thread-Index: AdWOIXQP9Tl8qH4zTESH2RWKfZGb7Q==
Date: Tue, 29 Oct 2019 06:34:36 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD23D9DC0C@dggemm526-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.54]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD23D9DC0Cdggemm526mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/OeaXLVPQE0J-EikQ10lnEWQdlio>
Subject: [iccrg] introducing draft-even-iccrg-dc-fast-congestion
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2019 06:34:48 -0000

Hi,
We submitted the draft after discussing the topic of better congestion control for Data Centers in the last IETF meeting.
The objective was to look at current congestion control mechanisms and propose a possible direction for DC CC.

The direction that looks promising to us is to reflect the network status more accurately taking into account that we are talking about a single DC domain.

We are looking for feedback if this direction looks promising and if there is an interest in working on this direction. The draft have some open questions that need to be addressed.

Please review the draft and provide feedback.

Thanks
Roni Even