Quality of Service |
When QoS is requested, GQoS invokes the services of the underlying QoS service provider (RSVP SP). The RSVP SP provides the following services:
The RSVP SP initiates and terminates all RSVP signaling on behalf of applications by communicating with the RSVP service (Rsvp.exe). It provides status regarding the QoS reservation to applications that are interested, and minimizes the need for applications to understand RSVP signaling.
The RSVP service communicates with the Kerberos Domain Controller to generate policy elements that are included in RSVP signaling messages. These identify the user so that per-user or per-subnet admission control policies can be applied to network resources.
The RSVP service uses the Traffic Control API to invoke traffic control on behalf of QoS-aware applications in response to GQoS calls or RSVP signaling messages. The RSVP service hides the complexity of the Traffic Control API from applications using the GQoS API, so that applications do not need to be redesigned to make use of traffic control.
The RSVP service communicates with an admission control server, like the Windows 2000 QoS ACS server, to prevent over-commitment of bandwidth on shared segments.