Transposition procedures when advertising service routes

The purpose of the SID Structure Sub-Sub-TLV is twofold:

Figure 1 shows how the FUNCTION part of the SID is transposed. SRv6 in Epipe services is not supported in Release 21.5, but the example illustrates how transposition works, and it would be similar for VPN-IP routes in Release 21.5.

Figure 1. Transposition of the FUNCTION into the NLRI

In the Figure 1 example, PE6 is configured with an Epipe that uses a configured locator with LB length = 40 bits and LN length = 24 bits. The FUNC length is set at 24, and 20 bits are always transposed into the NLRI (non-configurable). Based on the example in Figure 1, the following rules apply:

With the transposition procedure, multiple NLRIs with the same common SRv6 SID (minus the function) can be packed into the same BGP update, as is done for regular VPN-IP or EVPN route for MPLS tunnels. The packing benefit is illustrated in Figure 2.

Figure 2. Transposition and route packing
Note: The transposition procedures do not apply to service SIDs in the base router, advertised via IPv4 and IPv6 families.