rfc2006.txt

来自「<VC++网络游戏建摸与实现>源代码」· 文本 代码 · 共 2,027 行 · 第 1/5 页

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
      location without losing connectivity and without changing its IP
      address; it may continue to communicate with other Internet nodes
      at any location using its (constant) IP address, assuming link-
      layer connectivity to a point of attachment is available.

   Home Agent

      A router on a mobile node's home network which tunnels packets for
      delivery to the mobile node when it is away from home, and
      maintains current location information for the mobile node.

   Foreign Agent

      A router on a mobile node's visited network which provides routing
      services to the mobile node while registered.  The foreign agent
      detunnels and delivers packets to the mobile node that were
      tunneled by the mobile node's home agent. For datagrams sent by a
      mobile node, the foreign agent may serve as a default router for
      registered mobile nodes.

   This document specifies the objects used in managing these entities;
   namely, the Mobile Node, the Home Agent, and the Foreign Agent.













Cong, Hamlen & Perkins      Standards Track                     [Page 3]

RFC 2006          Mobile IP MIB Definition using SMIv2      October 1996


3.3.  MIB Groups

   Objects in this MIB are arranged into groups.  Each group is
   organized as a set of related objects.  The overall structure and the
   relationship between groups and the Mobile IP entities are shown
   below:

        Groups            Mobile Node  Foreign Agent  Home Agent
   mipSystemGroup            X               X             X
   mipSecAssociationGroup    X               X             X
   mipSecViolationGroup      X               X             X
   mnSystemGroup             X
   mnDiscoveryGroup          X
   mnRegistrationGroup       X
   maAdvertisementGroup                      X             X
   faSystemGroup                             X
   faAdvertisementGroup                      X
   faRegistrationGroup                       X
   haRegistrationGroup                                     X
   haRegNodeCountersGroup                                  X































Cong, Hamlen & Perkins      Standards Track                     [Page 4]

RFC 2006          Mobile IP MIB Definition using SMIv2      October 1996


4.  Definitions

    MIP-MIB DEFINITIONS ::= BEGIN

    IMPORTS
        Counter32, Gauge32, Integer32, IpAddress, experimental,
        MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
                                        FROM SNMPv2-SMI
        RowStatus, TruthValue, TimeStamp,
        TEXTUAL-CONVENTION
                                        FROM SNMPv2-TC
        MODULE-COMPLIANCE, OBJECT-GROUP
                                        FROM SNMPv2-CONF;

    mipMIB    MODULE-IDENTITY
        LAST-UPDATED    "9606040000Z"
        ORGANIZATION    "IETF Mobile IP Working Group"
        CONTACT-INFO
                "       David Cong
                Postal: Motorola
                        1301 E. Algonquin Rd.
                        Schaumburg, IL 60196
                Phone:  [phone]
                Email:  [e-mail]"
        DESCRIPTION
                "The MIB Module for the Mobile IP."
        ::= { mib-2 44 }

    mipMIBObjects    OBJECT IDENTIFIER ::= { mipMIB 1 }

    -- Groups under mipMIBObjects

    mipSystem    OBJECT IDENTIFIER ::= { mipMIBObjects 1 }
    mipSecurity    OBJECT IDENTIFIER ::= { mipMIBObjects 2 }
    mipMN    OBJECT IDENTIFIER ::= { mipMIBObjects 3 }
    mipMA    OBJECT IDENTIFIER ::= { mipMIBObjects 4 }
    mipFA    OBJECT IDENTIFIER ::= { mipMIBObjects 5 }
    mipHA    OBJECT IDENTIFIER ::= { mipMIBObjects 6 }

    mnSystem    OBJECT IDENTIFIER ::= { mipMN 1 }
    mnDiscovery    OBJECT IDENTIFIER ::= { mipMN 2 }
    mnRegistration    OBJECT IDENTIFIER ::= { mipMN 3 }

    maAdvertisement    OBJECT IDENTIFIER ::= { mipMA 2 }

    faSystem   OBJECT IDENTIFIER ::= { mipFA 1 }
    faAdvertisement   OBJECT IDENTIFIER ::= { mipFA 2 }
    faRegistration    OBJECT IDENTIFIER ::= { mipFA 3 }



