RFC 2108 (rfc2108) - Page 2 of 82
Definitions of Managed Objects for IEEE 802
Alternative Format: Original Text Document
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
4. Topology Mapping......................................... 75
5. Acknowledgements......................................... 79
6. References............................................... 80
7. Security Considerations.................................. 81
8. Authors' Addresses....................................... 81
1. The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of three
major components. They are:
o the SMI, described in RFC 1902 [6] - the mechanisms used
for describing and naming objects for the purpose of
management.
o the MIB-II, STD 17, RFC 1213 [5] - the core set of
managed objects for the Internet suite of protocols.
o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905
[9] - the protocol used for accessing managed information.
Textual conventions are defined in RFC 1903 [7], and conformance
statements are defined in RFC 1904 [8].
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. Relationship to RFC 1516
This MIB is intended as a superset of that defined by RFC 1516 [11],
which will go to historic status. This MIB includes all of the
objects contained in that MIB, plus several new ones which provide
de Graaf, et. al. Standards Track