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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Tue, 28 May 2019 15:22 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 19349120173 for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 08:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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=Bguv9oGW; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=QG+/OcW1
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 aS0TtzHDaIml for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 08:22:46 -0700 (PDT)
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 E5C91120254 for <lsr@ietf.org>; Tue, 28 May 2019 08:22:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3910; q=dns/txt; s=iport; t=1559056965; x=1560266565; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=EJyH47wGUWpDCo+7m66THZjsOGVrrfjUcH/peBluYuA=; b=Bguv9oGWbeo1G8fyhojqQsUIcWxmoJiaOgyGaipHXq2YLjSDyb56VBGF 0gCqQzg5NPTkkNtk509ACNwTqkIGqAss/Dqt3gy5xXmRFl6tUg9BuM3u/ jcSF8/aCf4FTu03MEozY0lmn0ZHdQqoX28cs+xoIzUfW6Qibl8l9yoIpY 4=;
IronPort-PHdr: =?us-ascii?q?9a23=3AwY5u9xRlrWkxY7r6HuHWL6hRp9psv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOiM7Gt9IWUVq13q6KkNSXs35Yg6arw=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CiAADfUe1c/4cNJK1lHAEBAQQBAQc?= =?us-ascii?q?EAQGBUwUBAQsBgT0pJwNpVSAECyiEE4NHA459gleJQY1qgS6BJANUCQEBAQw?= =?us-ascii?q?BARgLCgIBAYRAAheCTCM2Bw4BAwEBBAEBAgEEbRwMhUoBAQEBAwEBEBERDAE?= =?us-ascii?q?BLAsBCwQCAQYCEQQBAQMCIwMCAgIfBgsUAQUDCAIEAQ0FCBMHgjVMgWoDHQE?= =?us-ascii?q?CDI1ekGACgTiIX3GBL4J5AQEFhH0NC4IPAwaBDCgBi1IXgUA/gVeBTlAuPoI?= =?us-ascii?q?aRwEBgTopFYJzMoImiymCY4UZlHU9CQKCDY8xgTSCS5ZJgxuJU4hcjRwCBAI?= =?us-ascii?q?EBQIOAQEFgVYHKoFXcBU7gmyCDzcagx+FFIU/coEpixWCUgEB?=
X-IronPort-AV: E=Sophos;i="5.60,523,1549929600"; d="scan'208";a="569057313"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 May 2019 15:22:36 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x4SFMaeY032648 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 May 2019 15:22:36 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 28 May 2019 10:22:35 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 28 May 2019 11:22:34 -0400
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 28 May 2019 10:22:34 -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=EJyH47wGUWpDCo+7m66THZjsOGVrrfjUcH/peBluYuA=; b=QG+/OcW17n3RIWxYoenEFK3SPUiTbYQ8R4AyEsMPOzeL17ru1WOI0nhkyyZ8jg81+bLvd0JT8PlfWl5DN7GhJbxV+lVQjpuz+6PH04mXZlSitRiYVVLUw6Z3odkWcCXqS1lxN2OJdjzx4iC/WwzaErW3u3/OdvTeCiLAqdiZMmQ=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB3510.namprd11.prod.outlook.com (20.177.226.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.20; Tue, 28 May 2019 15:22:33 +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; Tue, 28 May 2019 15:22:33 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, "'Tony Li'" <tony1athome@gmail.com>, "'Robert Raszuk'" <robert@raszuk.net>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: =?utf-8?B?W0xzcl0g562U5aSNOiAgT3B0aW9uIEIgZnJvbSAiTWlncmF0aW9uIGJldHdl?= =?utf-8?Q?en_normal_flooding_and_flooding_reduction"?=
Thread-Index: AQHVFRzn7tvsGPEB6UiPOJKqVaEf+qaAp1Sw
Date: Tue, 28 May 2019 15:22:33 +0000
Message-ID: <BYAPR11MB3638783CFA80A251F23150EEC11E0@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>
In-Reply-To: <005401d5151c$cbda8120$638f8360$@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:30d:1320:e4f7:6d4c:8387:d33f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d057ef4a-d64b-4079-fdc4-08d6e3804ea3
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3510;
x-ms-traffictypediagnostic: BYAPR11MB3510:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYAPR11MB3510FA4ADEED1919DC2C40BEC11E0@BYAPR11MB3510.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00514A2FE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(39860400002)(366004)(396003)(136003)(189003)(199004)(13464003)(6116002)(2906002)(476003)(11346002)(446003)(486006)(66556008)(66946007)(66476007)(76116006)(14454004)(478600001)(64756008)(6436002)(6306002)(229853002)(73956011)(66446008)(966005)(55016002)(86362001)(9686003)(224303003)(68736007)(71200400001)(71190400001)(8936002)(6246003)(33656002)(53936002)(7736002)(256004)(52536014)(81156014)(14444005)(305945005)(5660300002)(53546011)(316002)(6506007)(76176011)(46003)(7696005)(102836004)(99286004)(4326008)(25786009)(74316002)(81166006)(186003)(110136005); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3510; H:BYAPR11MB3638.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: ODGjZ6XjoZ9XxfZHyLhURWRjyV+S+hRjkuw76Tb0kxjOLVmkAZdiqb0UwrzmGJofRtcfjW9uEeyZ3Mmwx85olVtvZ8oH6Qz3o8rRTr/3MAUgKjWZu00/catGt7QeQ99mAw1QmMOoxKzvUG8MOFk4131KhnZoQTUJFtRcq3IdRj//FnopfpdKnj4YHUlCYUuWanKI3/1C2taUw9XGEH/Z25N/likICMmn6k9g0RIEH0Lwr6bVsbGO8ZjlRKgIG273L+mb5XjjusMmWzZnap3S2RL9fAgwFvovkyg4mfYKWMzEnBcxTokUgnNtWFUC1ffgFfRSUKZL3EllJa2Fg3F3jD4geK9h5yNOC7VXBBAuNglP7UAIWomoNX5kZi0Y41VCX8Yx8RZlCmsEae1qQGUOK37n9fzM2VXd+AzkCRJJxss=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d057ef4a-d64b-4079-fdc4-08d6e3804ea3
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2019 15:22:33.2753 (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: BYAPR11MB3510
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/O7G00QjFbZyC-Y3yMUYFrCuxgOU>
Subject: Re: [Lsr] =?utf-8?b?562U5aSNOiAgT3B0aW9uIEIgZnJvbSAiTWlncmF0aW9uIGJl?= =?utf-8?q?tween_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: Tue, 28 May 2019 15:22:49 -0000

Aijun -

What is missing in this discussion is a definition of the problem to be solved.

Current draft relies on event driven updates to LSPs - the same mechanism that has been used for 30 years to detect all manner of changes in the network.

Before defining a "solution" (let alone voting for which one is best) it would be good to have a definition of what problem is unaddressed currently.

    Les


> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Aijun Wang
> Sent: Monday, May 27, 2019 11:16 PM
> To: 'Tony Li' <tony1athome@gmail.com>om>; 'Robert Raszuk'
> <robert@raszuk.net>
> Cc: lsr@ietf.org
> Subject: [Lsr] 答复: Option B from "Migration between normal flooding and
> flooding reduction"
> 
> Hi, Tony:
> 
> How the receiver judge the leader has stopped advertising the Area Leader
> sub-TLV? Do you need some timers?
> >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