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

["Dongjie (Jimmy)" <[e-mail]>]

Hi Gyan,

Thanks for your reply. So we (and others) are on the same page about the resources related functionality introduced to Flex-Algo: it need to be discussed separately from this draft.

If the authors agree with this, can this be reflected in an update of this draft?

Best regards,
Jie

From: Lsr [mailto:[e-mail]] On Behalf Of Gyan Mishra
Sent: Friday, June 11, 2021 9:37 AM
To: Dongjie (Jimmy) <[e-mail]>
Cc: [e-mail]; Christian Hopps <[e-mail]>
Subject: Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"


Hi Jimmy

Please see my comments in-line:

Thanks

Gyan
On Thu, Jun 10, 2021 at 4:20 AM Dongjie (Jimmy) <[e-mail]<mailto:[e-mail]>> wrote:
Hi Gyan,

Please see some comments inline:

From: Lsr [mailto:[e-mail]<mailto:[e-mail]>] On Behalf Of Gyan Mishra
Sent: Thursday, June 10, 2021 1:05 PM
To: Christian Hopps <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
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.
 Gyan> I agree as Les and others have mentioned any resources related functionality must first be reviewed and accepted by the WG as a separate document. I agree as others mentioned the main use case is for TI-LFA local protection of backup path so it can use other than default Algo 0.
Best regards,
Jie

Kind Regards

Gyan

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

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

Gyan Mishra

Network Solutions Architect

Email [e-mail]<mailto:[e-mail]>

M 301 502-1347

--

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

Gyan Mishra

Network Solutions Architect

Email [e-mail]<mailto:[e-mail]>

M 301 502-1347