Re: [Lsr] 答复: 答复: Option B from "Migration between normal flooding and flooding reduction"

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 29 May 2019 04:18 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 6BA93120052 for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 21:18:07 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=ehshG4G+; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=07biPvgg
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 ZBUbvV7VqcFR for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 21:18:05 -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 0378D120043 for <lsr@ietf.org>; Tue, 28 May 2019 21:18:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5724; q=dns/txt; s=iport; t=1559103485; x=1560313085; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=nSoDhnQ+BhaQ5aGP3syaXqs00bhdkxZrvgUVg0/imbQ=; b=ehshG4G+/j7y4eUC0Zihts3qb67P++uOlGwliCmL6uSnH+aLTln1AzK3 EUOsvAgxClqVGI0dJCNYPh1+PGiLdNOYxKhT+u9K8e3brh4UV7cn4CLA5 7kFlqJOs9pjWxNdb4rZvKHcRJMTpg9mmCmZX/PZN9RES5nwLdR2sEWF8w g=;
IronPort-PHdr: =?us-ascii?q?9a23=3Aeq/wdBUbpmlYWurpmHDuf1VCsRzV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTF?= =?us-ascii?q?dE7KdehAk8GIiAAEz/IuTtank1HcJZXlJ/8FmwMFNeH4D1YFiB6nA=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BIAACAB+5c/51dJa1kHAEBAQQBAQc?= =?us-ascii?q?EAQGBUQcBAQsBgT0kBScDaVUgBAsohBODRwOEUoougleJQo1rgS4UgRADVAk?= =?us-ascii?q?BAQEMAQEYDQgCAQGEQAIXgkwjNAkOAQMBAQQBAQIBBG0cDIVKAQEBBAEBEBE?= =?us-ascii?q?RDAEBLAsBCwQCAQYCEQQBAQECAhkKAwICAh8GCxQBBQMIAgQBDQUIGoI1TIF?= =?us-ascii?q?qAx0BAgyNMJBgAoE4iF9xgS+CeQEBBYUKDQuCDwMGgQwoAYtSF4FAP4FXgU5?= =?us-ascii?q?QLj6CGkcBAQIBgTcPGhWCczKCJosqgmOFGIdYjR89CQKCDYY0iH6BNIJLgh+?= =?us-ascii?q?GZ4Vth1iMcIcCgVqNHAIEAgQFAg4BAQWBTziBV3AVO4Jsgg83GoMfhRSFP3I?= =?us-ascii?q?BgSiLEYJSAQE?=
X-IronPort-AV: E=Sophos;i="5.60,525,1549929600"; d="scan'208";a="279246682"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 May 2019 04:18:03 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x4T4I2xi010617 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 May 2019 04:18:02 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 28 May 2019 23:18:01 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 28 May 2019 23:18:01 -0500
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 28 May 2019 23:18:01 -0500
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=nSoDhnQ+BhaQ5aGP3syaXqs00bhdkxZrvgUVg0/imbQ=; b=07biPvggerPnyBNFtZUU+MZR3Y/wl8f3qD3JuruWEFjj+y1I92KP5B8QszWYUtHOtFhbN2ovZJmsZc+ojBXk7ANHvV3/1jf2xlibcV/h/cGE3WYAITRXyK1lYKZkOsA54z9GzERD/yZ62lq2O32cA6W1JLfCuCEqbGWZtkB7E1Q=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB3159.namprd11.prod.outlook.com (20.177.126.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.18; Wed, 29 May 2019 04:18:00 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::ace2:8693:202d:5a30]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::ace2:8693:202d:5a30%7]) with mapi id 15.20.1922.021; Wed, 29 May 2019 04:18:00 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, "Peter Psenak (ppsenak)" <ppsenak@cisco.com>, "'Tony Li'" <tony1athome@gmail.com>, "'Robert Raszuk'" <robert@raszuk.net>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: =?utf-8?B?W0xzcl0g562U5aSNOiAg562U5aSNOiBPcHRpb24gQiBmcm9tICJNaWdyYXRp?= =?utf-8?B?b24gYmV0d2VlbiBub3JtYWwgZmxvb2RpbmcgYW5kIGZsb29kaW5nIHJlZHVj?= =?utf-8?Q?tion"?=
Thread-Index: AQHVFcAYLJw3Lv7SEUWkbie+h7FiJKaBfgtQ
Date: Wed, 29 May 2019 04:18:00 +0000
Message-ID: <BYAPR11MB3638F72A2CA160CFE4A39FA1C11F0@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <5316A0AB3C851246A7CA5758973207D463BBD21B@sjceml521-mbs.china.huawei.com> <CF5E5FE7-C2E2-4200-AE8A-6BF5E558258C@tony.li> <5316A0AB3C851246A7CA5758973207D463BC58F5@sjceml521-mbx.china.huawei.com> <BYAPR11MB3638190EC8AD3235AB2304E7C1060@BYAPR11MB3638.namprd11.prod.outlook.com> <5316A0AB3C851246A7CA5758973207D463BC5C32@sjceml521-mbx.china.huawei.com> <BYAPR11MB3638722A90E40777657001B8C1000@BYAPR11MB3638.namprd11.prod.outlook.com> <CAOj+MMEijyB7qd4oUaOe7W19j+76CjH+mzJ3mvcVtOjn5fvmdw@mail.gmail.com> <BYAPR11MB363863B393A181264E07B042C1000@BYAPR11MB3638.namprd11.prod.outlook.com> <MN2PR13MB3470B24A328311A23BAAC5B8A3000@MN2PR13MB3470.namprd13.prod.outlook.com> <MN2PR13MB34701B410A172A950BAE6B5EA31C0@MN2PR13MB3470.namprd13.prod.outlook.com> <FB4EDF4B-C94D-4654-8D3A-A1567E0D76B1@gmail.com> <CAOj+MMGDodnxktZCuqPfVDCRbu0+yUR--DiZKTqVQ=4thAM5rw@mail.gmail.com> <4DFD8BB4-AA63-4BE6-9927-4557AB32ABD9@gmail.com> <005401d5151c$cbda8120$638f8360$@org.cn> <e2b23e19-4a0a-3ad6-e647-c1afde1e5e 56@cisco.com> <003601d515bf$f2870750$d79515f0$@org.cn>
In-Reply-To: <003601d515bf$f2870750$d79515f0$@org.cn>
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:1008::275]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9ffdec40-520a-41a3-5839-08d6e3eca2c2
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BYAPR11MB3159;
x-ms-traffictypediagnostic: BYAPR11MB3159:
x-ms-exchange-purlcount: 2
x-ld-processed: 5ae1af62-9505-4097-a69a-c1553ef7840e,ExtAddr
x-microsoft-antispam-prvs: <BYAPR11MB3159AEA638670E32CE2FF8EFC11F0@BYAPR11MB3159.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0052308DC6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(366004)(346002)(376002)(39860400002)(13464003)(199004)(189003)(229853002)(81156014)(46003)(81166006)(186003)(8936002)(476003)(256004)(68736007)(14444005)(11346002)(446003)(86362001)(305945005)(7736002)(486006)(9686003)(6306002)(33656002)(6116002)(6436002)(55016002)(2906002)(224303003)(478600001)(966005)(74316002)(6246003)(4326008)(76176011)(53546011)(6506007)(25786009)(99286004)(7696005)(102836004)(14454004)(316002)(110136005)(76116006)(71190400001)(5660300002)(71200400001)(52536014)(66946007)(73956011)(66446008)(64756008)(66556008)(66476007)(53936002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3159; 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: f+vQoqYSvkSfxvfSMxnbP402zPGUd+vfRxu5UXPAdQ1UuDGby4K+7hVTE6pBVqQnb0pK3eDd4Q0Tl2KlO3eAhaOa/sZAAMJBmtj2fV/0TN/GXRKlI9O7MbUKUfNVBAb9omk81anyWnWYgQipIp1+5Fnr8h72N5gS7VPnLtdFCfy80mHZsGW8D05M6p4BXBlwh+mMyIQb3/krHdYZNZ6NDPiWPMmM0HRtHHQiQ0wbWQp4rjIkX2uJApksJggUdmkg0tt5QKKrZcFvCDK9Se0z9GY4ALij2e6TdwIylse4WNkpQkzqveM722cNenpkIilafvuoX1t1iJj427NDLYw+io8eIOtrZp35mAA0FDdQwargbggax20inBqBhH4qR3aEDCImoqWn3P32dXB+t+y1J9z2l7KAuCmN2MGVk02nOPk=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9ffdec40-520a-41a3-5839-08d6e3eca2c2
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2019 04:18:00.0917 (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: ginsberg@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3159
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/mNyTcecRNZeMQmLD0nVoFezY-AI>
Subject: Re: [Lsr] =?utf-8?b?562U5aSNOiAg562U5aSNOiBPcHRpb24gQiBmcm9tICJNaWdy?= =?utf-8?q?ation_between_normal_flooding_and_flooding_reduction=22?=
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, 29 May 2019 04:18:07 -0000

Aijun -


Please look at https://tools.ietf.org/html/draft-ietf-lsr-dynamic-flooding-02#section-6.4 which defines how to disable dynamic flooding w/o resigning as Area Leader.

Note that having deployed dynamic flooding in a network which functions poorly in its absence, disabling dynamic flooding has risks.
Nonetheless, I agree we need a way to disable dynamic flooding and it is helpful to be able to do so w/o altering what all possible area leader candidates are advertising - and we have that.

   Les

> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org>; On Behalf Of Aijun Wang
> Sent: Tuesday, May 28, 2019 6:44 PM
> To: Peter Psenak (ppsenak) <ppsenak@cisco.com>;; 'Tony Li'
> <tony1athome@gmail.com>;; 'Robert Raszuk' <robert@raszuk.net>;
> Cc: lsr@ietf.org
> Subject: [Lsr] 答复: 答复: Option B from "Migration between normal flooding
> and flooding reduction"
> 
> Hi, Peter:
> 
> Under the current mechanism, only all the candidate area leaders stop
> advertise this sub-TLV, then the network will be back to normal flooding?
> Is it more efficient that only one area leader indicates(according to the
> command from NMS) explicitly then the network will be back to normal
> flooding?
> 
> For the number of candidate area leaders, I support we should have more
> than one for consideration of redundancy.
> 
> -----邮件原件-----
> 发件人: Peter Psenak [mailto:ppsenak@cisco.com]
> 发送时间: 2019年5月28日 15:34
> 收件人: Aijun Wang; 'Tony Li'; 'Robert Raszuk'
> 抄送: lsr@ietf.org
> 主题: Re: [Lsr] 答复: Option B from "Migration between normal flooding and
> flooding reduction"
> 
> Aijun,
> 
> On 28/05/2019 08:15, Aijun Wang wrote:
> > Hi, Tony:
> >
> > How the receiver judge the leader has stopped advertising the Area Leader
> sub-TLV? Do you need some timers?
> 
> no timer needed, all event driven. Area Leader sub-TLV is removed from the
> LSP.
> 
> thanks,
> Peter
> 
> >>From the current discussion, I think the explicit instruction that proposed
> by Huaimo is more acceptable.
> >
> >
> > Best Regards.
> >
> > Aijun Wang
> > Network R&D and Operation Support Department China Telecom
> Corporation
> > Limited Beijing Research Institute,Beijing, China.
> >
> > -----邮件原件-----
> > 发件人: Tony Li [mailto:tony1athome@gmail.com]
> > 发送时间: 2019年5月27日 12:20
> > 收件人: Robert Raszuk
> > 抄送: lsr@ietf.org
> > 主题: Re: [Lsr] Option B from "Migration between normal flooding and
> flooding reduction"
> >
> >
> > Hi Robert,
> >
> >> The current draft is pretty robust in terms of area leader election. It also
> says that  "Any node that is capable MAY advertise its eligibility to become
> Area Leader”
> >
> >
> > Correct.  This can be all systems. It can be one. For redundancy, a few
> would be sensible.
> >
> >
> >> With that can you confirm the procedure to "resign" as area leader ?
> >
> >
> > Stop advertising the Area Leader sub-TLV.  It’s that simple.
> >
> >
> >> Especially that under those circumstances just having active area leader to
> resign clearly is not enough to change given flooding scheme.
> >
> >
> > If there are multiple potential area leaders, then all of them would have to
> resign.
> >
> >
> >> In some deployments all eligible nodes may advertise such capability
> which in turn the "resign" procedure would require NMS action to disable
> such capability by configuration and re-flooding it. Not that I am advocating it
> nor see need for complex migration procedures, but just would like to better
> understand the "resign" part.
> >
> >
> > Correct, this is rightfully an NMS operation.
> >
> > Tony
> >
> > _______________________________________________
> > 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
> >
> >
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr