Re: [Lsr] A question about draft-ietf-lsr-flex-algo

Huzhibo <huzhibo@huawei.com> Wed, 03 June 2020 12:41 UTC

Return-Path: <huzhibo@huawei.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 8F8103A0AC3; Wed, 3 Jun 2020 05:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 cFE-kO_ZP93K; Wed, 3 Jun 2020 05:41:36 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A22823A0AC2; Wed, 3 Jun 2020 05:41:36 -0700 (PDT)
Received: from lhreml734-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id A54F5249B243217198BF; Wed, 3 Jun 2020 13:41:32 +0100 (IST)
Received: from lhreml734-chm.china.huawei.com (10.201.108.85) by lhreml734-chm.china.huawei.com (10.201.108.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 3 Jun 2020 13:41:32 +0100
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by lhreml734-chm.china.huawei.com (10.201.108.85) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Wed, 3 Jun 2020 13:41:32 +0100
Received: from DGGEMM509-MBX.china.huawei.com ([169.254.9.92]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0487.000; Wed, 3 Jun 2020 20:40:56 +0800
From: Huzhibo <huzhibo@huawei.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "Peter Psenak (ppsenak)" <ppsenak@cisco.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-lsr-flex-algo@ietf.org" <draft-ietf-lsr-flex-algo@ietf.org>
Thread-Topic: A question about draft-ietf-lsr-flex-algo
Thread-Index: AdY5nzy1vCsc9nVaTnicFne+9P6tmgAASADAAADN0jA=
Date: Wed, 03 Jun 2020 12:40:56 +0000
Message-ID: <06CF729DA0D6854E8C1E5121AC3330DFAF670D16@dggemm509-mbx.china.huawei.com>
References: <06CF729DA0D6854E8C1E5121AC3330DFAF670C89@dggemm509-mbx.china.huawei.com> <AM0PR03MB4499C917B6760481045643389D880@AM0PR03MB4499.eurprd03.prod.outlook.com>
In-Reply-To: <AM0PR03MB4499C917B6760481045643389D880@AM0PR03MB4499.eurprd03.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.126]
Content-Type: multipart/alternative; boundary="_000_06CF729DA0D6854E8C1E5121AC3330DFAF670D16dggemm509mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/BhLEYsly2kqyPKa6e_daZDidGTo>
Subject: Re: [Lsr] A question about draft-ietf-lsr-flex-algo
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, 03 Jun 2020 12:41:40 -0000

Hi Alexander, Peter:

     Thank you very much,After I read the WG alias, I still have a lot of doubts, can we calculate the disjoint path by exclude  SRLG in flexalgo? In fact, unless you previously defined two disjoint planes using SRLG, you cannot guarantee that different FlexAlgo can calculate disjoint paths.

Thanks

Zhibo Hu
From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Wednesday, June 3, 2020 8:19 PM
To: Huzhibo <huzhibo@huawei.com>; Peter Psenak (ppsenak) <ppsenak@cisco.com>
Cc: lsr@ietf.org; draft-ietf-lsr-flex-algo@ietf.org
Subject: RE: A question about draft-ietf-lsr-flex-algo

Hi Zhibo Hu,
Welcome to the club - I have already asked the same question and got a response from Peter.
You can find the relevant email thread here<https://mailarchive.ietf.org/arch/msg/spring/wvowYz7mOwR9f6je46qPV_pD9pU/>.

My 2c,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>

From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of Huzhibo
Sent: Wednesday, June 3, 2020 3:07 PM
To: Peter Psenak (ppsenak) <ppsenak@cisco.com<mailto:ppsenak@cisco.com>>
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; draft-ietf-lsr-flex-algo@ietf.org<mailto:draft-ietf-lsr-flex-algo@ietf.org>
Subject: [Lsr] A question about draft-ietf-lsr-flex-algo

Hi Peter:

I noticed that draft-ietf-lsr-flex-algo-07 adds exclude SRLG TLV. SRLG defines a group of risk-sharing link groups. It is generally used to prevent the primary and standby paths from passing the same risk-sharing link group .I don't know why a group of SRLG links should be excluded from the FlexAlgo calculation. What is its usecase?

Thanks

Zhibo Hu

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this
transmission in error, please inform us by e-mail, phone or fax, and then delete the original
and all copies thereof.
___________________________________________________________________________