Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

Huaimo Chen <huaimo.chen@futurewei.com> Thu, 21 May 2020 03:59 UTC

Return-Path: <huaimo.chen@futurewei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5363A0A83 for <lsr@ietfa.amsl.com>; Wed, 20 May 2020 20:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, T_REMOTE_IMAGE=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 tg6lgAMGPiIx for <lsr@ietfa.amsl.com>; Wed, 20 May 2020 20:59:14 -0700 (PDT)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2119.outbound.protection.outlook.com [40.107.92.119]) (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 CEE513A0A87 for <lsr@ietf.org>; Wed, 20 May 2020 20:59:13 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LtblJkgJUfWPu7IdTTVZu8/2ORatf4EmHp0B0YeUogcPPOXcsnQMSlaA9twCJyEkKn/SeghKwEvwBP6cTiWsrjTG64lE/dFHyHAAAq54zgRHAz4oOswNJzgF88mbj/xR16NzZPk2MR7HIIYJRyTADNeiZ2hdFeEgcMoT1zAv3pocaG0hSmNkNL1X/5YY8laJbOKshGdeqNkTepYNH2Ml1r2rRrrMIyWt5lCuK8RUMOqBwJJj0KcyFQLVT+K1lYjhWFmv+ObkxL6Pv/3ZRHiuvAExv9h6sEMU1mYvI7Qg/m5H02wgTcnuTfgkbndxYg8qU2LzU1eOPcju8IyP/bz+bA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rfA2mfdpFInSLDLTHoJStj5z0qthKtrOmBglcJUhWp8=; b=jInAYJaz6tkSzgPDFIKHpd02jD6DNhSRtMwQ3HSgp7JmMO3iHbvdH7M1/l1lZW23DKOzci80zBKkD/yp1lDKB2hkezyULf1O52IQ8SfH9/k4GQnd7migXAwNNqQWpvymy6FtaulMshqmwmk67poStQjDJ20I1MB/1ShCcJq0Blxpzz7gevfZ6phBFWLMkMyvztbjKh7VivB2KxtYlWf/eawMHs34LQmTZKj9sP/sY1EKPO/Qbse3X6Rz1b+aHMPfhWfPK29Uoqj8h82j7m0El+QSHFeicA+aEE6V/k5jv7YwiETst1kWZCj2OCRTUhlPvxxYJ6s+TrKcxGxmeAj5Tg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rfA2mfdpFInSLDLTHoJStj5z0qthKtrOmBglcJUhWp8=; b=ORAhGrwLkEww4ri5UM/4xhUDISAl6Tp3YQXKBoSr6nCFdDrJKBWgRdSsaVWtIztKRKEFKSr+AaSs3UJ8WTNG7B5BTLSgNvPu6KE87ZlervFPxfJEZfq5Cx/c4E0aG1A94xnj3Du6p1VCHGQE6L+g+drWNqHpw19JktjQHOxcs+A=
Received: from MN2PR13MB3117.namprd13.prod.outlook.com (2603:10b6:208:13a::20) by MN2PR13MB2829.namprd13.prod.outlook.com (2603:10b6:208:f7::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.11; Thu, 21 May 2020 03:59:09 +0000
Received: from MN2PR13MB3117.namprd13.prod.outlook.com ([fe80::d5b6:8550:9c40:eec2]) by MN2PR13MB3117.namprd13.prod.outlook.com ([fe80::d5b6:8550:9c40:eec2%7]) with mapi id 15.20.3021.019; Thu, 21 May 2020 03:59:09 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
CC: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call
Thread-Index: AQHWKvCWbO+rNwui80Sty0q3wo/aI6iuQDRQgAC6fICAAVrmiIAAx0uAgADIYX8=
Date: Thu, 21 May 2020 03:59:09 +0000
Message-ID: <MN2PR13MB3117E84C778B11D71FAF8135F2B70@MN2PR13MB3117.namprd13.prod.outlook.com>
References: <63330FD6-EDE8-4938-AA85-948279C57E34@cisco.com> <DM6PR06MB509842BA0E42A4938ACB2B94EEB80@DM6PR06MB5098.namprd06.prod.outlook.com> <CABNhwV3jQ=C6ynJBsKhJW_b=hkq7CKPFG2ci0vXE_0jZH9KtXQ@mail.gmail.com> <MN2PR13MB3117C43CA052E4E29D7428CBF2B60@MN2PR13MB3117.namprd13.prod.outlook.com>, <CABNhwV2Y3kemTdHYBamZwAB+m5DefxqTC0shPan2cGHd9TARTg@mail.gmail.com>
In-Reply-To: <CABNhwV2Y3kemTdHYBamZwAB+m5DefxqTC0shPan2cGHd9TARTg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [2601:199:4300:8e5a:9ae:b16d:5e4c:325e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: dae65ad8-6561-443c-8c80-08d7fd3b50da
x-ms-traffictypediagnostic: MN2PR13MB2829:
x-microsoft-antispam-prvs: <MN2PR13MB2829E3DFE02CA5213783F796F2B70@MN2PR13MB2829.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 041032FF37
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: S3fbf+9d7AQVoFNe/HjZGjEPbvEX7YFFrwghJLk9gZjniHSVDvSKXFJDNL5EjYqSVEFowfCGBCl4y3kxac+HpJV8aXay3kCMiKZK5nCM5DJIRYSnPsJ4lfJn04l9Mtvxq/29zsjHQSqVxA3wBMMq7opujuROORwT+pm3SLtD2lL9txJsIwgZEZ37kO2mjD3+8c3dIBjIDWDr9Dhwn5mpYnvAVKdVQVlp/a/DqRUa9B+5T1RPkBXQTQdvi33CtEDMAuUOGNrSjtTfMmjln9koxMpNqHPHdHRKvP2Z+zz1zcAFrzofx8HdFqYmW1GN7Cqzfm1sdcAmmpo4IAj0J2bpmI4eLJ5RdY/yh3cIW0tD4Ra6F3C6HfGAZcFPsiRQr9GRhaW1575wq8aAcb8iqpsBXw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR13MB3117.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(136003)(396003)(366004)(376002)(39840400004)(346002)(478600001)(7696005)(53546011)(316002)(966005)(6506007)(4326008)(54906003)(166002)(33656002)(44832011)(52536014)(186003)(2906002)(8936002)(71200400001)(19627405001)(5660300002)(8676002)(6916009)(66946007)(76116006)(55016002)(86362001)(66556008)(66446008)(64756008)(66476007)(9686003); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: 9GnVpgeYmmYonteVbX5/7hNyc/qTVYVDz87htlaeGLNmLgDtHdy3DcoD4CGwcVaptCPUNbA08ocwv1IDTzK3vzjEJiuuZmZ4Y7Yh7Glc3tmpKIqYhz9tNn2az0VeDGTuIQHrtC0mGjMdXUsInXpqxlO4lK+0OVHTp0TJ+bW8jbtWElYUrLklRcQu+bukamjrKs/IoBP8kvU+9+MlL6woug11DhV9kg9rzbnqFonT7EdwI9ypw44VcbUH+ivKUhNkYOeFIpMNlHVv7VGbXgpXDDNx5iHad5L7QX6XA9DiZEpNrvSYRbLpNsN2aPoUFkRlEz8cDkaxW6FwjM0r+1iOMmycxPajJuI+gELHm9IbdOkBTY4h/Qmk/XtAXFt+yKSVH4PG2xyNb8ML6d8A6th4ysm6ofYWD/mjGEc3Ky1XGI7Vqtu5548Ar6qTpY4jqlBC4awcb9L8Y5qt8KGi1iSkDJtrqdPEtJcx6Ay+9C73xZoBDuSqXEzHqijalFGSmUBI63ik1zW3U2t5guEr8EAd60wlT8VEMD4ixHj7gX8+WZg=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3117E84C778B11D71FAF8135F2B70MN2PR13MB3117namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: dae65ad8-6561-443c-8c80-08d7fd3b50da
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2020 03:59:09.6223 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 9yPw1MPOrwNWkeiA0tpFOVpQGThEoFTya64kiKgP9/EN9GrMGmW+uHSoghkcYfXtraw5YNfXgbfHPapImvcThQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB2829
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/3zVhutGG0H1yBGTedab3heeiHJM>
Subject: Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2020 03:59:17 -0000

Hi Gyan,

    Thanks much for your questions. My answers are inline below with [HC].

Best Regards,
Huaimo
________________________________
From: Gyan Mishra <hayabusagsm@gmail.com>
Sent: Wednesday, May 20, 2020 11:14 AM
To: Huaimo Chen <huaimo.chen@futurewei.com>
Cc: Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org>rg>; lsr@ietf.org <lsr@ietf.org>
Subject: Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

Huaimo

This is a much needed feature that operators have been needing for densely meshed topologies that commonly exist in data centers to accommodate very high bandwidth E-W traffic.
[HC]: Thank you very much.

Below is link from Cisco which has introduced feature for dynamic flooding in clos high density ECMP data center topologies.

Please look at the feature description and it does seem to be exactly the same as this draft.  Please confirm.
[HC]: It seems different.

There maybe other vendors due to industry demand have to get the feature deployed before it reaches standards vendor consensus with the IETF.

https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/white-paper-c11-743015.html<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Fproducts%2Fcollateral%2Fswitches%2Fnexus-9000-series-switches%2Fwhite-paper-c11-743015.html&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949669307&sdata=9nLFlmBSFxBQayL0fCiq864Ylvzyksk3U0GmZPbhPts%3D&reserved=0>

We are testing this feature and planning to deploy but wanted to ensure that this is the same as the draft on the standards track.
[HC]: The feature appears implemented draft "Dynamic Flooding on Dense Graphs", which does not include any flooding topology computation algorithm.

Kind regards

Gyan


On Tue, May 19, 2020 at 11:52 PM Huaimo Chen <huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>> wrote:
Hi Gyan,

    Thank you very much for your questions and support.

    This Flooding Topology Computation algorithm can be used in the Dynamic Flooding on Dense Graphs to compute the flooding topologies for the data center clos dense meshed topologies with many ECMP paths. It can be used by the area leader in the centralized mode to compute the flooding topology.

Best Regards,
Huaimo
________________________________
From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> on behalf of Gyan Mishra <hayabusagsm@gmail.com<mailto:hayabusagsm@gmail.com>>
Sent: Tuesday, May 19, 2020 2:39 AM
To: Yanhe Fan <yfan@casa-systems.com<mailto:yfan@casa-systems.com>>
Cc: lsr@ietf.org<mailto:lsr@ietf.org> <lsr@ietf.org<mailto:lsr@ietf.org>>; Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>>
Subject: Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call


I support WG adoption and have a few questions related to the draft.

Does this flooding algorithm use the dynamic flooding algorithm used in data center clos dense meshed topologies with many ECMP paths where the flood is decoupled from the physical topology.  In the dynamic flooding algorithm mentioned in centralized mode the flooding is computed by the area leader and distributed to all nodes.  In distributed mode each mode the area leader determines the algorithm and then each node computes the flooding topology based on the algorithm.

This dynamic algorithm for optimized flood reduction would reduce the amount of redundant flooding in highly densely meshed ospf or Isis topologies.  So this optimization of flooding would improving overall link state routing protocol convergence.

Gyan

On Mon, May 18, 2020 at 3:37 PM Yanhe Fan <yfan@casa-systems.com<mailto:yfan@casa-systems.com>> wrote:

Support it as a co-author.



Thanks,

Yanhe



From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of Acee Lindem (acee)
Sent: Friday, May 15, 2020 3:40 PM
To: lsr@ietf.org<mailto:lsr@ietf.org>
Subject: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call



This begins a 3 week (due to holidays) WG adoption call for the “Flooding Topology Computation Algorithm” draft. Please issue your support or objection to this list by 11:59 PM, UTC on June 5th, 2020. Here is a URL for your convenience.



https://datatracker.ietf.org/doc/draft-cc-lsr-flooding-reduction/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-cc-lsr-flooding-reduction%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949679298&sdata=08cwC5X8u06cotUPxaWyOq3euYKGK9Pfh0pieb7Tqf0%3D&reserved=0>



Thanks,
Acee

_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949679298&sdata=tyTKAAIC3DyLtli74eDEYNscLfuULnvGwGUu25BeuBA%3D&reserved=0>
--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949689289&sdata=PPAEeVtUFf4l1J46AvbBRXWE6zymmTpZls6wSTCY5bI%3D&reserved=0>
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fmaps%2Fsearch%2F13101%2BColumbia%2BPike%2B%250D%250A%2BSilver%2BSpring%2C%2BMD%3Fentry%3Dgmail%26source%3Dg&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949689289&sdata=0lc7p9qzWy1VsJxX2ig1%2BHJWNHMfqWeyBBLf7wUCsV4%3D&reserved=0>

Gyan Mishra

Network Solutions Architect

M 301 502-1347
13101 Columbia Pike<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fmaps%2Fsearch%2F13101%2BColumbia%2BPike%2B%250D%250A%2BSilver%2BSpring%2C%2BMD%3Fentry%3Dgmail%26source%3Dg&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949699284&sdata=eZ%2BBnU124L7SGnc%2BQURZRhNmbMYvBMNTGG0to0%2BiuR8%3D&reserved=0>
Silver Spring, MD<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fmaps%2Fsearch%2F13101%2BColumbia%2BPike%2B%250D%250A%2BSilver%2BSpring%2C%2BMD%3Fentry%3Dgmail%26source%3Dg&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949699284&sdata=eZ%2BBnU124L7SGnc%2BQURZRhNmbMYvBMNTGG0to0%2BiuR8%3D&reserved=0>

--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7Caf6069f07e9c4b9b881508d7fcd08b26%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637255844949699284&sdata=%2FoV6iULRSggdYhbq%2FJosVJeUYYufjIKeQ3hTIjEzRfk%3D&reserved=0>

Gyan Mishra

Network Solutions Architect

M 301 502-1347
13101 Columbia Pike
Silver Spring, MD