RFC 2213 (rfc2213) - Page 3 of 21
Integrated Services Management Information Base using SMIv2
Alternative Format: Original Text Document
RFC 2213 Integrated Services MIB using SMIv2 September 1997
artifact of the explanatory method used. Objects defined in terms of
one of these methods are always encoded by means of the rules that
define the primitive type. Hence, no changes to the SMI or the SNMP
are necessary to accommodate these textual conventions which are
adopted merely for the convenience of readers and writers in pursuit
of the elusive goal of clear, concise, and unambiguous MIB documents.
2.2. Structure of MIB
The MIB is composed of the following sections:
Integrated Services
Interface Attributes Table
Interface Flow Table
3. Definitions
INTEGRATED-SERVICES-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Gauge32, Integer32, mib-2 FROM SNMPv2-SMI
TimeInterval, TEXTUAL-CONVENTION, RowStatus,
TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex, InterfaceIndex FROM IF-MIB;
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in [9].
intSrv MODULE-IDENTITY
LAST-UPDATED "9511030500Z" -- Thu Aug 28 09:04:13 PDT 1997
ORGANIZATION "IETF Integrated Services Working Group"
CONTACT-INFO
" Fred Baker
Postal: Cisco Systems
519 Lado Drive
Santa Barbara, California 93111
Tel: +1 805 681 0115
E-Mail:
John Krawczyk
Postal: ArrowPoint Communications
235 Littleton Road
Westford, Massachusetts 01886
Tel: +1 508 692 5875
E-Mail: "
DESCRIPTION
"The MIB module to describe the Integrated Services
Baker, et. al. Standards Track