Cong, Hamlen & Perkins      Standards Track                     [Page 5]

RFC 2006          Mobile IP MIB Definition using SMIv2      October 1996


    haRegistration    OBJECT IDENTIFIER ::= { mipHA 3 }

    -- Textual convention

    RegistrationFlags  ::= TEXTUAL-CONVENTION
        STATUS      current
        DESCRIPTION
                "This data type is used to define the registration
                flags for Mobile IP registration extension:
                   vjCompression
                       -- Request to use VJ compression
                   gre
                       -- Request to use GRE
                   minEnc
                       -- Request to use minimal encapsulation
                   decapsulationByMN
                       -- Decapsulation by mobile node
                   broadcastDatagram
                       -- Request to receive broadcasts
                   simultaneoursBindings
                       -- Request to retain prior binding(s)."
        SYNTAX      BITS {
                         vjCompression(0),
                         gre(1),
                         minEnc(2),
                         decapsulationbyMN(3),
                         broadcastDatagram(4),
                         simultaneousBindings(5)
                    }

    -- mipSystem Group

    mipEntities OBJECT-TYPE
        SYNTAX      BITS {
                         mobileNode(0),
                         foreignAgent(1),
                         homeAgent(2)
                    }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "This object describes which Mobile IP entities are
                supported by this managed entity. The entity may
                support more than one Mobile IP entities. For example,
                the entity supports both Foreign Agent (FA) and Home
                Agent (HA). Therefore, bit 1 and bit 2 are set to 1
                for this object."
        ::= { mipSystem 1 }



Cong, Hamlen & Perkins      Standards Track                     [Page 6]

RFC 2006          Mobile IP MIB Definition using SMIv2      October 1996


    mipEnable OBJECT-TYPE
        SYNTAX      INTEGER { enabled(1), disabled(2) }
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION
                "Indicates whether the Mobile IP protocol should be
                enabled for the managed entity. If it is disabled, the
                entity should disable both agent discovery and
                registration functions."
        ::= { mipSystem 2 }

    mipEncapsulationSupported   OBJECT-TYPE
        SYNTAX      BITS {
                         ipInIp(0),
                         gre(1),
                         minEnc(2),
                         other(3)
                    }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "Encapsulation methods supported by the Mobile IP
                entity. The entity may support multiple encapsulation
                methods or none of them:
                    ipInIp(0), -- IP Encapsulation within IP
                    gre(1),    -- Generic Routing Encapsulation,
                               -- refers to RFC1701
                    minEnc(2), -- Minimal Encapsulation within IP."
        ::= { mipSystem 3 }

    -- mipSecurity Group

    mipSecAssocTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF MipSecAssocEntry
        MAX-ACCESS      not-accessible
        STATUS      current
        DESCRIPTION
                "A table containing Mobility Security Associations."
        ::= { mipSecurity 1 }

    mipSecAssocEntry OBJECT-TYPE
        SYNTAX      MipSecAssocEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
                "One particular Mobility Security Association."
        INDEX   { mipSecPeerAddress, mipSecSPI }
        ::= { mipSecAssocTable 1 }



Cong, Hamlen & Perkins      Standards Track                     [Page 7]

RFC 2006          Mobile IP MIB Definition using SMIv2      October 1996


    MipSecAssocEntry ::=
        SEQUENCE {
            mipSecPeerAddress IpAddress,
            mipSecSPI Unsigned32,
            mipSecAlgorithmType INTEGER,
            mipSecAlgorithmMode INTEGER,
            mipSecKey OCTET STRING,
            mipSecReplayMethod INTEGER