tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

RFC 4295

 Errata 
Proposed STD
Pages: 109
Top     in Index     Prev     Next
in Group Index     Prev in Group     Next in Group     Group: MIP6

Mobile IPv6 Management Information Base

Part 1 of 5, p. 1 to 5
None       Next RFC Part

 


Top       ToC       Page 1 
Network Working Group                                           G. Keeni
Request for Comments: 4295                          Cyber Solutions Inc.
Category: Standards Track                                       K. Koide
                                                       Tohoku University
                                                               K. Nagami
                                                      INTEC NetCore Inc.
                                                           S. Gundavelli
                                                      Cisco Systems Inc.
                                                              April 2006


                Mobile IPv6 Management Information Base

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.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This memo defines a portion of the Management Information Base (MIB),
   the Mobile-IPv6 MIB, for use with network management protocols in the
   Internet community.  In particular, the Mobile-IPv6 MIB will be used
   to monitor and control the mobile node, home agent, and correspondent
   node functions of a Mobile IPv6 (MIPv6) entity.

Table of Contents

   1. The Internet-Standard Management Framework ......................2
   2. Overview ........................................................2
      2.1. The Mobile IPv6 Protocol Entities ..........................2
      2.2. Terminology ................................................3
   3. Mobile IPv6 Monitoring and Control Requirements .................3
   4. MIB Design ......................................................4
   5. The Mobile-IPv6 MIB .............................................6
   6. Security Considerations .......................................104
   7. IANA Considerations ...........................................106
   8. References ....................................................106
      8.1. Normative References .....................................106
      8.2. Informative References ...................................107
   9. Acknowledgements ..............................................107

Top      ToC       Page 2 
1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).

   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

2.  Overview

2.1.  The Mobile IPv6 Protocol Entities

   Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol that allows nodes
   to remain reachable while moving around in the IPv6 Internet.  An
   entity that implements the MIPv6 protocol is a MIPv6 entity.  There
   are three types of entities envisaged by the MIPv6 protocol.

      mobile node (MN): A node that can change its point of attachment
      from one link to another, while still being reachable via its home
      address.

      correspondent node (CN): A peer node with which a mobile node is
      communicating.  The correspondent node may be either mobile or
      stationary.  (Note that a correspondent node does not necessarily
      require MIPv6 support.)

      home agent (HA): A router on a mobile node's home link with which
      the mobile node has registered its current care-of address.  While
      the mobile node is away from home, the home agent intercepts
      packets on the home link destined to the mobile node's home
      address, encapsulates them, and routes them to the mobile node's
      registered care-of address.

   This document defines a set of managed objects (MOs) that can be used
   to monitor and control MIPv6 entities.

Top      ToC       Page 3 
2.2.  Terminology

   The terminology used in this document is consistent with the
   definitions used in Mobile IPv6 protocol specification [RFC3775].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14, RFC 2119 [RFC2119].

3.  Mobile IPv6 Monitoring and Control Requirements

   For managing a MIPv6 entity it is necessary to monitor
   the following:

       o capabilities of MIPv6 entities
       o traffic due to MIPv6
       o binding-related statistics (at home agent, correspondent
         node, and mobile node)
       o binding details (at home agent and correspondent node)
       o history of Binding Updates (at home agent, correspondent
         node, and mobile node)

   The MIPv6 protocol document stipulates that several MIPv6-related
   parameters should be manually configurable.  The MIPv6 MIB should
   define managed objects that can be used to configure the related
   parameters, for example:

       o the preference value the home agent will use in Router
         Advertisements;
       o the lifetime value the home agent will use in Router
         Advertisements;
       o whether a home agent will send ICMP Mobile Prefix
         Advertisements to mobile nodes;
       o whether a home agent will respond to ICMP Mobile Prefix
         Solicitation messages from mobile nodes; and
       o whether a home agent will process multicast group membership
         control messages from mobile nodes.

Top      ToC       Page 4 
4.  MIB Design

   The basic principle has been to keep the MIB as simple as possible
   and at the same time to make it effective enough so that the
   essential needs of monitoring and control are met.  It is envisaged
   that wherever possible existing MIBs will be used (e.g., IPSec MIB,
   Neighbor Discovery MIB, Tunnel MIB [RFC4087]) for monitor and control
   of MIPv6 entities.

   It is assumed that the Mobile IPv6 Management Information Base
   (MOBILEIPV6-MIB) will always be implemented in conjunction with the
   IPv6-capable version of the IP-MIB [RFC4293].  The MOBILEIPV6-MIB
   uses the textual conventions defined in the INET-ADDRESS-MIB
   [RFC4001].

   The Mobile-IPv6 MIB is composed of the following groups of
   definitions:

       - mip6Core: a generic group containing objects that are
         common to all the Mobile IPv6 entities.
       - mip6Ha: this group models the home agent service.  It is
         composed of objects specific to the services and associated
         advertisement parameters offered by the home agent on each
         of its links.  It also contains objects pertaining to the
         maintenance of the home agent list on each of the links on
         which the service is offered.
       - mip6Mn: this group models the mobile node service.  It is
         composed of objects specific to the Dynamic Home Agent
         discovery function and related parameters.  It also contains
         objects that record the movement of the mobile node.
       - mip6Cn: models the correspondent node and is primarily
         scoped to its participation in the Return Routability
         procedure for achieving Route Optimization triggered by
         the mobile node.
       - mip6Notifications: defines the set of notifications that
         will be used to asynchronously monitor the Mobile IPv6
         entities.

   The tables contained in the above groups are as follows:

       mip6BindingCacheTable   : models the binding cache on the home
                                 agent and correspondent node.  It
                                 contains details of the Binding Update
                                 requests that have been received and
                                 accepted.
       mip6BindingHistoryTable : tracks the history of the binding
                                 cache.
       mip6NodeTrafficTable    : the mobile node-wise traffic counters.

Top      ToC       Page 5 
       mip6MnHomeAddressTable  : contains all the home addresses
                                 pertaining to the mobile node and
                                 the corresponding registration status.
       mip6MnBLTable           : models the Binding Update List on the
                                 mobile node.  It contains information
                                 about the registration requests sent
                                 by the mobile node and the
                                 corresponding results.
       mip6CnCounterTable      : contains the mobile node-wise
                                 registration statistics.
       mip6HaConfTable         : contains the configurable
                                 advertisement parameters for all the
                                 interfaces on which the home agent
                                 service is advertised.
       mip6HaCounterTable      : contains registration statistics
                                 for all mobile nodes registered
                                 with the home agent.
       mip6HaListTable         : contains the list of all routers
                                 that are acting as home agents on
                                 each of the interfaces on which
                                 the home agent service is offered
                                 by this router.
       mip6HaGlAddrTable       : contains the global addresses of
                                 the home agents.


Next RFC Part