The Int-Serv model provides end-to-end absolute QoS guarantee for users, which of the following reason for the failure of large-scale commercial use?

Question

Options

• ABandwidth reservation is limited
• BLow forwarding efficiency
• CPoor scalability
• DNot conducive to traffic regulation

• A
  3% (2)
• B
  11% (7)
• C
  79% (50)
• D
  6% (4)

Explanation

Int-Serv requires every router along an end-to-end path to maintain per-flow reservation state using RSVP signaling. As the number of active flows across a large network grows into the millions, routers must store and refresh state for each individual flow, which exhausts memory and processing capacity - this is the fundamental scalability failure that makes large-scale deployment impractical. Option A is incorrect because Int-Serv is specifically designed to perform bandwidth reservation; the protocol's weakness is not a cap on reservable bandwidth but the overhead of managing those reservations at scale. Option B is incorrect because packet forwarding itself is not inherently slow in Int-Serv; the bottleneck is the control-plane state management, not the data-plane forwarding. Option D is incorrect because Int-Serv actually includes traffic policing mechanisms (such as token bucket enforcement) and is designed to work with traffic regulation, so this is not its weakness.

Memory tip: Think "per-flow state = scale fails." Int-Serv treats every flow individually at every hop, so the more flows, the more state every router must track - the internet has too many flows for this to work at scale.

No community discussion yet for this question.