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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 10 June 2021 08:20 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 2D2B23A39A3 for <lsr@ietfa.amsl.com>; Thu, 10 Jun 2021 01:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 Gen7xaP_6SlS for <lsr@ietfa.amsl.com>; Thu, 10 Jun 2021 01:20:05 -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 1F4363A39A4 for <lsr@ietf.org>; Thu, 10 Jun 2021 01:20:05 -0700 (PDT)
Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4G0xYr4GGvz6N6LM; Thu, 10 Jun 2021 16:13:20 +0800 (CST)
Received: from dggeme702-chm.china.huawei.com (10.1.199.98) by fraeml707-chm.china.huawei.com (10.206.15.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Thu, 10 Jun 2021 10:20:02 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme702-chm.china.huawei.com (10.1.199.98) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Thu, 10 Jun 2021 16:20:00 +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; Thu, 10 Jun 2021 16:20:00 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, Christian Hopps <chopps@chopps.org>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
Thread-Index: AQHXUnIbKtth+1IMrk6gmc5i1sGGmqsMQVKAgACzxrA=
Date: Thu, 10 Jun 2021 08:20:00 +0000
Message-ID: <6271b00c38694e6ab7f1b711c0e513d0@huawei.com>
References: <m2wnrlcitn.fsf@ja.int.chopps.org> <CABNhwV35Aj7fG+VNKXf8npAKVMCE3kZvduaVhFVxeovRSfo1gA@mail.gmail.com>
In-Reply-To: <CABNhwV35Aj7fG+VNKXf8npAKVMCE3kZvduaVhFVxeovRSfo1gA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.143]
Content-Type: multipart/related; boundary="_004_6271b00c38694e6ab7f1b711c0e513d0huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/DpemnjJ-KQ82f-_GO-WnWzNPz90>
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: Thu, 10 Jun 2021 08:20:10 -0000

Hi Gyan,

Please see some comments inline:

From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Gyan Mishra
Sent: Thursday, June 10, 2021 1:05 PM
To: Christian Hopps <chopps@chopps.org>
Cc: lsr@ietf.org
Subject: Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"


I support WG adoption of this draft.

This draft fills the gap where multiple algorithm identifiers are associated with a link applied to prefix sid and to add parity as now this draft provides Algo association with the adjacency SID as well.  At the end of the introduction is stated that the algorithm identifier should be included as part of the adjacency SID advertisement for SR-MPLS.   What about SRv6?

Does this draft update the SR IGP extensions for
SR-MPLS RFC 8665 8666 8667.

Also does it update the Flex Algo draft?

https://datatracker.ietf.org/doc/html/draft-ietf-lsr-flex-algo-16

In section 5 operations describes how flex Algo plane can now be differentiated on the same  adjacency link with the Algo identifier adjacency sid to Algo plane can now have QOS and link resources characteristics defined which maybe beneficial to TEAS network slicing application as well as used in conjunction with a resource sid for underlay resource provisioning for Enhanced VPN overlay.

[Jie] I see this may be related to the resource-aware SID and its usage for enhanced VPN. While as mentioned in several mails in this thread, the use cases of associating Flex-Algos with different link resources/QoS policy/etc. require new functionality to Flex-Algo, which needs to be discussed separately from this document.

Best regards,
Jie

Kind Regards

Gyan

On Wed, May 26, 2021 at 5:00 PM Christian Hopps <chopps@chopps.org<mailto:chopps@chopps.org>> wrote:

Hi Folks,

This begins a 2 week WG Adoption Call for the following draft:

https://datatracker.ietf.org/doc/draft-peng-lsr-algorithm-related-adjacency-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<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr
--

[图像已被发件人删除。]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>

M 301 502-1347