As per Relevance of the word integrated, we have this rfc below:
Network Working Group F.
Request for Comments: 2213 Cisco
Category: Standards Track J.
ArrowPoint
A.
Cisco
September 1997
Integrated Services Management Information Base 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 Integrated Services Model. Comments
be made to the Integrated Services Working Group, int-serv@isi.edu
Table of
1 The SNMPv2 Network Management Framework ............... 2
1.1 Object Definitions .................................. 2
2 Overview .............................................. 2
2.1 Textual Conventions ................................. 2
2.2 Structure of MIB .................................... 3
3 Definitions ........................................... 3
3.2 Interface Attributes Database ....................... 6
3.3 Integrated Services Interface Flows Database ........ 8
4 Security Considerations ............................... 19
5 Authors' Addresses .................................... 20
6 Acknowledgements ...................................... 20
7 References ............................................ 20
Baker, et. al. Standards Track [Page 1]
RFC 2213 Integrated Services 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
objects 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
Baker, et. al. Standards Track [Page 2]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
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
of the elusive goal of clear, concise, and unambiguous MIB documents
2.2. Structure of
The MIB is composed of the following sections
Integrated
Interface Attributes
Interface Flow
3.
INTEGRATED-SERVICES-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Gauge32, Integer32, mib-2 FROM SNMPv2-
TimeInterval, TEXTUAL-CONVENTION, RowStatus
TruthValue FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-
ifIndex, InterfaceIndex FROM IF-MIB
-- This MIB module uses the extended OBJECT-TYPE macro
-- defined in [9].
intSrv MODULE-
LAST-UPDATED "9511030500Z" -- Thu Aug 28 09:04:13 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.
John
Postal: ArrowPoint
235 Littleton
Westford, Massachusetts 01886
Tel: +1 508 692 5875
E-Mail: jjk@tiac.net
"The MIB module to describe the Integrated
Baker, et. al. Standards Track [Page 3]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
Protocol
::= { mib-2 52 }
intSrvObjects OBJECT IDENTIFIER ::= { intSrv 1 }
intSrvGenObjects OBJECT IDENTIFIER ::= { intSrv 2 }
intSrvNotifications OBJECT IDENTIFIER ::= { intSrv 3 }
intSrvConformance OBJECT IDENTIFIER ::= { intSrv 4 }
-- Textual
--
SessionNumber ::= TEXTUAL-
STATUS
"The Session Number convention is used
numbers identifying sessions or saved PATH
RESV information. It is a number in the
returned by a TestAndIncr variable, having
protocol meaning whatsoever but serving
as simple identifier
The alternative was a very complex instance
instance object that became unwieldy."
SYNTAX INTEGER (0..2147483647)
Protocol ::= TEXTUAL-
DISPLAY-HINT "d
STATUS
"The value of the IP Protocol field of an
Datagram Header. This identifies the
layer above IP. For example, the value 6
used for TCP and the value 17 is used for UDP
The values of this field are defined in the As
signed Numbers RFC."
SYNTAX INTEGER (1..255)
SessionType ::= TEXTUAL-
STATUS
"The value of the C-Type field of a Session ob
ject, as defined in the RSVP specification
This value determines the lengths of
strings and use of certain objects such as
'port' variables. If the C-Type calls for
IP6 address, one would expect all source, des
Baker, et. al. Standards Track [Page 4]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
tination, and next/previous hop addresses to
16 bytes long, and for the ports to be UDP/
port numbers, for example."
SYNTAX INTEGER (1..255)
Port ::= TEXTUAL-
DISPLAY-HINT "d
STATUS
"The value of the UDP or TCP Source or Destina
tion Port field, a virtual destination port
generalized port identifier used with the
Authentication Header or Encapsulating
Payload, or other session discriminator. If
is not used, the value should be of length 0.
This pair, when coupled with the IP
of the source and destination system and the
protocol field, uniquely identifies a
stream."
SYNTAX OCTET STRING (SIZE(2..4))
MessageSize ::= TEXTUAL-
DISPLAY-HINT "d
STATUS
"The size of a message in bytes. This is
to specify the minimum and maximum size of
message along an integrated services route."
SYNTAX INTEGER (0..'7FFFFFFF'h
BitRate ::= TEXTUAL-
DISPLAY-HINT "d
STATUS
"The rate, in bits/second, that data may
in the context. Applicable contexts
include the speed of an interface or
circuit, the data rate of a (potentially aggre
gated) data flow, or the data rate to be allo
cated for use by a flow."
SYNTAX INTEGER (0..'7FFFFFFF'h
BurstSize ::= TEXTUAL-
DISPLAY-HINT "d
STATUS
Baker, et. al. Standards Track [Page 5]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
"The number of octets of IP Data, including
Headers, that a stream may send without
for policing."
SYNTAX INTEGER (0..'7FFFFFFF'h
QosService ::= TEXTUAL-
STATUS
"The class of service in use by a flow."
SYNTAX INTEGER {
bestEffort (1), -- Best Effort
guaranteedDelay (2), -- Guaranteed
controlledLoad (5) -- Controlled
}
-- The Integrated Services Interface Attributes Database
-- information about resources allocated by resource
-- protocols, such as RSVP and ST-II
intSrvIfAttribTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The reservable attributes of the system's in
terfaces."
::= { intSrvObjects 1 }
intSrvIfAttribEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The reservable attributes of a given inter
face."
INDEX { ifIndex }
::= { intSrvIfAttribTable 1 }
IntSrvIfAttribEntry ::=
SEQUENCE {
intSrvIfAttribAllocatedBits BitRate
intSrvIfAttribMaxAllocatedBits BitRate
intSrvIfAttribAllocatedBuffer BurstSize
intSrvIfAttribFlows Gauge32,
intSrvIfAttribPropagationDelay Integer32,
Baker, et. al. Standards Track [Page 6]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
intSrvIfAttribStatus
}
intSrvIfAttribAllocatedBits OBJECT-
SYNTAX
UNITS "Bits per second
MAX-ACCESS read-
STATUS
"The number of bits/second currently
to reserved sessions on the interface."
::= { intSrvIfAttribEntry 1 }
intSrvIfAttribMaxAllocatedBits OBJECT-
SYNTAX
UNITS "Bits per second
MAX-ACCESS read-
STATUS
"The maximum number of bits/second that may
allocated to reserved sessions on the inter
face."
::= { intSrvIfAttribEntry 2 }
intSrvIfAttribAllocatedBuffer OBJECT-
SYNTAX
UNITS "Bytes
MAX-ACCESS read-
STATUS
"The amount of buffer space required to
the simultaneous burst of all reserved flows
the interface."
::= { intSrvIfAttribEntry 3 }
intSrvIfAttribFlows OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The number of reserved flows currently
on this interface. A flow can be created ei
ther from a reservation protocol (such as
or ST-II) or via configuration information."
::= { intSrvIfAttribEntry 4 }
Baker, et. al. Standards Track [Page 7]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
intSrvIfAttribPropagationDelay OBJECT-
SYNTAX Integer32
UNITS "microseconds
MAX-ACCESS read-
STATUS
"The amount of propagation delay that this in
terface introduces in addition to that intro
diced by bit propagation delays."
DEFVAL { 0 }-- by default, interfaces are presumed to
-- no extra
::= { intSrvIfAttribEntry 5 }
intSrvIfAttribStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"'active' on interfaces that are configured
RSVP."
::= { intSrvIfAttribEntry 6 }
-- The Integrated Services Active Flows
-- lists all flows active on an outgoing interface,
-- relevant attributes
intSrvFlowTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Information describing the reserved flows us
ing the system's interfaces."
::= { intSrvObjects 2 }
intSrvFlowEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information describing the use of a given in
terface by a given flow. The
intSrvFlowPoliced starts counting at the in
stallation of the flow."
Baker, et. al. Standards Track [Page 8]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
INDEX { intSrvFlowNumber }
::= { intSrvFlowTable 1 }
IntSrvFlowEntry ::=
SEQUENCE {
intSrvFlowNumber SessionNumber
intSrvFlowType SessionType
intSrvFlowOwner INTEGER
intSrvFlowDestAddr OCTET STRING
intSrvFlowSenderAddr OCTET STRING
intSrvFlowDestAddrLength INTEGER
intSrvFlowSenderAddrLength INTEGER
intSrvFlowProtocol Protocol
intSrvFlowDestPort Port
intSrvFlowPort Port
intSrvFlowFlowId INTEGER
intSrvFlowInterface InterfaceIndex
intSrvFlowIfAddr OCTET STRING
intSrvFlowRate BitRate
intSrvFlowBurst BurstSize
intSrvFlowWeight Integer32,
intSrvFlowQueue Integer32,
intSrvFlowMinTU MessageSize
intSrvFlowMaxTU MessageSize
intSrvFlowBestEffort Counter32,
intSrvFlowPoliced Counter32,
intSrvFlowDiscard TruthValue
intSrvFlowService QosService
intSrvFlowOrder INTEGER
intSrvFlowStatus
}
intSrvFlowNumber OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The number of this flow. This is for SNMP In
dexing purposes only and has no relation to
protocol value."
::= { intSrvFlowEntry 1 }
intSrvFlowType OBJECT-
SYNTAX
MAX-ACCESS read-
Baker, et. al. Standards Track [Page 9]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
STATUS
"The type of session (IP4, IP6, IP6 with
information, etc)."
::= { intSrvFlowEntry 2 }
intSrvFlowOwner OBJECT-
SYNTAX INTEGER {
other(1),
rsvp(2),
management(3)
}
MAX-ACCESS read-
STATUS
"The process that installed this flow in
queue policy database."
::= { intSrvFlowEntry 3 }
intSrvFlowDestAddr OBJECT-
SYNTAX OCTET STRING (SIZE(4..16))
MAX-ACCESS read-
STATUS
"The destination address used by all senders
this session. This object may not be
when the value of the RowStatus object is 'ac
tive'."
::= { intSrvFlowEntry 4 }
intSrvFlowSenderAddr OBJECT-
SYNTAX OCTET STRING (SIZE(4..16))
MAX-ACCESS read-
STATUS
"The source address of the sender selected
this reservation. The value of all zeroes in
dicates 'all senders'. This object may not
changed when the value of the RowStatus
is 'active'."
::= { intSrvFlowEntry 5 }
intSrvFlowDestAddrLength OBJECT-
SYNTAX INTEGER(0..128)
Baker, et. al. Standards Track [Page 10]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
MAX-ACCESS read-
STATUS
"The length of the destination address in bits
This is the CIDR Prefix Length, which for IP
hosts and multicast addresses is 32 bits.
object may not be changed when the value of
RowStatus object is 'active'."
::= { intSrvFlowEntry 6 }
intSrvFlowSenderAddrLength OBJECT-
SYNTAX INTEGER(0..128)
MAX-ACCESS read-
STATUS
"The length of the sender's address in bits
This is the CIDR Prefix Length, which for IP
hosts and multicast addresses is 32 bits.
object may not be changed when the value of
RowStatus object is 'active'."
::= { intSrvFlowEntry 7 }
intSrvFlowProtocol OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP Protocol used by a session. This ob
ject may not be changed when the value of
RowStatus object is 'active'."
::= { intSrvFlowEntry 8 }
intSrvFlowDestPort OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The UDP or TCP port number used as a destina
tion port for all senders in this session.
the IP protocol in use, specified
intSrvResvFwdProtocol, is 50 (ESP) or 51 (AH),
this represents a virtual destination
number. A value of zero indicates that the
protocol in use does not have ports. This ob
ject may not be changed when the value of
Baker, et. al. Standards Track [Page 11]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
RowStatus object is 'active'."
::= { intSrvFlowEntry 9 }
intSrvFlowPort OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The UDP or TCP port number used as a
port for this sender in this session. If
IP protocol in use, specified
intSrvResvFwdProtocol is 50 (ESP) or 51 (AH),
this represents a generalized port
(GPI). A value of zero indicates that the
protocol in use does not have ports. This ob
ject may not be changed when the value of
RowStatus object is 'active'."
::= { intSrvFlowEntry 10 }
intSrvFlowFlowId OBJECT-
SYNTAX INTEGER (0..16777215)
MAX-ACCESS read-
STATUS
"The flow ID that this sender is using,
this is an IPv6 session."
::= { intSrvFlowEntry 11 }
intSrvFlowInterface OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ifIndex value of the interface on
this reservation exists."
::= { intSrvFlowEntry 12 }
intSrvFlowIfAddr OBJECT-
SYNTAX OCTET STRING (SIZE(4..16))
MAX-ACCESS read-
STATUS
"The IP Address on the ifEntry on which
reservation exists. This is present
Baker, et. al. Standards Track [Page 12]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
to support those interfaces which layer multi
ple IP Addresses on the interface."
::= { intSrvFlowEntry 13 }
intSrvFlowRate OBJECT-
SYNTAX
UNITS "bits per second
MAX-ACCESS read-
STATUS
"The Reserved Rate of the sender's data stream
If this is a Controlled Load service flow,
rate is derived from the Tspec rate
(r). If this is a Guaranteed service flow
this rate is derived from the Rspec
rate parameter (R)."
::= { intSrvFlowEntry 14 }
intSrvFlowBurst OBJECT-
SYNTAX
UNITS "bytes
MAX-ACCESS read-
STATUS
"The size of the largest burst expected
the sender at a time
If this is less than the sender's
burst size, the receiver is asking the
to provide flow pacing beyond what would
provided under normal circumstances. Such pac
ing is at the network's option."
::= { intSrvFlowEntry 15 }
intSrvFlowWeight OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The weight used to prioritize the traffic
Note that the interpretation of this object
implementation-specific, as
vary in their use of weighting procedures."
::= { intSrvFlowEntry 16 }
Baker, et. al. Standards Track [Page 13]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
intSrvFlowQueue OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The number of the queue used by this traffic
Note that the interpretation of this object
implementation-specific, as
vary in their use of queue identifiers."
::= { intSrvFlowEntry 17 }
intSrvFlowMinTU OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The minimum message size for this flow.
policing algorithm will treat smaller
as though they are this size."
::= { intSrvFlowEntry 18 }
intSrvFlowMaxTU OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The maximum datagram size for this flow
will conform to the traffic specification.
value cannot exceed the MTU of the interface."
::= { intSrvFlowEntry 19 }
intSrvFlowBestEffort OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of packets that were remanded
best effort service."
::= { intSrvFlowEntry 20 }
intSrvFlowPoliced OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Baker, et. al. Standards Track [Page 14]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
"The number of packets policed since the incep
tion of the flow's service."
::= { intSrvFlowEntry 21 }
intSrvFlowDiscard OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"If 'true', the flow is to incur loss
traffic is policed. If 'false', policed traff
ic is treated as best effort traffic."
DEFVAL { false } -- traffic is, by default, treated as
--
::= { intSrvFlowEntry 22 }
intSrvFlowService OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The QoS service being applied to this flow."
::= { intSrvFlowEntry 23 }
intSrvFlowOrder OBJECT-
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-
STATUS
"In the event of ambiguity, the order in
the classifier should make its comparisons
The row with intSrvFlowOrder=0 is tried first
and comparisons proceed in the order of in
creasing value. Non-serial implementations
the classifier should emulate this behavior."
::= { intSrvFlowEntry 24 }
intSrvFlowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"'active' for all active flows. This
Baker, et. al. Standards Track [Page 15]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
may be used to install static classifier infor
mation, delete classifier information, or au
thorize such."
::= { intSrvFlowEntry 25 }
intSrvFlowNewIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object is used to assign values
intSrvFlowNumber as described in 'Textual Con
ventions for SNMPv2'. The network
reads the object, and then writes the
back in the SET that creates a new instance
intSrvFlowEntry. If the SET fails with
code 'inconsistentValue', then the process
be repeated; If the SET succeeds, then the ob
ject is incremented, and the new instance
created according to the manager's directions."
::= { intSrvGenObjects 1 }
-- conformance
intSrvGroups OBJECT IDENTIFIER ::= { intSrvConformance 1 }
intSrvCompliances OBJECT IDENTIFIER ::= { intSrvConformance 2 }
-- compliance
intSrvCompliance MODULE-
STATUS
"The compliance statement "
MODULE -- this
MANDATORY-GROUPS { intSrvIfAttribGroup, intSrvFlowsGroup }
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
Baker, et. al. Standards Track [Page 16]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS not-
Baker, et. al. Standards Track [Page 17]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
"This object is needed only in a system that imple
ments IPv6."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
"read-create access is not required. This may
read-only."
OBJECT
MIN-ACCESS read-
Baker, et. al. Standards Track [Page 18]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
"read-create access is not required. This may
read-only."
::= { intSrvCompliances 1 }
intSrvIfAttribGroup OBJECT-
OBJECTS {
intSrvIfAttribAllocatedBits, intSrvIfAttribMaxAllocatedBits
intSrvIfAttribAllocatedBuffer, intSrvIfAttribFlows
intSrvIfAttribPropagationDelay,
}
STATUS
"These objects are required for Systems sup
porting the Integrated Services Architecture."
::= { intSrvGroups 1 }
intSrvFlowsGroup OBJECT-
OBJECTS {
intSrvFlowType, intSrvFlowOwner, intSrvFlowDestAddr
intSrvFlowSenderAddr, intSrvFlowDestAddrLength
intSrvFlowSenderAddrLength, intSrvFlowProtocol
intSrvFlowDestPort, intSrvFlowPort, intSrvFlowInterface
intSrvFlowBestEffort, intSrvFlowRate, intSrvFlowBurst
intSrvFlowWeight, intSrvFlowQueue, intSrvFlowMinTU
intSrvFlowDiscard, intSrvFlowPoliced, intSrvFlowService
intSrvFlowIfAddr, intSrvFlowOrder,
}
STATUS
"These objects are required for Systems sup
porting the Integrated Services Architecture."
::= { intSrvGroups 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 19]
RFC 2213 Integrated Services 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
The authors would like to thank the following people for
feedback on this document
Lou Berger, Fore
Bob Braden,
Viswanatha Rao,
John Wroclawski,
7.
[1] Rose, M., Editor, "Management Information Base for
Management of TCP/IP-based internets", STD 17, RFC 1213, May 1990.
[2] Information processing systems - Open
Interconnection - Specification of Abstract
Notation One (ASN.1), International Organization
Standardization. International Standard 8824, (December
Baker, et. al. Standards Track [Page 20]
RFC 2213 Integrated Services MIB using SMIv2 September 1997
1987).
[3] Information processing systems - Open
Interconnection - Specification of Basic Encoding
for Abstract Notation One (ASN.1),
Organization for Standardization. International
8825, (December, 1987).
Baker, et. al. Standards Track [Page 21]
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
