Hi, Repeating my question about the SRv6 Path Verification<https://datatracker.ietf.org/doc/html/draft-yang-spring-srv6-verification-01> draft at the SPRING WG session today.
The diagrams used in the presentation assume that each local representation of each VPN service allocates and advertises just one service SRv6 SID. In this case the draft proposes using the locally allocated and advertised SRv6 SID as the Source address in the SRV6 encapsulation of the traffic it sends. However, the assumption above is not always correct. E.g., in the case of a L3VPN service over SRv6, a VRF that locally represents it in a given PE with multiple Attachment Circuits may allocate dedicated SRv6 service SIDs with End.DX4 or End.DX6 behavior for each of these ACs and advertise them in the VPN-IP routes representing routes that have been locally learned from each AC. My question was: How should the Source IPv6 address in the SRv6 encapsulations of traffic such a VRF sends to remote PEs be selected, and how would the VRF in the remote PE validate the path? Hopefully, these notes clarify my question. Regards, Sasha Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
