RFC 2128 (rfc2128) - Page 2 of 34
Dial Control Management Information Base using SMIv2
Alternative Format: Original Text Document
RFC 2128 Dial Control MIB March 1997
6 Security Considerations ...................................... 33
7 Author's Address ............................................. 34
1. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework presently consists of three
major components. They are:
o the SMI, described in RFC 1902 [1] - the mechanisms used for
describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed
objects for the Internet suite of protocols.
o the protocol, STD 15, RFC 1157 [3] and/or RFC 1905 [4], -
the protocol for accessing managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
1.1. Object Definitions
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to refer to the
object type.
2. Overview
2.1. Structure of MIB
Managing demand access circuits requires the following groups of
information:
o General configuration information.
o Information to describe peer configuration and peer statistics.
In this respect, peer configuration means information on how to
connect to peers on outgoing calls, how to identify peers on
incoming calls, and other call related configuration
information.
o Information to store active call information.
Roeck Standards Track