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

peng.shaofu@zte.com.cn Thu, 10 June 2021 06:18 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 DB7B13A364E for <lsr@ietfa.amsl.com>; Wed, 9 Jun 2021 23:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Km3ZGhvXtplG for <lsr@ietfa.amsl.com>; Wed, 9 Jun 2021 23:18:04 -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 90EDF3A364C for <lsr@ietf.org>; Wed, 9 Jun 2021 23:18:03 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.215]) by Forcepoint Email with ESMTPS id 40E142721F10603587C7; Thu, 10 Jun 2021 14:17:59 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id 251579BDA7A82198837C; Thu, 10 Jun 2021 14:17:59 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 15A6HgnK087571; Thu, 10 Jun 2021 14:17:42 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid201; Thu, 10 Jun 2021 14:17:42 +0800 (CST)
Date: Thu, 10 Jun 2021 14:17:42 +0800
X-Zmail-TransId: 2af960c1ae86fcbb2b77
X-Mailer: Zmail v1.0
Message-ID: <202106101417420546260@zte.com.cn>
In-Reply-To: <CABNhwV35Aj7fG+VNKXf8npAKVMCE3kZvduaVhFVxeovRSfo1gA@mail.gmail.com>
References: m2wnrlcitn.fsf@ja.int.chopps.org, CABNhwV35Aj7fG+VNKXf8npAKVMCE3kZvduaVhFVxeovRSfo1gA@mail.gmail.com
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: hayabusagsm@gmail.com
Cc: chopps@chopps.org, lsr@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 15A6HgnK087571
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/GnHSnjSIfyitEXmFDKjOgd_8aPc>
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 06:18:09 -0000

Hi Gyan,

Thanks for your support.
Please see inline [PSF]

Regards,
PSF


------------------原始邮件------------------
发件人:GyanMishra
收件人:Christian Hopps;
抄送人:lsr@ietf.org;
日 期 :2021年06月10日 13:05
主 题 :Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


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?

[PSF] For SRv6, tt was born with this ability, since SRv6 END.X SID can be allocated from an algorithm specific Locator.


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

[PSF] Yes.


Also does it update the Flex Algo draft?
https://datatracker.ietf.org/doc/html/draft-ietf-lsr-flex-algo-16

[PSF] No.


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.

[PSF] Agree. Flex-algo can be used alone as a network slicing mechanism for some limited scenarios, and adj-sid per algo provide a basis for this purpose. However this is outside the scope of this document, so it is not described in detailed. 


Kind Regards

Gyan

On Wed, May 26, 2021 at 5:00 PM Christian Hopps <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
https://www.ietf.org/mailman/listinfo/lsr

--

Gyan Mishra
Network Solutions Architect
Email gyan.s.mishra@verizon.com
M 301 502-1347