If you need dedicated delivery and want to request a reservation, you use an integrated service policy. There are two types of integrated service policies to create: Guaranteed and controlled load. In this example, guaranteed service is used.
The chief executive officer (CEO) of your company is going to give a live broadcast to a client across the country between 1:00 p.m.- 2:00 p.m. You must guarantee that IP telephony will have guaranteed bandwidth so that there are no interruptions during the broadcast. In this scenario, the application resides on the server.
Because the application your CEO is using requires a smooth, uninterrupted transfer, you decide to use a guaranteed integrated service policy. Guaranteed service controls the maximum queuing delay, so that packets will not be delayed over a designated amount of time.
An integrated service policy is an advanced policy that can require substantial resource. Integrated service policies require the following prerequisites:
Because your server does not have any RSVP-enabled applications, you must write your own RSVP-enabled applications. To write your own applications, use the ReSerVation Protocol (RAPI) API or qtoq quality of service (QoS) socket APIs. For more information, see QoS APIs and look for integrated service APIs.
QoS is a network solution. If you are unsure if the entire network has RSVP capabilities, you can still create an integrated service policy and use a marking to give it some priority; however, priority cannot be guaranteed.
You have a service-level agreement (SLA) with your ISP to ensure that the policies receive the requested priority. The QoS policy you create on the iSeries™ server enables traffic (in the policy) to receive priority throughout the network. The QoS policy does not guarantee the priority and is dependent on your SLA. In fact, taking advantage of QoS policies can give you some leverage to negotiate certain service-levels and rates. Use the service-level agreement link to find out more.