Question 280
For an inter-AS service aggregation carrier, the change record describes: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. What preventive validation should be standard?
Explanation
Correct Answer
Document DS-TE bandwidth constraints and test admission cases before enabling policy. This helps prevent recurrence of the issue: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. Acceptance evidence should be: An engineered pair of LSP requests is admitted or rejected in line with the expected class-type bandwidth budget.
Incorrect Answers
Verify flow-label behavior during software and hashing-policy upgrades. That is a sensible control for ANOTHER scenario: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. It is less targeted to this issue than: Document DS-TE bandwidth constraints and test admission cases before enabling policy.
Maintain a tested ingress-to-egress marking map for each QoS service class. That is a sensible control for ANOTHER scenario: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. It is less targeted to this issue than: Document DS-TE bandwidth constraints and test admission cases before enabling policy.
Validate peer hop counts before applying TTL-security to multihop sessions. That is a sensible control for ANOTHER scenario: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. It is less targeted to this issue than: Document DS-TE bandwidth constraints and test admission cases before enabling policy.