The complementary roles of RSVP and differentiated services in the full-service QoS network

Abstract

With the growth of the Internet and intranets, QoS technology that has been developed over a span of several years is quickly becoming more relevant. This article first defines QoS and introduces a taxonomy for QoS mechanisms. The evolution of several major QoS mechanisms is described with a special focus on RSVP and differentiated services. Special attention is paid to the role of the IETF in developing QoS mechanisms. We describe a QoS network that combines RSVP and differentiated services in a manner that realizes the benefits of each. We show that, in general, the adoption of increasingly sophisticated QoS mechanisms can enhance the ability of a network to offer high-quality service guarantees while simultaneously making efficient use of raw network resources. These mechanisms carry a cost in the form of increased overhead, which must be weighed against the benefits of the mechanism.

IP Radio Resource Control System

“…To implement this system, we propose putting more cooperative bandwidth control into the IP stack and following along the same architectural lines of the UMTS Radio Resource Control component described in [3]. However, we recommend using the existing IP stacks with QOS extensions as defined by [4], [5], [6], [7] and providing more programmable integration across the layered boundaries. Furthermore, we argue for a rate-based congestion control scheme [2] as a more transport compatible scheme with wireless traffic patterns and varying channel conditions.…”

A gateway architecture for IP satellite networks with dynamic resource management and DiffServ QoS provision

“…In the literature several methods have been proposed to provide quality of service control on IP networks [8]. The most scalable approach is the Differentiated Services (DS) [9].…”

Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network

“…This is becoming increasingly apparent for two reasons. QoS mechanisms need network wide information [4], and for them to succeed, they must not require a tremendous amount of support from the core network. It is becoming increasingly accepted that only at the edge of the network will there be sufficient resources to provide the mechanisms necessary to admit and control various QoS flows.…”