One document matched: draft-ietf-mobileip-mib-mn-00.txt
Mobile IP Working Group D. Cong & M. Hamlen, editor
INTERNET DRAFT Motorola
expires in six months C. Perkins, editor
IBM
December 1995
The Definitions of Managed Objects for the Mobile Node function
of IP Mobility Support
draft-ietf-mobileip-mib-mn-00.txt
Status of this Memo
This document is a submission by the Mobile-IP Working Group of the
Internet Engineering Task Force (IETF). Comments should be submitted
to the mobile-ip@smallworks.com mailing list.
Distribution of this memo is unlimited.
This document is 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
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts
Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast).
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it describes managed objects used for managing the
Mobile Node function definied in the Mobile IP Protocol.
Cong, Hamlen & Perkins expires in six months [Page 1]
Internet Draft Mobile IP MIB Definition December 18, 1995
Table of Contents
1. The Network Management Framework ...................... 2
2. Objects ............................................... 2
2.1 Format of Definitions ................................ 2
3. Overview .............................................. 3
3.1 Object Selection Criteria ............................ 3
3.2 Structure of the Mobile IP ........................... 3
3.3 MIB Groups ........................................... 4
4. Definitions ........................................... 4
5. Acknowledgements ...................................... 17
6. Security Considerations ............................... 17
7. References ............................................ 18
8. Chair's Address ....................................... 19
9. Editor's Address ...................................... 19
1. The Network Management Framework
The Internet-standard Network Management Framework consists of three
components. They are:
STD 16/RFC 1155 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management. STD
16/RFC 1212 defines a more concise description mechanism, which is
wholly consistent with the SMI.
STD 17/RFC 1213 which defines MIB-II, the core set of managed
objects for the Internet suite of protocols.
STD 15/RFC 1157 which defines the SNMP, the protocol used for
network access to managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
2. Objects
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) [3]
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to refer to the
object type.
2.1. Format of Definitions
Cong, Hamlen & Perkins expires in six months [Page 2]
Internet Draft Mobile IP MIB Definition December 18, 1995
Section 4 contains the specification of all object types contained in
this MIB module. The object types are defined using the conventions
defined in the SMI, as amended by the extensions specified in [5,6].
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. For example, the editors minimize the
management requirements in the Mobile Node.
(2) Require that objects be essential for either fault or
configuration management.
(3) Limit the total number of objects.
(4) Exclude objects which are simply derivable from others in
this or other MIBs.
3.2. Structure of the Mobile IP
This section describes the basic model of Mobile IP used in
developing the Mobile IP MIB. This information should be useful to
the implementor in understanding some of the basic design decisions
of the MIB.
The Mobile IP Protocol introduces these new funtional entities:
Mobile Node
A host or router that changes its point of attachment from one
network or subnetwork to another. A mobile node may change its
location without losing connectivity and without changing its
IP address.
Home Agent
A router on a mobile node's home network which tunnels packets
for delivery to the mobile node when it is away from home, and
maintains current location information for the mobile node.
Foreign Agent
Cong, Hamlen & Perkins expires in six months [Page 3]
Internet Draft Mobile IP MIB Definition December 18, 1995
A router on a mobile node's visited network which provides
routing services to the mobile node when it registers. The
foreign agent detunnels and delivers packets to the mobile node
that were tunneled by the mobile node's home agent. In the
reverse direction, the foreign agent may serve as a default
router for registered mobile node.
This document specifies the objects used in managing one of these
entities; namely, the Mobile node.
3.3. MIB Groups
The definitions of managed objects for Mobile IP have been organized
into several MIB groups:
(1) The Mobile Node Group
(2) The Foreign Agent Group
(3) The Home Agent Group
(4) The Security Group (Optional)
The first three groups are related to the three entities defined in
the Mobile IP Protocol specification. The Security Group is an
optional group for all three entities, because it includes security
configurations for each Mobile IP entity. If an agent seeking to
implement the Mobile IP MIB does not support SNMPv2 with privacy, it
is strongly advised that the Security Group not be implemented.
This document specifies the Mobile Node Group.
4. Definitions
MIP-MN-MIB DEFINITIONS ::= BEGIN
IMPORTS
Counter, IpAddress, TimeTicks
FROM RFC1155-SMI
mib-2, DisplayString, PhysAddress
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212;
-- Extend the MIB definitions
-- >>> D.C. Pending for assigned number for Mobile IP
mip OBJECT IDENTIFIER ::= { mib-2 999 }
-- There are four groups defined in Mobile IP MIB.
Cong, Hamlen & Perkins expires in six months [Page 4]
Internet Draft Mobile IP MIB Definition December 18, 1995
mn OBJECT IDENTIFIER ::= { mip 1 }
-- textual conventions
Boolean ::= INTEGER { true(1), false(2) }
-- Mobile Node Groups
mnSystem OBJECT IDENTIFIER ::= { mn 1 }
mnDiscovery OBJECT IDENTIFIER ::= { mn 2 }
mnRegistration OBJECT IDENTIFIER ::= { mn 3 }
-- Mobile Node System Group
mnMobileIPEnable OBJECT-TYPE
SYNTAX Boolean
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Enables the mobile node function as definied in IP
Mobility function. If it is true, it is enabled,
otherwise it is disabled."
::= { mnSystem 1 }
mnState OBJECT-TYPE
SYNTAX INTEGER {
home(1), -- MN is connected to home network
registered(2), -- MN has registered on foreign network
pending(3), -- MN has sent registration request(s)
-- and is waiting for the reply
isolated(4), -- MN is isolated from network
unknown(5) -- MN can not determine its state
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates mobile node's status of Mobile IP."
::= { mnSystem 2 }
mnCurrentHomeAgent OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Current home agent IP address. It is only valid
when mobile node is in registered or home state."
::= { mnSystem 3 }
Cong, Hamlen & Perkins expires in six months [Page 5]
Internet Draft Mobile IP MIB Definition December 18, 1995
mnHomeAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An IP address that is assigned for an extended period of
time to the mobile node. It remains unchanged regardless
of the mobile node's current point of attachment."
::= { mnSystem 4 }
-- Mobile node's home agent list
mnHATable OBJECT-TYPE
SYNTAX SEQUENCE OF MnHAEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table containing all of the mobile node's potential
home agents."
::= { mnSystem 5 }
mnHAEntry OBJECT-TYPE
SYNTAX MnHAEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Home agent information for a particular agent."
INDEX { mnHAAddress }
::= { mnHATable 1 }
MnHAEntry ::= SEQUENCE {
mnHAAddress IpAddress
}
mnHAAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"IP address of mobile node's Home Agent."
::= { mnHAEntry 1 }
-- Mobile node's Agent Discovery Group
-- Mobile node's Foreign Agent table
mnFATable OBJECT-TYPE
SYNTAX SEQUENCE OF MnFAEntry
Cong, Hamlen & Perkins expires in six months [Page 6]
Internet Draft Mobile IP MIB Definition December 18, 1995
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table containing all foreign agents that the mobile
node knows about and their corresponding COA(s). This
table is updated when advertisements are received by the
mobile node. If an advertisement expires, its entry(s)
should be deleted from the table. One foreign agent can
provide more than one COA in its advertisements."
::= { mnDiscovery 1 }
mnFAEntry OBJECT-TYPE
SYNTAX MnFAEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"One pair of foreign agent IP address and COA for
that foreign agent."
INDEX { mnFAAddress, mnCOA }
::= { mnFATable 1 }
MnFAEntry ::= SEQUENCE {
mnFAAddress IpAddress,
mnCOA IpAddress
}
mnFAAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Foreign agent's IP address."
::= { mnFAEntry 1 }
mnCOA OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"COA provided by the foreign agent."
::= { mnFAEntry 2 }
-- The most recently received Agent Advertisement
mnRecentAdvReceived OBJECT IDENTIFIER ::= { mnDiscovery 2 }
mnAdvSourceAddress OBJECT-TYPE
SYNTAX IpAddress
Cong, Hamlen & Perkins expires in six months [Page 7]
Internet Draft Mobile IP MIB Definition December 18, 1995
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The source IP address of the most recently
received Agent Advertisement. This address could
be the address of a home agent or a foreign agent."
::= { mnRecentAdvReceived 1 }
mnAdvSequence OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The sequence number of the most recently received
advertisement. The sequence number ranges from 0 to
0xffff. After the sequence number attains the value
0xffff, it will rollover to 256."
::= { mnRecentAdvReceived 2 }
mnAdvFlags OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The flags contained in the most recently received
advertisement. Flags can be distinguished by applying
the appropriate testing bit.
Flag Bitmask Indication
R 0x8000 FA registration required
B 0x4000 FA Busy bit
H 0x2000 Agent is Home Agent
F 0x1000 Agent is Foreign Agent
M 0x800 Agent offers minimal enc.
G 0x400 Agent offers GRE
V 0x200 Agent supports VJ compress."
::= { mnRecentAdvReceived 3 }
mnAdvRegLifetime OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The longest lifetime in seconds that the agent
is willing to accept in any registration request."
::= { mnRecentAdvReceived 4 }
mnAdvPeriod OBJECT-TYPE
SYNTAX INTEGER
Cong, Hamlen & Perkins expires in six months [Page 8]
Internet Draft Mobile IP MIB Definition December 18, 1995
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The maximum length of time that the Advertisement
is considered valid in the absence of further
Advertisements as defined in RFC 1256."
::= { mnRecentAdvReceived 5 }
mnAdvTimeReceived OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time at which the most recently received
advertisement was received."
::= { mnRecentAdvReceived 6 }
-- Mobile Node Discovery Group Counters
mnSolicitationsSent OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of Solicitations sent by the mobile node."
::= { mnDiscovery 3 }
mnAdvertisementsReceived OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of advertisements received by the mobile
node."
::= { mnDiscovery 4 }
mnAdvsDroppedInvalidExtension OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of advertisements dropped by the mobile
node due to both poorly formed extensions and
unrecognized extensions with extension number in the
range 0-127."
::= { mnDiscovery 5 }
mnAdvsIgnoredUnkownExtension OBJECT-TYPE
Cong, Hamlen & Perkins expires in six months [Page 9]
Internet Draft Mobile IP MIB Definition December 18, 1995
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of unrecognized extensions in the range
128-255 that were ignored by the mobile node."
::= { mnDiscovery 6 }
mnMoveFromHAToFA OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of times that the mobile node has detected
movement from its home network to a foreign network."
::= { mnDiscovery 7 }
mnMoveFromFAToFA OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of times that the mobile node has detected
movement from one foreign network to another foreign
network."
::= { mnDiscovery 8 }
mnMoveFromFAToHA OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of times that the mobile node has detected
movement from a foreign network to its home network."
::= { mnDiscovery 9 }
mnGratuitousARPsSend OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of Gratuitous ARPs sent by mobile node in
order to clear out any stale ARP entries in the ARP
caches of nodes on the home network."
::= { mnDiscovery 10 }
-- Mobile Node Registration Group
Cong, Hamlen & Perkins expires in six months [Page 10]
Internet Draft Mobile IP MIB Definition December 18, 1995
-- Registration table of mobile node
mnRegistrationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MnRegistrationEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table containing information about the mobile node's
attempted registration(s). The mobile node updates this
table based upon Registration Requests sent and
Registration Replies received in response to these
requests. Certain variables within this table are also
updated if when Registration Requests are retransmitted."
::= { mnRegistration 1 }
mnRegistrationEntry OBJECT-TYPE
SYNTAX MnRegistrationEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information about one registration attempt."
INDEX { mnRegAgentAddress, mnRegCOA}
::= { mnRegistrationTable 1 }
MnRegistrationEntry ::= SEQUENCE {
mnRegAgentAddress IpAddress,
mnRegCOA IpAddress,
mnRegFlags INTEGER,
mnRegID1 INTEGER,
mnRegID2 INTEGER,
mnRegTimeRequested INTEGER,
mnRegTimeRemain INTEGER,
mnRegTimeSent TimeTicks,
mnRegIsAccepted Boolean,
mnCOAIsLocal Boolean
}
mnRegAgentAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"IP address of the agent as used in the destination IP
address of the Registration Request. The agent may be a
home agent or a foreign agent."
::= { mnRegistrationEntry 1 }
mnRegCOA OBJECT-TYPE
Cong, Hamlen & Perkins expires in six months [Page 11]
Internet Draft Mobile IP MIB Definition December 18, 1995
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Care-of address for the registration."
::= { mnRegistrationEntry 2 }
mnRegFlags OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Registration flags sent by mobile node. Flags can
be distinguished by applying the testing bit.
Flag Bitmask Indication
S 0x80 Request to retain prior binding(s)
B 0x40 Request to receive broadcasts
D 0x20 COA is local to MN
M 0x10 Request to use minimal enc.
G 0x8 Request to use GRE."
::= { mnRegistrationEntry 3 }
mnRegID1 OBJECT-TYPE
SYNTAX INTEGER (SIZE (0..32))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Low-order 32 bits of identification used in that
registration by mobile node."
::= { mnRegistrationEntry 4 }
mnRegID2 OBJECT-TYPE
SYNTAX INTEGER (SIZE (0..32))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"High-order 32 bits of identification used in that
registration by mobile node."
::= { mnRegistrationEntry 5 }
mnRegTimeRequested OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"If the registration is pending, then this is the
lifetime requested by the mobile node (in seconds). If
Cong, Hamlen & Perkins expires in six months [Page 12]
Internet Draft Mobile IP MIB Definition December 18, 1995
the registration has been accepted, then this is the
lifetime actually granted by the home agent in the
reply."
::= { mnRegistrationEntry 6 }
mnRegTimeRemain OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of seconds remaining until this registration
expires. It has the same initial value as
mnRegTimeRequested and is only valid if mnRegIsAccepted
is TRUE."
::= { mnRegistrationEntry 7 }
mnRegTimeSent OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time when the last (re-)transmission occured."
::= { mnRegistrationEntry 8 }
mnRegIsAccepted OBJECT-TYPE
SYNTAX Boolean
ACCESS read-only
STATUS mandatory
DESCRIPTION
"True(1) if the mobile node has received a Registration
Reply indicating that service has been accepted; false(2)
otherwise. False(2) implies that the registration is
still pending."
::= { mnRegistrationEntry 9 }
mnCOAIsLocal OBJECT-TYPE
SYNTAX Boolean
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Whether the COA is local to (dynamically acquired by)
the mobile node or not. If it is false(2), the COA is
an address of the foreign agent."
::= { mnRegistrationEntry 10 }
-- Mobile Node Registration Group Counters
mnRegRequestsSent OBJECT-TYPE
Cong, Hamlen & Perkins expires in six months [Page 13]
Internet Draft Mobile IP MIB Definition December 18, 1995
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of registration requests sent by the mobile
node. This does not include deregistrations (those with
Lifetime equal to zero)."
::= { mnRegistration 2 }
mnDeregRequestsSent OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of deregistration requests sent by the
mobile node (those with Lifetime equal to zero)."
::= { mnRegistration 3 }
mnRegRepliesRecieved OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of registration replies received by the
mobile node in which the Lifetime is greater than zero."
::= { mnRegistration 4 }
mnDeRegRepliesRecieved OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of (de)registration replies received by the
mobile node in which the Lifetime is equal to zero."
::= { mnRegistration 5 }
mnRepliesInvalidHomeAddress OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of replies with invalid home address for
the mobile node."
::= { mnRegistration 6 }
mnRepliesUnknownHA OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
Cong, Hamlen & Perkins expires in six months [Page 14]
Internet Draft Mobile IP MIB Definition December 18, 1995
STATUS mandatory
DESCRIPTION
"Total number of replies with unknown home agents
(not in home agent table)."
::= { mnRegistration 7 }
mnRepliesUnknownFA OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of replies with unkown foreign agents if
replies relayed through foreign agent."
::= { mnRegistration 8 }
mnRepliesInvalidID OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of replies with invalid identification
fields."
::= { mnRegistration 9 }
mnRepliesDroppedInvalidEntension OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of replies dropped by the mobile node due to
both poorly formed extensions and unrecognized extensions
with extension number in the range 0-127."
::= { mnRegistration 10 }
mnRepliesIgnoredUnkownEntension OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of unrecognized extensions in the range
128-255 that were ignored by the mobile node."
::= { mnRegistration 11 }
mnRepliesHAAuthenticationFailure OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
Cong, Hamlen & Perkins expires in six months [Page 15]
Internet Draft Mobile IP MIB Definition December 18, 1995
"Total number of replies without a valid Home Agent to
Mobile Node authenticator."
::= { mnRegistration 12 }
mnRepliesFAAuthenticationFailure OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of replies without a valid Foreign Agent to
Mobile Node authenticator."
::= { mnRegistration 13 }
mnRegRequestsAccepted OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of registration requests accepted by the
mobile node's home agent (Code 0 and Code 1)."
::= { mnRegistration 14 }
mnRegRequestsDeniedByHA OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of registration requests denied by mobile
node's home agent (Sum of Code 128 through Code 191)."
::= { mnRegistration 15 }
mnRegRequestsDeniedByFA OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of registration requests denied by the
foreign agent (Sum of Codes 64 through Code 127)."
::= { mnRegistration 16 }
mnRegRequestsDeniedByHADueToID OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of Registration Request denied by home
agent due to identification mismatch."
::= { mnRegistration 17 }
Cong, Hamlen & Perkins expires in six months [Page 16]
Internet Draft Mobile IP MIB Definition December 18, 1995
mnRegRequestsWithDirectedBroadcast OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of registration requests sent by mobile
node with a directed broadcast address in the home agent
field."
::= { mnRegistration 18 }
mnAgentRebootsDectected OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of agent reboots detected by the mobile
node through sequence number of the advertisement."
::= { mnRegistration 19 }
END
5. Acknowledgments
This document was produced by the Mobile IP working group. The
editors wish to thank Jim Solomon, for his encouragement, patience,
and help. Thanks to Fredrick Tarberg and Fredrik Broman (KTH) for
their initial efforts on MIB definitions. Thanks to Frank
Kastenholz(FTP), for his comments on the initial MIB from KTH.
6. Security Considerations
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:
(1) All variables which represent a significant security risk
are placed in separate, optional, MIB Groups. As the MIB
Group is the quantum of implementation within a MIB, the
implementor of the MIB may elect not to implement these
groups.
(2) The implementor may choose to implement the variables
which present a security risk so that they may not be
Cong, Hamlen & Perkins expires in six months [Page 17]
Internet Draft Mobile IP MIB Definition December 18, 1995
written, i.e., the variables are READ-ONLY. This method
still presents a security risk, and is not recommended,
in that the variables, specifically the Mobile IP Security
Association variables, may be easily read.
(3) Using SNMPv2, the operator can place the variables into
MIB views which are protected in that the parties which
have access to those MIB views use authentication and
privacy protocols, or the operator may elect to make
these views not accessible to any party. In order to
facilitate this placement, all security-related variables
are placed in separate MIB Tables. This eases the
identification of the necessary MIB View Subtree.
(4) The Mobile IP Security MIB contains several objects which
are very sensitive from a security point of view.
Thus, in order to preserve the integrity, security and privacy of
the Mobile IP security features, an implementation will allow
access to this MIB only via SNMPv2 and then only for parties which
are privacy enhanced. Other access modes, e.g., SNMPv1 or SNMPv2
without privacy-enhancement, are very dangerous and the security
of the IP Mobility Support may be compromised. The other way to
access this information is by use of SNMPv1 in concert with the IP
security protocols (AH and ESP). This can also be done in a
secure fashion.
7.0 References
[1] Rose M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", STD 16, RFC
1155, Performance Systems International, Hughes LAN Systems, May
1990.
[2] McCloghrie K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets", STD 17, RFC
1213, Performance Systems International, March 1991.
[3] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization, International
Standard 8824, December 1987.
[4] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One
(ASN.1), International Organization for Standardization,
International Standard 8825, December 1987.
Cong, Hamlen & Perkins expires in six months [Page 18]
Internet Draft Mobile IP MIB Definition December 18, 1995
[5] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
STD 16, RFC 1212, Performance Systems International, Hughes LAN
Systems, March 1991.
[6] Rose, M., Editor, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, Performance Systems International, March
1991.
[7] McCloghrie, K., "Extensions to the Generic-Interface MIB", RFC
1229, Hughes LAN Systems, Inc., May 1991.
[8] Solomon J., "Mobile IP Protocol Applicability Statement",
Internet Draft -- work in progress, December, 1995.
[9] Perkins C., "IP Mobility Support", Internet Draft -- work in
progress, December, 1995.
[10] Perkins C., "IP Encapsulation within IP". Internet Draft --
work in progress, October 1995.
[11] Perkins C., "Minimal Encapsulation within IP". Internet Draft
-- work in progress, July 1995.
[12] Hanks S. et. al., "Generic Routing Encapsulation (GRE)",
RFC 1701, October 1994.
[13] Deering, S., "ICMP Router Discovery Messages", RFC 1256,
September 1991.
8. Chair's Addresses
The working group can be contacted via the current chairs:
Jim Solomon Tony Li
Motorola, Inc. cisco systems
1301 E. Algonquin Rd. 170 W. Tasman Dr.
Schaumburg, IL 60196 San Jose, CA 95134
Work: +1-708-576-2753 Work: +1-408-526-8186
E-mail: solomon@comm.mot.com E-mail: tli@cisco.com
9. Editor's Address
Questions about this memo can also be directed to:
David Cong
Room 3149
Cong, Hamlen & Perkins expires in six months [Page 19]
Internet Draft Mobile IP MIB Definition December 18, 1995
Motorola
1301 East Algonquin Rd.
Schaumburg, IL 60196
Work: +1-708-576-1357
Fax: +1-708-538-3472
E-mail: cong@comm.mot.com
Mark Hamlen
Room 4413
Motorola
1301 East Algonquin Rd.
Schaumburg, IL 60196
Work: +1-708-576-0346
Fax: +1-708-538-6150
E-mail: hamlen@comm.mot.com
Charles Perkins
Room J1-A25
T. J. Watson Research Center
IBM Corporation
30 Saw Mill River Rd.
Hawthorne, NY 10532
Work: +1-914-784-7350
Fax: +1-914-784-7007
E-mail: perk@watson.ibm.com
Cong, Hamlen & Perkins expires in six months [Page 20]
| PAFTECH AB 2003-2026 | 2026-04-21 09:58:41 |