RFC 2006 (rfc2006) - Page 2 of 52

The Definitions of Managed Objects for IP Mobility Support using SMIv2

RFC 2006          Mobile IP MIB Definition using SMIv2      October 1996


1.  The SNMP Network Management Framework

   The Internet-standard Network Management Framework presently consists
   of three major components.  They are:

      The SMI, described in RFC 1902 [1] - the mechanisms used for
      describing and naming objects for the purpose of management.

      The MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects
      for the Internet suite of protocols.

      The protocol, 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.

2.  Objects

2.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.

3.  Overview

3.1.  Object Selection Criteria

   To be consistent with IAB directives and good engineering practice,
   the authors have applied some criteria to select managed objects for
   the Mobile IP Protocol.

   (1)  Partition management functionality among the Mobile Node, Home
   Agent, and Foreign Agent according to the partitioning seen in
   the Mobile IP Protocol.

   (2)  Require that objects be essential for either fault or
   configuration management.

   (3)  Limit the total number of objects.




Cong, Hamlen & Perkins      Standards Track