smilint output for ./INTEGRATED-SERVICES-GUARANTEED-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| minor error | 1 |
| change recommended | 1 |
| warning | 3 |
| Message Types |
|---|
| Type | Count |
|---|
| integer-misuse (warning) | 3 |
| module-identity-registration (change recommended) | 1 |
| revision-missing (minor error) | 1 |
Messages:
INTEGRATED-SERVICES-GUARANTEED-MIB
1: -- extracted from rfc2214.txt
2: -- at Mon Nov 15 17:11:45 1999
15:
16: intSrvGuaranteed MODULE-IDENTITY
16: change recommended -
warning: uncontrolled MODULE-IDENTITY registration
17: LAST-UPDATED "9511030500Z" -- Thu Aug 28 09:04:22 PDT 1997
18: ORGANIZATION "IETF Integrated Services Working Group"
19: CONTACT-INFO
20: " Fred Baker
21: Postal: Cisco Systems
22: 519 Lado Drive
23: Santa Barbara, California 93111
24: Tel: +1 805 681 0115
25: E-Mail: fred@cisco.com"
26: DESCRIPTION
27: "The MIB module to describe the Guaranteed Service of
28: the Integrated Services Protocol"
29: ::= { intSrv 5 }
29: minor error -
revision for last update is missing
...
71:
72: intSrvGuaranteedIfBacklog OBJECT-TYPE
73: SYNTAX INTEGER (0..'0FFFFFFF'h)
73: warning -
warning: use Integer32 instead of INTEGER in SMIv2
74: UNITS "bytes"
75: MAX-ACCESS read-create
76: STATUS current
77: DESCRIPTION
78: "The Backlog parameter is the data backlog
79: resulting from the vagaries of how a specific
80: implementation deviates from a strict bit-by-
81: bit service. So, for instance, for packetized
82: weighted fair queueing, Backlog is set to the
83: Maximum Packet Size.
84:
85: The Backlog term is measured in units of bytes.
86: An individual element can advertise a Backlog
87: value between 1 and 2**28 (a little over 250
88: megabytes) and the total added over all ele-
89: ments can range as high as (2**32)-1. Should
90: the sum of the different elements delay exceed
91: (2**32)-1, the end-to-end error term should be
92: (2**32)-1."
93: ::= { intSrvGuaranteedIfEntry 1 }
94:
95: intSrvGuaranteedIfDelay OBJECT-TYPE
96: SYNTAX INTEGER (0..'0FFFFFFF'h)
96: warning -
warning: use Integer32 instead of INTEGER in SMIv2
97: UNITS "microseconds"
98: MAX-ACCESS read-create
99: STATUS current
100: DESCRIPTION
101: "The Delay parameter at each service element
102: should be set to the maximum packet transfer
103: delay (independent of bucket size) through the
104: service element. For instance, in a simple
105: router, one might compute the worst case amount
106: of time it make take for a datagram to get
107: through the input interface to the processor,
108: and how long it would take to get from the pro-
109: cessor to the outbound interface (assuming the
110: queueing schemes work correctly). For an Eth-
111: ernet, it might represent the worst case delay
112: if the maximum number of collisions is experi-
113: enced.
114:
115: The Delay term is measured in units of one mi-
116: crosecond. An individual element can advertise
117: a delay value between 1 and 2**28 (somewhat
118: over two minutes) and the total delay added all
119: elements can range as high as (2**32)-1.
120: Should the sum of the different elements delay
121: exceed (2**32)-1, the end-to-end delay should
122: be (2**32)-1."
123: ::= { intSrvGuaranteedIfEntry 2 }
124:
125: intSrvGuaranteedIfSlack OBJECT-TYPE
126: SYNTAX INTEGER (0..'0FFFFFFF'h)
126: warning -
warning: use Integer32 instead of INTEGER in SMIv2
127: MAX-ACCESS read-create
128: STATUS current
129: DESCRIPTION
130: "If a network element uses a certain amount of
131: slack, Si, to reduce the amount of resources
132: that it has reserved for a particular flow, i,
133: the value Si should be stored at the network
134: element. Subsequently, if reservation re-
135: freshes are received for flow i, the network
136: element must use the same slack Si without any
137: further computation. This guarantees consisten-
138: cy in the reservation process.
139:
140: As an example for the use of the slack term,
141: consider the case where the required end-to-end
142: delay, Dreq, is larger than the maximum delay
143: of the fluid flow system. In this, Ctot is the
144: sum of the Backlog terms end to end, and Dtot
145: is the sum of the delay terms end to end. Dreq
146: is obtained by setting R=r in the fluid delay
147: formula, and is given by
148:
149: b/r + Ctot/r + Dtot.
150:
151: In this case the slack term is
152:
153: S = Dreq - (b/r + Ctot/r + Dtot).
154:
155: The slack term may be used by the network ele-
156: ments to adjust their local reservations, so
157: that they can admit flows that would otherwise
158: have been rejected. A service element at an in-
159: termediate network element that can internally
160: differentiate between delay and rate guarantees
161: can now take advantage of this information to
162: lower the amount of resources allocated to this
163: flow. For example, by taking an amount of slack
164: s <= S, an RCSD scheduler [5] can increase the
165: local delay bound, d, assigned to the flow, to
166: d+s. Given an RSpec, (Rin, Sin), it would do so
167: by setting Rout = Rin and Sout = Sin - s.
168:
169: Similarly, a network element using a WFQ
170: scheduler can decrease its local reservation
171: from Rin to Rout by using some of the slack in
172: the RSpec. This can be accomplished by using
173: the transformation rules given in the previous
174: section, that ensure that the reduced reserva-
175: tion level will not increase the overall end-
176: to-end delay."
177: ::= { intSrvGuaranteedIfEntry 3 }
178: