Sending it again.
Juniper Business Use Only From: spring <spring-boun...@ietf.org> On Behalf Of Rajesh M Sent: Saturday, August 22, 2020 8:43 AM To: gdawra.i...@gmail.com; cfils...@cisco.com; rob...@raszuk.net; bruno.decra...@orange.com; zhuangshun...@huawei.com; jorge.raba...@nokia.com Cc: spring@ietf.org Subject: [spring] https://tools.ietf.org/html/draft-ietf-bess-srv6-services-04 [External Email. Be cautious of content] 5<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-bess-srv6-services-04*section-5__;Iw!!NEt6yMaO-gk!TZ1_c_CakbKuEYdXL_Wr1E0qNsD9LbXA6HMU_M2DQIT4UfAIr09QXsIIcfyxDZIY$>. BGP based L3 service over SRv6 When the egress PE sets the next-hop to a value that is not covered by the SRv6 Locator from which the SRv6 Service SID is allocated, then the ingress PE SHOULD perform reachability check for the SRv6 Service SID in addition to the BGP next-hop reachability procedures. I think we should mention, few points for egress side a) Recommended to set the bgp nexthop based upon locator. b) All the service SIDs across vrfs(DT4,DT6...) must be derived from the same locator (this is independent of setting bgp nexthop) Juniper Business Use Only
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
