Editing Integrated services (section)

== Problems ==
In order for IntServ to work, all routers along the traffic path must support it. Furthermore, many states must be stored in each router. As a result, IntServ works on a small-scale, but as the system [[Scalability|scales up]] to larger networks or the [[Internet]], it becomes resource intensive to track of all of the reservations.<ref>{{Citation |title=Int-Serv Architecture |url=http://transanatolia.eu/Analyses/Internet/ip%20qos%20architectures/int-serv_architecture.htm |accessdate=2011-12-09 |archive-url=https://web.archive.org/web/20120110185625/http://transanatolia.eu/Analyses/Internet/ip%20qos%20architectures/int-serv_architecture.htm |archive-date=2012-01-10 |url-status=dead }}</ref>

One way to solve the scalability problem is by using a multi-level approach, where per-microflow resource reservation (such as resource reservation for individual users) is done in the edge network, while in the [[core network]] resources are reserved for aggregate flows only.  The routers that lie between these different levels must adjust the amount of aggregate bandwidth reserved from the core network so that the reservation requests for individual flows from the edge network can be better satisfied.<ref>{{cite IETF |title=Aggregation of RSVP for IPv4 and IPv6 Reservations |rfc=3175}}</ref>