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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 27 May 2020 17:49 UTC

Return-Path: <ginsberg@cisco.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 3461F3A0797 for <lsr@ietfa.amsl.com>; Wed, 27 May 2020 10:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 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_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=LGiVU3Zv; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=u4D+mcO3
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 R7tE4KzGAjFe for <lsr@ietfa.amsl.com>; Wed, 27 May 2020 10:49:34 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 550CA3A064C for <lsr@ietf.org>; Wed, 27 May 2020 10:49:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11323; q=dns/txt; s=iport; t=1590601770; x=1591811370; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gZhIJPI9nBz5jTPNBI76nDpTQlnO9ysCklY7JSIXO18=; b=LGiVU3ZvaaTifOkDXUnsTRWAZn8ncyzK/8KVPBSG5NuFSrjyxZHSWiUx DNxGtbHky9okiLi4BGE+9QNDOliSzzREe7sqgTSP8PcmZjEliuLs1ixlw 1Nsd2YSZXnwW+GXYxftb40+52PfKeI0LRHyMxHaHd4ICpyS933ZdvTTJL s=;
IronPort-PHdr: =?us-ascii?q?9a23=3Ab7eLrRHYySyMxmuFeJC3qJ1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e401QebQYLd+rRAirmev6PhXDkG5pCM+DAHfYdXXh?= =?us-ascii?q?AIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtJH8DvIVnT8TW+6DcIEU?= =?us-ascii?q?D5Mgx4bu3+Bo/ViZGx0Oa/s53eaglFnnyze7R3eR63tg7W8MIRhNhv?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DZAQAsp85e/40NJK1mGwEBAQEBAQE?= =?us-ascii?q?BBQEBARIBAQEDAwEBAUCBSoEhL1IHb1gvLIdrA40/iXqJYYRnglIDVQsBAQE?= =?us-ascii?q?MAQElCAIEAQGERAKCFgIkOBMCAwEBCwEBBQEBAQIBBgRthVcMhXIBAQEBAxI?= =?us-ascii?q?bEwEBNwEPAgEIEQQBASQLIREdCAIEAQ0FCBqDBYF+TQMuAQ6kFwKBOYhhdIE?= =?us-ascii?q?0gwEBAQWBRkGDJQ0Lgg4DBoE4gmSJYBqBQT+BVIIfLj6CHkkCAgEBgWMrgxq?= =?us-ascii?q?CLY8OiH6LBo9XSgqCVIgqi1mEeoJkiQOSIZBSiXCCTZEsAgQCBAUCDgEBBYF?= =?us-ascii?q?qIoFWcBWDJFAYDZBADBcVgzqDRoFOhUJ0AjUCBggBAQMJfIw7AQE?=
X-IronPort-AV: E=Sophos;i="5.73,442,1583193600"; d="scan'208,217";a="485817145"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 May 2020 17:49:29 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 04RHnL8h002592 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 27 May 2020 17:49:29 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 27 May 2020 12:49:26 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 27 May 2020 12:49:26 -0500
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 27 May 2020 13:49:26 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CeYAjWuO+27XVCHdb4hyXEzVcG4rBwvNHwrfFQfrt3NwgVUn6QjNCnkRZRLUOdeyzxiJc7/h0PTVzNt3zi5PcF55PStLYLhClf2OtGscVP6cDVBLntYOcNHo3UMOT+ihGSPt59LGvlk6PrpaiXGHjSWDepk/m3qasNfwX8QFOiIoUafHS3fg2IlSvmPt/vtKfqThlL+xk9cT13d/owDawfn7KkdfhC6TzoTEIdAY5Fx+PhoWMCwnDN4C0jnf9D1Q8QUhHcTvaKdGqAY7sh7khmhGnjI3pjl55LxtJaSz9wH3awcHNWcmUu2+2iVPoyBm5wV5Z9FELdM0hxD89YBrRA==
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=yIP/RqPnd1HlURXVfRlOPr010Hjuz+DfYHXZ3FhHVhU=; b=Tt6P7By+K9VB0wMH8HNOxICtXtlsdKUh5YzVOG0Bp3jWSZo5mNCUGriWqdDBiBBbhHqvYDnnUEAsbO8LPNM0zYeqOu8hrelyzikFfdoQ0xD5nTp9TgTzWqs8eDJfD2oMZReylutZ6gF5fMY/O4BL1QPPI2+NIYXvNyLWhu09X7d0/qge27Gydjsg+HiPWUXSZUDQ2LfiVrKsOk4wBwmx1fvJD+7K5sppm/nyBxz0i+d50DzTZdrF39Yv/E/Nu5FGpjqAtRmfRla+2d/2A0GhFt/oc5O2ASKb/BMBg2BMYFs3pftYuX1524c3Q+pPzjgx7mTBcArm165tOUWpzpaHoQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yIP/RqPnd1HlURXVfRlOPr010Hjuz+DfYHXZ3FhHVhU=; b=u4D+mcO3Ut3JeQdVsEWZVsuIs07QW+LKYHEjiY47SQ+T9dEprMwqt+x+GG6gsxEehHV4XrcM+rOtkAvQT9uLod3yIMGtPOmRAvh+75+tL2MGO6dF8kNtM3Cq1P8CurC10JCt23FjjmuPGyERrVNt8cMaYp2hHO6TTdYrHN0TM6M=
Received: from SA0PR11MB4624.namprd11.prod.outlook.com (2603:10b6:806:98::19) by SA0PR11MB4766.namprd11.prod.outlook.com (2603:10b6:806:92::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.19; Wed, 27 May 2020 17:49:25 +0000
Received: from SA0PR11MB4624.namprd11.prod.outlook.com ([fe80::83e:6d8:464c:273d]) by SA0PR11MB4624.namprd11.prod.outlook.com ([fe80::83e:6d8:464c:273d%4]) with mapi id 15.20.3021.029; Wed, 27 May 2020 17:49:25 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "tony.li@tony.li" <tony.li@tony.li>, Gyan Mishra <hayabusagsm@gmail.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, Huaimo Chen <huaimo.chen@futurewei.com>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Thread-Topic: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call
Thread-Index: AQHWKvCWbO+rNwui80Sty0q3wo/aI6iuQDRQgAC6fICAAVrmiIAAx0uAgAAJcYCACyDrEA==
Date: Wed, 27 May 2020 17:49:25 +0000
Message-ID: <SA0PR11MB462438CE12785AD7B2372BAFC1B10@SA0PR11MB4624.namprd11.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> <98470E08-B758-45F4-930D-60015D2EAA3B@tony.li>
In-Reply-To: <98470E08-B758-45F4-930D-60015D2EAA3B@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: tony.li; dkim=none (message not signed) header.d=none;tony.li; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2602:306:36ca:6640:15dd:6a31:4ad8:c409]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ca3236f9-c060-4043-b5da-08d802664bd6
x-ms-traffictypediagnostic: SA0PR11MB4766:
x-microsoft-antispam-prvs: <SA0PR11MB4766E56B9D37C873CD283AD0C1B10@SA0PR11MB4766.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 04163EF38A
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: gpqjwuQlnxtz0Up/zsoffdhnHzV3rdgDl4eUNGJwiJDyKmz+4vweYV1VKTMW+QAb0dcMMfAuw+/PRfOjdj9MVzWsx2+T4wePp/uodnIoITrYvazcI/eg0QWZ0Pq4YEcZ3Axar8PsY91UOZmgUpVRpMTN1doijze30Yi//giDCJsAoXkiHNHrOYpqOttbWrsX5aTpQOkYMG9ByDjgbESOb6tS7XcIpn/Z87oyBU6mCXMT1mDvxsLs+h95wPoRCEf4FEPfOKpId/iOw3v0Zf642SbhAxYd7hHmAD3T536g6/4dzHGYOmPceionH4RWYhd9hLI8zIlSiitI9bzYkUrqF97FIcikJPOD0LpLqEykgSiEwlMH5xu2J6vJpURW295uaW4JLKkDFG5jktw153iIOg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SA0PR11MB4624.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(396003)(376002)(346002)(39860400002)(366004)(136003)(5660300002)(8936002)(7696005)(53546011)(478600001)(6506007)(4326008)(166002)(54906003)(110136005)(83380400001)(33656002)(966005)(186003)(76116006)(9686003)(316002)(66946007)(55016002)(2906002)(71200400001)(52536014)(8676002)(66556008)(66446008)(64756008)(66476007)(86362001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: pJjBkkcFRkh7MGh0qioYRpla99bYE7jE9EO2UAfYoGIELoWz8CeSgCbCJSOcR5THdnaw0HlLUjCfe6ocgORNKsM6yN033zscInyh/Sbz2InvO9sX69705EgvoMCwrPfW+rTnXQMCym9XxByXm5Z6oSSCW+SrYpySnvgigZCeaJnwglQPX2qkFkvqHAz6I8/GSp5DkSYaOmo5NRuBrwfM+tVOvuXDNYQ6m22FNaIpOQNQEPf3lHwOE2GLhVrTNYY9gUmYbbKDe1dFv1hEUR2P0s52n+KoTDqBZeg1Ppo4qzlw/9kjXh6T29Z5R3Kpa4q8yYn+AXvqh0CqKr/wRB2wrlobantxcmOgdZ/C7U6+episL8wuG0MYL2q7kLp+eY2NCWb3nMctSY4xLg8/wQlY9n+UmCDUjXQEf0EUj3M9pbwOR++gHZbIGnemvDj93YiiO+Xn0kV/FShwFxflppG3U4LRd9PfoQ9yOGnOtNxRxq8+PU0txPDZIWjb+R9qGlMyPAzVZCkW3xeStwNQwOmQdZxc7fNoaKZ/eiO1/VdY+c4xWRvjH7nVRDnMu39lFVte
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SA0PR11MB462438CE12785AD7B2372BAFC1B10SA0PR11MB4624namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ca3236f9-c060-4043-b5da-08d802664bd6
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 May 2020 17:49:25.3783 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 9P/CXx5vIxyCmCZ/Z1z2XvR3Qxue6qlr13JaLmKfLns/mvfWWCZKAeP+f3Kwn+JOQ09/vqwYvAgX0i0nPgb6Xg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA0PR11MB4766
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/YotBm3kU9zqfT95o70OQb-aaNe0>
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: Wed, 27 May 2020 17:49:36 -0000

