L3VPN remains a fundamental network service due to its combination of traffic isolation, scalability, operational simplicity, and predictable performance. As a result, it is one of the most widely deployed WAN services for both enterprises and service providers.
After the physical topology and control plane were established, the L3VPN service was verified on all participating Provider Edge nodes. The validation used SRv6 with the End.DT46 behavior. The End.DT46 performs packet decapsulation and a lookup in a VRF that supports both IPv4 and IPv6. This enables dual-stack L3VPN services over an IPv6 SRv6 underlay.
Control-plane verification confirmed that each PE received VPNv4 and VPNv6 routes from remote PEs, and these routes included SRv6 service SIDs. These SIDs were verified to be of type End.DT46. Each egress PE instantiated a local End.DT46 SID and was bound to the correct VRF.
Data-plane validation was performed using end-to-end traffic tests between VPN endpoints. IPv4 and IPv6 traffic were forwarded successfully.

For the L3VPN service, a group of participants used SRv6 transposition as defined in RFC 9252. These participants advertised VPN-IP routes using transposed SRv6 SIDs. The common locator was signaled using the SRv6 SID Structure TLV. The function part of the SID was carried in the MPLS label field of the BGP NLRI.