draft-ietf-mip4-rfc2006bis-01.txt   draft-ietf-mip4-rfc2006bis-02.txt 
Mobile IP Working Group R. Rathi Mobile IP Working Group R. Rathi
INTERNET DRAFT K. Leung Internet Draft K. Leung
October 2003 H. Sjostrand
June 15, 2006
The Definitions of Managed Objects for IP Mobility Support The Definitions of Managed Objects for IP Mobility Support
using SMIv2, revised using SMIv2, revised
draft-ietf-mip4-rfc2006bis-01.txt draft-ietf-mip4-rfc2006bis-02.txt
Status of this Memo Status of this Memo
This document is an Internet Draft and is in full conformance with By submitting this Internet-Draft, each author represents that
all provisions of Section 10 of RFC2026. Internet Drafts are working any applicable patent or other IPR claims of which he or she is
documents of the Internet Engineering Task Force (IETF), its areas, aware have been or will be disclosed, and any of which he or she
and working groups. Note that other groups may also distribute becomes aware will be disclosed, in accordance with Section 6 of
working documents as Internet Drafts. BCP 79.
Internet Drafts are draft documents valid for a maximum of six months This document may not be modified, and derivative works of it may not
be created, other than to extract section "Mobile IP MIP definitions"
as-is for separate use.
This document may only be posted in an Internet-Draft.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html
This Internet-Draft will expire on Nov 15, 2006.
Abstract Abstract
This memo defines the Management Information Base (MIB) for use with This memo defines the Management Information Base (MIB) for use with
network management protocols in TCP/IP-based internets. In network management protocols in TCP/IP-based internets. In
particular, it describes managed objects used for managing the Mobile particular, it describes managed objects used for managing the Mobile
Node, Foreign Agent and Home Agent of the Mobile IP Protocol. Node, Foreign Agent and Home Agent of the Mobile IP Protocol.
This memo is intended to update and possibly obsolete RFC 2006, This memo is intended to update and possibly obsolete RFC 2006,
however, it is designed to be backward compatible. however, it is designed to be backward compatible
Table of Contents
1. The Network Management Framework . . . . . . . . . . . . . . . . 2
2. Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Object Selection Criteria . . . . . . . . . . . . . . . . . . . 3
3.2. Structure of the Mobile IP . . . . . . . . . . . . . . . . . . 4
3.3. MIB Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.4. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 5
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 76
6. Security Considerations . . . . . . . . . . . . . . . . . . . . . 77
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
A. Changes from RFC 2006 . . . . . . . . . . . . . . . . . . . . . . 80
B. Chair and Editor Addresses . . . . . . . . . . . . . . . . . . . 85
C. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 86
1. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [2].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [11], STD 16, RFC 1212 [12] and RFC 1215 [13].
The second version, called SMIv2, is described in STD 58, RFC
2578 [1], STD 58, RFC 2579 [3] and STD 58, RFC 2580 [4].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [6]. A second version of the SNMP
message protocol, which is not an Internet standards track pro-
tocol, is called SNMPv2c and described in RFC 1901 [14] and RFC
1906 [15]. The third version of the message protocol is called
SNMPv3 and described in RFC 1906 [15], RFC 2572 [16] and RFC
2574 [8].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [6]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[7].
o A set of fundamental applications described in RFC 2573 [17] and Conventions used in this document
the view-based access control mechanism described in RFC 2575
[9].
A more detailed introduction to the current SNMP Management Framework The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
can be found in RFC 2570 [10]. "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119].
Managed objects are accessed via a virtual information store, termed Table of Contents
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A 1. The Internet-Standard Management Framework.....................2
MIB conforming to the SMIv1 can be produced through the appropriate 2. Structure of the MIB...........................................3
translations. The resulting translated MIB must be semantically 2.1. Structure of the Mobile IP................................3
equivalent, except where objects or events are omitted because no 2.2. MIB Groups................................................4
translation is possible (use of Counter64). Some machine readable 2.3. Protocol Extensions.......................................4
information in SMIv2 will be converted into textual descriptions in 2.4. Textual Conventions.......................................5
SMIv1 during the translation process. However, this loss of machine 3. Mobile IP MIB Definitions......................................5
readable information is not considered to change the semantics of the 4. Security Considerations.......................................99
MIB. 5. IANA Considerations..........................................100
6. Acknowledgments..............................................100
APPENDIX A: Changes from RFC 2006...............................102
A.1. Changes in draft-ietf-mobileip-rfc2006bis-00............102
A.2. Changes in draft-ietf-mobileip-rfc2006bis-02............105
A.3. Changes in draft-ietf-mobileip-rfc2006bis-03............106
A.4. Changes in draft-ietf-mip4-rfc2006bis-00................107
A.5. Changes in draft-ietf-mip4-rfc2006bis-01................107
A.6. Changes in draft-ietf-mip4-rfc2006bis-02................107
7. References...................................................108
7.1. Normative References....................................108
7.2. Informative References..................................110
Author's Addresses..............................................110
Intellectual Property Statement.................................110
Disclaimer of Validity..........................................111
Copyright Statement.............................................111
Acknowledgment..................................................111
2. Objects 1. The Internet-Standard Management Framework
2.1. Object Definitions 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 Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the subset of Abstract Syntax Notation One (ASN.1) accessed through the Simple Network Management Protocol (SNMP).
defined in the SMI. In particular, each object type is named by an Objects in the MIB are defined using the mechanisms defined in the
OBJECT IDENTIFIER, an administratively assigned name. The object Structure of Management Information (SMI). This memo specifies a MIB
type together with an object instance serves to uniquely identify a module that is compliant to the SMIv2, which is described in STD 58,
specific instantiation of the object. For human convenience, we RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
often use a textual string, termed the descriptor, to refer to the [RFC2580].
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 configura-
tion management.
(3) Limit the total number of objects. 2. Structure of the MIB
(4) Exclude objects which are simply derivable from others in this This memo defines a portion of the Management Information Base (MIB)
or other MIBs. for the use with network management protocols in the Internet
community. In particular, it describes managed objects for the
Mobile IP Protocol (MIP), as defined in [RFC3344].
3.2. Structure of the Mobile IP 2.1. Structure of the Mobile IP
This section describes the basic model of Mobile IP used in develop- This section describes the basic model of Mobile IP used in
ing the Mobile IP MIB. This information should be useful to the developing the Mobile IP MIB. This information should be useful to
implementor in understanding some of the basic design decisions of the implementor in understanding some of the basic design decisions
the MIB. of the MIB.
The Mobile IP Protocol introduces these new functional entities: The Mobile IP Protocol introduces these new functional entities:
Mobile Node Mobile Node
A host or router that changes its point of attachment from one A host or router that changes its point of attachment from one
network or subnetwork to another. A mobile node may change its network or subnetwork to another. A mobile node may change its
location without losing connectivity and without changing its IP location without losing connectivity and without changing its IP
address; it may continue to communicate with other Internet nodes address; it may continue to communicate with other Internet nodes
at any location using its (constant) IP address, assuming link- at any location using its (constant) IP address, assuming link-
layer connectivity to a point of attachment is available. layer connectivity to a point of attachment is available.
Home Agent Home Agent
A router on a mobile node's home network which tunnels packets A router on a mobile node's home network which tunnels packets for
for delivery to the mobile node when it is away from home, and delivery to the mobile node when it is away from home, and
maintains current location information for the mobile node. maintains current location information for the mobile node.
Foreign Agent Foreign Agent
A router on a mobile node's visited network which provides rout- A router on a mobile node's visited network which provides routing
ing services to the mobile node while registered. The foreign services to the mobile node while registered. The foreign agent
agent detunnels and delivers packets to the mobile node that were detunnels and delivers packets to the mobile node that were
tunneled by the mobile node's home agent. For datagrams sent by a 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 mobile node, the foreign agent may serve as a default router for
registered mobile nodes. registered mobile nodes.
This document specifies the objects used in managing these entities; This document specifies the objects used in managing these entities;
namely, the Mobile Node, the Home Agent, and the Foreign Agent. namely, the Mobile Node, the Home Agent, and the Foreign Agent.
3.3. MIB Groups 2.2. MIB Groups
Objects in this MIB are arranged into groups. Each group is orga- Objects in this MIB are arranged into groups. Each group is
nized as a set of related objects. The overall structure and the organized as a set of related objects. The overall structure and the
relationship between groups and the Mobile IP entities are shown relationship between groups and the Mobile IP entities are shown
below: below:
Groups Mobile Node Foreign Agent Home Agent Groups Mobile Node Foreign Agent Home Agent
mipSystemGroup X X X
mipSecAssociationGroup X X X MipSystemGroup X X X
mipSecViolationGroup X X X MipSecAssociationGroup2 X X X
mnSystemGroup X MipSecViolationGroup2 X X X
MnSystemGroup2 X
mnDiscoveryGroup X mnDiscoveryGroup X
mnRegistrationGroup X mnRegistrationGroup2 X
maAdvertisementGroup X X maAdvertisementGroup2 X X
maAdvertisementNAIGroup X X
faSystemGroup X faSystemGroup X
faAdvertisementGroup X faAdvertisementGroup2 X
faRegistrationGroup X faRegistrationGroup2 X
haRegistrationGroup X haRegistrationGroup2 X
haRegNodeCountersGroup X haRegNodeCountersGroup2 X
mipSecNotificationsGroup2 X X
3.4. Protocol Extensions 2.3. Protocol Extensions
Apart from changes to base specification of Mobile IP [24], it has Apart from changes to base specification of Mobile IP [RFC3344], it
been enhanced in number of ways through its ability for added capa- has been enhanced in number of ways through its ability for added
bilities. Implementations of those capabilities have not been able capabilities. Implementations of those capabilities have not been
to have any management capabilities present in RFC 2006 compliant MIB able to have any management capabilities present in RFC 2006
module agents, since the capabilities themselves postdated the adop- compliant
tion of RFC 2006. For several significant capabilities, in the form
of NAI extension [21], Challenge/Response Extensions [22], Reverse MIB module agents, since the capabilities themselves postdated the
Tunneling [23], and Vendor/Organization-Specific Extensions [25], the adoption of RFC 2006. For several significant capabilities, in the
form of NAI extension [RFC2794], Challenge/Response Extensions
[RFC3012], Reverse Tunneling [RFC3024], Vendor/Organization-Specific
Extensions [RFC3115] and Extensions for carrying NAI [RFC3846], the
MIB Module defined in this document exposes object types to manage MIB Module defined in this document exposes object types to manage
those extended capabilities and their operation. those extended capabilities and their operation.
NAI extension requires a thorough redefinition of MIB table row NAI extension requires a thorough redefinition of MIB table row
indices from the RFC 2006 state since it provides a one more way to indices from the RFC 2006 state since it provides a one more way to
identify the mobile nodes apart from home address. The functional identify the mobile nodes apart from home address. The functional
differences between this memo and RFC 2006 are explained in Appendix differences between this memo and RFC 2006 [RFC2002] are explained in
A. Appendix A.
2.4. Textual Conventions
The RegistrationFlags, MipEntityIdentifierType, MipEntityIdentifier,
MipEntityIdentifierNAI and MipDeliveryStyle are used as textual
conventions in this document. These textual conventions are used for
the convenience of humans reading the MIB. Objects defined using
these conventions are always encoded by means of the rules that
define their primitive type. However, the textual conventions
havecspecial semantics associated with them. Hence, no changes to
the SMI or the SNMP are necessary to accommodate these textual
conventions which are adopted merely for the convenience of readers.
3. Mobile IP MIB Definitions
MIP-MIB DEFINITIONS ::= BEGIN MIP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Gauge32, Integer32, IpAddress, Unsigned32, Counter32, Gauge32, Integer32, IpAddress,
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2 Unsigned32, MODULE-IDENTITY, OBJECT-TYPE,
FROM SNMPv2-SMI NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578]
RowStatus, TruthValue, TimeStamp, RowStatus, TruthValue, TimeStamp,
TEXTUAL-CONVENTION StorageType, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP,
FROM SNMPv2-CONF; NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndex
FROM IF-MIB; -- [RFC2863]
mipMIB MODULE-IDENTITY mipMIB MODULE-IDENTITY
LAST-UPDATED "200309250000Z" LAST-UPDATED "200605260000Z"
ORGANIZATION "IETF Mobile IP Working Group" ORGANIZATION "IETF Mobile IP Working Group"
CONTACT-INFO CONTACT-INFO
" Kent Leung " Ravindra Rathi
Postal: Cisco Systems Greenfield Networks
170 West Tasman Drive rrathi@greenfieldnetworks.com
San Jose, CA 95134 Kent Leung
USA Cisco Systems, Inc.
Phone: +1 408-526-5030 kleung@cisco.com
Email: kleung@cisco.com"
Hans Sjostrand
ipUnplugged
hans@ipunplugged.com"
DESCRIPTION DESCRIPTION
"The MIB Module for the Mobile IP." "The MIB module for configuring and displaying Mobile
REVISION "200309250000Z" IP Information.
Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices."
REVISION "200605260000Z"
DESCRIPTION DESCRIPTION
"Updated for latest changes to Mobile IP." "Updated for latest changes to Mobile IP."
REVISION "199606040000Z" REVISION "199606040000Z"
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC 2006." "Initial revision, published as part of RFC 2006."
::= { mib-2 44 } ::= { mib-2 44 }
mipMIBObjects OBJECT IDENTIFIER ::= { mipMIB 1 } mipMIBObjects OBJECT IDENTIFIER ::= { mipMIB 1 }
-- =================================================================
-- Groups under mipMIBObjects -- Groups under mipMIBObjects
mipSystem OBJECT IDENTIFIER ::= { mipMIBObjects 1 } mipSystem OBJECT IDENTIFIER ::= { mipMIBObjects 1 }
mipSecurity OBJECT IDENTIFIER ::= { mipMIBObjects 2 } mipSecurity OBJECT IDENTIFIER ::= { mipMIBObjects 2 }
mipMN OBJECT IDENTIFIER ::= { mipMIBObjects 3 } mipMN OBJECT IDENTIFIER ::= { mipMIBObjects 3 }
mipMA OBJECT IDENTIFIER ::= { mipMIBObjects 4 } mipMA OBJECT IDENTIFIER ::= { mipMIBObjects 4 }
mipFA OBJECT IDENTIFIER ::= { mipMIBObjects 5 } mipFA OBJECT IDENTIFIER ::= { mipMIBObjects 5 }
mipHA OBJECT IDENTIFIER ::= { mipMIBObjects 6 } mipHA OBJECT IDENTIFIER ::= { mipMIBObjects 6 }
mnSystem OBJECT IDENTIFIER ::= { mipMN 1 } mnSystem OBJECT IDENTIFIER ::= { mipMN 1 }
skipping to change at page 6, line 41 skipping to change at page 7, line 4
mipMN OBJECT IDENTIFIER ::= { mipMIBObjects 3 } mipMN OBJECT IDENTIFIER ::= { mipMIBObjects 3 }
mipMA OBJECT IDENTIFIER ::= { mipMIBObjects 4 } mipMA OBJECT IDENTIFIER ::= { mipMIBObjects 4 }
mipFA OBJECT IDENTIFIER ::= { mipMIBObjects 5 } mipFA OBJECT IDENTIFIER ::= { mipMIBObjects 5 }
mipHA OBJECT IDENTIFIER ::= { mipMIBObjects 6 } mipHA OBJECT IDENTIFIER ::= { mipMIBObjects 6 }
mnSystem OBJECT IDENTIFIER ::= { mipMN 1 } mnSystem OBJECT IDENTIFIER ::= { mipMN 1 }
mnDiscovery OBJECT IDENTIFIER ::= { mipMN 2 } mnDiscovery OBJECT IDENTIFIER ::= { mipMN 2 }
mnRegistration OBJECT IDENTIFIER ::= { mipMN 3 } mnRegistration OBJECT IDENTIFIER ::= { mipMN 3 }
maAdvertisement OBJECT IDENTIFIER ::= { mipMA 2 } maAdvertisement OBJECT IDENTIFIER ::= { mipMA 2 }
faSystem OBJECT IDENTIFIER ::= { mipFA 1 } faSystem OBJECT IDENTIFIER ::= { mipFA 1 }
faAdvertisement OBJECT IDENTIFIER ::= { mipFA 2 } faAdvertisement OBJECT IDENTIFIER ::= { mipFA 2 }
faRegistration OBJECT IDENTIFIER ::= { mipFA 3 } faRegistration OBJECT IDENTIFIER ::= { mipFA 3 }
haRegistration OBJECT IDENTIFIER ::= { mipHA 3 } haRegistration OBJECT IDENTIFIER ::= { mipHA 3 }
-- All deprecated definitions are put towards the end of the MIB. -- All deprecated definitions are put towards the end of the MIB.
-- Textual convention -- =================================================================
-- MIP Textual conventions
RegistrationFlags ::= TEXTUAL-CONVENTION RegistrationFlags ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used to define the registration "This data type is used to define the registration
flags for Mobile IP registration extension: flags for Mobile IP registration extension:
reserved1 reserved
-- Reserved -- Should be set to zero.
reverseTunnel
-- Request to support reverse tunneling
reserved2
-- Reserved
gre gre
-- Request to use GRE -- Request to use GRE
minEnc minEnc
-- Request to use minimal encapsulation -- Request to use minimal encapsulation
decapsulationByMN decapsulationByMN
-- Decapsulation by mobile node -- Decapsulation by mobile node
broadcastDatagram broadcastDatagram
-- Request to receive broadcasts -- Request to receive broadcasts
simultaneousBindings simultaneoursBindings
-- Request to retain prior binding(s) -- Request to retain prior binding(s).
reverseTunnel reverseTunnel
-- Request to support reverse tunneling." -- Reverse Tunneling requested; see [rfc3024]."
SYNTAX BITS { SYNTAX BITS {
reserved1(1), reserved(0),
reverseTunnel(2), gre(1),
reserved2(3), minEnc(2),
gre(4), decapsulationbyMN(3),
minEnc(5), broadcastDatagram(4),
decapsulationbyMN(6), simultaneousBindings(5),
broadcastDatagram(7), reverseTunnel(6)
simultaneousBindings(8)
} }
MipEntityIdentifierType ::= TEXTUAL-CONVENTION MipEntityIdentifierType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that represents a type of Mobile IP entity "A value that represents a type of Mobile IP entity
identifier. identifier.
other(1) Indicates identifier which other(1) Indicates identifier which
is not in one of the formats defined is not in one of the formats defined
below. below.
ipaddress(2) IP address as defined by InetAddressIPv4 ipaddress(2) IP address as defined by IpAddress
textual convention in INET-ADDRESS-MIB. textual convention in INET-ADDRESS-MIB.
nai(3) A network access identifier as defined by nai(3) A network access identifier as defined by
the MipEntityIdentifierNAI textual the MipEntityIdentifierNAI textual
convention." convention."
REFERENCE REFERENCE
"RFC2851 - Textual Conventions for Internet Network "RFC2851 - Textual Conventions for Internet Network
Addresses" Addresses"
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
skipping to change at page 8, line 39 skipping to change at page 9, line 14
period of time. Note that the first 64 octets are used period of time. Note that the first 64 octets are used
as index element." as index element."
SYNTAX OCTET STRING (SIZE (1..64)) SYNTAX OCTET STRING (SIZE (1..64))
MipEntityIdentifierNAI ::= TEXTUAL-CONVENTION MipEntityIdentifierNAI ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a Network Access Identifier (NAI). Mobile "Represents a Network Access Identifier (NAI). Mobile
nodes may use NAI to authenticate themselves to the nodes may use NAI to authenticate themselves to the
foreign agent and home agent and to get the home foreign agent and home agent and to get the home
address dynamically from the home agent." address dynamically from the home agent.
If there are no NAI assigned, a null octet string is
used."
REFERENCE REFERENCE
"RFC2794 - Mobile IP Network Access Identifier "RFC2794 - Mobile IP Network Access Identifier
Extension for IPv4" Extension for IPv4"
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (0..255))
MipDeliveryStyle ::= TEXTUAL-CONVENTION MipDeliveryStyle ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used to indicate the delivery "This data type is used to indicate the delivery
style requested by the mobile node in its registration style requested by the mobile node in its registration
request." request."
REFERENCE REFERENCE
"RFC3024 - Reverse Tunneling for Mobile IP" "RFC3024 - Reverse Tunneling for Mobile IP"
SYNTAX INTEGER { direct(1), encapsulating(2) } SYNTAX INTEGER { direct(1), encapsulating(2) }
-- =================================================================
-- mipSystem Group -- mipSystem Group
mipEntities OBJECT-TYPE mipEntities OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
mobileNode(0), mobileNode(0),
foreignAgent(1), foreignAgent(1),
homeAgent(2) homeAgent(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 9, line 39 skipping to change at page 10, line 29
enabled for the managed entity. If it is disabled, the enabled for the managed entity. If it is disabled, the
entity should disable both agent discovery and entity should disable both agent discovery and
registration functions." registration functions."
::= { mipSystem 2 } ::= { mipSystem 2 }
mipEncapsulationSupported OBJECT-TYPE mipEncapsulationSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
ipInIp(0), ipInIp(0),
gre(1), gre(1),
minEnc(2), minEnc(2),
other(3) other(3),
mipUdp(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Encapsulation methods supported by the Mobile IP "Encapsulation methods supported by the Mobile IP
entity. The entity may support multiple encapsulation entity. The entity may support multiple encapsulation
methods or none of them: methods or none of them:
ipInIp(0), -- IP Encapsulation within IP ipInIp(0) -- IP Encapsulation within IP [RFC2003]
gre(1), -- Generic Routing Encapsulation, gre(1) -- Generic Routing Encapsulation [RFC1701]
-- refers to RFC1701 minEnc(2) -- Minimal Encapsulation within IP [RFC2004]
minEnc(2), -- Minimal Encapsulation within IP." other(3) -- Some other other encapsulation
mipUdp(4) -- MIP UDP encapsulation [RFC3519]"
::= { mipSystem 3 } ::= { mipSystem 3 }
-- =================================================================
-- mipSecurity Group -- mipSecurity Group
--
-- Mobile IP security violation total counter -- Mobile IP security violation total counter
--
mipSecTotalViolations OBJECT-TYPE mipSecTotalViolations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of security violations in the entity." "Total number of security violations in the entity."
::= { mipSecurity 2 } ::= { mipSecurity 2 }
mipSecurityAssocsCount OBJECT-TYPE mipSecurityAssocsCount OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of mobility security associations "Total number of mobility security associations
known to the entity i.e. the number of entries in known to the entity i.e. the number of entries in
the mipSecurityAssocTable." the mipSecurityAssocTable."
::= { mipSecurity 4 } ::= { mipSecurity 4 }
--
-- Mobile IP security association table -- Mobile IP security association table
--
mipSecurityAssocTable OBJECT-TYPE mipSecurityAssocTable OBJECT-TYPE
SYNTAX SEQUENCE OF MipSecurityAssocEntry SYNTAX SEQUENCE OF MipSecurityAssocEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing Mobility Security Associations." "A table containing Mobility Security Associations."
::= { mipSecurity 5 } ::= { mipSecurity 5 }
mipSecurityAssocEntry OBJECT-TYPE mipSecurityAssocEntry OBJECT-TYPE
skipping to change at page 11, line 8 skipping to change at page 12, line 23
MipSecurityAssocEntry ::= MipSecurityAssocEntry ::=
SEQUENCE { SEQUENCE {
mipSecurityPeerIdType MipEntityIdentifierType, mipSecurityPeerIdType MipEntityIdentifierType,
mipSecurityPeerId MipEntityIdentifier, mipSecurityPeerId MipEntityIdentifier,
mipSecuritySPI Unsigned32, mipSecuritySPI Unsigned32,
mipSecurityAlgorithmType INTEGER, mipSecurityAlgorithmType INTEGER,
mipSecurityAlgorithmMode INTEGER, mipSecurityAlgorithmMode INTEGER,
mipSecurityKey OCTET STRING, mipSecurityKey OCTET STRING,
mipSecurityReplayMethod INTEGER, mipSecurityReplayMethod INTEGER,
mipSecurityReplayTime Unsigned32, mipSecurityReplayTime Unsigned32,
mipSecurityStatus RowStatus mipSecurityPeerNAI MipEntityIdentifierNAI,
mipSecurityPeerIpAddress IpAddress,
mipSecurityStatus RowStatus,
mipSecurityStorageType StorageType
} }
mipSecurityPeerIdType OBJECT-TYPE mipSecurityPeerIdType OBJECT-TYPE
SYNTAX MipEntityIdentifierType SYNTAX MipEntityIdentifierType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the peer entity's identifier." "The type of the peer entity's identifier."
::= { mipSecurityAssocEntry 1 } ::= { mipSecurityAssocEntry 1 }
skipping to change at page 13, line 4 skipping to change at page 14, line 36
SYNTAX Unsigned32 (3..255) SYNTAX Unsigned32 (3..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The replay-protection time difference that is "The replay-protection time difference that is
acceptable for this Mobility Security Association when acceptable for this Mobility Security Association when
MipSecurityReplayMethod is set to timestamps." MipSecurityReplayMethod is set to timestamps."
DEFVAL { 7 } DEFVAL { 7 }
::= { mipSecurityAssocEntry 8 } ::= { mipSecurityAssocEntry 8 }
mipSecurityPeerNAI OBJECT-TYPE
SYNTAX MipEntityIdentifierNAI
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The NAI of the peer entity with which this
node shares the mobility security association.
Note that the security association must atleast have
either a NAI, or a non-zero ip address defined."
DEFVAL { ''H } -- the empty string
::= { mipSecurityAssocEntry 9 }
mipSecurityPeerIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP Address of the peer entity with which this
node shares the mobility security association.
If the IP address of peer entity is not yet defined,
an all zero ip address (0.0.0.0) should be used.
Note that the security association must atleast have
either a NAI, or a non-zero ip address defined."
::= { mipSecurityAssocEntry 10 }
mipSecurityStatus OBJECT-TYPE mipSecurityStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status for this table." "The row status for this table."
::= { mipSecurityAssocEntry 9 } ::= { mipSecurityAssocEntry 11 }
mipSecurityStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this entry."
::= { mipSecurityAssocEntry 12 }
--
-- Mobile IP security violation table -- Mobile IP security violation table
--
mipSecurityViolationTable OBJECT-TYPE mipSecurityViolationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MipSecurityViolationEntry SYNTAX SEQUENCE OF MipSecurityViolationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing information about security "A table containing information about security
violations." violations."
::= { mipSecurity 6 } ::= { mipSecurity 6 }
skipping to change at page 13, line 41 skipping to change at page 16, line 29
MipSecurityViolationEntry ::= MipSecurityViolationEntry ::=
SEQUENCE { SEQUENCE {
mipSecurityViolatorIdType MipEntityIdentifierType, mipSecurityViolatorIdType MipEntityIdentifierType,
mipSecurityViolatorId MipEntityIdentifier, mipSecurityViolatorId MipEntityIdentifier,
mipSecurityViolationCounter Counter32, mipSecurityViolationCounter Counter32,
mipSecurityRecentViolationSPI Unsigned32, mipSecurityRecentViolationSPI Unsigned32,
mipSecurityRecentViolationTime TimeStamp, mipSecurityRecentViolationTime TimeStamp,
mipSecurityRecentViolationIDLow Unsigned32, mipSecurityRecentViolationIDLow Unsigned32,
mipSecurityRecentViolationIDHigh Unsigned32, mipSecurityRecentViolationIDHigh Unsigned32,
mipSecurityRecentViolationReason INTEGER mipSecurityRecentViolationReason INTEGER,
mipSecurityViolatorNAI MipEntityIdentifierNAI,
mipSecurityViolatorIpAddress IpAddress,
mipSecurityRecentViolationErrCode Unsigned32,
mipSecurityviolationStorageType StorageType
} }
mipSecurityViolatorIdType OBJECT-TYPE mipSecurityViolatorIdType OBJECT-TYPE
SYNTAX MipEntityIdentifierType SYNTAX MipEntityIdentifierType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of Violator's identifier." "The type of Violator's identifier."
::= { mipSecurityViolationEntry 1 } ::= { mipSecurityViolationEntry 1 }
skipping to change at page 15, line 38 skipping to change at page 18, line 39
missingSecurityExtension(5), missingSecurityExtension(5),
other(6) other(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reason for the most recent security violation for "Reason for the most recent security violation for
this peer." this peer."
::= { mipSecurityViolationEntry 8 } ::= { mipSecurityViolationEntry 8 }
mipSecurityViolatorNAI OBJECT-TYPE
SYNTAX MipEntityIdentifierNAI
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAI of the security violator."
::= { mipSecurityViolationEntry 9 }
mipSecurityViolatorIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP Address of the security violator. If the
IP address of security violator is not yet defined,
an all zero ip address (0.0.0.0) should be returned."
::= { mipSecurityViolationEntry 10 }
mipSecurityRecentViolationErrCode OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The error code for the most recent security
violation for this peer. If there where no reply
message sent back, then zero is used."
::= { mipSecurityViolationEntry 11 }
mipSecurityviolationStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this entry."
::= { mipSecurityViolationEntry 12 }
-- =================================================================
-- mipMN Group -- mipMN Group
-- mipSystem Group
--
-- MN System Group
--
mnState OBJECT-TYPE mnState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
home(1), home(1),
registered(2), registered(2),
pending(3), pending(3),
isolated(4), isolated(4),
unknown(5) unknown(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 16, line 33 skipping to change at page 20, line 41
DESCRIPTION DESCRIPTION
"An IP address that is assigned for an extended period "An IP address that is assigned for an extended period
of time to the mobile node. It remains unchanged of time to the mobile node. It remains unchanged
regardless of the mobile node's current point of regardless of the mobile node's current point of
attachment. If mobile node doesn't have home address attachment. If mobile node doesn't have home address
assigned yet then this object will take the default assigned yet then this object will take the default
value." value."
DEFVAL { '00000000'H } DEFVAL { '00000000'H }
::= { mnSystem 2 } ::= { mnSystem 2 }
mnIdentifierType OBJECT-TYPE
SYNTAX MipEntityIdentifierType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the identifier of the mobile node."
::= { mnSystem 4 }
mnIdentifier OBJECT-TYPE
SYNTAX MipEntityIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identifier of the mobile node."
::= { mnSystem 5 }
--
-- Mobile node's home agent list -- Mobile node's home agent list
--
mnHATable OBJECT-TYPE mnHATable OBJECT-TYPE
SYNTAX SEQUENCE OF MnHAEntry SYNTAX SEQUENCE OF MnHAEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing all of the mobile node's potential "A table containing all of the mobile node's potential
home agents." home agents."
::= { mnSystem 3 } ::= { mnSystem 3 }
skipping to change at page 17, line 41 skipping to change at page 22, line 35
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status for this home agent entry. If the "The row status for this home agent entry. If the
status is set to 'createAndGo' or 'active', then the status is set to 'createAndGo' or 'active', then the
mobile node can use mnHAAddress as a valid candidate mobile node can use mnHAAddress as a valid candidate
for a home agent. If the status is set to 'destroy', for a home agent. If the status is set to 'destroy',
then the mobile node should delete this row, and then the mobile node should delete this row, and
deregister from that home agent." deregister from that home agent."
::= { mnHAEntry 3 } ::= { mnHAEntry 3 }
mnIdentifierType OBJECT-TYPE --
SYNTAX MipEntityIdentifierType -- Mobile node's foreign agent list
MAX-ACCESS read-only --
STATUS current
DESCRIPTION
"The type of the identifier of the mobile node."
::= { mnSystem 4 }
mnIdentifier OBJECT-TYPE
SYNTAX MipEntityIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identifier of the mobile node."
::= { mnSystem 5 }
mnFATable OBJECT-TYPE mnFATable OBJECT-TYPE
SYNTAX SEQUENCE OF MnFAEntry SYNTAX SEQUENCE OF MnFAEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing all foreign agents that the mobile "A table containing all foreign agents that the mobile
node knows about and their corresponding COA (care-of node knows about and their corresponding COA (care-of
address). This COA is an address of a foreign agent address). This COA is an address of a foreign agent
with which the mobile node is registered. The table is with which the mobile node is registered. The table is
skipping to change at page 19, line 11 skipping to change at page 24, line 6
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A care-of address being offered by this foreign agent "A care-of address being offered by this foreign agent
or a co-located care-of address which the mobile node or a co-located care-of address which the mobile node
has associated with one of its own network has associated with one of its own network
interfaces." interfaces."
::= { mnFAEntry 2 } ::= { mnFAEntry 2 }
-- Mobile Node Agent discovery information
-- Mobile node could store multiple agent advertisements, however, -- Mobile node could store multiple agent advertisements, however,
-- only the most recently received agent advertisement information -- only the most recently received agent advertisement information
-- is required to be made available to the manager station. -- is required to be made available to the manager station.
mnRecentAdvReceived OBJECT IDENTIFIER ::= { mnDiscovery 2 } mnRecentAdvReceived OBJECT IDENTIFIER ::= { mnDiscovery 2 }
mnAdvSourceAddress OBJECT-TYPE mnAdvSourceAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 19, line 40 skipping to change at page 24, line 37
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequence number of the most recently received "The sequence number of the most recently received
advertisement. The sequence number ranges from 0 to advertisement. The sequence number ranges from 0 to
0xffff. After the sequence number attains the value 0xffff. After the sequence number attains the value
0xffff, it will roll over to 256." 0xffff, it will roll over to 256."
::= { mnRecentAdvReceived 2 } ::= { mnRecentAdvReceived 2 }
mnAdvFlags OBJECT-TYPE mnAdvFlags OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
reserved0(0),
gre(1), gre(1),
minEnc(2), minEnc(2),
foreignAgent(3), foreignAgent(3),
homeAgent(4), homeAgent(4),
busy(5), busy(5),
regRequired(6), regRequired(6),
reverseTunnel(7) reverseTunnel(7)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 21, line 9 skipping to change at page 26, line 19
mnAdvTimeReceived OBJECT-TYPE mnAdvTimeReceived OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time at which the most recently received "The time at which the most recently received
advertisement was received." advertisement was received."
::= { mnRecentAdvReceived 6 } ::= { mnRecentAdvReceived 6 }
--
-- Mobile Node Discovery Group Counter -- Mobile Node Discovery Group Counter
--
mnSolicitationsSent OBJECT-TYPE mnSolicitationsSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Solicitation sent by the mobile "Total number of Solicitation sent by the mobile
node." node."
::= { mnDiscovery 3 } ::= { mnDiscovery 3 }
skipping to change at page 22, line 48 skipping to change at page 28, line 27
mnAgentRebootsDectected OBJECT-TYPE mnAgentRebootsDectected OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of agent reboots detected by the mobile "Total number of agent reboots detected by the mobile
node through sequence number of the advertisement." node through sequence number of the advertisement."
::= { mnDiscovery 11 } ::= { mnDiscovery 11 }
-- =================================================================
-- Mobile Node Registration Group -- Mobile Node Registration Group
--
-- Registration table of mobile node -- Registration table of mobile node
--
mnRegistrationTable OBJECT-TYPE mnRegistrationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MnRegistrationEntry SYNTAX SEQUENCE OF MnRegistrationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing information about the mobile "A table containing information about the mobile
node's attempted registration(s). The mobile node node's attempted registration(s). The mobile node
updates this table based upon Registration Requests updates this table based upon Registration Requests
sent and Registration Replies received in response to sent and Registration Replies received in response to
these requests. Certain variables within this table these requests. Certain variables within this table
skipping to change at page 26, line 7 skipping to change at page 32, line 20
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Delivery style requested by the mobile node in the "Delivery style requested by the mobile node in the
registration request. If mobile node is operating with registration request. If mobile node is operating with
a co-located care-of address i.e. when mnCOAIsLocal is a co-located care-of address i.e. when mnCOAIsLocal is
true(1), this object should not be instantiated." true(1), this object should not be instantiated."
DEFVAL { direct } DEFVAL { direct }
::= { mnRegistrationEntry 11 } ::= { mnRegistrationEntry 11 }
--
-- Mobile Node Registration Group Counters -- Mobile Node Registration Group Counters
--
mnRegRequestsSent OBJECT-TYPE mnRegRequestsSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of registration requests sent by the "Total number of registration requests sent by the
mobile node. This does not include deregistrations mobile node. This does not include deregistrations
(those with Lifetime equal to zero)." (those with Lifetime equal to zero)."
::= { mnRegistration 2 } ::= { mnRegistration 2 }
skipping to change at page 29, line 28 skipping to change at page 36, line 21
mnRegRequestsWithDirectedBroadcast OBJECT-TYPE mnRegRequestsWithDirectedBroadcast OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Registration Requests sent by mobile "Total number of Registration Requests sent by mobile
node with a directed broadcast address in the home node with a directed broadcast address in the home
agent field." agent field."
::= { mnRegistration 18 } ::= { mnRegistration 18 }
-- =================================================================
-- MA Advertisement Group -- MA Advertisement Group
--
-- MA Advertisement Group Counters -- MA Advertisement Group Counters
--
maAdvertisementsSent OBJECT-TYPE maAdvertisementsSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of advertisements sent by the mobility "Total number of advertisements sent by the mobility
agent." agent."
::= { maAdvertisement 2 } ::= { maAdvertisement 2 }
skipping to change at page 30, line 11 skipping to change at page 37, line 16
maSolicitationsReceived OBJECT-TYPE maSolicitationsReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of solicitations received by the "Total number of solicitations received by the
mobility agent." mobility agent."
::= { maAdvertisement 4 } ::= { maAdvertisement 4 }
--
-- Mobility agent advertisement configuration table -- Mobility agent advertisement configuration table
--
maAdvertConfTable OBJECT-TYPE maAdvertConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MaAdvertConfEntry SYNTAX SEQUENCE OF MaAdvertConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing configurable advertisement "A table containing configurable advertisement
parameters for all advertisement interfaces in parameters for all advertisement interfaces in
the mobility agent." the mobility agent."
::= { maAdvertisement 5 } ::= { maAdvertisement 5 }
skipping to change at page 30, line 34 skipping to change at page 37, line 41
SYNTAX MaAdvertConfEntry SYNTAX MaAdvertConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Advertisement parameters for one advertisement "Advertisement parameters for one advertisement
interface." interface."
INDEX { maAdvertIfIndex } INDEX { maAdvertIfIndex }
::= { maAdvertConfTable 1 } ::= { maAdvertConfTable 1 }
MaAdvertConfEntry ::= SEQUENCE { MaAdvertConfEntry ::= SEQUENCE {
maAdvertIfIndex Integer32, maAdvertIfIndex InterfaceIndex,
maAdvertMaxRegLifetime Integer32, maAdvertMaxRegLifetime Integer32,
maAdvertPrefixLengthInclusion TruthValue, maAdvertPrefixLengthInclusion TruthValue,
maAdvertAddress IpAddress, maAdvertAddress IpAddress,
maAdvertMaxInterval Integer32, maAdvertMaxInterval Integer32,
maAdvertMinInterval Integer32, maAdvertMinInterval Integer32,
maAdvertMaxAdvLifetime Integer32, maAdvertMaxAdvLifetime Integer32,
maAdvertResponseSolicitationOnly TruthValue, maAdvertResponseSolicitationOnly TruthValue,
maAdvertService BITS, maAdvertService BITS,
maAdvertStatus RowStatus maAdvertNetworkNAI MipEntityIdentifierNAI,
maAdvertStatus RowStatus,
maAdvertStorageType StorageType
} }
maAdvertIfIndex OBJECT-TYPE maAdvertIfIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value from Interfaces table of "The ifIndex value from Interfaces table of
MIB II for advertisement interface." MIB II for advertisement interface."
::= { maAdvertConfEntry 1 } ::= { maAdvertConfEntry 1 }
maAdvertMaxRegLifetime OBJECT-TYPE maAdvertMaxRegLifetime OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The longest lifetime in seconds that mobility agent "The longest lifetime in seconds that mobility agent
is willing to accept in any Registration Request." is willing to accept in any Registration Request."
::= { maAdvertConfEntry 2 } ::= { maAdvertConfEntry 2 }
skipping to change at page 32, line 50 skipping to change at page 40, line 37
SYNTAX BITS { foreignAgent(0), SYNTAX BITS { foreignAgent(0),
homeAgent(1) homeAgent(1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates which mobility services are offered on this "Indicates which mobility services are offered on this
interface." interface."
::= { maAdvertConfEntry 9 } ::= { maAdvertConfEntry 9 }
maAdvertNetworkNAI OBJECT-TYPE
SYNTAX MipEntityIdentifierNAI
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This parameter defines the network NAI as adverticed.
The advertised NAI will be included in every HA and FA
agent advertisement that is sent out on the interface
where the NAI is configured."
DEFVAL { ''H } -- the empty string
::= { maAdvertConfEntry 10 }
maAdvertStatus OBJECT-TYPE maAdvertStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status for the agent advertisement table. If "The row status for the agent advertisement table. If
this column status is 'active', the manager should not this column status is 'active', the manager should not
change any column in the row." change any column in the row."
::= { maAdvertConfEntry 10 } ::= { maAdvertConfEntry 11 }
maAdvertStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this entry."
::= { maAdvertConfEntry 12 }
-- =================================================================
-- Foreign Agent Group -- Foreign Agent Group
--
-- Foreign Agent System Group -- Foreign Agent System Group
--
faCOATable OBJECT-TYPE faCOATable OBJECT-TYPE
SYNTAX SEQUENCE OF FaCOAEntry SYNTAX SEQUENCE OF FaCOAEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing all of the care-of addresses "A table containing all of the care-of addresses
(COAs) supported by the foreign agent. New entries can (COAs) supported by the foreign agent. New entries can
be added to the table. The order of entries in the be added to the table. The order of entries in the
faCOATAble is also the order in which the COAs are faCOATAble is also the order in which the COAs are
skipping to change at page 33, line 40 skipping to change at page 42, line 16
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry of COA" "Entry of COA"
INDEX { faSupportedCOA } INDEX { faSupportedCOA }
::= { faCOATable 1 } ::= { faCOATable 1 }
FaCOAEntry ::= FaCOAEntry ::=
SEQUENCE { SEQUENCE {
faSupportedCOA IpAddress, faSupportedCOA IpAddress,
faCOAStatus RowStatus faCOAStatus RowStatus,
faCOAStorageType StorageType
} }
faSupportedCOA OBJECT-TYPE faSupportedCOA OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Care-of-address supported by this foreign agent." "Care-of-address supported by this foreign agent."
::= { faCOAEntry 1 } ::= { faCOAEntry 1 }
faCOAStatus OBJECT-TYPE faCOAStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status for COA entry." "The row status for COA entry."
::= { faCOAEntry 2 } ::= { faCOAEntry 2 }
faCOAStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this entry."
DEFVAL { nonVolatile }
::= { faCOAEntry 3 }
--
-- Foreign Agent Advertisement Group -- Foreign Agent Advertisement Group
--
-- FA needs to implement MA Advertisement Group plus that group -- FA needs to implement MA Advertisement Group plus that group
-- Foreign agent advertisement configuration table. -- Foreign agent advertisement configuration table.
faAdvertConfTable OBJECT-TYPE faAdvertConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF FaAdvertConfEntry SYNTAX SEQUENCE OF FaAdvertConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing additional configurable "A table containing additional configurable
advertisement parameters beyond that provided by advertisement parameters beyond that provided by
skipping to change at page 35, line 27 skipping to change at page 44, line 32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of last challenge values "Indicates the number of last challenge values
which can be used by mobile node in the registration which can be used by mobile node in the registration
request sent to the foreign agent on this interface." request sent to the foreign agent on this interface."
REFERENCE REFERENCE
"RFC3012 - Mobile IPv4 Challenge/Response Extensions" "RFC3012 - Mobile IPv4 Challenge/Response Extensions"
DEFVAL { 2 } DEFVAL { 2 }
::= { faAdvertConfEntry 3 } ::= { faAdvertConfEntry 3 }
-- Foreign Agent Registration Group --
-- Foreign Agent Registration Group Counters -- Foreign Agent Registration Group Counters
--
faRegRequestsReceived OBJECT-TYPE faRegRequestsReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of valid Registration Requests "Total number of valid Registration Requests
received." received."
::= { faRegistration 2 } ::= { faRegistration 2 }
faRegRequestsRelayed OBJECT-TYPE faRegRequestsRelayed OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Registration Requests relayed to home "Total number of Registration Requests relayed to home
agent by foreign agent." agent by foreign agent."
::= { faRegistration 3 } ::= { faRegistration 3 }
faReasonUnspecified OBJECT-TYPE faReasonUnspecified OBJECT-TYPE
skipping to change at page 41, line 25 skipping to change at page 51, line 36
::= { faRegistration 28 } ::= { faRegistration 28 }
faRegVisitorCount OBJECT-TYPE faRegVisitorCount OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of entries in faRegVisitorTable." "The current number of entries in faRegVisitorTable."
::= { faRegistration 29 } ::= { faRegistration 29 }
--
-- Foreign Agent Visitors List -- Foreign Agent Visitors List
--
faRegVisitorTable OBJECT-TYPE faRegVisitorTable OBJECT-TYPE
SYNTAX SEQUENCE OF FaRegVisitorEntry SYNTAX SEQUENCE OF FaRegVisitorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the foreign agent's visitor list. "A table containing the foreign agent's visitor list.
The foreign agent updates this table in response to The foreign agent updates this table in response to
registration events from mobile nodes." registration events from mobile nodes."
::= { faRegistration 30 } ::= { faRegistration 30 }
skipping to change at page 42, line 8 skipping to change at page 52, line 30
faRegVisitorIdType MipEntityIdentifierType, faRegVisitorIdType MipEntityIdentifierType,
faRegVisitorId MipEntityIdentifier, faRegVisitorId MipEntityIdentifier,
faRegVisitorHomeAddress IpAddress, faRegVisitorHomeAddress IpAddress,
faRegVisitorHomeAgentAddress IpAddress, faRegVisitorHomeAgentAddress IpAddress,
faRegVisitorTimeGranted Integer32, faRegVisitorTimeGranted Integer32,
faRegVisitorTimeRemaining Gauge32, faRegVisitorTimeRemaining Gauge32,
faRegVisitorRegFlags RegistrationFlags, faRegVisitorRegFlags RegistrationFlags,
faRegVisitorRegIDLow Unsigned32, faRegVisitorRegIDLow Unsigned32,
faRegVisitorRegIDHigh Unsigned32, faRegVisitorRegIDHigh Unsigned32,
faRegVisitorRegIsAccepted TruthValue, faRegVisitorRegIsAccepted TruthValue,
faRegVisitorDeliveryStyle MipDeliveryStyle faRegVisitorDeliveryStyle MipDeliveryStyle,
faRegVisitorNAI MipEntityIdentifierNAI,
faRegVisitorInPkts Counter32,
faRegVisitorInOctets Counter32,
faRegVisitorOutPkts Counter32,
faRegVisitorOutOctets Counter32
} }
faRegVisitorIdType OBJECT-TYPE faRegVisitorIdType OBJECT-TYPE
SYNTAX MipEntityIdentifierType SYNTAX MipEntityIdentifierType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the visitor's identifier." "The type of the visitor's identifier."
::= { faRegVisitorEntry 1 } ::= { faRegVisitorEntry 1 }
faRegVisitorId OBJECT-TYPE faRegVisitorId OBJECT-TYPE
SYNTAX MipEntityIdentifier SYNTAX MipEntityIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier of the visitor." "The identifier of the visitor."
::= { faRegVisitorEntry 2 } ::= { faRegVisitorEntry 2 }
faRegVisitorHomeAddress OBJECT-TYPE faRegVisitorHomeAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
skipping to change at page 44, line 14 skipping to change at page 55, line 16
faRegVisitorDeliveryStyle OBJECT-TYPE faRegVisitorDeliveryStyle OBJECT-TYPE
SYNTAX MipDeliveryStyle SYNTAX MipDeliveryStyle
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Delivery style requested by the mobile node in its "Delivery style requested by the mobile node in its
registration request." registration request."
DEFVAL { direct } DEFVAL { direct }
::= { faRegVisitorEntry 11 } ::= { faRegVisitorEntry 11 }
-- Home Agent Group faRegVisitorNAI OBJECT-TYPE
SYNTAX MipEntityIdentifierNAI
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAI of the Mobile node. "
::= { faRegVisitorEntry 12 }
-- Home Agent Registration Group faRegVisitorInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets, received from the MN.
Discontinuities in the value of this counter can
occur."
::= { faRegVisitorEntry 13 }
faRegVisitorInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets, received from the MN.
Discontinuities in the value of this counter can
occur."
::= { faRegVisitorEntry 14 }
faRegVisitorOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets, sent to the MN.
Discontinuities in the value of this counter can
occur."
::= { faRegVisitorEntry 15 }
faRegVisitorOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets, sent to the MN.
Discontinuities in the value of this counter can
occur."
::= { faRegVisitorEntry 16 }
-- =================================================================
-- Home Agent Group
--
-- Home agent mobility binding list -- Home agent mobility binding list
--
haMobilityBindingTable OBJECT-TYPE haMobilityBindingTable OBJECT-TYPE
SYNTAX SEQUENCE OF HaMobilityBindingEntry SYNTAX SEQUENCE OF HaMobilityBindingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the home agent's mobility binding "A table containing the home agent's mobility binding
list. The home agent updates this table in response list. The home agent updates this table in response
to registration events from mobile nodes." to registration events from mobile nodes."
::= { haRegistration 1 } ::= { haRegistration 1 }
skipping to change at page 44, line 49 skipping to change at page 57, line 19
HaMobilityBindingEntry ::= SEQUENCE { HaMobilityBindingEntry ::= SEQUENCE {
haMobilityBindingMN IpAddress, haMobilityBindingMN IpAddress,
haMobilityBindingCOA IpAddress, haMobilityBindingCOA IpAddress,
haMobilityBindingSourceAddress IpAddress, haMobilityBindingSourceAddress IpAddress,
haMobilityBindingRegFlags RegistrationFlags, haMobilityBindingRegFlags RegistrationFlags,
haMobilityBindingRegIDLow Unsigned32, haMobilityBindingRegIDLow Unsigned32,
haMobilityBindingRegIDHigh Unsigned32, haMobilityBindingRegIDHigh Unsigned32,
haMobilityBindingTimeGranted Unsigned32, haMobilityBindingTimeGranted Unsigned32,
haMobilityBindingTimeRemaining Gauge32, haMobilityBindingTimeRemaining Gauge32,
haMobilityBindingMnIdType MipEntityIdentifierType, haMobilityBindingMnIdType MipEntityIdentifierType,
haMobilityBindingMnId MipEntityIdentifier haMobilityBindingMnId MipEntityIdentifier,
haMobilityBindingHA IpAddress,
haMobilityBindingNAI MipEntityIdentifierNAI,
haMobilityBindingInPkts Counter32,
haMobilityBindingInOctets Counter32,
haMobilityBindingOutPkts Counter32,
haMobilityBindingOutOctets Counter32
} }
haMobilityBindingMN OBJECT-TYPE haMobilityBindingMN OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Mobile node's home (IP) address." "Mobile node's home (IP) address."
::= { haMobilityBindingEntry 1 } ::= { haMobilityBindingEntry 1 }
haMobilityBindingCOA OBJECT-TYPE haMobilityBindingCOA OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
skipping to change at page 46, line 17 skipping to change at page 59, line 7
"High 32 bits of Identification used in that binding by "High 32 bits of Identification used in that binding by
the mobile node." the mobile node."
::= { haMobilityBindingEntry 6 } ::= { haMobilityBindingEntry 6 }
haMobilityBindingTimeGranted OBJECT-TYPE haMobilityBindingTimeGranted OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lifetime in seconds granted to the mobile node "The lifetime in seconds granted to the mobile
for this registration." node for this registration."
::= { haMobilityBindingEntry 7 } ::= { haMobilityBindingEntry 7 }
haMobilityBindingTimeRemaining OBJECT-TYPE haMobilityBindingTimeRemaining OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds remaining until the "The number of seconds remaining until the
registration is expired. It has the same initial value registration is expired. It has the same initial value
skipping to change at page 46, line 49 skipping to change at page 59, line 39
::= { haMobilityBindingEntry 9 } ::= { haMobilityBindingEntry 9 }
haMobilityBindingMnId OBJECT-TYPE haMobilityBindingMnId OBJECT-TYPE
SYNTAX MipEntityIdentifier SYNTAX MipEntityIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier of the mobile node." "The identifier of the mobile node."
::= { haMobilityBindingEntry 10 } ::= { haMobilityBindingEntry 10 }
-- Home Agent Registration Group Counters haMobilityBindingHA OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Mobile node's home agent (IP) address."
::= { haMobilityBindingEntry 11 }
haMobilityBindingNAI OBJECT-TYPE
SYNTAX MipEntityIdentifierNAI
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAI of the Mobile node. "
::= { haMobilityBindingEntry 12 }
haMobilityBindingInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets, received from the MN.
Discontinuities in the value of this counter can
occur."
::= { haMobilityBindingEntry 13 }
haMobilityBindingInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets, received from the MN.
Discontinuities in the value of this counter can
occur."
::= { haMobilityBindingEntry 14 }
haMobilityBindingOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets, sent to the MN.
Discontinuities in the value of this counter can
occur."
::= { haMobilityBindingEntry 15 }
haMobilityBindingOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets, sent to the MN.
Discontinuities in the value of this counter can
occur."
::= { haMobilityBindingEntry 16 }
--
-- Home agent registration Counters for all mobile nodes. -- Home agent registration Counters for all mobile nodes.
--
haRegistrationAccepted OBJECT-TYPE haRegistrationAccepted OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Registration Requests accepted by "Total number of Registration Requests accepted by
home agent (Code 0)." home agent (Code 0)."
::= { haRegistration 3 } ::= { haRegistration 3 }
skipping to change at page 51, line 69 skipping to change at page 67, line 28
haRegMobilityBindingCount OBJECT-TYPE haRegMobilityBindingCount OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of entries in "The current number of entries in
haMobilityBindingTable." haMobilityBindingTable."
::= { haRegistration 27 } ::= { haRegistration 27 }
--
-- Home agent registration Counters per node -- Home agent registration Counters per node
--
haRegCounterTable OBJECT-TYPE haRegCounterTable OBJECT-TYPE
SYNTAX SEQUENCE OF HaRegCounterEntry SYNTAX SEQUENCE OF HaRegCounterEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing registration statistics for all "A table containing registration statistics for all
mobile nodes authorized to use this home agent." mobile nodes authorized to use this home agent."
::= { haRegistration 28 } ::= { haRegistration 28 }
skipping to change at page 52, line 44 skipping to change at page 69, line 28
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time at which the most recent Registration "The time at which the most recent Registration
Request was denied by the home agent for this mobile Request was denied by the home agent for this mobile
node." node."
::= { haRegCounterEntry 5 } ::= { haRegCounterEntry 5 }
haRegRecentServiceDeniedCode OBJECT-TYPE haRegRecentServiceDeniedCode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (0..255)
reasonUnspecified(128),
admProhibited(129),
insufficientResource(130),
mnAuthenticationFailure(131),
faAuthenticationFailure(132),
idMismatch(133),
poorlyFormedRequest(134),
tooManyBindings(135),
unknownHA(136),
reverseTunnelUnavailable(137),
reverseTunnelBitNotSet(138),
encapsulationUnavailable(139),
mnCvseUnsupported(140),
faCvseUnsupported(141)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Code indicating the reason why the most recent "The Code indicating the reason why the most recent
Registration Request for this mobile node was rejected Registration Request for this mobile node was rejected
by the home agent." by the home agent."
::= { haRegCounterEntry 6 } ::= { haRegCounterEntry 6 }
mipMIBNotificationPrefix OBJECT IDENTIFIER ::= { mipMIB 2 } -- =================================================================
-- MIP Notifications
mipMIBNotificationPrefix OBJECT IDENTIFIER ::= { mipMIB 2 }
mipMIBNotifications OBJECT IDENTIFIER ::= mipMIBNotifications OBJECT IDENTIFIER ::=
{ mipMIBNotificationPrefix 0 } { mipMIBNotificationPrefix 0 }
mipAuthFailure2 NOTIFICATION-TYPE mipAuthFailure2 NOTIFICATION-TYPE
OBJECTS { mipSecurityRecentViolationSPI, OBJECTS { mipSecurityViolatorNAI,
mipSecurityViolatorIpAddress,
mipSecurityViolationCounter,
mipSecurityRecentViolationSPI,
mipSecurityRecentViolationTime,
mipSecurityRecentViolationIDLow, mipSecurityRecentViolationIDLow,
mipSecurityRecentViolationIDHigh, mipSecurityRecentViolationIDHigh,
mipSecurityRecentViolationReason mipSecurityRecentViolationReason,
mipSecurityRecentViolationErrCode
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mipAuthFailure2 indicates that the Mobile IP "The mipAuthFailure2 indicates that the Mobile IP
entity has an authentication failure when it validates entity has an authentication failure when it validates
the mobile Registration Request or Reply." the mobile Registration Request or Reply."
::= { mipMIBNotifications 2 } ::= { mipMIBNotifications 2 }
-- =================================================================
-- MIP Conformance Statements
mipMIBConformance OBJECT IDENTIFIER ::= { mipMIB 3 } mipMIBConformance OBJECT IDENTIFIER ::= { mipMIB 3 }
mipGroups OBJECT IDENTIFIER ::= { mipMIBConformance 1 } mipGroups OBJECT IDENTIFIER ::= { mipMIBConformance 1 }
mipCompliances OBJECT IDENTIFIER ::= { mipMIBConformance 2 } mipCompliances OBJECT IDENTIFIER ::= { mipMIBConformance 2 }
--
-- compliance statements -- compliance statements
--
mipCompliance2 MODULE-COMPLIANCE mipCompliance2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMPv2 entities which "The compliance statement for SNMPv2 entities which
implement the Mobile IP MIB." implement the Mobile IP MIB."
MODULE MODULE
MANDATORY-GROUPS { mipSystemGroup } MANDATORY-GROUPS { mipSystemGroup }
GROUP mipSecAssociationGroup2 GROUP mipSecAssociationGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory for Mobile IP entities (MN, "This group is mandatory for Mobile IP entities (MN,
FA, and HA) which support security associations. FA, and HA) which support security associations.
Mobile Nodes and Home Agents must implement this Mobile Nodes and Home Agents must implement this
group. Foreign Agents must implement this group if group. Foreign Agents must implement this group if
they maintain any security associations." they maintain any security associations."
skipping to change at page 54, line 38 skipping to change at page 71, line 40
GROUP mnRegistrationGroup2 GROUP mnRegistrationGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory for mobile nodes." "This group is mandatory for mobile nodes."
GROUP maAdvertisementGroup2 GROUP maAdvertisementGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory for the mobility agents (HA "This group is mandatory for the mobility agents (HA
and FA) since they must implement Agent and FA) since they must implement Agent
Advertisement." Advertisement."
GROUP maAdvertisementNAIGroup
DESCRIPTION
"This group is mandatory for the mobility agents (HA
and FA) that implements agent NAIs in accordance with
[RFC3846]."
GROUP faSystemGroup GROUP faSystemGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for foreign agents." "This group is mandatory for foreign agents."
GROUP faAdvertisementGroup2 GROUP faAdvertisementGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory for foreign agents." "This group is mandatory for foreign agents."
GROUP faRegistrationGroup2 GROUP faRegistrationGroup2
DESCRIPTION DESCRIPTION
skipping to change at page 55, line 16 skipping to change at page 72, line 30
GROUP haRegNodeCountersGroup2 GROUP haRegNodeCountersGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory for home agents which log "This group is mandatory for home agents which log
registration counters for each individual mobile registration counters for each individual mobile
node." node."
GROUP mipSecNotificationsGroup2 GROUP mipSecNotificationsGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory for Mobile IP entities (MN, "This group is mandatory for Mobile IP entities (MN,
FA, and HA) that can report the security violations." FA, and HA) that can report the security violations."
::= { mipCompliances 2 } ::= { mipCompliances 2 }
--
-- Units of conformance -- Units of conformance
--
mipSystemGroup OBJECT-GROUP mipSystemGroup OBJECT-GROUP
OBJECTS { mipEntities, mipEnable, mipEncapsulationSupported } OBJECTS { mipEntities, mipEnable, mipEncapsulationSupported }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the basic Mobile IP "A collection of objects providing the basic Mobile IP
entity's management information." entity's management information."
::= { mipGroups 1 } ::= { mipGroups 1 }
mnDiscoveryGroup OBJECT-GROUP mnDiscoveryGroup OBJECT-GROUP
OBJECTS { mnFAAddress, mnCOA, mnAdvSourceAddress, OBJECTS { mnFAAddress, mnCOA, mnAdvSourceAddress,
mnAdvSequence, mnAdvFlags, mnAdvMaxRegLifetime, mnAdvSequence, mnAdvFlags, mnAdvMaxRegLifetime,
mnAdvMaxAdvLifetime, mnAdvTimeReceived, mnAdvMaxAdvLifetime, mnAdvTimeReceived,
mnSolicitationsSent, mnAdvertisementsReceived, mnSolicitationsSent, mnAdvertisementsReceived,
mnAdvsDroppedInvalidExtension, mnAdvsDroppedInvalidExtension,
mnAdvsIgnoredUnknownExtension, mnMoveFromHAToFA, mnAdvsIgnoredUnknownExtension, mnMoveFromHAToFA,
mnMoveFromFAToFA, mnMoveFromFAToHA, mnMoveFromFAToFA, mnMoveFromFAToHA,
mnGratuitousARPsSend, mnAgentRebootsDectected } mnGratuitousARPsSend, mnAgentRebootsDectected }
STATUS current STATUS current
skipping to change at page 56, line 4 skipping to change at page 73, line 27
mobile node." mobile node."
::= { mipGroups 5 } ::= { mipGroups 5 }
faSystemGroup OBJECT-GROUP faSystemGroup OBJECT-GROUP
OBJECTS { faCOAStatus} OBJECTS { faCOAStatus}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the basic "A collection of objects providing the basic
management information for foreign agents." management information for foreign agents."
::= { mipGroups 8 } ::= { mipGroups 8 }
mipSecAssociationGroup2 OBJECT-GROUP mipSecAssociationGroup2 OBJECT-GROUP
OBJECTS { mipSecurityAlgorithmType, mipSecurityAlgorithmMode, OBJECTS { mipSecurityAlgorithmType, mipSecurityAlgorithmMode,
mipSecurityKey, mipSecurityReplayMethod, mipSecurityKey,
mipSecurityReplayMethod,
mipSecurityReplayTime, mipSecurityStatus, mipSecurityReplayTime, mipSecurityStatus,
mipSecurityAssocsCount } mipSecurityPeerNAI, mipSecurityPeerIpAddress,
mipSecurityStorageType, mipSecurityAssocsCount }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the management "A collection of objects providing the management
information for security associations of Mobile IP information for security associations of Mobile IP
entities." entities."
::= { mipGroups 14 } ::= { mipGroups 14 }
mipSecViolationGroup2 OBJECT-GROUP mipSecViolationGroup2 OBJECT-GROUP
OBJECTS { mipSecTotalViolations, OBJECTS { mipSecTotalViolations,
mipSecurityViolationCounter, mipSecurityViolationCounter,
mipSecurityRecentViolationSPI, mipSecurityRecentViolationSPI,
mipSecurityRecentViolationTime, mipSecurityRecentViolationTime,
mipSecurityRecentViolationIDLow, mipSecurityRecentViolationIDLow,
mipSecurityRecentViolationIDHigh, mipSecurityRecentViolationIDHigh,
mipSecurityRecentViolationReason } mipSecurityRecentViolationReason,
mipSecurityViolatorNAI,
mipSecurityViolatorIpAddress,
mipSecurityRecentViolationErrCode,
mipSecurityviolationStorageType }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the management "A collection of objects providing the management
information for security violation logging of Mobile information for security violation logging of Mobile
IP entities." IP entities."
::= { mipGroups 15 } ::= { mipGroups 15 }
mnSystemGroup2 OBJECT-GROUP mnSystemGroup2 OBJECT-GROUP
OBJECTS { mnState, mnCurrentHA, mnHomeAddress, OBJECTS { mnState, mnCurrentHA, mnHomeAddress,
mnHAStatus, mnIdentifierType, mnIdentifier } mnHAStatus, mnIdentifierType, mnIdentifier }
skipping to change at page 57, line 24 skipping to change at page 75, line 19
mobile node." mobile node."
::= { mipGroups 17 } ::= { mipGroups 17 }
maAdvertisementGroup2 OBJECT-GROUP maAdvertisementGroup2 OBJECT-GROUP
OBJECTS { maAdvertMaxRegLifetime, OBJECTS { maAdvertMaxRegLifetime,
maAdvertPrefixLengthInclusion, maAdvertAddress, maAdvertPrefixLengthInclusion, maAdvertAddress,
maAdvertMaxInterval, maAdvertMinInterval, maAdvertMaxInterval, maAdvertMinInterval,
maAdvertMaxAdvLifetime, maAdvertMaxAdvLifetime,
maAdvertResponseSolicitationOnly, maAdvertResponseSolicitationOnly,
maAdvertService, maAdvertStatus, maAdvertService, maAdvertStatus,
maAdvertStorageType,
maAdvertisementsSent, maAdvertisementsSent,
maAdvsSentForSolicitation, maAdvsSentForSolicitation,
maSolicitationsReceived } maSolicitationsReceived }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing management "A collection of objects providing management
information for the Agent Advertisement function information for the Agent Advertisement function
within mobility agents." within mobility agents."
::= { mipGroups 18 } ::= { mipGroups 18 }
maAdvertisementNAIGroup OBJECT-GROUP
OBJECTS { maAdvertNetworkNAI }
STATUS current
DESCRIPTION
"A collection of objects providing management
information for the Agent Advertisement function
that implements Agent NAIS is accordance with
[RFC3846]."
::= { mipGroups 19 }
faAdvertisementGroup2 OBJECT-GROUP faAdvertisementGroup2 OBJECT-GROUP
OBJECTS { faAdvertIsBusy, faAdvertRegRequired, OBJECTS { faAdvertIsBusy, faAdvertRegRequired,
faAdvertChallengeWindow } faAdvertChallengeWindow, faCOAStorageType }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing supplemental "A collection of objects providing supplemental
management information for the Agent Advertisement management information for the Agent Advertisement
function within a foreign agent." function within a foreign agent."
::= { mipGroups 19 } ::= { mipGroups 20 }
faRegistrationGroup2 OBJECT-GROUP faRegistrationGroup2 OBJECT-GROUP
OBJECTS { faRegVisitorCount, faRegVisitorHomeAddress, OBJECTS { faRegVisitorCount, faRegVisitorHomeAddress,
faRegVisitorHomeAgentAddress, faRegVisitorHomeAgentAddress,
faRegVisitorTimeGranted, faRegVisitorTimeGranted,
faRegVisitorTimeRemaining, faRegVisitorRegFlags, faRegVisitorTimeRemaining, faRegVisitorRegFlags,
faRegVisitorRegIDLow, faRegVisitorRegIDHigh, faRegVisitorRegIDLow, faRegVisitorRegIDHigh,
faRegVisitorRegIsAccepted, faRegVisitorRegIsAccepted,
faRegVisitorDeliveryStyle, faRegRequestsReceived, faRegVisitorDeliveryStyle,
faRegVisitorNAI, faRegVisitorInPkts,
faRegVisitorInOctets,
faRegVisitorOutPkts, faRegVisitorOutOctets,
faRegRequestsReceived,
faRegRequestsRelayed, faReasonUnspecified, faRegRequestsRelayed, faReasonUnspecified,
faAdmProhibited, faInsufficientResource, faAdmProhibited, faInsufficientResource,
faMNAuthenticationFailure, faRegLifetimeTooLong, faMNAuthenticationFailure, faRegLifetimeTooLong,
faPoorlyFormedRequests, faPoorlyFormedRequests,
faEncapsulationUnavailable, faEncapsulationUnavailable,
faHAUnreachable, faRegRepliesRecieved, faHAUnreachable, faRegRepliesRecieved,
faRegRepliesRelayed, faHAAuthenticationFailure, faRegRepliesRelayed, faHAAuthenticationFailure,
faPoorlyFormedReplies, faPoorlyFormedReplies,
faReverseTunnelUnavailable, faReverseTunnelUnavailable,
faReverseTunnelBitNotSet, faReverseTunnelBitNotSet,
faMnTooDistant, faDeliveryStyleUnsupported, faMnTooDistant, faDeliveryStyleUnsupported,
faNonZeroHomeAddressRequired, faUnknownChallenge, faNonZeroHomeAddressRequired, faUnknownChallenge,
faMissingChallenge, faStaleChallenge, faMissingChallenge, faStaleChallenge,
faCvsesFromMnUnsupported, faCvsesFromHaUnsupported, faCvsesFromMnUnsupported, faCvsesFromHaUnsupported,
faNvsesFromMnIgnored, faNvsesFromHaIgnored } faNvsesFromMnIgnored, faNvsesFromHaIgnored }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing management "A collection of objects providing management
information for the registration function within a information for the registration function within a
foreign agent." foreign agent."
::= { mipGroups 20 } ::= { mipGroups 21 }
haRegistrationGroup2 OBJECT-GROUP haRegistrationGroup2 OBJECT-GROUP
OBJECTS { haMobilityBindingMN, haMobilityBindingCOA, OBJECTS { haMobilityBindingMN, haMobilityBindingCOA,
haMobilityBindingSourceAddress, haMobilityBindingSourceAddress,
haMobilityBindingRegFlags, haMobilityBindingRegFlags,
haMobilityBindingRegIDLow, haMobilityBindingRegIDLow,
haMobilityBindingRegIDHigh, haMobilityBindingRegIDHigh,
haMobilityBindingTimeGranted, haMobilityBindingTimeGranted,
haMobilityBindingTimeRemaining, haMobilityBindingTimeRemaining,
haMobilityBindingMnIdType, haMobilityBindingMnId, haMobilityBindingMnIdType, haMobilityBindingMnId,
haMobilityBindingHA, haMobilityBindingNAI,
haMobilityBindingInPkts, haMobilityBindingInOctets,
haMobilityBindingOutPkts,
haMobilityBindingOutOctets,
haRegistrationAccepted, haMultiBindingUnsupported, haRegistrationAccepted, haMultiBindingUnsupported,
haReasonUnspecified, haAdmProhibited, haReasonUnspecified, haAdmProhibited,
haInsufficientResource, haMNAuthenticationFailure, haInsufficientResource, haMNAuthenticationFailure,
haFAAuthenticationFailure, haIDMismatch, haFAAuthenticationFailure, haIDMismatch,
haPoorlyFormedRequest, haTooManyBindings, haPoorlyFormedRequest, haTooManyBindings,
haUnknownHA, haGratuitiousARPsSent, haUnknownHA, haGratuitiousARPsSent,
haProxyARPsSent, haRegRequestsReceived, haProxyARPsSent, haRegRequestsReceived,
haDeRegRequestsReceived, haRegRepliesSent, haDeRegRequestsReceived, haRegRepliesSent,
haDeRegRepliesSent, haReverseTunnelUnavailable, haDeRegRepliesSent, haReverseTunnelUnavailable,
haReverseTunnelBitNotSet, haReverseTunnelBitNotSet,
haEncapsulationUnavailable, haCvsesFromMnUnsupported, haEncapsulationUnavailable,
haCvsesFromFaUnsupported, haRegMobilityBindingCount, haCvsesFromMnUnsupported,
haCvsesFromFaUnsupported,
haRegMobilityBindingCount,
haNvsesFromMnIgnored, haNvsesFromFaIgnored } haNvsesFromMnIgnored, haNvsesFromFaIgnored }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing management "A collection of objects providing management
information for the registration function within a information for the registration function within a
home agent." home agent."
::= { mipGroups 21 } ::= { mipGroups 22 }
haRegNodeCountersGroup2 OBJECT-GROUP haRegNodeCountersGroup2 OBJECT-GROUP
OBJECTS { haRegServiceRequestsAccepted, OBJECTS { haRegServiceRequestsAccepted,
haRegServiceRequestsDenied, haRegServiceRequestsDenied,
haRegOverallServiceTime, haRegOverallServiceTime,
haRegRecentServiceAcceptedTime, haRegRecentServiceAcceptedTime,
haRegRecentServiceDeniedTime, haRegRecentServiceDeniedTime,
haRegRecentServiceDeniedCode } haRegRecentServiceDeniedCode }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing management "A collection of objects providing management
information for counters related to the registration information for counters related to the registration
function within a home agent." function within a home agent."
::= { mipGroups 22 } ::= { mipGroups 23 }
mipSecNotificationsGroup2 NOTIFICATION-GROUP mipSecNotificationsGroup2 NOTIFICATION-GROUP
NOTIFICATIONS { mipAuthFailure2 } NOTIFICATIONS { mipAuthFailure2 }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification related to security violations." "The notification related to security violations."
::= { mipGroups 23 } ::= { mipGroups 24 }
-- =================================================================
-- Deprecated Definitions -- Deprecated Definitions
-- Deprecated objects --
-- Security group specific deprecated objects -- Security group specific deprecated objects
--
mipSecAssocTable OBJECT-TYPE mipSecAssocTable OBJECT-TYPE
SYNTAX SEQUENCE OF MipSecAssocEntry SYNTAX SEQUENCE OF MipSecAssocEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table containing Mobility Security Associations." "A table containing Mobility Security Associations."
::= { mipSecurity 1 } ::= { mipSecurity 1 }
mipSecAssocEntry OBJECT-TYPE mipSecAssocEntry OBJECT-TYPE
skipping to change at page 61, line 30 skipping to change at page 80, line 38
timestamps(2), timestamps(2),
nonces(3) nonces(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The replay-protection method supported for this SPI "The replay-protection method supported for this SPI
within this Mobility Security Association." within this Mobility Security Association."
::= { mipSecAssocEntry 6 } ::= { mipSecAssocEntry 6 }
--
-- Mobile IP security violation table -- Mobile IP security violation table
--
mipSecViolationTable OBJECT-TYPE mipSecViolationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MipSecViolationEntry SYNTAX SEQUENCE OF MipSecViolationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table containing information about security "A table containing information about security
violations." violations."
::= { mipSecurity 3 } ::= { mipSecurity 3 }
skipping to change at page 63, line 42 skipping to change at page 83, line 25
missingSecurityExtension(5), missingSecurityExtension(5),
other(6) other(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Reason for the most recent security violation for "Reason for the most recent security violation for
this peer." this peer."
::= { mipSecViolationEntry 7 } ::= { mipSecViolationEntry 7 }
-- Mobility agent advertisement specific deprecated objects --
-- Depricated Mobility agent advertisement configuration table
-- Mobility agent advertisement configuration table --
maAdvConfigTable OBJECT-TYPE maAdvConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MaAdvConfigEntry SYNTAX SEQUENCE OF MaAdvConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table containing configurable advertisement "A table containing configurable advertisement
parameters for all advertisement interfaces in parameters for all advertisement interfaces in
the mobility agent." the mobility agent."
::= { maAdvertisement 1 } ::= { maAdvertisement 1 }
skipping to change at page 66, line 38 skipping to change at page 86, line 41
maAdvStatus OBJECT-TYPE maAdvStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The row status for the agent advertisement table. If "The row status for the agent advertisement table. If
this column status is 'active', the manager should not this column status is 'active', the manager should not
change any column in the row." change any column in the row."
::= { maAdvConfigEntry 9 } ::= { maAdvConfigEntry 9 }
--
-- Foreign agent specific deprecated objects -- Foreign agent specific deprecated objects
--
faIsBusy OBJECT-TYPE faIsBusy OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Whether or not the foreign agent is too busy to "Whether or not the foreign agent is too busy to
accept additional registrations. If true(1), the agent accept additional registrations. If true(1), the agent
is busy and any Agent advertisements sent from this is busy and any Agent advertisements sent from this
agent should have the 'B' bit set to 1." agent should have the 'B' bit set to 1."
::= { faAdvertisement 1 } ::= { faAdvertisement 1 }
skipping to change at page 67, line 17 skipping to change at page 87, line 28
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Whether or not this foreign agent requires "Whether or not this foreign agent requires
registration even from those mobile nodes that have registration even from those mobile nodes that have
acquired their own, colocated care-of address. If acquired their own, colocated care-of address. If
true(1), registration is required and any Agent true(1), registration is required and any Agent
Advertisements sent from this agent should have the Advertisements sent from this agent should have the
'R' bit set to 1." 'R' bit set to 1."
::= { faAdvertisement 2 } ::= { faAdvertisement 2 }
-- Foreign Agent Visitors List --
-- Deprecated Foreign Agent Visitors List
--
faVisitorTable OBJECT-TYPE faVisitorTable OBJECT-TYPE
SYNTAX SEQUENCE OF FaVisitorEntry SYNTAX SEQUENCE OF FaVisitorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table containing the foreign agent's visitor list. "A table containing the foreign agent's visitor list.
The foreign agent updates this table in response to The foreign agent updates this table in response to
registration events from mobile nodes." registration events from mobile nodes."
::= { faRegistration 1 } ::= { faRegistration 1 }
skipping to change at page 69, line 47 skipping to change at page 90, line 33
faVJCompressionUnavailable OBJECT-TYPE faVJCompressionUnavailable OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Total number of Registration Requests denied by "Total number of Registration Requests denied by
foreign agent -- requested Van Jacobson header foreign agent -- requested Van Jacobson header
compression unavailable (Code 73)." compression unavailable (Code 73)."
::= { faRegistration 11 } ::= { faRegistration 11 }
-- Home agent specific deprecated objects --
-- Deprecated Home agent registration Counters per node
-- Home agent registration Counters per node --
haCounterTable OBJECT-TYPE haCounterTable OBJECT-TYPE
SYNTAX SEQUENCE OF HaCounterEntry SYNTAX SEQUENCE OF HaCounterEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table containing registration statistics for all "A table containing registration statistics for all
mobile nodes authorized to use this home agent." mobile nodes authorized to use this home agent."
::= { haRegistration 2 } ::= { haRegistration 2 }
skipping to change at page 72, line 4 skipping to change at page 93, line 11
tooManyBindings(135), tooManyBindings(135),
unknownHA(136) unknownHA(136)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The Code indicating the reason why the most recent "The Code indicating the reason why the most recent
Registration Request for this mobile node was rejected Registration Request for this mobile node was rejected
by the home agent." by the home agent."
::= { haCounterEntry 7 } ::= { haCounterEntry 7 }
--
-- deprecated traps -- deprecated traps
--
mipAuthFailure NOTIFICATION-TYPE mipAuthFailure NOTIFICATION-TYPE
OBJECTS { mipSecViolatorAddress, OBJECTS { mipSecViolatorAddress,
mipSecRecentViolationSPI, mipSecRecentViolationSPI,
mipSecRecentViolationIDLow, mipSecRecentViolationIDLow,
mipSecRecentViolationIDHigh, mipSecRecentViolationIDHigh,
mipSecRecentViolationReason mipSecRecentViolationReason
} }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The mipAuthFailure indicates that the Mobile IP "The mipAuthFailure indicates that the Mobile IP
entity has an authentication failure when it validates entity has an authentication failure when it validates
the mobile Registration Request or Reply. the mobile Registration Request or Reply.
Implementation of this trap is optional." Implementation of this trap is optional."
::= { mipMIBNotifications 1 } ::= { mipMIBNotifications 1 }
--
-- deprecated compliance statement -- deprecated compliance statement
--
mipCompliance MODULE-COMPLIANCE mipCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for SNMPv2 entities which "The compliance statement for SNMPv2 entities which
implement the Mobile IP MIB." implement the Mobile IP MIB."
MODULE MODULE
MANDATORY-GROUPS { mipSystemGroup } MANDATORY-GROUPS { mipSystemGroup }
GROUP mipSecAssociationGroup GROUP mipSecAssociationGroup
skipping to change at page 73, line 41 skipping to change at page 95, line 19
GROUP haRegNodeCountersGroup GROUP haRegNodeCountersGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for home agents which log "This group is mandatory for home agents which log
registration counters for each individual mobile registration counters for each individual mobile
node." node."
GROUP mipSecNotificationsGroup GROUP mipSecNotificationsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for Mobile IP entities (MN, "This group is mandatory for Mobile IP entities (MN,
FA, and HA) that can report the security violations." FA, and HA) that can report the security violations."
::= { mipCompliances 1 } ::= { mipCompliances 1 }
--
-- Deprecated groups -- Deprecated groups
--
mipSecAssociationGroup OBJECT-GROUP mipSecAssociationGroup OBJECT-GROUP
OBJECTS { mipSecAlgorithmType, mipSecAlgorithmMode, OBJECTS { mipSecAlgorithmType, mipSecAlgorithmMode,
mipSecKey, mipSecReplayMethod } mipSecKey, mipSecReplayMethod }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects providing the management "A collection of objects providing the management
information for security associations of Mobile IP information for security associations of Mobile IP
entities." entities."
::= { mipGroups 2 } ::= { mipGroups 2 }
mipSecViolationGroup OBJECT-GROUP mipSecViolationGroup OBJECT-GROUP
OBJECTS { mipSecTotalViolations, OBJECTS { mipSecTotalViolations,mipSecViolatorAddress,
mipSecViolationCounter, mipSecRecentViolationSPI, mipSecViolationCounter, mipSecRecentViolationSPI,
mipSecRecentViolationTime, mipSecRecentViolationTime,
mipSecRecentViolationIDLow, mipSecRecentViolationIDLow,
mipSecRecentViolationIDHigh, mipSecRecentViolationIDHigh,
mipSecRecentViolationReason } mipSecRecentViolationReason }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects providing the management "A collection of objects providing the management
information for security violation logging of Mobile information for security violation logging of Mobile
IP entities." IP entities."
skipping to change at page 76, line 45 skipping to change at page 99, line 7
"A collection of objects providing management "A collection of objects providing management
information for counters related to the registration information for counters related to the registration
function within a home agent." function within a home agent."
::= { mipGroups 12 } ::= { mipGroups 12 }
mipSecNotificationsGroup NOTIFICATION-GROUP mipSecNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mipAuthFailure } NOTIFICATIONS { mipAuthFailure }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The notification related to security violations." "The notification related to security violations."
::= { mipGroups 13 } ::= { mipGroups 13 }
END END
5. Acknowledgments 4. Security Considerations
The origin of this document is from RFC 2006 "The Definitions of Man-
aged Objects for IP Mobility Support using SMIv2" written by D. Cong,
M. Hamlen and C. Perkins. The editor wishes to acknowledge the good
work of these original authors. Thanks to Roy Jose, Rudreshwar N,
Basavaraj Patil, and Sri Gundavelli for their useful comments and
contributions.
6. Security Considerations Assuming that secure network management (such as SNMP v3) is
implemented, the objects represented in this MIB do not pose a threat
to the security of the network.
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure envi- environments. The support for SET operations in a non-secure
ronment without proper protection can have a negative effect on net- environment without proper protection can have a negative effect on
work operations. network operations.
The Mobile IP MIB affords the network operator the ability to config- There are a number of managed objects in this MIB that may contain
ure and control the Mobile IP links of a particular system, including sensitive information. These are contained in the
the Mobile IP authentication protocols, and shared secret key. This mipSecurityAssocTable, mipSecurityViolationTable, faRegVisitorTable,
represents a security risk. and haMobilityBindingTable. It is thus important to control even GET
access to these objects and possibly to even encrypt the values of
these object when sending them over the network via SNMP. Not all
versions of SNMP provide features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.
The Mobile IP MIB affords the network operator the ability to
configure and control the Mobile IP links of a particular system,
including the Mobile IP authentication protocols, and shared secret
key. This represents a security risk.
These risks are addressed in the following manners: These risks are addressed in the following manners:
(1) All variables which represent a significant security risk are 1. All variables which represent a significant security risk are
placed in separate MIB Groups. By providing Agent Capability placed in separate MIB Groups. By providing Agent Capability
Statements, the implementor of the MIB may elect not to imple- Statements, the implementor of the MIB may elect not to implement
ment these groups. these groups.
(2) The MIB allows the manager station to create the security asso- 2. The MIB allows the manager station to create the security
ciation for Mobile IP entities. However, the agent should association for Mobile IP entities. However, the agent should
always return 0 length octet string when the manager station always return 0 length octet string when the manager station
retrieves the shared security key in the mipSecAssocTable. In retrieves the shared security key in the mipSecAssocTable. In
this way, the Mobile IP entities can prevent the key leaking this way, the Mobile IP entities can prevent the key leaking from
from SNMP GET, GET-NEXT, or GET-BULK requests. SNMP GET, GET-NEXT, or GET-BULK requests.
(3) The MIB defines a trap for Mobile IP entities to send a notifi-
cation to the manager station if there is a security violation.
In this way, the operator can notice the source of an intruder.
(4) The MIB also defines a table to log the security violations in
the Mobile IP entities. The manager station can retrieve this
log to analyze the security violation instances in the system.
Thus, in order to preserve the integrity, security and privacy of the 3. The MIB defines a trap for Mobile IP entities to send a
Mobile IP security features, an implementation SHOULD allow access to notification to the manager station if there is a security
this MIB only via SNMPv3. violation. In this way, the operator can notice the source of an
intruder.
SNMPv1 by itself is not a secure environment. Even if the network 4. The MIB also defines a table to log the security violations in the
itself is secure (for example by using IPSec), even then, there is no Mobile IP entities. The manager station can retrieve this log to
control as to who on the secure network is allowed to access and analyze the security violation instances in the system.
GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security fea- It is recommended that the implementers consider the security
tures as provided by the SNMPv3 framework. Specifically, the use of features as provided by the SNMPv3 framework. Specifically, the use
the User-based Security Model RFC 2574 [8] and the View-based Access of the User-based Security Model RFC 2574 [RFC2574] and the View-
Control Model RFC 2575 [9] is recommended. based Access Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (change/cre- (users) that have legitimate rights to indeed GET or SET
ate/delete) them. (change/create/delete) them.
7. References
[1] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Structure of Management Information Ver-
[2] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
[3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
[4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Conformance Statements for SMIv2", STD
[5] McCloghrie, K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, March 1991.
[6] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Net-
work Management Protocol", STD 15, RFC 1157, May 1990.
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[8] Blumenthal U., "User-based Security Model (USM) for version 3 of
the Simple Network Management Protocol (SNMPv3)", RFC 2574,
April 1999.
[9] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Proto-
[10] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
to Version 3 of the Internet-standard Network Management Frame-
[11] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
[12] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[13] M. Rose, "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Intro-
duction to Community-based SNMPv2", RFC 1901, January 1996.
[15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Trans-
port Mappings for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1906, January 1996.
[16] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.
[17] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999.
[18] Solomon J., "Mobile IP Protocol Applicability Statement", RFC
2005, October 1996.
[19] Perkins C., "IP Mobility Support", RFC 2002, Octoer 1996.
[20] Cong, D., Hamlen, M., and Perkins, C., "The Definitions of Man-
aged Objects for IP Mobility Support using SMIv2", RFC 2006,
October 1996.
[21] Calhoun, P., and Perkins, C., "Mobile IP Network Access Identi-
fier Extension for IPv4", RFC 2794, January 2000.
[22] Calhoun, P., and Perkins, C., "Mobile IPv4 Challenge/Response
Extension", RFC 3012, November 2000.
[23] Montenegro, G., "Reverse Tunneling for Mobile IP", RFC 3024,
January 2001.
[24] Perkins, C., "IP Mobility Support for IPv4, revised (work in 5. IANA Considerations
progress)", draft-ietf-mobileip-rfc2002-bis-08.txt, September
2001.
[25] Dommety, G., and Leung, K., "Mobile IP Vendor/Organization- Spe- The MIB module in this document uses the following IANA-assigned
cific Extensions", RFC 3115, April 2001. OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
[26] Perkins, C., "IP Encapsulation within IP", RFC 2003, October Descriptor OBJECT IDENTIFIER value
1996. ---------- -----------------------
[27] Perkins, C., "Minimal Encapsulation within IP", RFC 2004, Octo- mipMIB { mib-2 44 }
ber 1996.
[28] Hanks S. et. al., "Generic Routing Encapsulation (GRE)", RFC Editor's Note (to be removed prior to publication): this draft makes
1701, October 1994. no additional requests of the IANA.
[29] Deering, S., "ICMP Router Discovery Messages", RFC 1256, Septem- 6. Acknowledgments
ber 1991.
[30] Daniele, M., Haberman, B., Routhier, S., and Schoenwaelder, J., The origin of this document is from RFC 2006 "The Definitions of
"Textual Conventions for Internet Network Addresses", RFC 2851, Managed Objects for IP Mobility Support using SMIv2" written by D.
June 2000. Cong, M. Hamlen and C. Perkins. The editor wishes to acknowledge the
good work of these original authors. Thanks to Roy Jose, Rudreshwar
N, Basavaraj Patil, Sri Gundavelli and Olavi Kompulainen for their
useful comments and contributions.
A. Changes from RFC 2006 to draft-ietf-mobileip-rfc2006bis-00.txt APPENDIX A: Changes from RFC 2006
A.1 The changes from RFC 2006 are the following: A.1. Changes in draft-ietf-mobileip-rfc2006bis-00
- Section "The Network Management Framework" was updated. - Section "The Network Management Framework" was updated.
- Subsection Protocol Extensions was created under section Overview. - Subsection Protocol Extensions was created under section
Overview.
- Section Security Considerations was updated. - Section Security Considerations was updated.
- Changes to the MIB definition are following. Changes are listed - Changes to the MIB definition are following. Changes are
in the order of their occurrence in the MIB definition. listed in the order of their occurrence in the MIB definition.
(1) The textual convention RegistrationFlags was updated. The bit (1) The textual convention RegistrationFlags was updated. The
for VJ compression was removed and bit for reverse tunneling was bit for VJ compression was removed and bit for reverse
added. tunneling was added.
(2) Three new textual conventions were added : MipEntityIdentifier- Three new textual conventions were added :
Type, MipEntityIdentifier and MipEntityIdentifierNAI. These MipEntityIdentifierType, MipEntityIdentifier and
MipEntityIdentifierNAI. These
textual conventions were defined to take into account that textual conventions were defined to take into account that
mobile nodes can be identified by other than ipaddress. mobile nodes can be identified by other than ipaddress.
(3) New textual convention MipDeliveryStyle was added to represent (3) New textual convention MipDeliveryStyle was added to
the delivery style requested by mobile node in the registration represent the delivery style requested by mobile node in the
request. registration request.
mipSecAssocTable was deprecated and replaced with
(4) mipSecAssocTable was deprecated and replaced with mipSecurityAs- mipSecurityAssocTable to support the mobile nodes identified
socTable to support the mobile nodes identified by NAI. Indices by NAI. Indices of the table were changed.
of the table were changed. mipSecurityStatus object was added mipSecurityStatus object was added
to manage the creation of new security associations in the to manage the creation of new security associations in the
table. Default value clause was added to following three table. Default value clause was added to following three
objects of the new table. objects of the new table.
- mipSecurityAlgorithmType - mipSecurityAlgorithmType
- mipSecurityAlgorithmMode - mipSecurityAlgorithmMode
- mipSecurityReplayMethod - mipSecurityReplayMethod
hmac was added to the enumeration list of hmac was added to the enumeration list of
mipSecurityAlgorithmMode object. mipSecurityAlgorithmMode object.
(5) A new object mipSecurityAssocsCount was added. This gives the (5) A new object mipSecurityAssocsCount was added. This gives the
number of security associations in the mipSecurityAssocTable. number of security associations in the mipSecurityAssocTable.
(6) mipSecViolationTable was deprecated and replaced with mipSecuri- (6) mipSecViolationTable was deprecated and replaced with
tyViolationTable to support the mobile nodes identified by NAI. mipSecurityViolationTable to support the mobile nodes
Indices of the table were changed. The objects corresponding to identified by NAI.
mipSecRecentViolationIDLow and mipSecRecentViolationIDHigh in Indices of the table were changed.The objects corresponding
the new table are changed to have the syntax of Unsigned32 to mipSecRecentViolationIDLow and mipSecRecentViolationIDHigh
in the new table are changed to have the syntax of Unsigned32
instead of Integer32. instead of Integer32.
(7) Description of the mnHomeAddress object was changed to support (7) Description of the mnHomeAddress object was changed to
dynamic home address assignment and default value clause was support dynamic home address assignment and default value
added. clause was added.
(8) Two new objects mnIdentifierType and mnIdentifier were added to (8) Two new objects mnIdentifierType and mnIdentifier were added
the mnSystem group. to the mnSystem group.
(9) object mnAdvFlags was refined. The bit for VJ compression was (9) object mnAdvFlags was refined. The bit for VJ compression
removed and bit for reverse tunneling was added. was removed and bit for reverse tunneling was added.
(10) Lower limit of value-range for objects mnAdvMaxRegLifetime and (10) Lower limit of value-range for objects mnAdvMaxRegLifetime
mnAdvMaxAdvLifetime is changed to 1 from 0. and mnAdvMaxAdvLifetime is changed to 1 from 0.
(11) A new object mnRegDeliveryStyle was added to the mnRegistra- (11) A new object mnRegDeliveryStyle was added to the mnRegistra-
tionTable tionTable
(12) maAdvConfigTable was deprecated and replaced with maAdvertCon- (12) maAdvConfigTable was deprecated and replaced with
fTable to support configuration of advertisement parameters on maAdvertConfTable to support configuration of advertisement
unnumbered interfaces. Index of the table was changed. A new parameters on unnumbered interfaces.
object maAdvertService was added to maAdvertConfTable to indi- Index of the table was changed. A new
cate the mobility services offered on the network interface. object maAdvertService was added to maAdvertConfTable to
indicate the mobility services offered on the network
interface.
(13) objects faIsBusy and faRegistrationRequired were deprecated and (13) objects faIsBusy and faRegistrationRequired were deprecated,
replaced with faAdvertConfTable. This is to allow for different replaced with faAdvertConfTable. This is to allow for
settings of 'B' and 'R' bit on different network interfaces. different settings of 'B' and 'R' bit on different network
interfaces.
(14) A new object faChallengeWindow was added to the faAdvertCon- (14) A new object faChallengeWindow was added to the faAdvertCon-
fTable to allow for configuration of challenge window. fTable to allow for configuration of challenge window.
(15) faVisitorTable was deprecated and replaced with faRegVisi- (15) faVisitorTable was deprecated and replaced with faRegVisi-
torTable to support the visitors identified by NAI. Indices of torTable to support the visitors identified by NAI. Indices of
the table were changed. The objects corresponding to faVisitor- the table were changed. The objects corresponding to
RegIDLow and faVisitorRegIDHigh in the new table are changed to faVisitorRegIDLow and faVisitorRegIDHigh in the new table
have the syntax of Unsigned32 instead of Integer32. are changed to have the syntax of Unsigned32 instead of
Integer32.
(16) A new object faRegVisitorDeliveryStyle was added to the (16) A new object faRegVisitorDeliveryStyle was added to the
FaRegVisitorTable to indicate the delivery style requested by FaRegVisitorTable to indicate the delivery style requested by
the mobile node. the mobile node.
(17) A new object faRegVisitorCount was added to count the number of (17) A new object faRegVisitorCount was added to count the number
entries in faRegVisitorTable. of entries in faRegVisitorTable.
(18) faVJCompressionUnavailable object was deprecated. (18) faVJCompressionUnavailable object was deprecated.
(19) Five new counters specific to reverse tunneling function in for- (19) Five new counters specific to reverse tunneling function in
eign agent were added to faRegistration group. These objects for eign agent were added to faRegistration group. These
are objects are
- faReverseTunnelUnavailable - faReverseTunnelUnavailable
- faReverseTunnelBitNotSet - faReverseTunnelBitNotSet
- faMnTooDistant - faMnTooDistant
- faDeliveryStyleUnsupported - faDeliveryStyleUnsupported
- faNonZeroHomeAddressRequired - faNonZeroHomeAddressRequired
(20) Three new counters specific to agent advertisement challenge (20) Three new counters specific to agent advertisement challenge
extension were added to faRegistration group. These objects are extension were added to faRegistration group. These objects
- faUnknownChallenge - faUnknownChallenge
- faMissingChallenge - faMissingChallenge
- faStaleChallenge - faStaleChallenge
(21) Two new counters specific to processing of vendor specific (21) Two new counters specific to processing of vendor specific
extensions by foreign agent were added to faRegistration group. extensions by FA were added to faRegistration group.
These objects are These objects are
- faCvsesFromMnRejected - faCvsesFromMnRejected
- faCvsesFromHaRejected - faCvsesFromHaRejected
(22) Two new objects haMobilityBindingMnIdType and haMobilityBind- (22) Two new objects haMobilityBindingMnIdType and haMobilityBind-
ingMnId were added to the haMobilityBindingTable to accommodate ingMnId were added to the haMobilityBindingTable to
for the mobile nodes not identified by the ipaddress. Syntax of accommodate for the mobile nodes not identified by the
objects haMobilityBindingRegIDLow and haMobilityBindingRegIDHigh ipaddress. Syntax of objects haMobilityBindingRegIDLow and
haMobilityBindingRegIDHigh
was changed to Unsigned32 from Integer32. was changed to Unsigned32 from Integer32.
(23) haCounterTable was deprecated and replaced with haRegCoun- (23) haCounterTable was deprecated and replaced with haRegCoun-
terTable to support the mobile nodes identified by NAI. Indices terTable to support the MNs identified by NAI. Indices
of the table were changed. The syntax of object corresponding of the table were changed. The syntax of object corresponding
to haRecentServiceDeniedCode in the new table was changed to add to haRecentServiceDeniedCode in the new table was changed to
more error codes. add more error codes.
(24) Three new counters specific to reverse tunneling function in (24) Three new counters specific to reverse tunneling function in
home agent were added to the haRegistration group. These home agent were added to the haRegistration group. These
objects are objects are
- haReverseTunnelUnavailable - haReverseTunnelUnavailable
- haReverseTunnelBitNotSet - haReverseTunnelBitNotSet
- haEncapsulationUnavailable - haEncapsulationUnavailable
-
(25) Two new counters specific to processing of vendor specific (25) Two new counters specific to processing of vendor specific
extensions by home agent were added to haRegistration group. extensions by home agent were added to haRegistration group.
These objects are These objects are
- haCvsesFromMnRejected - haCvsesFromMnRejected
- haCvsesFromFaRejected - haCvsesFromFaRejected
(26) A new object haRegMobilityBindingCount was added to count the (26) A new object haRegMobilityBindingCount was added to count the
number of entries in haMobilityBindingTable. number of entries in haMobilityBindingTable.
(27) mipAuthFailure notification was deprecated and replaced with (27) mipAuthFailure notification was deprecated and replaced with
mipAuthFailure2. mipAuthFailure2.
(28) Compliance statement mipCompliance was deprecated and replaced (28) Compliance statement mipCompliance was deprecated and
with mipCompliance2. replaced with mipCompliance2.
(29) Conformance groups were depreciated as needed due to the fact (29) Conformance groups were depreciated as needed due to the fact
that many new items have been added to the MIB. These groups that many new items have been added to the MIB. These groups
include: include:
-mipSecAssociationGroup -mipSecAssociationGroup
-mipSecViolationGroup -mipSecViolationGroup
-mnSystemGroup -mnSystemGroup
-mnRegistrationGroup -mnRegistrationGroup
-maAdvertisementGroup -maAdvertisementGroup
-faAdvertisementGroup -faAdvertisementGroup
skipping to change at page 84, line 6 skipping to change at page 105, line 40
-mipSecViolationGroup2 -mipSecViolationGroup2
-mnSystemGroup2 -mnSystemGroup2
-mnRegistrationGroup2 -mnRegistrationGroup2
-maAdvertisementGroup2 -maAdvertisementGroup2
-faAdvertisementGroup2 -faAdvertisementGroup2
-faRegistrationGroup2 -faRegistrationGroup2
-haRegistrationGroup2 -haRegistrationGroup2
-haRegNodeCountersGroup2 -haRegNodeCountersGroup2
-mipSecNotificationsGroup2 -mipSecNotificationsGroup2
A.2 The changes from versions draft-ietf-mobileip-rfc2006bis-01.txt A.2. Changes in draft-ietf-mobileip-rfc2006bis-02
draft-ietf-mobileip-rfc2006bis-02.txt
(1) The textual convention RegistrationFlags was updated to conform to the sequence order of the flag bits in RFC 3344. (1) The textual convention RegistrationFlags was updated to conform
to the sequence order of the flag bits in RFC 3344.
(2) Typos "CmiEntityIdentfier" changed "MipEntityIdentifier". (2) Typos "CmiEntityIdentfier" changed "MipEntityIdentifier".
(3) A new object MipSecurityReplayTime was added for acceptable replay protection time range using timestamps. (3) A new object MipSecurityReplayTime was added for acceptable
replay protection time range using timestamps.
(4) The following objects changed to have the syntax of Unsigned32 instead of Integer32. (4) The following objects changed to have the syntax of Unsigned32
instead of Integer32.
-mnRegIDHigh -mnRegIDHigh
-mnRegIDLow -mnRegIDLow
-mnRegTimeRequested -mnRegTimeRequested
-haMobilityBindingTimeGranted -haMobilityBindingTimeGranted
-mipSecurityRecentViolationSPI -mipSecurityRecentViolationSPI
(5) The following values added to object haRegRecentServiceDeniedCode. (5) The following values added to object
haRegRecentServiceDeniedCode.
-mnCvseUnsupported (140) -mnCvseUnsupported (140)
-faCvseUnsupported (141) -faCvseUnsupported (141)
(6) The following object names were changed to provide better meaning since these are rejection counters. (6) The following object names were changed to provide better meaning
since these are rejection counters.
-haCvsesFromMnRejected to haCvsesFromMnUnsupported -haCvsesFromMnRejected to haCvsesFromMnUnsupported
-haCvsesFromFaRejected to haCvsesFromFaUnsupported -haCvsesFromFaRejected to haCvsesFromFaUnsupported
-faCvsesFromMnRejected to faCvsesFromMnUnsupported -faCvsesFromMnRejected to faCvsesFromMnUnsupported
-faCvsesFromHaRejected to faCvsesFromHaUnsupported -faCvsesFromHaRejected to faCvsesFromHaUnsupported
(7) The following objects were added to HA registration counters. (7) The following objects were added to HA registration counters.
-haNvsesFromMnIgnored -haNvsesFromMnIgnored
-haNvsesFromFaIgnored -haNvsesFromFaIgnored
(8) The following objects were added to FA registration counters. (8) The following objects were added to FA registration counters.
-faNvsesFromMnIgnored -faNvsesFromMnIgnored
-faNvsesFromHaIgnored -faNvsesFromHaIgnored
A.3 The changes from versions draft-ietf-mobileip-rfc2006bis-02.txt A.3. Changes in draft-ietf-mobileip-rfc2006bis-03
draft-ietf-mobileip-rfc2006bis-03.txt
(1) The size of the MipEntityIdentifier is changed to OCTET STRING of (1) The size of the MipEntityIdentifier is changed to OCTET STRING of
size 64 octets size 64 octets
(2) Changed the SYNTAX for mnAdvSequence object to Integer32 (2) Changed the SYNTAX for mnAdvSequence object to Integer32
(3) Changed the SYNTAX for mnAdvMaxRegLifeTime object to Integer32 (3) Changed the SYNTAX for mnAdvMaxRegLifeTime object to Integer32
(4) Changed the SYNTAX for mnAdvMaxAdvLifeTime object to Integer32 (4) Changed the SYNTAX for mnAdvMaxAdvLifeTime object to Integer32
(5) faNvsesFromMnIgnored is anchored at faRegistration 27 (5) faNvsesFromMnIgnored is anchored at faRegistration 27
(6) faNvsesFromHaIgnored is anchored at faRegistration 28 (6) faNvsesFromHaIgnored is anchored at faRegistration 28
(7) faRegVisitorCount is anchored at faRegistration 29 (7) faRegVisitorCount is anchored at faRegistration 29
(8) Changed the faCvsesFromHaSupported object name to faCvsesFromHaUnsupported (8) Changed the faCvsesFromHaSupported object name to
faCvsesFromHaUnsupported
(9) Added faNvsesFromMnIgnored and faNvsesFromHaIgnored to faRegistrationGroup2 (9) Added faNvsesFromMnIgnored and faNvsesFromHaIgnored to
faRegistrationGroup2
(10) faRegVisitorTable is anchored at faRegistration 30 (10) faRegVisitorTable is anchored at faRegistration 30
(11) Added the haNvsesFromMnIgnored object to the haRegistrationGroup2 (11) Added the haNvsesFromMnIgnored object to the
haRegistrationGroup2
(12) Added the haNvsesFromFaIgnored object to the haRegistrationGroup2 (12) Added the haNvsesFromFaIgnored object to the
haRegistrationGroup2
(13) Added the NOTIFICATION-GROUP to the imports (13) Added the NOTIFICATION-GROUP to the imports
A.4 The changes from versions draft-ietf-mobileip-rfc2006bis-03.txt A.4. Changes in draft-ietf-mip4-rfc2006bis-00
draft-ietf-mip4-rfc2006bis-00.txt
(1) Draft retitled to draft-ietf-mip4-rfc2006bis-00.txt (1) Draft retitled to draft-ietf-mip4-rfc2006bis-00.txt
A.5 The changes from versions draft-ietf-mip4-rfc2006bis-00.txt to A.5. Changes in draft-ietf-mip4-rfc2006bis-01
draft-ietf-mip4-rfc2006bis-01.txt
(1) Chair addresses updated. (1) Chair addresses updated.
B. Chair and Editor Addresses A.6. Changes in draft-ietf-mip4-rfc2006bis-02
The working group can be contacted via the current chairs: 1) Aligned RegistrationFlags with rfc2006.
Pete McCann Henrik Levkowetz Issue:
Lucent Technologies ipUnplugged AB
Rm 9C-226R Arenavagen 33
1960 Lucent Lane
Naperville, Illinois 60563 Stockholm S-121 28
USA Sweden
Phone: +1 630 713 9359 Phone: +46 708 32 16 08
Email: mccap@lucent.com Email: henrik@levkowetz.com
Questions about this memo can also be directed to the editors: mnAdvFlags are totally difeerent from teh adverticed octet, but has
the same dataformat (octet). Shouldn't we change it to the 3344 octet
|R|B|H|F|M|G|r|T|
2) mipEncapsulationSupported OBJECT-TYPE should also contain RFC3519
UDP Tunnel option. Aded new bit to the object since new bit is
allowed for MIB revision. (RFC 2578, section 10.2 and RFC4181,
section 4.9).
3) mipSecurityAssocEntry and mipSecurityViolationEntry now contain
the full NAI and the address objects. Since the index could be either
or, and the NAI could be crippled in the index.
4) The error code for a security violation is added. The reason
object itself isn't enough (it's almost always other(6). Added
mipSecRecentViolationErrorCode to mipSecViolationTable
5) maAdvertIfIndex should be InterfaceIndex from IF-MIB, not integer
6) With RFC3846, NAI is equally applicable to links and
adverticements. So, NAI needs to be included for Mobility agent
advertisement interfaces.
Added in a group for those that implement agent NAI's a'la RFC3846.
7) NAI needs to be added in the FA Visitor table. The NAI isn't
necessarily included in the index, and it might also be crippled if
it's to long.
8) Packet and byte conters per session added. This is a most useful
debug-tool, and is also practice in all comparable mibs. They should
be kept per registration sessson in the FA and HA.
9) HA and NAI information is included in haMobilityBindingTable.
There could be many per snmp-agent, so which ha a particular ha
session is pertaining to should be incluided in the table. Also, the
NAI (as described before) is included.
10) haRegRecentServiceDeniedCode can't be enumerated. It's handled by
IANA and should therefore be one of the IANA considerations, the
sytax is changed to open INTEGER.
11) The mipAuthFailure2 notification needs additional objects. Traps
should be complete and don't require addditional read operations. the
mipAuthFailure2 trap adds objects from hte seviolation table.
12) StorageType a'la rfc2579 is added to those tables where they are
needed.
13) Updated template stuff, such as mib boiler plate, security
considerations, references and TC conventions.
7. References
7.1. Normative References
[RFC1701] Hanks S. et. al., "Generic Routing Encapsulation (GRE)",
RFC1701, October 1994.
[RFC2002] Perkins C., "IP Mobility Support", RFC 2002, Octoer 1996.
[RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003,
October 1996.
[RFC2004] Perkins, C., "Minimal Encapsulation within IP", RFC 2004,
October 1996.
[RFC2006] Cong, D., Hamlen, M., and Perkins, C., "The Definitions of
Managed Objects for IP Mobility Support using SMIv2", RFC
2006, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2574] Blumenthal U., "User-based Security Model (USM) for version
3 of the Simple Network Management Protocol (SNMPv3)", RFC
2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC2794] Calhoun, P., and Perkins, C., "Mobile IP Network Access
Identifier Extension for IPv4", RFC 2794, January 2000.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB" RFC 2863, June 2000.
[RFC3012] Calhoun, P., and Perkins, C., "Mobile IPv4
Challenge/Response Extension", RFC 3012, November 2000.
[RFC3024] Montenegro, G., "Reverse Tunneling for Mobile IP", RFC
3024, January 2001.
[RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/Organization
Specific Extensions", RFC 3115, April 2001.
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002.
[RFC3519] H. Levkowetz and S. Vaarala, "Mobile IP Traversal of
[RFC3846] F. Johansson and T. Johansson, Mobile IPv4 Extension for
7.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Author's Addresses
Ravindra Rathi Kent Leung Ravindra Rathi Kent Leung
Intel Corporation Cisco Systems, Inc. Greenfield Networks Cisco Systems, Inc.
136, Airport Road 170 West Tasman Drive #2/2, Union Street 170 West Tasman Drive
Bangalore - 560 017 San Jose, CA. 95134 Bangalore - 560 001 San Jose, CA. 95134
India USA India USA
Phone: +91 80 507 5553 Phone: +1 408 526 5030 Phone: +91 80 4151 8871 Phone: +1 408 526 5030
Email: ravindra.rathi@intel.com Email: kleung@cisco.com Email: rrathi@greenfieldnetworks.com Email: kleung@cisco.com
C. Full Copyright Statement Hans Sjostrand
ipUnplugged
Arenavagen 21
121 29 Stockholm
Sweden
Phone: +46 8 725 5900
Email: hans@ipunplugged.com
Copyright (C) The Internet Society (2000). All Rights Reserved. Intellectual Property Statement
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this doc-
ument itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop-
ing Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or as
required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be The IETF takes no position regarding the validity or scope of any
revoked by the Internet Society or its successors or assigns. Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
This document and the information contained herein is provided on an Copies of IPR disclosures made to the IETF Secretariat and any
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING assurances of licenses to be made available, or the result of an
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING attempt made to obtain a general license or permission for the use of
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION such proprietary rights by implementers or users of this
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- specification can be obtained from the IETF on-line IPR repository at
CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 227 change blocks. 
506 lines changed or deleted 872 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/