As per Relevance of the word guaranteed, we have this rfc below:
Network Working Group F.
Request for Comments: 2214 Cisco
Category: Standards Track J.
ArrowPoint
A.
Cisco
September 1997
Integrated Services Management Information
Guaranteed Service Extensions using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in TCP/IP-based internets
In particular, it defines objects for managing the the
attributes defined in the Guaranteed Service of the
Services Model. Comments should be made to the Integrated
Working Group, intserv@isi.edu
Table of
1 The SNMPv2 Network Management Framework ............... 2
1.1 Object Definitions .................................. 2
2 Overview .............................................. 2
2.1 Textual Conventions ................................. 2
3 Definitions ........................................... 3
3.1 Interface Attributes Database ....................... 3
3.2 Notifications ....................................... 6
4 Security Considerations ............................... 7
5 Authors' Addresses .................................... 8
6 Acknowledgements ...................................... 8
7 References ............................................ 8
Baker, et. al. Standards Track [Page 1]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
1. The SNMPv2 Network Management
The SNMPv2 Network Management Framework consists of four
components. They are
o RFC 1441 which defines the SMI, the mechanisms used
describing and naming objects for the purpose
management
o STD 17, RFC 1213 defines MIB-II, the core set of managed
for the Internet suite of protocols
o RFC 1445 which defines the administrative and
architectural aspects of the framework
o RFC 1448 which defines the protocol used for
access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
1.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The
type together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience,
often use a textual string, termed the descriptor, to refer to
object type
2.
2.1. Textual
Several new data types are introduced as a textual convention in
MIB document. These textual conventions enhance the readability
the specification and can ease comparison with other
if appropriate. It should be noted that the introduction of
these textual conventions has no effect on either the syntax nor
semantics of any managed objects. The use of these is merely
artifact of the explanatory method used. Objects defined in terms
one of these methods are always encoded by means of the rules
define the primitive type. Hence, no changes to the SMI or the
are necessary to accommodate these textual conventions which
adopted merely for the convenience of readers and writers in
Baker, et. al. Standards Track [Page 2]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
of the elusive goal of clear, concise, and unambiguous MIB documents
3.
INTEGRATED-SERVICES-GUARANTEED-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-
RowStatus FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-
intSrv FROM INTEGRATED-SERVICES-
ifIndex FROM IF-MIB
-- This MIB module uses the extended OBJECT-TYPE macro
-- defined in [9].
intSrvGuaranteed MODULE-
LAST-UPDATED "9511030500Z" -- Thu Aug 28 09:04:22 PDT 1997
ORGANIZATION "IETF Integrated Services Working Group
CONTACT-
" Fred
Postal: Cisco
519 Lado
Santa Barbara, California 93111
Tel: +1 805 681 0115
E-Mail: fred@cisco.com
"The MIB module to describe the Guaranteed Service
the Integrated Services Protocol
::= { intSrv 5 }
intSrvGuaranteedObjects OBJECT
::= { intSrvGuaranteed 1 }
intSrvGuaranteedNotifications OBJECT
::= { intSrvGuaranteed 2 }
intSrvGuaranteedConformance OBJECT
::= { intSrvGuaranteed 3 }
-- The Integrated Services Interface Attributes
-- contains information that is shared with other
-- procedures such as ST-II
intSrvGuaranteedIfTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
Baker, et. al. Standards Track [Page 3]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
"The attributes of the system's interfaces ex
ported by the Guaranteed Service."
::= { intSrvGuaranteedObjects 1 }
intSrvGuaranteedIfEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The reservable attributes of a given inter
face."
INDEX { ifIndex }
::= { intSrvGuaranteedIfTable 1 }
IntSrvGuaranteedIfEntry ::=
SEQUENCE {
intSrvGuaranteedIfBacklog INTEGER
intSrvGuaranteedIfDelay INTEGER
intSrvGuaranteedIfSlack INTEGER
intSrvGuaranteedIfStatus
}
intSrvGuaranteedIfBacklog OBJECT-
SYNTAX INTEGER (0..'0FFFFFFF'h
UNITS "bytes
MAX-ACCESS read-
STATUS
"The Backlog parameter is the data
resulting from the vagaries of how a
implementation deviates from a strict bit-by
bit service. So, for instance, for
weighted fair queueing, Backlog is set to
Maximum Packet Size
The Backlog term is measured in units of bytes
An individual element can advertise a
value between 1 and 2**28 (a little over 250
megabytes) and the total added over all ele
ments can range as high as (2**32)-1.
the sum of the different elements delay
(2**32)-1, the end-to-end error term should
(2**32)-1."
::= { intSrvGuaranteedIfEntry 1 }
intSrvGuaranteedIfDelay OBJECT-
Baker, et. al. Standards Track [Page 4]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
SYNTAX INTEGER (0..'0FFFFFFF'h
UNITS "microseconds
MAX-ACCESS read-
STATUS
"The Delay parameter at each service
should be set to the maximum packet
delay (independent of bucket size) through
service element. For instance, in a
router, one might compute the worst case
of time it make take for a datagram to
through the input interface to the processor
and how long it would take to get from the pro
cessor to the outbound interface (assuming
queueing schemes work correctly). For an Eth
ernet, it might represent the worst case
if the maximum number of collisions is experi
enced
The Delay term is measured in units of one mi
crosecond. An individual element can
a delay value between 1 and 2**28 (
over two minutes) and the total delay added
elements can range as high as (2**32)-1.
Should the sum of the different elements
exceed (2**32)-1, the end-to-end delay
be (2**32)-1."
::= { intSrvGuaranteedIfEntry 2 }
intSrvGuaranteedIfSlack OBJECT-
SYNTAX INTEGER (0..'0FFFFFFF'h
MAX-ACCESS read-
STATUS
"If a network element uses a certain amount
slack, Si, to reduce the amount of
that it has reserved for a particular flow, i
the value Si should be stored at the
element. Subsequently, if reservation re
freshes are received for flow i, the
element must use the same slack Si without
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-
delay, Dreq, is larger than the maximum
of the fluid flow system. In this, Ctot is
Baker, et. al. Standards Track [Page 5]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
sum of the Backlog terms end to end, and
is the sum of the delay terms end to end.
is obtained by setting R=r in the fluid
formula, and is given
b/r + Ctot/r + Dtot
In this case the slack term
S = Dreq - (b/r + Ctot/r + Dtot).
The slack term may be used by the network ele
ments to adjust their local reservations,
that they can admit flows that would
have been rejected. A service element at an in
termediate network element that can
differentiate between delay and rate
can now take advantage of this information
lower the amount of resources allocated to
flow. For example, by taking an amount of
s <= S, an RCSD scheduler [5] can increase
local delay bound, d, assigned to the flow,
d+s. Given an RSpec, (Rin, Sin), it would do
by setting Rout = Rin and Sout = Sin - s
Similarly, a network element using a
scheduler can decrease its local
from Rin to Rout by using some of the slack
the RSpec. This can be accomplished by
the transformation rules given in the
section, that ensure that the reduced reserva
tion level will not increase the overall end
to-end delay."
::= { intSrvGuaranteedIfEntry 3 }
intSrvGuaranteedIfStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"'valid' on interfaces that are configured
the Guaranteed Service."
::= { intSrvGuaranteedIfEntry 4 }
-- No notifications are currently
-- conformance
Baker, et. al. Standards Track [Page 6]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
intSrvGuaranteedGroups OBJECT
::= { intSrvGuaranteedConformance 1 }
intSrvGuaranteedCompliances OBJECT
::= { intSrvGuaranteedConformance 2 }
-- compliance
intSrvGuaranteedCompliance MODULE-
STATUS
"The compliance statement "
MODULE -- this
MANDATORY-GROUPS {
}
::= { intSrvGuaranteedCompliances 1 }
intSrvGuaranteedIfAttribGroup OBJECT-
OBJECTS {
intSrvGuaranteedIfBacklog
intSrvGuaranteedIfDelay
intSrvGuaranteedIfSlack
}
STATUS
"These objects are required for Systems sup
porting the Guaranteed Service of the Integrat
ed Services Architecture."
::= { intSrvGuaranteedGroups 2 }
4. Security
The use of an SNMP SET results in an RSVP or Integrated
reservation under rules that are different compared to if
reservation was negotiated using RSVP. However, no other
considerations exist other than those imposed by SNMP itself
Baker, et. al. Standards Track [Page 7]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
5. Authors'
Fred
Postal: Cisco
519 Lado
Santa Barbara, California 93111
Phone: +1 805 681 0115
EMail: fred@cisco.
John
Postal: ArrowPoint
235 Littleton
Westford, Massachusetts 01886
Phone: +1 508 692 5875
EMail: jjk@tiac.
Arun
Postal: Cisco
210 W. Tasman
San Jose, California 95314
Phone: +1 408 526 7685
EMail: arun@cisco.
6.
This document was produced by the Integrated Services Working Group
7.
[1] Rose, M., Editor, "Management Information Base
Network Management of TCP/IP-based internets", STD 17, RFC 1213,
May 1990.
[2] Information processing systems - Open
Interconnection - Specification of Abstract Syntax Notation
(ASN.1), International Organization for Standardization
International Standard 8824, (December, 1987).
[3] Information processing systems - Open
Interconnection - Specification of Basic Encoding Rules
Abstract Notation One (ASN.1), International Organization
Standardization. International Standard 8825, (December, 1987).
Baker, et. al. Standards Track [Page 8]
RFC 2214 IS Guaranteed Service MIB using SMIv2 September 1997
Baker, et. al. Standards Track [Page 9]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
