SegmentRouting must cooperate with SDN controller to support traffic engineering.

Question

Options

• ATrue
• BFalse

• A
  24% (6)
• B
  76% (19)

Explanation

Segment Routing (SR) is specifically designed to enable traffic engineering without requiring cooperation from an SDN controller, making option B correct. SR achieves this by encoding the entire forwarding path as a stack of segment identifiers (SIDs) in the packet header at the ingress node, so intermediate nodes simply follow those instructions without needing centralized coordination.

Option A is wrong because it conflates SR with older traffic engineering approaches like RSVP-TE, which do require per-flow signaling and more centralized management. SR's defining strength is that it distributes the traffic engineering intelligence to the head-end node, eliminating the need for a mandatory control-plane dependency.

While SR can optionally integrate with an SDN controller (such as a Segment Routing Path Computation Element, or SR-PCE) to compute more complex paths, this cooperation is an enhancement, not a requirement.

Memory tip: Remember SR as "self-routing" - the source node stamps the full path onto the packet, so the network steers itself without a controller holding its hand.

No community discussion yet for this question.