Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 28 May 2021 06:24 UTC

Return-Path: <jie.dong@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 4BD913A1AFF for <lsr@ietfa.amsl.com>; Thu, 27 May 2021 23:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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 ZY4Lit0vPmu4 for <lsr@ietfa.amsl.com>; Thu, 27 May 2021 23:24:14 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 022DA3A1AF9 for <lsr@ietf.org>; Thu, 27 May 2021 23:24:14 -0700 (PDT)
Received: from fraeml736-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FrvTr6WZjz6T0yZ for <lsr@ietf.org>; Fri, 28 May 2021 14:12:00 +0800 (CST)
Received: from dggeme704-chm.china.huawei.com (10.1.199.100) by fraeml736-chm.china.huawei.com (10.206.15.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Fri, 28 May 2021 08:24:08 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme704-chm.china.huawei.com (10.1.199.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 28 May 2021 14:24:06 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2176.012; Fri, 28 May 2021 14:24:06 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "peng.shaofu@zte.com.cn" <peng.shaofu@zte.com.cn>
CC: "chopps@chopps.org" <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Re:[Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
Thread-Index: AQHXUnIbKtth+1IMrk6gmc5i1sGGmqr4OmBw//+GeQCAAKjswA==
Date: Fri, 28 May 2021 06:24:06 +0000
Message-ID: <4c7dfd1ff17447b680f6796fd24d03d6@huawei.com>
References: m2wnrlcitn.fsf@ja.int.chopps.org, 039fea6a52d44688990a6ebc9bef0472@huawei.com <202105281159584020571@zte.com.cn>
In-Reply-To: <202105281159584020571@zte.com.cn>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.143]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/SNYHPEcezZTOW0dCykFTUBDqZxI>
Subject: Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
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: Fri, 28 May 2021 06:24:20 -0000

Hi PSF,

Thanks for your pointer to another document which defines the encodings of per-Algo TE link attributes.

But my comments are related to the text in section 3 and 5 of this document, which describes new use cases and operation of Flex-Algo with per Flex-Algo resource reservation or per Flex-Algo QoS policy on the same link. These require extensions to the function of Flex-Algo, which IMO needs to be discussed and compared with other alternative mechanisms. And as you indicated, there are related encoding extensions proposed in other document, thus it may not be just a local behavior. 

So could you reply to the comments in my previous mail?

Best regards,
Jie

> -----Original Message-----
> From: peng.shaofu@zte.com.cn [mailto:peng.shaofu@zte.com.cn]
> Sent: Friday, May 28, 2021 12:00 PM
> To: Dongjie (Jimmy) <jie.dong@huawei.com>
> Cc: chopps@chopps.org; lsr@ietf.org
> Subject: Re:[Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency
> SID Advertisement"
> 
> Hi Jie,
> 
> Thanks for your comments.
> 
> In this document, there are not any extensions to describe resource reservation
> per algo. Are you aiming at another draft
> (https://datatracker.ietf.org/doc/draft-cp-lsr-fa-aware-te/) ?  Please find out
> what you are talking about first.
> Adj-SID per algo can distinguish traffic behavior in local. You are welcome to
> add more usecases based on section 3.
> 
> Regards,
> PSF
> 
> 
> ------------------原始邮件------------------
> 发件人:Dongjie(Jimmy)
> 收件人:Christian Hopps;lsr@ietf.org;
> 日 期 :2021年05月28日 11:40
> 主 题 :Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency
> SID Advertisement"
> Hi,
> I don't support the adoption of this document.
> It seems this document aims to introduce per Flex-Algo Adj-SID to SR-MPLS, its
> typical use case is to provide protection path with Flex-Algo constraints for
> Adj-SID of a particular Flex-Algo, which is described in the case 3 of section 3.
> However, section 3 and section 5 shows that it also aims to introduce further
> changes to the usage and operation of Flex-Algo, which is to provide resource
> reservation based on Flex-Algo. IMO these changes to Flex-Algo deserves
> further discussion and is not only related to the per Flex-Algo Adj-SID extension.
> Here are some comments about this change to Flex-Algo:
> 1. Flex-Algo defines the constraints for path computation in a distributed
> manner, it is not for resource reservation.
> 2. Reserving resources for each Flex-Algo on a link does not make sense. The
> correlation between Flex-Algo and the network links is based on administrative
> groups (color), and the color of the link may or may not be included in the
> Flex-Algo definition. To follow the color based link correlation, a more practical
> approach would be to use Flex-Algo with L2 bundle as defined in
> draft-zhu-lsr-isis-sr-vtn-flexalgo, which uses color to correlate the L3 link and
> the L2 member link to a Flex-Algo, this avoids the extension for per-FlexAlgo
> resource reservation.
> 3. The Flex-Algo link TE attributes are advertised using ASLA, the TE attributes
> are shared by all Flex-Algos which include the link according to the FAD, and
> based on previous discussion, it seems there is no intention to introduce per
> Flex-Algo ID link attributes.
> Best regards,
> Jie
> > -----Original Message-----
> > From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Christian Hopps
> > Sent: Thursday, May 27, 2021 4:57 AM
> > To: lsr@ietf.org
> > Cc: chopps@chopps.org
> > Subject: [Lsr] LSR WG Adoption Call for "Algorithm Related
> > IGP-Adjacency SID Advertisement"
> >
> >
> > Hi Folks,
> >
> > This begins a 2 week WG Adoption Call for the following draft:
> >
> > https://datatracker.ietf.org/doc/draft-peng-lsr-algorithm-related-adja
> > cency-sid
> > /
> >
> > Please indicate your support or objections by June 9th, 2021
> >
> > Authors, please respond to the list indicating whether you are aware
> > of any IPR that applies to this draft.
> >
> > Thanks,
> > Acee and Chris.
> >
> > _______________________________________________
> > 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