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

Yingzhen Qu <yingzhen.qu@futurewei.com> Fri, 05 June 2020 19:37 UTC

Return-Path: <yingzhen.qu@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 048873A0437 for <lsr@ietfa.amsl.com>; Fri, 5 Jun 2020 12:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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_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 zA87UBX92XIR for <lsr@ietfa.amsl.com>; Fri, 5 Jun 2020 12:37:43 -0700 (PDT)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2126.outbound.protection.outlook.com [40.107.237.126]) (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 0F9043A045B for <lsr@ietf.org>; Fri, 5 Jun 2020 12:37:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=G/qx3fiE244KfTdxicdPL8VzXLOZ1hbhxQSfS5rI/yA9Ojo1R8fK6vHa+2Fa+DVrbFcdPv5Iz++BekZYpr8uBrj7BBNDTVGqsINSr1CBE4S3eUnRzRC3iOhfrMmul70tt9jB3bwSt1X+6rKDEdSREzW1JDNgrKdElwsWApsKevDK3AkNW3xuTkoSdKPDbmFIBGFPQNbckeGeJGvCaJFtqPwNaG1Nz9m6cot/OUfqixkAoIQ0uB1NuJ7T9TTYd0u0kK4vQIVhQnPzNbZvPml4sIf2EAkRwtN5U9RP9BcKdyZ885cGIzIAZKo4ct7Ht2ZjKmBSF5pu35Ih41uJFrJX9w==
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=XNv2L3ubX32bjVNCqhVR16/0MHlNBLLI2ah6jlvMJiY=; b=AwWyffLlBD6MIWjUD5OHt4nn6APjpkvidqD8ma0ZYY63MYbFa0oNvWIlp0p5q/ojd/fvpLX/8Cq/9+7PiCyCFg5iFeX7IycJtKn2ilnAi+uP6cORjEK45pUn7FD2Eu1vWAOC5gdGb3OGAug4Qm5vP+GZSZ5RpexwfZsihqP5++ab3JUl3uglS2ddeZI+Ies+RPuuL0eXdeLSzQPoSwu9yrU8kyqCzJbCopscHyXT2GaY/g3lvy6gd6PFJgGw1vgVUMRiVowaAFqPcjXl2u5CeTaolCZWGe3WfIBGsFNlA6bnvSBmT0PJXBF/MrePmiDqaXB0Oee2vmM7w05cYrZqag==
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=XNv2L3ubX32bjVNCqhVR16/0MHlNBLLI2ah6jlvMJiY=; b=tSetLLkdB459XECCvJvTWL/JbdgfVuyxFCOPec/gZKf4yYHLx7Z69z0SSrNs3uNvGYzextmYoxUZ+pjSOz/wsXwgbSZJKq5lIEv6yOd6cyK9+27hEMP7g8u++g5jxmIk9YK2rtlFomzsta+TIcKOTwg0lB0C5FwhqQaj5ljqnA4=
Received: from BY5PR13MB3048.namprd13.prod.outlook.com (2603:10b6:a03:188::21) by BYAPR13MB2406.namprd13.prod.outlook.com (2603:10b6:a02:c8::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.10; Fri, 5 Jun 2020 19:37:40 +0000
Received: from BY5PR13MB3048.namprd13.prod.outlook.com ([fe80::28f0:8a33:3418:b39b]) by BY5PR13MB3048.namprd13.prod.outlook.com ([fe80::28f0:8a33:3418:b39b%4]) with mapi id 15.20.3088.000; Fri, 5 Jun 2020 19:37:40 +0000
From: Yingzhen Qu <yingzhen.qu@futurewei.com>
To: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, Huaimo Chen <huaimo.chen@futurewei.com>
Thread-Topic: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call
Thread-Index: AQHWO1m9yw++VQZRYkaPzDWvpZxjvKjJ9X6A
Date: Fri, 5 Jun 2020 19:37:39 +0000
Message-ID: <8FACDF6D-B0E7-4EE5-B568-A32450D8BA5F@futurewei.com>
References: <7B1E9ED7-F2B6-45AA-9E64-AD9E5B439D02@cisco.com>
In-Reply-To: <7B1E9ED7-F2B6-45AA-9E64-AD9E5B439D02@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [2601:646:9500:c900:a0f5:a272:5138:6a1e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 41eead7b-4948-4332-128d-08d80987e8b8
x-ms-traffictypediagnostic: BYAPR13MB2406:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BYAPR13MB2406FB05E14CCED3A1F34519E1860@BYAPR13MB2406.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0425A67DEF
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: JjYMwKy+/Z58a6X6Zlom/eAHgfXUPNAupvDfEs+yLgMQw2ka20P/eOdx5EdKaBhF05zdO0I3PInoVZ9nZsxGopYy/eG8VB8zpSQB7M/2xu3yqGYekJ3VtBL2mEP5F3wcybXJf5B1AOI/2GKocYaAbNiifuV3foFyWBymN9c/qxRXr0wewTX5IQ8DdFKofS3TYpUVi13+Tg5QSPanmlK716nLywqsVWANqUxjRqYFC0L3g/7uvDxnWkl2kie48Id787T7HeOF2D4pLmhHpoGEhiU/pRuKbN2KrkRvCNglv+Bc9MWsFs6NTOV1gpMouAlDOiFmNYHzENSjHW0iRFvqx8WKP1u1JBuiRSCxP95+TH2A5CSBDkA/fYEqvIFPnyovTugYCn+3xODekaT/FqHGxQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR13MB3048.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39850400004)(346002)(136003)(366004)(396003)(376002)(64756008)(71200400001)(110136005)(966005)(36756003)(5660300002)(2906002)(6512007)(6506007)(6636002)(53546011)(2616005)(44832011)(66446008)(83380400001)(9326002)(8936002)(86362001)(76116006)(66476007)(8676002)(166002)(66556008)(33656002)(478600001)(316002)(186003)(6486002)(66946007); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: pj5M+9a9gWbwRDsRzQ73+8Aj3LA8lzU0LNxjZJCinBTEJibpbkVf43ip2oJCtbxaTLE995mwaOhDRWBbIlO6uoxF2fc/CxujlJUEue7/TjglMyxRdEkCArSFrjjl/3Yt6c1lXOlLD5UMd2zEbHuG9KaJHMRb5OI0F1pijsA3+7UAsgu3tB8j00/IlgrDPrLXnYXEHTrFh1yB0PbZmgTB22U51sHispLElb+OvVQzUt6bu9IwvCa+aMsMe9Yq/6eOriclTV9i+vcpGrhfSPsNdBsLFkLUvTH+EXAQrlkZBp9whMUv+Wfb/SmYx7vd5VhpHM5gAECR6UyjhppKdFpalPZ3o7f4DPro8+9Ily5C4GbFoGG7DcxWMLJ2JgQhA2I/a42kOpEnv22hvsvXFtEzoFvr8/w7TOsKxxh13JUwAlJbjDTb7L0Au3KLqX6oJfNi4Kwfk6xObj2MHuj+4eu/npLNhfdq+e1rUepO+0Rl1J8Oka9Ahd9+o6qonCwyeGpQgyyr2gOfJ7FAXFZchDP7RbJKxMnyy4zt6gF0VU0mDAMNpUq2+DptgfhdenlFMXDx
Content-Type: multipart/alternative; boundary="_000_8FACDF6DB0E74EE5B568A32450D8BA5Ffutureweicom_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 41eead7b-4948-4332-128d-08d80987e8b8
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2020 19:37:40.0139 (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: 0ziYoIsRVvc/NaKVXT1vyYu7xDOg7I6oIlAySWz14/9lus6YIur9I1y4KqbAfrRAq2973b2HUDZFl152v8BwTg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR13MB2406
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4hah_I2E5NJpwezh9AqDaSVJItI>
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: Fri, 05 Jun 2020 19:37:45 -0000

Hi,

I support adoption of this draft.

Hi Huaimo,

I have a question regarding the draft. At the end of section 3, it says if there is any change in the base topology, the flooding topology MUST be re-computed. So in case of a link failure in the base topo, it’s possible that the link is not part of the flooding topology (e.g. one of the multiple links between two nodes), it might be optimal if we can figure it out and save recalculation here.

Thanks,
Yingzhen

From: Lsr <lsr-bounces@ietf.org> on behalf of "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Date: Friday, June 5, 2020 at 10:09 AM
To: "lsr@ietf.org" <lsr@ietf.org>
Subject: Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call
Resent-From: <yingzhen.qu@huawei.com>

Speaking as WG Member:

Hi Authors,

I have a couple technical comments on the draft.


  1.  The algorithm only computes a single graph with single path to each node. While I-D.ietf-lsr-dynamic-flooding failure and computation of an updated flooding topology, many of the other algorithms (both draft and proprietary) attempt to compute two or more paths to each node.
  2.  Since this algorithm is slated for use as a distributed algorithm, all routers in the area must use the same value for MaxD or they may compute different flooding topologies. This is cannot be guaranteed by a single algorithm IANA value unless we allow some number of algorithm specific parameters to be advertised by the area leader (which might not be a bad idea).
  3.   Similarly, the constraints in section 4.2 must be applied uniformly and different constraints would require new IANA algorithm allocation.

Thanks,
Acee

From: Lsr <lsr-bounces@ietf.org> on behalf of "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Date: Friday, May 15, 2020 at 3:40 PM
To: "lsr@ietf.org" <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%7Cyingzhen.qu%40futurewei.com%7C548f8195e2c645d22c8308d8097321cf%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637269737558376155&sdata=ZzzEb%2BAoqJIlp9eAtAnQ8CCgTqamuCYqcBCTeNOMhc0%3D&reserved=0>

Thanks,
Acee