Re: [tsvwg] FW: New Version Notification for draft-even-tsvwg-datacenter-fast-congestion-00.txt

"Roni Even (A)" <roni.even@huawei.com> Sun, 09 February 2020 06:52 UTC

Return-Path: <roni.even@huawei.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 3CDC01200B7 for <tsvwg@ietfa.amsl.com>; Sat, 8 Feb 2020 22:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 1KzonQNxI9Nf for <tsvwg@ietfa.amsl.com>; Sat, 8 Feb 2020 22:52:25 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 219111200B3 for <tsvwg@ietf.org>; Sat, 8 Feb 2020 22:52:25 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id B4B89200252E1EA8C22C for <tsvwg@ietf.org>; Sun, 9 Feb 2020 06:52:21 +0000 (GMT)
Received: from DGGEMM422-HUB.china.huawei.com (10.1.198.39) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 9 Feb 2020 06:52:20 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.174]) by dggemm422-hub.china.huawei.com ([10.1.198.39]) with mapi id 14.03.0439.000; Sun, 9 Feb 2020 14:52:15 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>
CC: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] FW: New Version Notification for draft-even-tsvwg-datacenter-fast-congestion-00.txt
Thread-Index: AQHV2+tNCUTbW4oGekaKJH6Wht6FXagMHytQ///9yACABlXc0A==
Date: Sun, 9 Feb 2020 06:52:15 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD27D82EB8@DGGEMM506-MBX.china.huawei.com>
References: <6E58094ECC8D8344914996DAD28F1CCD27D76B44@dggemm526-mbx.china.huawei.com> <202002051406.015E6OEE097443@gndrsh.dnsmgr.net>
In-Reply-To: <202002051406.015E6OEE097443@gndrsh.dnsmgr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/zApGgFpjzsGfQ0xDRDsW0UMICXk>
Subject: Re: [tsvwg] FW: New Version Notification for draft-even-tsvwg-datacenter-fast-congestion-00.txt
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, 09 Feb 2020 06:52:27 -0000

Hi Rod,
Thanks, I missed having a reference, will add it
Roni Even

> -----Original Message-----
> From: Rodney W. Grimes [mailto:ietf@gndrsh.dnsmgr.net]
> Sent: Wednesday, February 05, 2020 4:06 PM
> To: Roni Even (A)
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] FW: New Version Notification for draft-even-tsvwg-
> datacenter-fast-congestion-00.txt
> 
> > Hi,
> > We submitted this new draft based on the offline discussions in the last
> IETF meetings. We thank all the people who commented so far.
> > It propose a network based solution and provides initial tests results. We
> intend to run more tests and update the document accordingly.
> >
> > Please review and comment
> 
> I see several references to ECN and CE marks yet no normative referecne to
> RFC3168 that defines these terms, nor any reference to RFC8257 which
> modifies the symatics of ECN signalling defined in RFC3168.  Could you add
> clarifying language please?
> 
> Regards,
> Rod Grimes
> 
> > Roni Even
> >
> > -----Original Message-----
> > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > Sent: Wednesday, February 05, 2020 8:13 AM
> > To: Liumengzhu; zhangyali (D); Roni Even (A)
> > Subject: New Version Notification for draft-even-tsvwg-datacenter-fast-
> congestion-00.txt
> >
> >
> > A new version of I-D, draft-even-tsvwg-datacenter-fast-congestion-00.txt
> > has been successfully submitted by Roni Even and posted to the IETF
> repository.
> >
> > Name:		draft-even-tsvwg-datacenter-fast-congestion
> > Revision:	00
> > Title:		Data Center Fast Congestion Management
> > Document date:	2020-02-04
> > Group:		Individual Submission
> > Pages:		10
> > URL:            https://www.ietf.org/internet-drafts/draft-even-tsvwg-
> datacenter-fast-congestion-00.txt
> > Status:         https://datatracker.ietf.org/doc/draft-even-tsvwg-datacenter-
> fast-congestion/
> > Htmlized:       https://tools.ietf.org/html/draft-even-tsvwg-datacenter-fast-
> congestion-00
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-even-tsvwg-
> datacenter-fast-congestion
> >
> >
> > Abstract:
> >    A good congestion control for data centers (DC) should provide low
> >    latency, fast convergence and high link utilization.  Since multiple
> >    applications with different requirements may run on the DC network it
> >    is important to provide fairness between different applications that
> >    may use different congestion algorithms.  An important issue from the
> >    user perspective is to achieve short Flow Completion Time (FCT).
> >    This document proposes data center congestion control direction
> >    aiming to achieve high performance while proving fairness.
> >
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at tools.ietf.org.
> >
> > The IETF Secretariat
> >
> >
> >