Re: [Lsr] Open issues with Dynamic Flooding: Including LANs in the Flooding Topology

"Acee Lindem (acee)" <acee@cisco.com> Tue, 02 April 2019 17:32 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 F2AAC12016E for <lsr@ietfa.amsl.com>; Tue, 2 Apr 2019 10:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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=LBInlUSx; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=QZg7WUlX
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 MmIF3BYBXQ-R for <lsr@ietfa.amsl.com>; Tue, 2 Apr 2019 10:32:14 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D07A2120155 for <lsr@ietf.org>; Tue, 2 Apr 2019 10:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9780; q=dns/txt; s=iport; t=1554226333; x=1555435933; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=wVBgDQkuIG+zIrPD6UEOTDl3Ap4egQ28Q4WteEpjg74=; b=LBInlUSxhbFDIW9MFLMozaGgIAXe3wiMaGbHv6l9N/OZKV1zBx1dPIi9 bTmdpkk8ctF2BWyo0Q7q7GDgNLIje0a8/24iv/sr4Mzk6gDD701GIT4zJ nO58XdRjararPz606arb5GEeF3S1uSdKesvSJXE4BFSiwq146nVf363eJ k=;
IronPort-PHdr: 9a23:9b/DhxV26ggh8tuZWlcYulmjzJvV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSANiJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdEwd4TgxRmBceEDUPhK/u/Zic3EexJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJAAAmnKNc/51dJa1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwIBAQEBAQsBgT0kBScDaHQECycKhASDRwOPOIIyJZcRgS6BJANUDgEBGAsJhEACF4UlIjYHDQEBAwEBCQEDAm0cDIVKAQEBAQIBAQEhEQwBASwLAQsEAgEIEQQBAQECAiYCAgIlCxUICAEBBAENBRuCPEsBgV0DDQgBDqMkAooUcYEvgnkBAQWCRoI+GIIMAwWBCyQBizIXgX+BEAEnDBOCTD6CYQEBgWEmgmQxgiaNBZdyYAkCk2YalDiLRpNcAgQCBAUCDgEBBYFUBiuBVnAVOyoBgkGCCgwXE4M4g0aBToU/coEojF8qgQQBgR4BAQ
X-IronPort-AV: E=Sophos;i="5.60,301,1549929600"; d="scan'208";a="253980421"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Apr 2019 17:32:12 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x32HWCPK004423 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Apr 2019 17:32:12 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 2 Apr 2019 12:32:11 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 2 Apr 2019 12:32:10 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 2 Apr 2019 12:32:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wVBgDQkuIG+zIrPD6UEOTDl3Ap4egQ28Q4WteEpjg74=; b=QZg7WUlX4aSuedKxKB6k4D1nS2BDJgoL7ApzeIzXVvSfe2niuy3VDHuBssjLvdogVc4Wbbs03jfxJbMdUFyCyEqysrzn7gcP5xkH4zscriAOPVhb8HJPUvIcyALmfTbqs0XnMdgfVD+FBhcKqkpvKzCzkdgLa5AK4+Mnvm3g504=
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com (10.174.112.11) by BN6PR1101MB2145.namprd11.prod.outlook.com (10.174.112.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.16; Tue, 2 Apr 2019 17:32:08 +0000
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::9c05:e282:840b:51a1]) by BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::9c05:e282:840b:51a1%8]) with mapi id 15.20.1750.017; Tue, 2 Apr 2019 17:32:08 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "tony.li@tony.li" <tony.li@tony.li>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Open issues with Dynamic Flooding: Including LANs in the Flooding Topology
Thread-Index: AdTpaHQSJ2OEwOMHTqWFPg0qsGKR5QAAOwQAAAPskoD//77JgA==
Date: Tue, 02 Apr 2019 17:32:08 +0000
Message-ID: <2559E621-E114-4130-8406-6E2ABC76FBE8@cisco.com>
References: <BYAPR11MB3638BB41DF7AC03595F4AE46C1560@BYAPR11MB3638.namprd11.prod.outlook.com> <BYAPR11MB3638AF73D0D401E53EBB2B74C1560@BYAPR11MB3638.namprd11.prod.outlook.com> <FCA6F7ED-B720-496D-930C-8E2B7E64CE90@tony.li>
In-Reply-To: <FCA6F7ED-B720-496D-930C-8E2B7E64CE90@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [173.38.117.82]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b6b9ed72-8007-4fa1-9a6d-08d6b79121ed
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BN6PR1101MB2145;
x-ms-traffictypediagnostic: BN6PR1101MB2145:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BN6PR1101MB21456673ABF6DE5B088E672BC2560@BN6PR1101MB2145.namprd11.prod.outlook.com>
x-forefront-prvs: 0995196AA2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(39860400002)(366004)(136003)(396003)(13464003)(85664002)(199004)(189003)(476003)(26005)(256004)(33656002)(102836004)(186003)(71190400001)(6116002)(25786009)(86362001)(105586002)(11346002)(316002)(478600001)(53546011)(3846002)(446003)(2906002)(82746002)(7736002)(99286004)(6506007)(110136005)(2616005)(14444005)(71200400001)(6436002)(81156014)(6306002)(2501003)(14454004)(106356001)(97736004)(305945005)(5660300002)(53936002)(966005)(76176011)(6512007)(486006)(229853002)(8676002)(68736007)(83716004)(6636002)(66066001)(36756003)(6246003)(4326008)(81166006)(8936002)(561944003)(6486002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR1101MB2145; H:BN6PR1101MB2226.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: AYJspxU6QZCaWRPzjn3PoiEOeAiGoTW9ygHYdEw4Gse8gb/qSCDxwD/bOiMDXtuB5jN8we9tFI3HKr13qo98iAumIEixGn99DWlWxRuO5V71pVfmL0N2jQHxczQqqUfyzJRqdSuorsFa9MjQEtfJ5WRtFUWRzawYtmZfW214PnFJ9Egim3YfgAoI4wtbamAqLnrxoz/2X/hpgy5ziuaioTgZt1lp3uPpmyqFsV9pemxY0luJf0gaWKMgTHRMgX+4yFHdEcqhKm4KyrKa7OaKka+lBn/KqJbPehKiGmRS3cyTAcBI++F5nJlBzmUKqaT5uaU9MELEN7l/cMoCQ6kQBsy5XGoFFhTzBkbE2d7vTxlQ++UNfcPkqhObg0R2LSXqut2XRKqdNWTeq4bq7LovUXrPfBNwVE2A3yCnk0ag8nU=
Content-Type: text/plain; charset="utf-8"
Content-ID: <D332199F742FBF4E9A096E8F46414EED@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b6b9ed72-8007-4fa1-9a6d-08d6b79121ed
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2019 17:32:08.4362 (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-Transport-CrossTenantHeadersStamped: BN6PR1101MB2145
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/RYO0Xx2mXb-_umy3Kr9j7Qey7aA>
Subject: Re: [Lsr] Open issues with Dynamic Flooding: Including LANs in the Flooding Topology
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: Tue, 02 Apr 2019 17:32:17 -0000

I agree as well. 
Thanks,
Acee

On 4/2/19, 1:26 PM, "Lsr on behalf of tony.li@tony.li" <lsr-bounces@ietf.org on behalf of tony.li@tony.li> wrote:

    
    I am in complete agreement with both Les’s extensive analysis and opinion.  ;-)
    
    Tony
    
    
    > On Apr 2, 2019, at 8:37 AM, Les Ginsberg (ginsberg) <ginsberg@cisco.com> wrote:
    > 
    > In reply to my own post, here is my opinion regarding including LANs in the Flooding Topology:
    > 
    > While I think it would be "nice" and simplifying to be able to ignore LANs, I think we are unable to do so because the possibility that LANs are actually in use as transit links in some topologies exists.
    > 
    > NOTE: I am not persuaded by the argument that some operators have LANs that could be operated in point-to-point mode but they simply don't configure the links to do so. If a customer is serious about flooding reduction then they need to also do what they can to reduce unnecessary LSPs/LSAs from even being generated.
    > 
    > Even if we treat LANs as always enabled for flooding , any algorithm to calculate the flooding topology would be sub-optimal if it did not consider the fact that flooding is occurring on the LANs.
    > 
    > Bottom line, unless we are confident that LANs will not exist in the topologies where flooding optimizations will be used, not supporting LANs seems to be an undesirable restriction.
    > 
    >   Les
    > 
    > 
    >> -----Original Message-----
    >> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Les Ginsberg (ginsberg)
    >> Sent: Tuesday, April 02, 2019 8:31 AM
    >> To: tony.li@tony.li; lsr@ietf.org
    >> Subject: [Lsr] Open issues with Dynamic Flooding: Including LANs in the
    >> Flooding Topology
    >> 
    >> (I have altered the subject so we can discuss the two issues in Tony's
    >> previous post separately.)
    >> 
    >> 
    >> There are several  aspects to consider when discussing LAN support in the
    >> context of flooding optimizations:
    >> 
    >> 1)Flooding topology advertisement (centralized mode only)
    >> 
    >> Support for encoding LANs when advertising the flooding topology requires
    >> that
    >> we include not only all routers in the set of "nodes" in the network but also
    >> (to use IS-IS terminology) all “pseudo-nodes” as well. This means when
    >> advertising the set of nodes and associated indeces used in calculating the
    >> flooding topology there needs to be an indication as to whether a given
    >> entry is a node or a pseudo-node. The encoding for this is straightforward
    >> in IS-IS (include pseudo-node ID in the node identifier) but more complex
    >> in OSPF.
    >> 
    >> However, this is a problem with a straightforward solution and is therefore
    >> not a significant consideration.
    >> 
    >> 2)Enablement/disablement of flooding on a LAN
    >> 
    >> Correct operation of flooding on a LAN requires all nodes connected to the
    >> LAN perform their role when the LAN is enabled for flooding and conversely
    >> all nodes suppress flooding via the LAN when flooding is disabled for
    >> flooding. This applies to temporary enablement of flooding on a LAN in the
    >> event of a partitioned flooding topology i.e., if any node connected to the
    >> LAN
    >> signals enablement of temporary flooding on the LAN all nodes connected to
    >> the
    >> LAN MUST honor that request.
    >> 
    >> Selective enablement of flooding on a LAN based on whether it is part
    >> of the calculated flooding topology therefore entails some additional
    >> complexity.
    >> 
    >> Note that this discussion assumes that flooding operation on a LAN
    >> is not altered by the introduction of flooding optimizations. For example
    >> there is no proposal to selectively enable transmission of LSPs/LSAs on
    >> a LAN only by a subset of the nodes connected to the LAN.
    >> 
    >> 3)Use of LANs in flooding topology algorithms
    >> 
    >> When LANs are considered part of the flooding topology, any algorithm
    >> used to compute the flooding topology has to consider how to use LANs.
    >> For example, using a LAN might have an advantage in that by enabling
    >> flooding on a single LAN multiple nodes are now connected to the flooding
    >> topology. This might reduce the number of point-to-point edges required
    >> in the flooding topology and/or decrease the diameter of the flooding
    >> topology.
    >> 
    >> But use of a LAN might either increase the diameter of the flooding topology
    >> and thereby affect convergence or unnecessarily increase the degree of
    >> connectivity of certain nodes to the flooding topology and thereby reduce
    >> the optimization achieved.
    >> 
    >> If LANs are always enabled for flooding but are not included in the set of
    >> nodes considered as part of the flooding topology (see point #1 above) then
    >> "false partitions" might occur during the calculation of the flooding
    >> topology.
    >> 
    >> Whether LANs are considered part of the flooding topology or not, the
    >> presence
    >> of a LAN introduces the possibility that there are "hidden nodes" to which
    >> flooding is actually occurring but which are not explicitly mentioned in
    >> the calculated flooding topology.
    >> 
    >> 4)Deployment Limitations
    >> 
    >> The significance of support for LANs depends upon their existence in a
    >> deployment where the use of flooding optimizations is desired.
    >> 
    >> If all links are point-to-point then the question is irrelevant.
    >> 
    >> If all links are point-to-point but ethernet links have not been configured
    >> to operate in point-to-point mode then lack of support for LANs would
    >> compromise the value of flooding optimizations. A counter argument to this
    >> case is that unnecessary operation in LAN mode itself increases the number
    >> of
    >> LSPs/LSAs that need to be flooded by as much as 50% and therefore is
    >> something which SHOULD be addressed by altering configuration. There
    >> should
    >> then be motivation for network operators to enable point-to-point operation
    >> where possible even if they have not done so before.
    >> 
    >> If LANs with more than 2 connected nodes are present and are used for
    >> transiting traffic then lack of support for LAN circuits for flooding
    >> optimizations will lead to diminished effectiveness of flooding optimizations.
    >> 
    >> Summary:
    >> 
    >> When forming an opinion on whether to include LANs in the flooding
    >> topology
    >> it is prudent to consider the above points.
    >> 
    >> 
    >> 
    >> _______________________________________________
    >> Lsr mailing list
    >> Lsr@ietf.org
    >> https://www.ietf.org/mailman/listinfo/lsr
    
    _______________________________________________
    Lsr mailing list
    Lsr@ietf.org
    https://www.ietf.org/mailman/listinfo/lsr