SR-Policy Computation and Signaling using BGP-SR


BGP can be used as an alternative to PCEP for distributing SR Policies to headend routers. Compared to PCEP, which relies on a dedicated PCE–PCC relationship and maintains per-peer control-plane state for path setup and updates, BGP follows a route-based distribution model to propagate policy intent across the network using the BGP SR Policy address family. With the SR Policy extensions, policies can be advertised to multiple headends using standard BGP procedures. This reduces dependence on session-based per-path control and enables more scalable distribution of traffic-steering policies across the network.
The testing validated BGP-based signaling and policy installation. SR Policies were advertised to headend routers, and the correct reception, parsing, and instantiation of these policies were verified. The validation included both SR-MPLS and SRv6 data planes, including SRv6 with both full SIDs and µSIDs. We tested candidate paths carrying multiple Segment Lists for multipath forwarding.

Figure 52

Figure 52: SR-Policy Computation and Signaling using BGP-SR

PCEPCC
ZTE ZENIC ONE R22Keysight IxNetwork

Table 10: SR-Policy Computation and Signaling using BGP-SR - µSID with IPv6 Destination Address

PCEPCC
ZTE ZENIC ONE R22Keysight IxNetwork

Table 11: SR-Policy Computation and Signaling using BGP-SR - SRv6 Full SID with IPv6 Destination Address

PCEPCC
Nokia Network Services Platform (NSP)Arista 7280R3
ZTE ZENIC ONE R22Arista 7280R3

Table 12: SR-Policy Computation and Signaling using BGP-SR - SR-MPLS with IPv6 Destination Address

PCEPCC
Keysight IxNetworkArista 7280R3
Nokia Network Services Platform (NSP)Arista 7280R3
ZTE ZENIC ONE R22Arista 7280R3

Table 13: SR-Policy Computation and Signaling using BGP-SR - SR-MPLS with IPv4 Destination Address

Interested in our testing services?

If you are interested and would like to receive more information, please send us an email and sign up for our newsletter to stay up-to-date.