In SRv6 BE scenarios, the original IPv6 packet encapsulation structure remains unchanged. SRv6 packets continue to be IPv6 packets and can be recognized by common IPv6 devices.
Huawei SRv6 Best Effort uses the native IPv6 forwarding plane. The ingress may place the service SID in an outer IPv6 destination address, and ordinary IPv6-capable P routers forward according to their IPv6 FIB without needing to execute SRv6-specific endpoint behavior. SRv6 BE typically uses shortest-path transport based on IGP reachability rather than explicitly engineered segment lists. The packet remains a valid IPv6 packet that standard IPv6 routers can recognize and carry. This supports A as the intended answer, without implying that SRv6 services never add an outer IPv6 header or optional routing extension.
Technical Deep Dive:
A is TRUE. SRv6 represents forwarding instructions as 128-bit IPv6 SIDs combining a routable locator with an endpoint function and possibly arguments. In Best Effort mode an IPv6 underlay computes reachability to the destination locator; intermediate P routers perform ordinary longest-prefix-match forwarding. The SRv6-capable egress PE recognizes the local service SID and executes its behavior, such as End.DT4 for a customer IPv4 VPN. This compatibility allows gradual introduction of SRv6 services without demanding SID processing on every transit node. It is important not to interpret 'original IPv6 packet structure remains unchanged' as a guarantee of no encapsulation overhead: an outer IPv6 header may be added when carrying VPN traffic, and an SRH may be present in other SRv6 modes. The claim concerns the fundamental use of standard IPv6 forwarding and packet format rather than the absence of additional headers.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit