INT-SERV-GUARANTEED-MIB: View SNMP OID List / Download MIB

The MIB module to describe the Guaranteed Service of the Integrated Services Protocol

The attributes of the system's interfaces ex- ported by the Guaranteed Service.

The reservable attributes of a given inter- face.

The parameter C is the data backlog resulting from the vagaries of how a specific implementa- tion deviates from a strict bit-by-bit service. So, for instance, for packetized weighted fair queueing, C is set to the Maximum Packet Size. The error term C is measured in units of bytes. An individual element can advertise a C value between 1 and 2**28 (a little over 250 mega- bytes) and the total added over all elements can range as high as (2**32)-1. Should the sum of the different elements delay exceed (2**32)-1, the end-to-end error term should be (2**32)-1.

The parameter D at each service element should be set to the maximum packet transfer delay (independent of bucket size) through the ser- vice element. For instance, in a simple router, one might compute the worst case amount of time it make take for a datagram to get through the input interface to the processor, and how long it would take to get from the pro- cessor to the outbound interface (assuming the queueing schemes work correctly). For an Eth- ernet, it might represent the worst case delay if the maximum number of collisions is experi- enced. The error term D is measured in units of one microsecond. An individual element can adver- tise a delay value between 1 and 2**28 (some- what over two minutes) and the total delay ad- ded all elements can range as high as (2**32)- 1. Should the sum of the different elements delay exceed (2**32)-1, the end-to-end delay should be (2**32)-1.

If a network element uses a certain amount of slack, Si, to reduce the amount of resources that it has reserved for a particular flow, i, the value Si should be stored at the network element. Subsequently, if reservation re- freshes are received for flow i, the network element must use the same slack Si without any further computation. This guarantees consisten- cy in the reservation process. As an example for the use of the slack term, consider the case where the required end-to-end delay, Dreq, is larger than the maximum delay of the fluid flow system. The latter is ob- tained by setting R=r in the fluid delay formu- la, and is given by b/r + Ctot/r + Dtot. In this case the slack term is S = Dreq - (b/r + Ctot/r + Dtot). The slack term may be used by the network ele- ments to adjust their local reservations, so that they can admit flows that would otherwise have been rejected. A service element at an in- termediate network element that can internally differentiate between delay and rate guarantees can now take advantage of this information to lower the amount of resources allocated to this flow. For example, by taking an amount of slack s <= S, an RCSD scheduler [5] can increase the local delay bound, d, assigned to the flow, to d+s. Given an RSpec, (Rin, Sin), it would do so by setting Rout = Rin and Sout = Sin - s. Similarly, a network element using a WFQ scheduler can decrease its local reservation from Rin to Rout by using some of the slack in the RSpec. This can be accomplished by using the transformation rules given in the previous section, that ensure that the reduced reserva- tion level will not increase the overall end- to-end delay.

'valid' on interfaces that are configured for the Guaranteed Service.

These objects are required for Systems sup- porting the Guaranteed Service of the Integrat- ed Services Architecture.

The compliance statement