Hi Rajesh, The FlexAlgo for SRv6 is described in https://datatracker.ietf.org/doc/draft-ietf-lsr-flex-algo/ and that would require different SRv6 Locators for the FlexAlgo. When the SRv6 Service SID is allocated from the SRv6 Locator for a FlexAlgo then the service flow will be forwarded along with FlexAlgo path.
I am not entirely sure that I got your question though. Thanks, Ketan From: Rajesh M <mraj...@juniper.net> Sent: 17 May 2021 12:30 To: gdawra.i...@gmail.com; Clarence Filsfils (cfilsfil) <cfils...@cisco.com>; Ketan Talaulikar (ketant) <ket...@cisco.com>; rob...@raszuk.net; bruno.decra...@orange.com; spring@ietf.org Subject: https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services Hi All, As per draft "When providing best-effort connectivity to the egress PE, the ingress PE encapsulates the payload in an outer IPv6 header where the destination address is the SRv6 Service SID associated with the related BGP route update." If we allocate SRv6 Service SID per-VRF then how to support a) Different flex algo with in a VRF ? b) Different flex algo with in a internet (default VRF or global) Thanks Rajesh Juniper Business Use Only
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
