IETF Logo Mail Archive

Re: [Lsr] Open issues with Dynamic Flooding

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Thu, 07 March 2019 17:50 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 59FF512796C for <lsr@ietfa.amsl.com>; Thu, 7 Mar 2019 09:50:38 -0800 (PST)
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_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=Fbkn0OKM; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=VAoVtYve
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 HFAPnC45FJbA for <lsr@ietfa.amsl.com>; Thu, 7 Mar 2019 09:50:36 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32BAF127968 for <lsr@ietf.org>; Thu, 7 Mar 2019 09:50:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15676; q=dns/txt; s=iport; t=1551981036; x=1553190636; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EJ6Iipe2QZRwF5jasMxnHZ/yPogU3xJKyp/tkYXwK4s=; b=Fbkn0OKMRVoEsnWk6QOAcD78zqzFs2xoGVe5ZDojtA01G/4Sf1cYXsp0 3DSLsceiwmTu4reA/3nHJ1zncNRPOcCAo92RpG2eYfvx7vb61d/nlRWMt xGohJy7/AS/233NP1UPApDUJuDaOKPbe1u7u5gdyZZluEowq7rlR4uKdw 4=;
IronPort-PHdr: 9a23:gB/juR/NZMm4iP9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVcGED1bxIeTlRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALAABdWYFc/5RdJa1aChoBAQEBAQIBAQEBBwIBAQEBgVMDAQEBAQsBgQ0vUANodAQLJ4QJg0cDjy+CV5IwhXOBJANUCwEBLIRAAheEHiI2Bw0BAQMBAQcBAwJtHAELhUoBAQEEIwoTAQE3AQ8CAQgRBAEBKAMCAgIwFAkIAgQOBQiDG4ERTAMVAQKgLgKKFHGBL4J4AQEFhH8YggsIgS8BixwPF4FAP4FXgh4uhFYEKTSCVDGCJoxJhAaTSAkCkxyBeIVmi1eKcZI4AgQCBAUCDQEBBYFOAy4ogS5wFYMnggqDboNGhw1ygSiKCyqCIwEB
X-IronPort-AV: E=Sophos;i="5.58,451,1544486400"; d="scan'208,217";a="534550404"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2019 17:50:21 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x27HoLR7009464 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 7 Mar 2019 17:50:21 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 7 Mar 2019 11:50:20 -0600
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 7 Mar 2019 12:50:18 -0500
Received: from NAM02-SN1-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; Thu, 7 Mar 2019 11:50:18 -0600
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=EJ6Iipe2QZRwF5jasMxnHZ/yPogU3xJKyp/tkYXwK4s=; b=VAoVtYveDnuVr26dezNGHo/YUTLWeolroZ0YjifElD5sc7VBbXV8r+6Eg3BPFleCfN6OlrzHaQEMDeld6vD8fjlMBh1FjAdIQ3RwPgcgUr+vGE+JY4Pi90clF8lMceX9aYTKXvREet/lB/2+nlk5BxbWTA99Us1ORO853Pnee1I=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB2789.namprd11.prod.outlook.com (52.135.228.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Thu, 7 Mar 2019 17:50:17 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::b414:f534:f20a:a26d]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::b414:f534:f20a:a26d%3]) with mapi id 15.20.1686.016; Thu, 7 Mar 2019 17:50:17 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "tony.li@tony.li" <tony.li@tony.li>
CC: "lsr@ietf.org" <lsr@ietf.org>, "Peter Psenak (ppsenak)" <ppsenak@cisco.com>
Thread-Topic: [Lsr] Open issues with Dynamic Flooding
Thread-Index: AQHU0rNloYabtT6NFku+G8W9bkhmEKX8p2UAgACQ6YCAAALpAIAABY6AgAA9MgCAAAYKgIAABbWAgAAGcQCAAt1tAIAABduQ
Date: Thu, 07 Mar 2019 17:50:17 +0000
Message-ID: <BYAPR11MB3638D584975FF64B348D6705C14C0@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <AAD29CF0-F0CA-4C3C-B73A-78CD2573C446@tony.li> <c1adac3a-cd4b-130e-d225-a5f40bf0ef55@cisco.com> <F3C4B9B2-F101-4E28-8928-9208D5EBAF99@tony.li> <be28dbcf-8382-329a-229f-5b146538fabe@cisco.com> <966E5756-8CEF-47F4-8564-E23D38F0743E@tony.li> <c8f40acb-94fe-f42a-aa0a-3a42e0067be8@cisco.com> <7F522B6C-9D28-4533-8ABD-9F492D9AF26C@tony.li> <a33ff3ba-975b-2ef2-93e9-1bc9664fdd5a@cisco.com> <2932F33A-1F9E-4C20-A233-E569D8935AE4@tony.li> <C723C078-72FD-426C-99F2-F0A494E0E971@tony.li>
In-Reply-To: <C723C078-72FD-426C-99F2-F0A494E0E971@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=ginsberg@cisco.com;
x-originating-ip: [2001:420:30d:1320:68bd:e582:7215:61f8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b5aafb2a-1f1e-44ae-28d2-08d6a3255c12
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BYAPR11MB2789;
x-ms-traffictypediagnostic: BYAPR11MB2789:
x-ld-processed: 5ae1af62-9505-4097-a69a-c1553ef7840e,ExtAddr
x-microsoft-exchange-diagnostics: 1;BYAPR11MB2789;23:NTRQNjhodjfpAgxoeMU59BlpWLNlfEiNe4n+0IdwxQOtUG+vTMViw5VdiWcvim3FuDg8fIN/F7lr4ILHgaSP9VLE3NyT/d+NNgPA+x2G61BmeukxR0Af1wCIbin6bIed78x2TwsAkas2ChQTh5xy0luH1wjfNmFGYUM5NKvbqQGKxfIqGwciO/lWXxHCiyTivS5aZsjZKeVyNB+78yMHrGFusTAq2A/+vqXv/S6ueW7EKT60h7UpuUuvw5YF9IyKnmLSo+ddj3rMmvt7+CECxn9NIrZdlh6/A/AnM1IoYO9BlbTeVyITF3wRoWrDyaWDd6XoO1msSLRjJfX+aB3uoAQxr4bpXao8nkZfG+KAo8pRvgtXJxMFtWuCMXMhcrDwGyoF0fkwA7hMHb9R/tSRCWTalTB7+Xw9p+9xNNQ8/2Ic/S3sAooGgEORWasGIyvGpMYdg9sgm6MArrbM4fTjd/gUQxuEWO42DT/XNhsIKrmSDJSb+2QutfPB/CgmxIlLEgjam2hH5Rz8j1FxnQyMZ9sYOcnQIVRuEaoWs3OR9t7t6zv23r5cNVyjeny+YlvxmKLV8kMDx7hsbXJ9sEUdDGNKFW++Ntt9E6A5TBkIuz1roIiZqtaUSTtt0dLbH00L0h2bj014NXNkAzlAFeA6LxIoektOqudv7k/Jlvkv2UdBAO/Y+SKidmcBCnU3iKJjMg2jgLQEl8iJghT98W2GUxMshkGjAnb2pc/kn6URA6HnIAN/yd6qL3qic67RGzH1dxnp88qINnUQ+6/9yqSy7hBaCyx3VUEoG2+hpRoNL86s0icTTQ7ov8ley9yn6BHVD6ElpjBX5Rk4f2btstN+FYHoC2C44V35ayoikbuOw1hjAMkr5D9LJMcG5s0VuB7ZFpiskw1NoFamXsSebkazA08SpqDBs1qOEAt5tLSQCEwoWmRqdxRRs0pB3mg6ylsCE7Na4oEe9cL9Ehmk0uqb6zDt7m6tkL8wwv45qOHNR+R6WwUDsyAE0PSRncBEyhK5vejY5Ztl+rKvXfq5ppjdMj8Q/V8LXGpjknEznUUaDU2djGLrXD6XI0xX9SlAUaCjtpXOCLwznQqJInh+yiMiplU71gdQudiTkJwcCvtACoWleDKfaltplkkENWDaFrjh50BolG1V2kxVPEwRXqRjKFDWIde0urFufdjjHIRUZOmZufyHraOaIkfk2barkvQY7IlLSRcufnvxIuj8aQP3QQmOh6kXoxj9bUU6po50QgnbGri2Wp/bwsNTCqNeh0x2Qyz2oKElCEr/tMOWDb04cdraqz2dzzG7h+6ttepZP0BRfM4qlztrAuz4wLvq/EvfihTWG8TqbsU5H3vUzvPGqmorNOOX17apOvFtUJfosKMdaajHWUjF8+FmPjNCJv0P
x-microsoft-antispam-prvs: <BYAPR11MB2789B9C26A651AB5825598AEC14C0@BYAPR11MB2789.namprd11.prod.outlook.com>
x-forefront-prvs: 096943F07A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(366004)(39860400002)(136003)(346002)(199004)(189003)(2906002)(46003)(6116002)(790700001)(33656002)(54906003)(486006)(11346002)(446003)(74316002)(476003)(6506007)(8676002)(53546011)(102836004)(8936002)(6916009)(76176011)(81156014)(81166006)(99286004)(71200400001)(71190400001)(229853002)(7696005)(186003)(106356001)(105586002)(2501003)(14444005)(256004)(97736004)(52536013)(4326008)(316002)(6246003)(68736007)(53936002)(107886003)(7736002)(2351001)(5660300002)(86362001)(66574012)(14454004)(5640700003)(55016002)(6306002)(6436002)(54896002)(9686003)(478600001)(25786009)(236005)(93886005); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2789; H:BYAPR11MB3638.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: ZHpjPF/uPndZ7WmSa/0BBZ6p0Khyg4agKgy4GYi/G8kTMIMYnz12VKagt1OggaDYIzNUHLnkl0CLeDjkXaxh0ZtcarZXZNt8B5AALEY77rBoD+EnU6NyxwFyw91KEm5m5/gsaJKxAcwzdAkuH+MrRi9dYtVGJotscVx3A29dSN6ANByd6CvipLbK040mYlzC6Q6y6k7CMN95oezwsJUzqECdgQZN6VoOXlyxOm+RqvFbHc+GFRH89usu8nlHrEMNlsjIaqW3lpQscMiuE4De+tvaQH/b6bUH1I820mEU9svbNNdT9pWTNJUIIvDfc4OR0zz25GAoWYI95zuVl28ju+jNMPBFQuO9VA+8naW5CP2DC1XbhTaQ9lpBlU1tZPSuzBW7u7PecW9/SYjtuehcfTJlYHfXd3SByySLTT5/Blk=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB3638D584975FF64B348D6705C14C0BYAPR11MB3638namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b5aafb2a-1f1e-44ae-28d2-08d6a3255c12
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2019 17:50:17.2364 (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: BYAPR11MB2789
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.21, xch-rcd-011.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/eOFOflTRFpQNH_z4a6lQouzs7-4>
Subject: Re: [Lsr] Open issues with Dynamic Flooding
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, 07 Mar 2019 17:50:39 -0000

Tony -

From: Lsr <lsr-bounces@ietf.org> On Behalf Of tony.li@tony.li
Sent: Thursday, March 07, 2019 9:16 AM
To: Tony Li <tony.li@tony.li>
Cc: lsr@ietf.org; Peter Psenak (ppsenak) <ppsenak@cisco.com>
Subject: Re: [Lsr] Open issues with Dynamic Flooding




On Mar 5, 2019, at 1:31 PM, tony.li@tony.li<mailto:tony.li@tony.li> wrote:

Let me propose that we add something to sections 6.7.5, 6.7.9, and 6.7.11 like:

Addition of temporary flooding should be done with caution, as the addition of excessive connectivity to the flooding topology may trigger unwanted behavior. Routers SHOULD add temporary flooding in a rate limited manner, if not configured otherwise.

[Les:] The first sentence is OK with me. The second one I think goes beyond anything on which we can claim consensus.
Whether adding the first sentence alone is worth a new revision I think is questionable – but I certainly would not oppose it.

Regarding LANs, the encoding for OSPF is more problematic – basically we need to identify the value as a router id or a network LSA id (or something like that).
So, committing to this without consensus has a downside that we might live to regret.

I am in agreement with Peter’s position. LANs introduce additional complexity and it is not clear that including that support is a real benefit in the topologies in which we expect the flooding optimizations to be used.
I know you believe real deployments may need this support – but what I don’t know is whether we have hard evidence to support that position.

I am also wondering whether the following serves us better:

a)We keep LANs always enabled for flooding
b)The algorithms consider this and are biased towards using LANs when possible as this is a cheaper way to enable flooding to multiple nodes than many P2P interfaces.

IN this way we keep the simplicity of not having to define LAN behavior/encoding, yet reap benefits in topologies where LANs have a significant presence.

Let me know what problems you see with this approach.

   Les


Hi,

I haven’t heard any feedback on this.  Can we please adopt this?

The draft cutoff is Monday, March 11.  Could we please incorporate this change and the addition of the pseudonode identifier by then?

Tony

v2.23.0 | Report a Bug | By Email