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. Kind Regards Gyan On Wed, May 26, 2021 at 5:00 PM Christian Hopps <[email protected]> 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 > [email protected] > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email [email protected] <[email protected]>* *M 301 502-1347*
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
