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

"Acee Lindem (acee)" <acee@cisco.com> Wed, 29 May 2019 14:00 UTC

Return-Path: <acee@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 2FB01120058 for <lsr@ietfa.amsl.com>; Wed, 29 May 2019 07:00:06 -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=GiHlmqrU; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=eTdPNBys
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 7sFr8L1WpWSj for <lsr@ietfa.amsl.com>; Wed, 29 May 2019 07:00:02 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7BCA120098 for <lsr@ietf.org>; Wed, 29 May 2019 07:00:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5362; q=dns/txt; s=iport; t=1559138402; x=1560348002; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=849PunvMzRiZGdUJGQzfF0lXS9bRsSMmr92SKp2vaZs=; b=GiHlmqrUtFm9LckO68/7q5vQ2M6opEsSPCzkZ4bLLsu82AMDrSLXHsqU +iEhAmv5BzUdajN1PG2bV2fzSyVLXtlyIs8PPWMX0T3hdOOvnIdrnoEWU SqJaN/07AvmX9Jn4NtOn9Qmk5jRZ5h9QWGfG35FCiguUK4WiUJqFhhjsW E=;
IronPort-PHdr: =?us-ascii?q?9a23=3AaEOYWxPO/x0mT1cBeSMl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEuKg/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDOIdJSw?= =?us-ascii?q?dDjMwXmwI6B8vQAEb2IdbhbjcxG4JJU1o2t3w=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AXAABDj+5c/4ENJK1lGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBUQYBAQELAYE9KScDaVUgBAsoCoQJg0cDhFKKHoJXiUKNa4EuFIE?= =?us-ascii?q?QA1QJAQEBDAEBGAsKAgEBhEACF4JeIzQJDgEDAQEEAQECAQRtHAyFSwEBAQM?= =?us-ascii?q?BARAREQwBASwLAQ8CAQYCGAICIwMCAgIfBgsUAQULAgQBDQUigjVLAYFqAx0?= =?us-ascii?q?BAgyNW5BgAoE4iF9xgS+CeQEBBYUGDQuCDwMGgQwoAYtSF4F/gTgfgU5QLj6?= =?us-ascii?q?CGkcBAYE6Dy+CczKCJosrG4JJhRmHXI0iPgkCgg2POoE1gjAbjneHXIx1iGG?= =?us-ascii?q?NIAIEAgQFAg4BAQWBTziBV3AVOyoBgkGCDzcagx+FFIU/coEpikyBMQGBIAE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.60,527,1549929600"; d="scan'208";a="277635697"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 May 2019 14:00:00 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x4TDxxa2019562 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 May 2019 14:00:00 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 29 May 2019 08:59:58 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 29 May 2019 08:59:58 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 29 May 2019 09:59:58 -0400
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=849PunvMzRiZGdUJGQzfF0lXS9bRsSMmr92SKp2vaZs=; b=eTdPNBysv4zJrZZyU0XLiTmHmWY/x6d6fL7cmVVNr0EcNC0GMxn6fTLV11cfnSkWtQ+fWkWKebvC1d9MB5bs4LHe+VH+an8jFlTzXRqFNEUbjV+y6DzsdCGskIKYyGt0EeXggPvsB0mZcDPCgBGuwJ4gaJuFXSscca6DjEvkpTw=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB3488.namprd11.prod.outlook.com (52.135.112.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.16; Wed, 29 May 2019 13:59:57 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::3006:a080:19fa:623e]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::3006:a080:19fa:623e%6]) with mapi id 15.20.1922.021; Wed, 29 May 2019 13:59:57 +0000
From: "Acee Lindem (acee)" <acee@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: AQHVFcAYX2mU2puNTkCEvs7z/7drXKaB3wkA
Date: Wed, 29 May 2019 13:59:57 +0000
Message-ID: <5E97580A-8A7A-4C4F-A482-05C4BA0BE5C1@cisco.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> <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=acee@cisco.com;
x-originating-ip: [173.38.117.66]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bd1a3f41-f3eb-43d8-c306-08d6e43def2d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:SN6PR11MB3488;
x-ms-traffictypediagnostic: SN6PR11MB3488:
x-ms-exchange-purlcount: 1
x-ld-processed: 5ae1af62-9505-4097-a69a-c1553ef7840e,ExtAddr
x-microsoft-antispam-prvs: <SN6PR11MB34880AA234438B976A311872C21F0@SN6PR11MB3488.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0052308DC6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(346002)(136003)(366004)(396003)(189003)(199004)(99286004)(102836004)(6512007)(224303003)(8936002)(6306002)(25786009)(476003)(53936002)(66066001)(2616005)(446003)(14444005)(6506007)(11346002)(256004)(53546011)(4326008)(76176011)(110136005)(486006)(33656002)(6116002)(6246003)(3846002)(26005)(6486002)(229853002)(66946007)(5660300002)(966005)(6436002)(68736007)(81166006)(7736002)(71200400001)(64756008)(305945005)(91956017)(73956011)(186003)(76116006)(66556008)(81156014)(66446008)(66476007)(2906002)(316002)(86362001)(36756003)(478600001)(71190400001)(83716004)(14454004)(82746002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3488; H:SN6PR11MB2845.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: wuF5Yd2PQxvaEQB+HkInVHmz9Zxo58i9UPhyqeKezZKUAdOAg8lefTziGbnoLE7nqK0aHp+vFlarI/bBjOxqZDdQ7f0enrAZ+fqFXPmXabnEYOBHJ2x2rRTx6xcsPIh8NLqjdIwKjzqEjHwYFyws7PU+UfFOmOz1XhvwjptiperoObu2XOmMnYupO1Nlrm8BhHR8ASGPUaO/O6BbZd+0lW61PDJnmbuUG0essrowlS+V+Ey+66Jw/BO1uMVeTl0G9fRJ8HtL+IXvffYcqKAWEPPajk7Wj043IxNbCrlDeIX6EK9DfH2beL7e4f9j+UQAiM7LUa/7W7LVOXMxCWCu/5fM+BPV/I4PUAwyYOgEl/7Ry5Szgizcm4yb8JG84lUMMqYK3DZZ4D71WvPKM0gW6xWiRNG7tYOubAGt+WJz7tI=
Content-Type: text/plain; charset="utf-8"
Content-ID: <B7D36B9F3A1BF1429C1CDE169BBFED3B@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bd1a3f41-f3eb-43d8-c306-08d6e43def2d
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2019 13:59:57.5565 (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: acee@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB3488
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/qwG1t9ZxAGWgJZvdz-4yH-kAuNA>
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 14:00:06 -0000

Hi Aijun, 
The current machinery supports a model where you can have as many area leader candidates as you believe you need for redundancy. It is deployment dependent on how many you have. We really want the same machinery to handle both failure or the area leader or changes to the configuration of the flooding algorithm. However, I'd expect the latter to be a rare event. 
Thanks,
Acee

On 5/28/19, 9:44 PM, "Lsr on behalf of Aijun Wang" <lsr-bounces@ietf.org on behalf of wangaijun@tsinghua.org.cn> wrote:

    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