RFC 1850 (rfc1850) - Page 3 of 80
OSPF Version 2 Management Information Base
Alternative Format: Original Text Document
RFC 1850 OSPF MIB November 1995
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 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. Changes from RFC 1253
The changes from RFC 1253 are the following:
(1) The textual convention PositiveInteger was changed from
1..'FFFFFFFF'h to 1..'7FFFFFFF'h at the request of
Marshall Rose.
(2) The textual convention TOSType was changed to reflect the
TOS values defined in the Router Requirements Draft, and
in accordance with the IP Forwarding Table MIB's values.
(3) The names of some objects were changed, conforming to the
convention that an acronym (for example, LSA) is a single
word ("Lsa") in most SNMP names.
(4) textual changes were made to make the MIB readable by
Dave Perkins' SMIC MIB Compiler in addition to Mosy.
This involved changing the case of some characters in
certain names and removing the DEFVAL clauses for
Counters.
(5) The variables ospfAreaStatus and ospfIfStatus were added,
having been overlooked in the original MIB.
(6) The range of the variable ospfLsdbType was extended to
include multicastLink (Group-membership LSA) and
nssaExternalLink (NSSA LSA).
(7) The variable ospfIfMetricMetric was renamed
ospfIfMetricValue, and the following text was removed
from its description:
"The value FFFF is distinguished to mean 'no route via
Baker & Coltun Standards Track