The Definitions of Managed Objects for IP Mobility Support using SMIv2
RFC 2006

 
Document Type RFC - Proposed Standard (October 1996; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2006 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                       D. Cong & M. Hamlen, Editors
Request for Comments: 2006                                      Motorola
Category: Standards Track                             C. Perkins, Editor
                                                                     IBM
                                                            October 1996

       The Definitions of Managed Objects for IP Mobility Support
                              using SMIv2

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Abstract

   This memo defines the Management Information Base (MIB) for use with
   network management protocols in TCP/IP-based internets.  In
   particular, it describes managed objects used for managing the Mobile
   Node, Foreign Agent and Home Agent of the Mobile IP Protocol.

Table of Contents

   1. The Network Management Framework ......................    2
   2. Objects ...............................................    2
   2.1 Object Definitions ...................................    2
   3. Overview ..............................................    2
   3.1 Object Selection Criteria ............................    2
   3.2 Structure of the Mobile IP ...........................    3
   3.3 MIB Groups ...........................................    4
   4. Definitions ...........................................    5
   5. Acknowledgements ......................................   49
   6. Security Considerations ...............................   49
   7. References ............................................   50
   8. Chair's Address .......................................   51
   9. Editors' Addresses ....................................   52

Cong, Hamlen & Perkins      Standards Track                     [Page 1]
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                     [Page 2]
RFC 2006          Mobile IP MIB Definition using SMIv2      October 1996

   (4)  Exclude objects which are simply derivable from others in this or
   other MIBs.

3.2.  Structure of the Mobile IP

   This section describes the basic model of Mobile IP used in
   developing the Mobile IP MIB. This information should be useful to
   the implementor in understanding some of the basic design decisions
   of the MIB.

   The Mobile IP Protocol introduces these new funtional entities:

   Mobile Node

      A host or router that changes its point of attachment from one
      network or subnetwork to another.  A mobile node may change its
Show full document text