RFC 2366 (rfc2366) - Page 2 of 76
Definitions of Managed Objects for Multicast over UNI 3
Alternative Format: Original Text Document
RFC 2366 Multicast MIB July 1998
3 IP over ATM Multicast Address Resolution Server MIB
Definitions ............................................... 6
4 Acknowledgments ..............................................73
5 References ...................................................73
6 Security Considerations ......................................74
7 Authors' Addresses ...........................................75
8 Full Copyright Statement .....................................76
1. The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of these
components. They are:
o the SMI, described in RFC 1902 [2] - the mechanisms used for
describing and naming objects for the purpose of management.
o the Textual Conventions, described in RFC 1903 [3] for SNMPv2.
o the Conformance Statements, described in RFC 1904 [4] for
SNMPv2.
o the Simple Network Management Protocol, described in
RFC 1157 [5].
o the Protocol Operations, described in RFC 1905 [6] for
SNMPv2.
o the MIB-II, STD 17, RFC 1213 [7] - the core set of managed
objects for the Internet suite of protocols for SNMPv2.
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 also refer to
the object type.
Chung & Greene Standards Track
