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

peng.shaofu@zte.com.cn Mon, 31 May 2021 01:40 UTC

Return-Path: <peng.shaofu@zte.com.cn>
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 2F2D23A1D53 for <lsr@ietfa.amsl.com>; Sun, 30 May 2021 18:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 va4tKblEC3Lp for <lsr@ietfa.amsl.com>; Sun, 30 May 2021 18:40:54 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 44F483A1D57 for <lsr@ietf.org>; Sun, 30 May 2021 18:40:53 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id E720D1D9C39C83BA46E7 for <lsr@ietf.org>; Mon, 31 May 2021 09:40:49 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id B5C6CE0C4D68CF869BF9; Mon, 31 May 2021 09:40:49 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse-fl2.zte.com.cn with SMTP id 14V1eW8T009708; Mon, 31 May 2021 09:40:32 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid201; Mon, 31 May 2021 09:40:32 +0800 (CST)
Date: Mon, 31 May 2021 09:40:32 +0800
X-Zmail-TransId: 2af960b43e90e65a87c3
X-Mailer: Zmail v1.0
Message-ID: <202105310940326388344@zte.com.cn>
In-Reply-To: <4c7dfd1ff17447b680f6796fd24d03d6@huawei.com>
References: m2wnrlcitn.fsf@ja.int.chopps.org, 202105281159584020571@zte.com.cn, 4c7dfd1ff17447b680f6796fd24d03d6@huawei.com
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: jie.dong@huawei.com
Cc: chopps@chopps.org, lsr@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 14V1eW8T009708
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/OVBmGs_cQo3UqcHiYjWsYixETYU>
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: Mon, 31 May 2021 01:40:59 -0000

Hi Jie,

Thanks. 
Again, in this document we describe local behavior per algorithm thanks to adj-sid per algo, but not describe any resource reservatoin extensions to flex-algo. the later can be discussed in another thread.
IMO the local behavior can be any local policies, such as local repair path, local queue, local priority for entry installation, etc. Adj-sid per algo provides the basis for these local behavior. It is useful to describe how adj-sid per algo can satisfy these usecases, also to facilitate readers to understand its use.

You are very concerned about the extension of resource reservation. Although it is not related to this document and should be discussed in another thread, I will try to answer it in your previous email.

Regards,
PSF




------------------原始邮件------------------
发件人:Dongjie(Jimmy)
收件人:彭少富10053815;
抄送人:chopps@chopps.org;lsr@ietf.org;
日 期 :2021年05月28日 14:24
主 题 :RE: Re:[Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
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