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

"Acee Lindem (acee)" <acee@cisco.com> Fri, 05 June 2020 16:52 UTC

Return-Path: <acee@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 CF0A63A08D1 for <lsr@ietfa.amsl.com>; Fri, 5 Jun 2020 09:52:53 -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_H3=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=KDNrIIoW; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=IJda2tUC
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 s-kAn1ywAQe7 for <lsr@ietfa.amsl.com>; Fri, 5 Jun 2020 09:52:52 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 016D43A08C6 for <lsr@ietf.org>; Fri, 5 Jun 2020 09:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11943; q=dns/txt; s=iport; t=1591375971; x=1592585571; h=from:to:subject:date:message-id:mime-version; bh=/UhXQwCVwK8z+uLYjnsvRmt0Gm/6y22is2jhB8Li/SA=; b=KDNrIIoWeZjDjV+SztLAH/OeU0u9ELSQzcT1EZIFSaNxLJBu+dhHP48m aUFa/jJ1o2KQjeM7JGCHIiTSUm27u8hp5Jk63TUE1BciplKhOdLrOfTWJ F3Fl7QaYAVzvn7u9UsnTiqV/3hUBH3bj4g3G23p0HibpIsslJ/YGN0wgo 4=;
IronPort-PHdr: 9a23:63HsRB2DaApEsak0smDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxWGv6dsgUPHG4LB5KEMh+nXtvXmXmoNqdaEvWsZeZNBHxkClY0NngMmDcLEbC+zLPPjYyEgWsgXUlhj8iK6PFRbXsHkaA6arni79zVHHBL5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxFjA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DzCQDTd9pe/5tdJa1mHgEBCxIMgy0vUgdvWC8sCoQbg0YDjUGTaYRoglIDVQsBAQEMAQEjCgIEAQGERBmCHQIkOBMCAwEBCwEBBQEBAQIBBgRthVsBC4VyAQMDEgsGHQEBOBEBCBEDAQIkBwIEMB0KBBMigwQBgX5NAy4BDqd3AoE5iGF2gTKDAQEBBYFGQYNNGIIOAwaBOIJkiWgaggCBESccgh8uPoJnAgIBAYIBDYJnM4ItkgaGL5tNCoJZiDaQSwMdgmeJEJJKkQCJf5QLAgQCBAUCDgEBBYFqIoFWcBU7KgGCPlAXAg2QQDiDOoUUhUJ0AjUCBgEHAQEDCXyNPQGBDwEB
X-IronPort-AV: E=Sophos;i="5.73,477,1583193600"; d="scan'208,217";a="769437300"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Jun 2020 16:52:50 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 055GqoC9028642 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <lsr@ietf.org>; Fri, 5 Jun 2020 16:52:50 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 5 Jun 2020 11:52:50 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 5 Jun 2020 11:52:50 -0500
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 5 Jun 2020 12:52:49 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ll5O7gqdgqm44N+3JJUh328qdWa56GfE8YmQzcA1yHLcRa+LE1hUITkypGmQsUpWfHjQqv7htUY1SmUZmsqWe1mbyZcJlrf2wcu3Gn+1v3GoAM3KwNcpttimV2tLoq+5euTeRD+kUroayJiqrm8HwiRoeF2U+Xnx+YR9ZzLzYUT4WgEng3qx/RJUF59+O8RB0/ILBiYg9PWUpFGyhnqzKP2PyRkrZjkfyaqFBvJUyJl8C3zTpJs60xmLXD3OHB3U9sA9HsC0RYQ6r/UrLgqjZGYTkKpgPawaP8l5MjcSn+50y8RzYuRc8x7L3Ws8AWRK4DMZMBRcBYSeBGq6c2hXYg==
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=/UhXQwCVwK8z+uLYjnsvRmt0Gm/6y22is2jhB8Li/SA=; b=at0pKLkPzf5nXL1MkR7OtpBbLx/jq5nxorzeC4cWEa9eIic3JiLrk/pHGJhN9dIuqGtsiuYoLPErVS9LWt0OxaizXG0lWpeEtP/nec3BKE2gXDR3Z1Bb3z0xVml0bUQN9NRd8WZ7GzXSQFVypZDpPar77Jmge5oCzcjqQl19xgw22FV0jlHtKmK/B2aMKu6pH5mdd7zs4EyVTotQ2wf/DIdI++7GRjeZqGA4D+T6zQtmTD94Gaic0VC2qmKm5aH4uf3ZBj3lZ4D0Yf1hU2gj2WmIP5Q9xocDwSAcWEmJDE6oOSvrUNaVORJexciwwmjZEkcH8PSOWK8JMeMj07/NGw==
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=/UhXQwCVwK8z+uLYjnsvRmt0Gm/6y22is2jhB8Li/SA=; b=IJda2tUCVBmwMIftV1KMXWMjZ2mIeOfLQT1FzV9B1Ruw5LliE7enBu2mMfY7hnP3/QNUaVu4OZm6ItG8XNgxyOKDtBNTALxrZILmDMNCwIFPx0TgqP6iczZqx2nklav/6iKrGP3ljonYSmN9nOEwWdtpMlSWW8X9mbFyWpsOtcU=
Received: from BYAPR11MB2887.namprd11.prod.outlook.com (2603:10b6:a03:89::27) by BYAPR11MB2693.namprd11.prod.outlook.com (2603:10b6:a02:cc::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.18; Fri, 5 Jun 2020 16:52:46 +0000
Received: from BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::4950:e26c:503f:768e]) by BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::4950:e26c:503f:768e%6]) with mapi id 15.20.3066.018; Fri, 5 Jun 2020 16:52:46 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "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: AQHWO1m9yw++VQZRYkaPzDWvpZxjvA==
Date: Fri, 05 Jun 2020 16:52:46 +0000
Message-ID: <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/16.37.20051002
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ff3b7bc9-4dd9-44b9-6356-08d80970dfc2
x-ms-traffictypediagnostic: BYAPR11MB2693:
x-microsoft-antispam-prvs: <BYAPR11MB2693287EBB6CFE42D07FD3A1C2860@BYAPR11MB2693.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0425A67DEF
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: puvufkF+0yy/pZTTaDnPaOkfn3pALVQK3W+Hhmqa7S7zqTfyZhrqzmBKIiaYP/VvIjGf9grR/s2ZNOABXOCUhh9OHNXWdUeTe0YuExAGsmG+UX6TtGqwvploUOnrgDZBXvoVGaA5qeuTKmx/IxcfluB2iRHRfUGcD1hmEzVxjOo1MdpUmMW1f3VeuHEaWGvrBo7P0+z7+sLQH8fKwK0l0yJdzcpDchYUklUYpYc/AVUkWVm+hqK2R32G+16yKZDlGeAQQC5Rb3raB6+lBNVBgD4ibBvlq2+rVR0KBz142PyXaO8/WL77nYPAWnqLwwbRdEF6VHkGN+a0VGBZv6sFGvvA6nRgjMLWkaWEwLxExuP1lF8fbgFagU3SJgldf0wZ5ucsxR8qMAgFbHzYsa/SJg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2887.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39860400002)(366004)(376002)(346002)(396003)(136003)(478600001)(64756008)(76116006)(6506007)(5660300002)(66556008)(53546011)(66946007)(33656002)(66446008)(66476007)(316002)(86362001)(2616005)(6916009)(6512007)(8676002)(186003)(36756003)(83380400001)(966005)(8936002)(71200400001)(166002)(26005)(6486002)(2906002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: AD9A1krxGNAJ0Ry2DkNYvLlXeKIGjh7y96FJQPpzYh5F69uQAsFtiMKNZUGbFK3srcx/L7+xRgwneAw+7MelIYpyCEoOFk93nUPHkHgsdgCf1iBi2mc3po+a7NvCzlCxQoZfC9DD/lACNJHr0l8J33TJtOm8gOFnEib55pYv+n1envg6texvvF6pYUekogegHYMmQjKQBry5EaSG5AXzf6Hm3rWLIYlnkp024ECyRo9GcvP8h8eoqZdkJTJ7sjj6S7C6AZwf2/uWBtgUtLABFzzWdV00aFeKr9CNTKomimsbTKY3lithLvKd+5ZKAKGS+1kJCt4wvpkJBVqQ+PDEzI8SlKfutt6fqfgezlYOpbA/PshbJP5R12wyHO63GYHhdMbtd0zfOP3t5PROpEkmwMR95AsW1pgArYAcQ5Fe7i2K+SykK6GQUy47pRbxjwnqrB7ynGMR3q4j/hfxIgQOKf9jJodqqwVHYpuYIZB3FYzIKm5jnfSa+zLNMfQ8cJTe
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_7B1E9ED7F2B645AA9E64AD9E5B439D02ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ff3b7bc9-4dd9-44b9-6356-08d80970dfc2
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2020 16:52:46.6281 (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: EH9vxZaD5jskyZwNVfPx02I4QRos45ceet+PqtyP00wMD9jMTsRAXFjfw0OO1ovI
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2693
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/vGCFyu02e_Nk-PABZl7m6JpYfTk>
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 16:52:54 -0000

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/

Thanks,
Acee