Re: [Lsr] Multiple failures in Dynamic Flooding

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 06 March 2019 18:29 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 57D3213120D; Wed, 6 Mar 2019 10:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 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, 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=BWJoB2Yc; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=mrzLALcU
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 IoVuBoaWoFOS; Wed, 6 Mar 2019 10:29:53 -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 C397E13103C; Wed, 6 Mar 2019 10:29:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7266; q=dns/txt; s=iport; t=1551896993; x=1553106593; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=nUCBASnBCu768Q+oCSKXXvfUrK1EASO0U80dQF2Ai6w=; b=BWJoB2YcmEVZND5i8sAy29GFgf/643uYBIhQuA2Gqa1RtX8inN5XgDlq zDv0FMxI5LRA/hroMzXWbxD2r9PIR+Ah6AiX3YKXrB1sAyDsQzZL3HgLB 6+Q57OEBVfFUjoU8Hc8XEiFb/ZlUuk8qyHhmvrnASjaHaqEc8FNTyUNbb E=;
IronPort-PHdr: 9a23:AscWThBJpZhgS1Ns2323UyQJPHJ1sqjoPgMT9pssgq5PdaLm5Zn5IUjD/qs03kTRU9Dd7PRJw6rNvqbsVHZIwK7JsWtKMfkuHwQAld1QmgUhBMCfDkiuI//sdCY3BstqX15+9Hb9Ok9QS47z
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAADQEIBc/5xdJa1kGwEBAQEDAQEBBwMBAQGBUQYBAQELAYENLyknA2h0BAsnhAiDRwOEUIsBlQeFc4EkA1QKAQEBLIRAAheEGiI0CQ0BAQMBAQMBAwJtHAyFSwYjChMBATcBDwIBCEICAgIwJQIEAQ0NgxuBEUwDFQECoE0CihRxgS+CeAEBBYR/GIILCIEvAYRZhk8XgUA/gVeCHi6FA4MIMYImjEeEBpNECQKTF5Mvim+SMQIEAgQFAg0BAQWBRziBVnAVgyeCCoEjAQeCQ4pTcoEoih8qgiMBAQ
X-IronPort-AV: E=Sophos;i="5.58,448,1544486400"; d="scan'208,217";a="533705704"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Mar 2019 18:29:50 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x26ITowT019574 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 6 Mar 2019 18:29:50 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Mar 2019 12:29:50 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Mar 2019 12:29:49 -0600
Received: from NAM01-BY2-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.1473.3 via Frontend Transport; Wed, 6 Mar 2019 13:29:49 -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=nUCBASnBCu768Q+oCSKXXvfUrK1EASO0U80dQF2Ai6w=; b=mrzLALcUSNl/Xxg2ELf8DPLoHxMhDYi8kqHL55Viay5dWgc/mqCm7FCMaIyReS+RRDjsNMkmsTj6akCcOoH87DCrdb+VtLs9Wvyk0CM1b1AghH3x0fstty6BAKxH+EGP/4JR0v5DWuMYco71EhenbPYlMKHJjUXYiVg+T9C5AMo=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB2888.namprd11.prod.outlook.com (20.177.225.88) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Wed, 6 Mar 2019 18:29:47 +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; Wed, 6 Mar 2019 18:29:47 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "tony.li@tony.li" <tony.li@tony.li>, Huaimo Chen <huaimo.chen@huawei.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>, Christian Hopps <chopps@chopps.org>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>
Thread-Topic: [Lsr] Multiple failures in Dynamic Flooding
Thread-Index: AQHU1DO0xw6ZW2WTWUCDw73GtE+zJKX+68pA
Date: Wed, 06 Mar 2019 18:29:47 +0000
Message-ID: <BYAPR11MB36389C97FEB934EEC932A81EC1730@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <sa6lg2md2ok.fsf@chopps.org> <SN6PR11MB284553735B2351FB584BE792C17F0@SN6PR11MB2845.namprd11.prod.outlook.com> <5316A0AB3C851246A7CA5758973207D463B5858A@sjceml521-mbx.china.huawei.com> <420ed1b5-d849-99cc-bcb0-d159783e4de2@cisco.com> <5316A0AB3C851246A7CA5758973207D463B59041@sjceml521-mbx.china.huawei.com> <0B4DF2AC-8EE1-41CA-B357-98325067CA30@gmail.com> <5316A0AB3C851246A7CA5758973207D463B66FE9@sjceml521-mbx.china.huawei.com> <78A866F4-9AF0-481A-9DEC-B04DE72AFDA3@tony.li>
In-Reply-To: <78A866F4-9AF0-481A-9DEC-B04DE72AFDA3@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:c0c8:1007::680]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6a257bb1-a149-4cba-2678-08d6a261b658
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:BYAPR11MB2888;
x-ms-traffictypediagnostic: BYAPR11MB2888:
x-microsoft-exchange-diagnostics: 1;BYAPR11MB2888;23:o3Ho/rFbz1MjU9b+lA/WAEkhrAi763X4ozEW+v5K1+rengFRZdTRcWJ/O0/F/fuL13xtMVCfTpF3rtBC2GAiLB9CF3oRY1gTTOiqWy9fFpxaRblJX85lMfh1dclW9n2O7BMhRgZBguQqGTGBpH+XjpAtNGXBMZm2sT3rvZdnmkFG7VzmuPI1v0VEIUfPX+8H5nHIB8xKBnQedTD9qZxPtBheZ4dng7cQv6V7i9n+ppl6veBtfvChrOKTwNeLlxwbeE9ylu0vALFlNJi3E1KEWEcPX2UoaQ+DS4r+iAB0r4o/RMjco02N7bTWSUL6MqLwUDVHAgOXxtSnjI8u6hL30wDXY5ax3+Msp68TNz52MFCKpvUDFON152ttQo/7gWFN5fiuaOi4u0v4E0g96c7ZUbjqBepsrL89v4QqUvMfDIN3uF90f+0vB+R/JJ75pnjkqZ6YStpKHemdYTdDesQIo8lMqoBcnejJfP3yVkR5ZZW8JAV3aiGdleHNu6U5FlEXHxlKWSwvfKd+ekTZNJvPuvvmF1bohoPcHrOc6UlkT1hrpx6uuI7ii9qsgWLDa8cJ2wXcr4QWsP/N4+sOCUAEx4j+TaK/ELsy+zdHR4vxoTmCOOPBooEYLZ563NR7JDbauPM9iqpYgz6KMa32KNqvynOjyg2IrYUyDwHV9nOSz3yZMUrwBf01aZJsHWIte9Qa5eZswmZ2KZovnlCUbPwg220DiZ2d7xN7x93RG0Dt/YL640+I+BoIQ4IUXssrfOKT6ZUHIWLoYZqmb6e36Bt0nV2V//5eLUL9/0035y6naOgExmu58vV72tQmtuxwr0y2Je7AMZtckyGSpmtMQFQ4aRJ1Fi5Uz3Nku5TWEJIwCW9r4JjzcKtp+5nJrQJOWO4b0oWRaf3/FZJbvsMFJLBw49UCrsx7zNTa4YX0iAtd7Evg9WsjBmHxYoXwQOsWusCPFxoOoZuout1mMHvX7OlX0+NlvLf0f3QKYFxY2etGmNvVPEWYQ4PE5pRqRh3apyTlylDk0fCZ2uIZWVVNN8Q/wbcbyCjZyv+NrRzzmK4vYaDtRu/vlAJUaLYQK0LomxfmcuroOK59r8rG+50DNUfLYJUQNL7Ys/D6gAbN7fGrVgkYwmb0TKLHXo8A6/AaTq4a+myZkmqHcFCPw4yRxCmw8V68z9cUnc3DL/o+B0Kyv3Ij3M71AZwr+U0po+WeEVdzQdNswjeFA7veujtRSrGT27P4/2MEkBmxMseGMyif+YsQq505ohppXDvRPrsYhcFFsVj+uh9tGkew7Y+EOpse/g==
x-microsoft-antispam-prvs: <BYAPR11MB28885019EE6A7B56AC65D929C1730@BYAPR11MB2888.namprd11.prod.outlook.com>
x-forefront-prvs: 0968D37274
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(136003)(39860400002)(366004)(396003)(199004)(189003)(81166006)(4744005)(5660300002)(8936002)(14454004)(7696005)(790700001)(476003)(6116002)(105586002)(11346002)(110136005)(446003)(478600001)(54906003)(14444005)(93886005)(2906002)(106356001)(256004)(486006)(71200400001)(46003)(86362001)(25786009)(71190400001)(102836004)(316002)(186003)(97736004)(55016002)(2501003)(6506007)(229853002)(81156014)(9686003)(6246003)(54896002)(52536013)(7736002)(53936002)(74316002)(6436002)(33656002)(99286004)(76176011)(68736007)(8676002)(4326008)(6306002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2888; 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: vecXnUaj8sHopHMQDdF0i0R5v2e1z+fq6wsavG7+BekFWZbbu4r99PzuIeOA5EV/X7IqsbMiXDQ41QFJ9wLB1LjvgcQ2NCU4RCacy53/2PL6oz/eEdAlkxFSpWGqUpFaOBfK6grMvVt6agMfzB5nRPdpi5+zgtjxAl3vSsQlvZSOi4gioVQtH1Yw+m/Ou32sWGrNO/ZmpobXBY3z408i/Jb6PLsPsZb0SX4jBLd4KVmpFpjf8eOsdFcKgshmRPmu5uw90s/VNqaMXhE/+fdycyo/0iJiafVJK/haH7E3HsoxJIxzNmxm1xmdbutLz6Ng61GJBzKVHsqigYkr4W8+UWrf0idzmtedrMmCLmjXsiMDsmpf09X4Tetydgt6B5g0KI+IQofDm/cs8yp8bEl0vqW2f/4bCr5orzar/Exi/+c=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB36389C97FEB934EEC932A81EC1730BYAPR11MB3638namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6a257bb1-a149-4cba-2678-08d6a261b658
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2019 18:29:47.2400 (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: BYAPR11MB2888
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/H4uu5kfrBrPssRlc9bOqH4Zqj4c>
Subject: Re: [Lsr] Multiple failures in 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: Wed, 06 Mar 2019 18:29:55 -0000

It takes too long when Hello packet is lost. Repairing split flooding topology needs to be fast.


Fortunately, lost hello packets are a relatively rare occurrence.  While repairing the flooding topology needs to be done expediently, attempting to do so and triggering a cascade failure of the network is counter-productive. Given this alternative, a bit of extra delay when adding a new system to the network, or trying to recover from multiple failures seems wise. Rushing and making things worse does not.  The first
priority must remain network stability.



[Les:] Just to put this minor issue to rest…
It would also be possible for the node making the temporary flooding request to send hellos at a faster rate (say once a second rather than once every 10 seconds) until it sees that the neighbor is sending LSP/SNP updates.
This just isn’t a significant issue.

   Les