IETF Logo Mail Archive

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

Peter Psenak <ppsenak@cisco.com> Tue, 28 May 2019 07:34 UTC

Return-Path: <ppsenak@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 66B201200C4 for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 00:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, T_DKIMWL_WL_HIGH=-0.01, 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
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 B08WG0HBlyMr for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 00:34:27 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C39D12008A for <lsr@ietf.org>; Tue, 28 May 2019 00:34:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2198; q=dns/txt; s=iport; t=1559028866; x=1560238466; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=+/TKoJlGiYM/HQXFfzUVNdZhi4TeLpecZy429fuv/OY=; b=Q1W1W837XqQUKBvaUWLBkkqg5Tx6Nf98APFG4E3rWlXktl/dFxPWW/ge TOZRf6QvNEGGqWiATt9qgNkizB14HRxOnUS1ZR7XExyFN1NpcNHKldy16 x6W4ysssapPNQCBBu9jxrdkypsMnVqy7q7+QQbW4gg8pm97uiiZa3EIhT 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHAABA4+xc/xbLJq1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwIBAQEBAQsBgWaBE4EEKIQTiHuMH4lBjxgUgWcJAQEBDhgLDAEBhEACgwA2Bw4BAwEBBAEBAgEEbRwMhUsBAQQBASEPAQU2CxAJAhgCAiMDAgIhBh8RBgEMBgIBAYJTSwGBagMdD4tNm2qBL4VHgjINXYFABoEMKAGLaYFAP4E4gW1QLj6CGkcBAYE6D4MiglgEiyWHfIdXjR49CYIPghKNH4E0gioGG4xeghSHV4xuiFyNRIFVATGBVzMaCBsVO4JsgkYaiDOFQT0DMIxnglIBAQ
X-IronPort-AV: E=Sophos;i="5.60,521,1549929600"; d="scan'208";a="12537445"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 May 2019 07:34:24 +0000
Received: from [10.60.140.55] (ams-ppsenak-nitro6.cisco.com [10.60.140.55]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTP id x4S7YNbk017686; Tue, 28 May 2019 07:34:23 GMT
To: Aijun Wang <wangaijun@tsinghua.org.cn>, 'Tony Li' <tony1athome@gmail.com>, 'Robert Raszuk' <robert@raszuk.net>
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>
Cc: lsr@ietf.org
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <e2b23e19-4a0a-3ad6-e647-c1afde1e5e56@cisco.com>
Date: Tue, 28 May 2019 09:34:23 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <005401d5151c$cbda8120$638f8360$@org.cn>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.60.140.55, ams-ppsenak-nitro6.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/JXajBwZ6Rdvg_gPdrcWEZF7egJ8>
Subject: Re: [Lsr] 答复: Option B from "Migration between normal flooding and flooding reduction"
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 07:34:28 -0000

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
>
>

v2.23.0 | Report a Bug | By Email