Tony/Gyan -

Please find my replies inline.

From: Lsr <lsr-bounces@ietf.org> On Behalf Of tony.li@tony.li
Sent: Wednesday, May 20, 2020 8:48 AM
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: lsr@ietf.org; Huaimo Chen <huaimo.chen@futurewei.com>om>; Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org>
Subject: Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call


Hi Gyan,



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.

Thank you.


Please look at the feature description and it does seem to be exactly the same as this draft.  Please confirm.


It would appear to be a different, proprietary, and unpublished algorithm.

[Les:] Yes, this is a different algorithm than either https://datatracker.ietf.org/doc/draft-chen-lsr-dynamic-flooding-algorithm/ or  https://datatracker.ietf.org/doc/draft-cc-lsr-flooding-reduction/

We are contemplating submitting a draft for this algorithm to the WG.



This will give us three different implementations, using three different algorithms, none of which will inter-operate.  Whee!!! :-(


[Les:] As I understand it, draft-chen only supports centralized mode - which is why it is Informational track and does not have interoperability concerns.
Sarah/Tony - do you have plans to extend this to support distributed mode and then standardize it?

At present there are no standard algorithm candidates which have achieved WG status - though that likely will change very soon.
And the point of allowing multiple standardized algorithms to be defined was in the expectation that more than one might be proven useful.



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


Our implementation shipped last year.

[Les:] As did Cisco's.


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.


It does not appear to be, but someone from Cisco should confirm.

[Les:] Confirmed.

   Les

Tony