draft-ietf-nemo-mib-01.txt   draft-ietf-nemo-mib-02.txt 
Nemo Working Group Sri Gundavelli NEMO Working Group Sri Gundavelli
INTERNET-DRAFT Cisco Systems Internet-Draft Cisco Systems
Expires: January 15, 2006 Glenn M. Keeni Expires: April 24, 2007 Glenn M. Keeni
Cyber Solutions Cyber Solutions
Kazuhide Koide Kazuhide Koide
Tohoku University Tohoku University
Kenichi Nagami Kenichi Nagami
INTEC NetCore INTEC NetCore
October 21, 2006
July 16, 2005
NEMO Management Information Base NEMO Management Information Base
<draft-ietf-nemo-mib-01.txt> draft-ietf-nemo-mib-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 40 skipping to change at page 1, line 39
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 document is a product of the nemo Working Group. Comments should This Internet-Draft will expire on April 24, 2007.
be addressed to the authors or the mailing list at nemo@ietf.org
This Internet-Draft will expire on January 15, 2006
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB), This memo defines a portion of the Management Information Base (MIB),
the network mobility support (NEMO) MIB, for use with network the network mobility support (NEMO) MIB, for use with network
management protocols in the Internet community. In particular, the management protocols in the Internet community. In particular, the
NEMO MIB will be used to monitor and control a mobile ipv6 node with NEMO MIB will be used to monitor and control a mobile ipv6 node with
NEMO functionality. NEMO functionality.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework .................... 3 1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Overview ...................................................... 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. MIB Design .................................................... 4 2.1. The Mobile IPv6 Protocol and NEMO entities . . . . . . . . 3
4. The NEMO MIB .................................................. 5 2.2. Implementation Guidance . . . . . . . . . . . . . . . . . 3
5. Security Considerations .......................................32 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations ...........................................32 3. MIB Design . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgments ...............................................33 4. The NEMO MIB . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. References ....................................................34 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
9. Authors' Addresses ............................................36 6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
10. Full Copyright Statement ......................................37 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.1. Normative References . . . . . . . . . . . . . . . . . . . 31
8.2. Informative References . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
Intellectual Property and Copyright Statements . . . . . . . . . . 34
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. 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. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Overview 2. Overview
2.1 The Mobile IPv6 Protocol and NEMO entities. 2.1. The Mobile IPv6 Protocol and NEMO entities
Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes
to remain reachable while moving around in the IPv6 Internet. Network to remain reachable while moving around in the IPv6 Internet.
Mobility Basic Support (NEMO) [RFC3963] is an extension to the Mobile Network Mobility Basic Support (NEMO) [RFC3963] is an extension to
IPv6 protocol which facilitates the movement of an entire network. the Mobile IPv6 protocol which facilitates the movement of an entire
The goals of Network Mobility support and related terminology are network. The goals of Network Mobility support and related
discussed in [NEMOGOAL] and [NEMOTERM], respectively. terminology are discussed in [NEMOGOAL] and [NEMOTERM], respectively.
Typically mobile routers implement NEMO functionality for achieving Typically mobile routers implement NEMO functionality for achieving
network mobility. However, a mobile router may also function as a network mobility. However, a mobile router may also function as a
mobile node. In the context of this document, an entity that mobile node. In the context of this document, an entity that
implements the NEMO protocol is a NEMO entity. implements the NEMO protocol is a NEMO entity.
This document defines a set of managed objects (MOs) that can be used This document defines a set of managed objects (MOs) that can be used
to monitor and control NEMO entities. to monitor and control NEMO entities.
2.2 Implementation Guidance 2.2. Implementation Guidance
This document focuses on the management of a NEMO entity. The This document focuses on the management of a NEMO entity. The
MIPv6MIB [10] defines the managed objects for a mobile node. MIPv6MIB [10] defines the managed objects for a mobile node.
Implementations supporting both the mobile node and NEMO Implementations supporting both the mobile node and NEMO
functionality SHOULD implement the managed objects defined for the functionality SHOULD implement the managed objects defined for the
NEMO entities and mobile nodes from both the MIPv6MIB and NEMOMIB. NEMO entities and mobile nodes from both the MIPv6MIB and NEMOMIB.
2.3 Terminology. 2.3. Terminology
The terminology used in this document is consistent with the The terminology used in this document is consistent with the
definitions used in the Mobile IPv6 protocol specification[RFC3775] definitions used in the Mobile IPv6 protocol specification[RFC3775]
and the NEMO Basic Support specification [NEMO]. and the NEMO Basic Support specification [NEMO].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, RFC 2119 [RFC2119]. 14, RFC 2119 [RFC2119].
3. MIB Design 3. MIB Design
The NEMO MIB comprises of the following primary groups: The NEMO MIB comprises of the following primary groups:
- nemoSystem o nemoSystem
- nemoConfiguration
- nemoStats o nemoConfiguration
- nemoNotifications
- nemoConformance o nemoStats
o nemoNotifications
o nemoConformance
The nemoSystem group provides the general information of the NEMO The nemoSystem group provides the general information of the NEMO
entity. The objects in this group cover the current home registration entity. The objects in this group cover the current home
state. registration state.
The nemoConfiguration group contains information relevant to the The nemoConfiguration group contains information relevant to the
implementation and operation of the NEMO protocol. implementation and operation of the NEMO protocol.
The nemoStats group defines the statistics related to the NEMO The nemoStats group defines the statistics related to the NEMO
protocol operations. protocol operations.
The nemoNotifications group defines the notifications generated by The nemoNotifications group defines the notifications generated by
the NEMO entity in response to the operationally interesting state the NEMO entity in response to the operationally interesting state
chanages in the NEMO protocol. chanages in the NEMO protocol.
skipping to change at page 6, line 31 skipping to change at page 6, line 26
Support Group E-mail: nemo@ietf.org" Support Group E-mail: nemo@ietf.org"
DESCRIPTION DESCRIPTION
"The MIB module for monitoring a NEMO entity. "The MIB module for monitoring a NEMO entity.
Copyright (C) The Internet Society 2004. This Copyright (C) The Internet Society 2004. This
version of this MIB module is part of RFC XXXX; version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices. see the RFC itself for full legal notices.
" "
-- RFC Ed.: replace XXXX with actual RFC number & remove this note -- RFC Ed.: replace XXXX with actual RFC number and remove this
-- note
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number & remove this note -- RFC Ed.: replace XXXX with actual RFC number and remove this
-- note
::= { mib-2 XXX } -- will be assigned by IANA ::= { mib-2 XXX } -- will be assigned by IANA
-- IANA Reg.: Please assign a value for "XXX" under the 'mib-2' -- IANA Reg.: Please assign a value for "XXX" under the 'mib-2'
-- subtree and record the assignment in the SMI Numbers registry. -- subtree and record the assignment in the SMI Numbers
-- registry.
--
-- RFC Ed.: When the above assignment has been made, please -- RFC Ed.: When the above assignment has been made, please
-- remove the above note -- remove the above note
-- replace "XXX" here with the assigned value and -- replace "XXX" here with the assigned value and
-- remove this note. -- remove this note.
-- The NEMO MIB has the following 5 primary groups -- The NEMO MIB has the following 5 primary groups
nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 } nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 }
nemoSystem OBJECT IDENTIFIER ::= { nemoMIB 1 } nemoSystem OBJECT IDENTIFIER ::= { nemoMIB 1 }
nemoConfiguration OBJECT IDENTIFIER ::= { nemoMIB 2 } nemoConfiguration OBJECT IDENTIFIER ::= { nemoMIB 2 }
nemoStats OBJECT IDENTIFIER ::= { nemoMIB 3 } nemoStats OBJECT IDENTIFIER ::= { nemoMIB 3 }
nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 4 } nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 4 }
-- The nemoConfiguration group has the following sub groups -- The nemoConfiguration group has the following sub groups
nemoRegistration OBJECT IDENTIFIER ::= { nemoConfiguration 1 } nemoRegistration OBJECT IDENTIFIER ::= { nemoConfiguration 1 }
-- The nemoStats group has the following sub groups -- The nemoStats group has the following sub groups
nemoHomeAgentDiscovery OBJECT IDENTIFIER ::= { nemoStats 1 } nemoHomeAgentDiscovery OBJECT IDENTIFIER ::= { nemoStats 1 }
nemoTotalTraffic OBJECT IDENTIFIER ::= { nemoStats 2 } nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 2 }
nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 3 } nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 3 }
nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 4 }
-- Textual Conventions -- Textual Conventions
NemoStatus ::= TEXTUAL-CONVENTION NemoStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the state of the NEMO entity. "This object represents the state of the NEMO
The entity could be at home, isolated, roaming or in entity. The entity could be at home, isolated,
unknown state. roaming or in unknown state.
" "
SYNTAX INTEGER { SYNTAX INTEGER {
isolated (1), isolated (1),
roaming (2), roaming (2),
home (3), home (3),
unknown (4) unknown (4)
} }
-- NemoPrefixRegMode ::= TEXTUAL-CONVENTION
-- STATUS current
-- DESCRIPTION
-- "This object represents the state of the NEMO entity.
-- The entity could be at home, isolated, roaming or in
-- unknown state.
-- "
-- SYNTAX INTEGER {
-- implicitmode (1),
-- explicitmode (2)
-- }
-- --
-- --
-- nemoSystem group -- nemoSystem group
-- --
-- --
nemoRoamingStatus OBJECT-TYPE nemoRoamingStatus OBJECT-TYPE
SYNTAX NemoStatus SYNTAX NemoStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the current status of the mobile router. "Indicates the current status of the mobile router.
The status indicates if the mobile router is at home, The status indicates if the mobile router is at
roaming isolated or in an unknown state. home, roaming, isolated or in an unknown state.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 1 } ::= { nemoSystem 1 }
nemoRegisteredUpTime OBJECT-TYPE nemoRegisteredUpTime 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 time (in seconds) for which the mobile router "The time (in seconds) for which the mobile router
has been up and registered with its home agent. has been up and registered with its home agent.
" "
REFERENCE
"RFC3963 : Section 6.4"
::= { nemoSystem 2 } ::= { nemoSystem 2 }
nemoLastAcceptedRegTime OBJECT-TYPE nemoLastAcceptedRegTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp when the last registration was accepted "The timestamp when the last registration was
by the home agent. accepted by the home agent.
" "
REFERENCE
"RFC3963 : Section 6.6"
::= { nemoSystem 3 } ::= { nemoSystem 3 }
nemoLastRejectedRegTime OBJECT-TYPE nemoLastRejectedRegTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp when the last registration was rejected "The timestamp when the last registration was
by the home agent. rejected by the home agent.
" "
REFERENCE
"RFC3963 : Section 6.6"
::= { nemoSystem 4 } ::= { nemoSystem 4 }
nemoTimeSinceLastRoamed OBJECT-TYPE nemoTimeSinceLastRoamed 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 time elapsed (in seconds) since the last time the "The time elapsed (in seconds) since the last time
mobile router roamed. the mobile router roamed.
" "
REFERENCE
"RFC3963 : Section 6.6"
::= { nemoSystem 5 } ::= { nemoSystem 5 }
nemoRegHomeAgentAddressType OBJECT-TYPE nemoRegHomeAgentAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type of the nemoRegHomeAgentAddress that "The address type of the nemoRegHomeAgentAddress
follows. that follows.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 6 } ::= { nemoSystem 6 }
nemoRegHomeAgentAddress OBJECT-TYPE nemoRegHomeAgentAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The home agent address of the mobile router which "The home agent address of the mobile router which
was used in the last accepted registration. was used in the last accepted registration.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 7 } ::= { nemoSystem 7 }
nemoRegHomeAddressType OBJECT-TYPE nemoRegHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type of the nemoRegHomeAddress that "The address type of the nemoRegHomeAddress that
follows. follows.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 8 } ::= { nemoSystem 8 }
nemoRegHomeAddress OBJECT-TYPE nemoRegHomeAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The home address of the mobile router which is used "The home address of the mobile router which is
in the last accepted registration. used in the last accepted registration.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 9 } ::= { nemoSystem 9 }
nemoRegHomeAddressPrefixLength OBJECT-TYPE nemoRegHomeAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length of the home address that the "The prefix length of the home address that the
mobile router is using for roaming. mobile router is using for roaming.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 10 } ::= { nemoSystem 10 }
nemoRegCareofAddressType OBJECT-TYPE nemoRegCareofAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type of the nemoRegCareofAddress that "The address type of the nemoRegCareofAddress that
follows. follows.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 11 } ::= { nemoSystem 11 }
nemoRegCareofAddress OBJECT-TYPE nemoRegCareofAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The care-of address of the mobile router which is "The care-of address of the mobile router which is
used in the last accepted registration. used in the last accepted registration.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 12 } ::= { nemoSystem 12 }
nemoRegCareofAddressPrefixLength OBJECT-TYPE nemoRegCareofAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length of the care-of Address that the "The prefix length of the care-of Address that the
mobile router currently is using for roaming. mobile router currently is using for roaming.
" "
REFERENCE
"RFC3963 : Section 3"
::= { nemoSystem 13 } ::= { nemoSystem 13 }
nemoActiveRoamingIfIndex OBJECT-TYPE nemoActiveRoamingIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface index of the current active "The interface index of the current active
roaming interface. roaming interface.
" "
REFERENCE
"RFC3963 : Section 5.5"
::= { nemoSystem 14 } ::= { nemoSystem 14 }
nemoEstablishedHomeTunnelIfIndex OBJECT-TYPE nemoEstablishedHomeTunnelIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface index of the tunnel established "The interface index of the tunnel established
between the mobile router and the home agent between the mobile router and the home agent
for NEMO traffic. for NEMO traffic.
" "
REFERENCE
"RFC3963 : Section 5.5"
::= { nemoSystem 15 } ::= { nemoSystem 15 }
-- --
-- --
-- nemoConfiguration group -- nemoConfiguration group
-- --
-- --
-- --
-- nemoRegistration sub group -- nemoRegistration sub group
-- --
nemoHomeRegLifeTime OBJECT-TYPE nemoHomeRegLifeTime OBJECT-TYPE
SYNTAX Gauge32 (4..262143) SYNTAX Gauge32 (4..262143)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lifetime requested by the mobile router (in "The lifetime requested by the mobile router (in
seconds) in the Binding registration. It is between seconds) in the Binding registration. It is
4 and 262143 secs. between 4 and 262143 secs.
" "
::= { nemoRegistration 1 } ::= { nemoRegistration 1 }
nemoHomeRegRetryCount OBJECT-TYPE nemoHomeRegRetryCount OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of registration attempts "The maximum number of registration attempts
allowed for the mobile router. allowed for the mobile router.
skipping to change at page 13, line 34 skipping to change at page 14, line 4
eui64 (0), eui64 (0),
random (1) random (1)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the nemoHomeAddressIdentifier "The type of the nemoHomeAddressIdentifier
that follows. that follows.
" "
::= { nemoRegistration 6 } ::= { nemoRegistration 6 }
nemoHomeAddressIdentifierInetType OBJECT-TYPE nemoHomeAddressIdentifierInetType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the nemoHomeAddressIdentifier "The InetAddressType of the
that follows. nemoHomeAddressIdentifier that follows.
" "
::= { nemoRegistration 7 } ::= { nemoRegistration 7 }
nemoHomeAddressIdentifier OBJECT-TYPE nemoHomeAddressIdentifier OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast routable address assigned to the mobile "The unicast routable address assigned to the
router. This is used as the permanent address of mobile router. This is used as the permanent
the mobile router in the sense that it remains address of the mobile router in the sense that it
unchanged regardless of the mobile router's current remains unchanged regardless of the mobile
point ofattachment. router's current point ofattachment.
The type of the address represented by this object The type of the address represented by this object
is specified by the corresponding nemoHomeAddressType is specified by the corresponding
object. nemoHomeAddressType object.
" "
::= { nemoRegistration 8 } ::= { nemoRegistration 8 }
nemoHomeIfIndex OBJECT-TYPE nemoHomeIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface index of the mobile router where the "The interface index of the mobile router where the
home address is configured. home address is configured.
" "
::= { nemoRegistration 9 } ::= { nemoRegistration 9 }
nemoPrefixRegMode OBJECT-TYPE nemoPrefixRegMode OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
implicitMode (0), implicitMode (0),
skipping to change at page 15, line 19 skipping to change at page 15, line 33
"A table representing the potential home networks "A table representing the potential home networks
that the mobile router can use that the mobile router can use
" "
::= { nemoRegistration 12 } ::= { nemoRegistration 12 }
nemoHomeNetworkPrefixEntry OBJECT-TYPE nemoHomeNetworkPrefixEntry OBJECT-TYPE
SYNTAX NemoHomeNetworkPrefixEntry SYNTAX NemoHomeNetworkPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the binding cache table. It represents a "An entry in the binding cache table. It represents
single home network entry a single home network entry
Implementors need to be aware that if the total Implementors need to be aware that if the total
number of octets in nemoHomeNetworkPrefix number of octets in nemoHomeNetworkPrefix
exceeds 113 then OIDs of column exceeds 113 then OIDs of column
instances in this row will have more than 128 instances in this row will have more than 128
sub-identifiers and cannot be accessed using sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3. SNMPv1, SNMPv2c, or SNMPv3.
" "
INDEX { nemoHomeNetworkPrefixType, nemoHomeNetworkPrefix, INDEX { nemoHomeNetworkPrefixType, nemoHomeNetworkPrefix,
nemoHomeNetworkPrefixLength } nemoHomeNetworkPrefixLength }
skipping to change at page 16, line 32 skipping to change at page 16, line 46
is configured for the mobile router. is configured for the mobile router.
" "
::= { nemoHomeNetworkPrefixEntry 3 } ::= { nemoHomeNetworkPrefixEntry 3 }
nemoHomeNetworkPrefixLifeTime OBJECT-TYPE nemoHomeNetworkPrefixLifeTime OBJECT-TYPE
SYNTAX Gauge32 (4..262143) SYNTAX Gauge32 (4..262143)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lifetime requested by the mobile router (in "The lifetime requested by the mobile router (in
seconds) in the Binding registration. It is between seconds) in the Binding registration. It is
4 and 262143 secs. between 4 and 262143 secs.
" "
::= { nemoHomeNetworkPrefixEntry 4 } ::= { nemoHomeNetworkPrefixEntry 4 }
-- --
-- nemoPrefixTable -- nemoPrefixTable
-- --
nemoPrefixTable OBJECT-TYPE nemoPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoPrefixEntry SYNTAX SEQUENCE OF NemoPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 17, line 13 skipping to change at page 17, line 26
DESCRIPTION DESCRIPTION
"A table representing the NEMO prefixes. "A table representing the NEMO prefixes.
" "
::= { nemoConfiguration 2 } ::= { nemoConfiguration 2 }
nemoPrefixEntry OBJECT-TYPE nemoPrefixEntry OBJECT-TYPE
SYNTAX NemoPrefixEntry SYNTAX NemoPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the binding cache table. It represents a "An entry in the binding cache table. It represents
single Binding Update. a single Binding Update.
Implementors need to be aware that if the total Implementors need to be aware that if the total
number of octets in nemoPrefix number of octets in nemoPrefix
exceeds 114 then OIDs of column exceeds 114 then OIDs of column
instances in this row will have more than 128 instances in this row will have more than 128
sub-identifiers and cannot be accessed using sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3. SNMPv1, SNMPv2c, or SNMPv3.
" "
INDEX { nemoPrefixType, nemoPrefix, nemoPrefixLength } INDEX { nemoPrefixType, nemoPrefix, nemoPrefixLength }
::= { nemoPrefixTable 1 } ::= { nemoPrefixTable 1 }
skipping to change at page 18, line 6 skipping to change at page 18, line 20
that follows. that follows.
" "
::= { nemoPrefixEntry 1 } ::= { nemoPrefixEntry 1 }
nemoPrefix OBJECT-TYPE nemoPrefix OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mobile network prefix that is delegated to the "The mobile network prefix that is delegated to the
mobile router and advertised in the mobile network. mobile router and advertised in the mobile
The type of the address represented by this object network. The type of the address represented by
is specified by the corresponding this object is specified by the corresponding
nemoPrefixType object. nemoPrefixType object.
" "
::= { nemoPrefixEntry 2 } ::= { nemoPrefixEntry 2 }
nemoPrefixLength OBJECT-TYPE nemoPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length of the mobile network prefix. "The prefix length of the mobile network prefix.
skipping to change at page 18, line 43 skipping to change at page 19, line 13
-- --
-- nemoRoamingIfTable -- nemoRoamingIfTable
-- --
nemoRoamingIfTable OBJECT-TYPE nemoRoamingIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoRoamingIfEntry SYNTAX SEQUENCE OF NemoRoamingIfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table representing the roaming interfaces. "A table representing the roaming interfaces.
Each entry represents a configured roaming interface Each entry represents a configured roaming
with the roaming characterstics. interface with the roaming characterstics.
" "
::= { nemoConfiguration 3 } ::= { nemoConfiguration 3 }
nemoRoamingIfEntry OBJECT-TYPE nemoRoamingIfEntry OBJECT-TYPE
SYNTAX NemoRoamingIfEntry SYNTAX NemoRoamingIfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the roaming interface table. It "An entry in the roaming interface table. It
represents a single roaming interface entry. represents a single roaming interface entry.
" "
INDEX { nemoRoamingIfIndex, nemoRoamingIfPriority } INDEX { nemoRoamingIfIndex, nemoRoamingIfPriority }
::= { nemoRoamingIfTable 1 } ::= { nemoRoamingIfTable 1 }
skipping to change at page 20, line 5 skipping to change at page 20, line 20
This value will be configured between 0 and 255. This value will be configured between 0 and 255.
" "
::= { nemoRoamingIfEntry 2 } ::= { nemoRoamingIfEntry 2 }
nemoRoamingIfDescription OBJECT-TYPE nemoRoamingIfDescription OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the interface that will be used "The description of the interface that will be used
for roaming to foreign networks in the mobile router. for roaming to foreign networks in the mobile
router.
" "
::= { nemoRoamingIfEntry 3 } ::= { nemoRoamingIfEntry 3 }
nemoRoamingIfRoamHoldDownTime OBJECT-TYPE nemoRoamingIfRoamHoldDownTime OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the time for which hold on to "This object indicates the time for which hold on
the interface. to the interface. This value is configured to
This value is configured to avoid interface flapping. avoid interface flapping.
" "
::= { nemoRoamingIfEntry 4 } ::= { nemoRoamingIfEntry 4 }
--- ---
--- ---
--- nemoStats group --- nemoStats group
--- ---
--- ---
-- --
skipping to change at page 20, line 39 skipping to change at page 21, line 11
-- --
nemoDHAADRequests OBJECT-TYPE nemoDHAADRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of dynamic home agent address "The total number of dynamic home agent address
discovery requests sent by the mobile router. discovery requests sent by the mobile router.
" "
REFERENCE
"RFC3963 : Section 7.1."
::= { nemoHomeAgentDiscovery 1 } ::= { nemoHomeAgentDiscovery 1 }
nemoDHAADRepliesWNemoSupport OBJECT-TYPE nemoDHAADRepliesWNemoSupport OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of dynamic home agent address "The total number of dynamic home agent address
discovery replies sent by the home agent with NEMO discovery replies sent by the home agent with NEMO
support. support.
" "
REFERENCE
"RFC3963 : Section 7.2."
::= { nemoHomeAgentDiscovery 2 } ::= { nemoHomeAgentDiscovery 2 }
nemoDHAADRepliesWONemoSupport OBJECT-TYPE nemoDHAADRepliesWONemoSupport OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of dynamic home agent address "The total number of dynamic home agent address
discovery replies sent by the home agent without discovery replies sent by the home agent without
NEMO support. NEMO support.
" "
REFERENCE
"RFC3963 : Section 7.2."
::= { nemoHomeAgentDiscovery 3 } ::= { nemoHomeAgentDiscovery 3 }
nemoDHAADDiscoveryTimeouts OBJECT-TYPE nemoDHAADDiscoveryTimeouts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of dynamic home agent address "The total number of dynamic home agent address
discovery requested by the mobile router and that discovery requested by the mobile router and that
was timeout. was timeout.
" "
::= { nemoHomeAgentDiscovery 4 } ::= { nemoHomeAgentDiscovery 4 }
-- --
-- nemoStats:nemoTotalTraffic
--
nemoInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the IPv6 datagrams
received by the nodes in the NEMO networks.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 1 }
nemoHCInOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the IPv6 datagrams
received by the NEMO networks.
This object is a 64-bit version of nemoInOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 2 }
nemoInPackets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the IPv6 datagrams
received by the nodes in the NEMO networks.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 3 }
nemoHCInPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of IPv6 packets received by
the nodes in the NEMO networks.
This object is a 64-bit version of nemoInOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 4 }
nemoOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the IPv6 datagrams
sent by the nodes in the NEMO networks.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 5 }
nemoHCOutOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the IPv6 datagrams
sent by the NEMO networks.
This object is a 64-bit version of nemoInOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 6 }
nemoOutPackets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the IPv6 datagrams
sent by the nodes in the NEMO networks.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 7 }
nemoHCOutPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of IPv6 packets sent by the nodes
in the NEMO networks.
This object is a 64-bit version of nemoInOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoTotalTraffic 8 }
--
-- nemoStats:nemoBindingRegcounters -- nemoStats:nemoBindingRegcounters
-- --
nemoBindingUpdates OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Updates sent by the
mobile router.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoBindingRegCounters 1 }
nemoBindingAcks OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgements
received by the mobile router.
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router.
"
::= { nemoBindingRegCounters 2 }
nemoBindingAcksWONemoSupport OBJECT-TYPE nemoBindingAcksWONemoSupport OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of Binding Acks without the "The total number of Binding Acks without the
NEMO support received by the mobile router. NEMO support received by the mobile router.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoBindingRegCounters 3 } REFERENCE
"RFC3963 : Section 5.3."
::= { nemoBindingRegCounters 1 }
nemoBindingAckNotHomeRegn OBJECT-TYPE nemoBindingAckNotHomeRegn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of Binding Update requests "The total number of Binding Update requests
rejected by the home agent with the status code rejected by the home agent with the status code
in the Binding Acknowledgment indicating in the Binding Acknowledgment indicating
'Not Home Registration' 'Not Home Registration'
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoBindingRegCounters 4 } REFERENCE
"RFC3963 : Section 6.2."
::= { nemoBindingRegCounters 2 }
nemoBindingRegTypeChanged OBJECT-TYPE nemoBindingRegTypeChanged OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Discontinuities in the value of this counter can "The total number of Binding Update requests
rejected by the home agent with status code
in the Binding Acknowledgement indicating
'Registration type change disallowed' (Code 139).
Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoBindingRegCounters 5 } REFERENCE
"RFC3963 : Section 6.2"
::= { nemoBindingRegCounters 3 }
nemoOpNotSupported OBJECT-TYPE nemoOpNotSupported OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of Binding Update requests rejected "The total number of Binding Update requests
by the home agent with status code in the rejected by the home agent with status code in the
Binding Acknowledgement indicating Binding Acknowledgement indicating
'Mobile Router Operation not permitted' (Code 140). 'Mobile Router Operation not permitted'
(Code 140).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoBindingRegCounters 6 } REFERENCE
"RFC3963 : Section 6.6"
::= { nemoBindingRegCounters 4 }
nemoInvalidPrefix OBJECT-TYPE nemoInvalidPrefix OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of Binding Update requests rejected "The total number of Binding Update requests
by the home agent with status code in the Binding rejected by the home agent with status code in the
Acknowledgement indicating 'Invalid Prefix' Binding Acknowledgement indicating 'Invalid
(Code 141). Prefix' (Code 141).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoBindingRegCounters 7 } REFERENCE
"RFC3963 : Section 6.6."
::= { nemoBindingRegCounters 5 }
nemoNotAuthorizedForPrefix OBJECT-TYPE nemoNotAuthorizedForPrefix OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of Binding Update requests rejected "The total number of Binding Update requests
by the home agent with status code in the Binding rejected by the home agent with status code in the
Acknowledgement indicating 'Not Authorized for Binding Acknowledgement indicating 'Not Authorized
Prefix' (Code 142). for Prefix' (Code 142).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoBindingRegCounters 8 } REFERENCE
"RFC3963 : Section 6.6."
::= { nemoBindingRegCounters 6 }
nemoForwardingSetupFailed OBJECT-TYPE nemoForwardingSetupFailed OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of Binding Update requests rejected "The total number of Binding Update requests
by the home agent with status code in the Binding rejected by the home agent with status code in the
Acknowledgement indicating 'Forwarding Setup failed' Binding Acknowledgement indicating 'Forwarding
(Code 143). Setup failed' (Code 143).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoBindingRegCounters 9 } REFERENCE
"RFC3963 : Section 6.6."
::= { nemoBindingRegCounters 7 }
-- --
-- nemoStats:nemoRoamingCounters -- nemoStats:nemoRoamingCounters
-- --
nemoMovedHome OBJECT-TYPE nemoMovedHome OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of times the mobile router has detected "Number of times the mobile router has detected
skipping to change at page 29, line 5 skipping to change at page 26, line 35
nemoHomeTunnelEstablished NOTIFICATION-TYPE nemoHomeTunnelEstablished NOTIFICATION-TYPE
OBJECTS { OBJECTS {
nemoActiveRoamingIfIndex, nemoActiveRoamingIfIndex,
nemoEstablishedHomeTunnelIfIndex, nemoEstablishedHomeTunnelIfIndex,
nemoRegCareofAddressType, nemoRegCareofAddressType,
nemoRegCareofAddress nemoRegCareofAddress
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by the mobile router every "This notification is sent by the mobile router
time the tunnel is established between the home agent every time the tunnel is established between the
and the mobile router. home agent and the mobile router.
" "
REFERENCE
"RFC3963 : Section 5.5"
::= { nemoNotifications 1 } ::= { nemoNotifications 1 }
nemoHomeTunnelReleased NOTIFICATION-TYPE nemoHomeTunnelReleased NOTIFICATION-TYPE
OBJECTS { OBJECTS {
nemoActiveRoamingIfIndex, nemoActiveRoamingIfIndex,
nemoEstablishedHomeTunnelIfIndex, nemoEstablishedHomeTunnelIfIndex,
nemoRegCareofAddressType, nemoRegCareofAddressType,
nemoRegCareofAddress nemoRegCareofAddress
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by the mobile router every "This notification is sent by the mobile router
time the tunnel is deleted between the home agent and every time the tunnel is deleted between the home
the mobile router. agent and the mobile router.
" "
REFERENCE
"RFC3963 : Section 5.5"
::= { nemoNotifications 2} ::= { nemoNotifications 2}
-- Conformance information -- Conformance information
nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 } nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 }
nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 } nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 }
-- Units of conformance -- Units of conformance
nemoSystemGroup OBJECT-GROUP nemoSystemGroup OBJECT-GROUP
OBJECTS { OBJECTS {
nemoRoamingStatus, nemoRoamingStatus,
skipping to change at page 30, line 46 skipping to change at page 28, line 38
nemoDHAADDiscoveryTimeouts nemoDHAADDiscoveryTimeouts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A collection of objects for basic NEMO " A collection of objects for basic NEMO
configuration monitoring." configuration monitoring."
::= { nemoGroups 2 } ::= { nemoGroups 2 }
nemoStatsGroup OBJECT-GROUP nemoStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
nemoInOctets,
nemoHCInOctets,
nemoInPackets,
nemoHCInPackets,
nemoOutOctets,
nemoHCOutOctets,
nemoOutPackets,
nemoHCOutPackets,
nemoBindingUpdates, nemoBindingUpdates,
nemoBindingAcks, nemoBindingAcks,
nemoBindingAcksWONemoSupport, nemoBindingAcksWONemoSupport,
nemoBindingAckNotHomeRegn, nemoBindingAckNotHomeRegn,
nemoBindingRegTypeChanged, nemoBindingRegTypeChanged,
nemoOpNotSupported, nemoOpNotSupported,
nemoInvalidPrefix, nemoInvalidPrefix,
nemoNotAuthorizedForPrefix, nemoNotAuthorizedForPrefix,
nemoForwardingSetupFailed, nemoForwardingSetupFailed,
nemoMovedHome, nemoMovedHome,
skipping to change at page 32, line 4 skipping to change at page 29, line 32
" "
::= { nemoGroups 4 } ::= { nemoGroups 4 }
-- Compliance statements -- Compliance statements
nemoCoreCompliance MODULE-COMPLIANCE nemoCoreCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities "The compliance statement for SNMP entities
which implement the MOBILEIPV6-MIB. which implement the MOBILEIPV6-MIB.
There are a number of INDEX objects that cannot be There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, represented in the form of OBJECT clauses in
but for which there are compliance requirements, SMIv2, but for which there are compliance
expressed in OBJECT clause form in this description: requirements, expressed in OBJECT clause form in
this
description:
-- OBJECT nemoBindingHomeAddressType -- OBJECT nemoBindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) } -- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- ipv6 addresses for the nemoBindingHomeAddress -- ipv6 addresses for the nemoBindingHomeAddress
-- object. -- object.
-- --
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { nemoSystemGroup, MANDATORY-GROUPS { nemoSystemGroup,
nemoConfigurationGroup, nemoConfigurationGroup,
nemoStatsGroup, nemoStatsGroup,
nemoNotificationGroup nemoNotificationGroup
} }
::= { nemoCompliances 1 } ::= { nemoCompliances 1 }
END END
5. Security Considerations 5. IANA Considerations
IANA should assign a base arc in the mib-2 (standards track) OID tree
for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB.
6. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write. Such objects may be with a MAX-ACCESS clause of read-write. Such objects may be
considered sensitive or vulnerable in some network environments. The considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. These protection can have a negative effect on network operations. These
are the tables and objects and their sensitivity/vulnerability: are the tables and objects and their sensitivity/vulnerability:
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
skipping to change at page 33, line 41 skipping to change at page 31, line 14
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations
IANA should assign a base arc in the mib-2 (standards track) OID tree
for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB.
7. Acknowledgments 7. Acknowledgments
The authors would like to thank T.J Kniveton and Thierry Ernst for The authors would like to thank T.J Kniveton and Thierry Ernst for
their inputs to the document and also would like to thank Kent Leung their inputs to the document and also would like to thank Kent Leung
and Pascal Thubert for their discussions Mobile Router and Pascal Thubert for their inputs on Mobile Router implementations.
implementations.
8. References 8. References
8.1 Normative References 8.1. Normative References
[RFC2119] Bradner, S., Key words for use in RFCs to Indicate [RFC2119] Bradner, S., Key words for use in RFCs to Indicate
Requirements Levels, BCP 14, RFC 2119, March 1997. Requirements Levels, BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, Structure of Management Rose, M. and S. Waldbusser, Structure of Management Information
Information Version 2 (SMIv2), STD 58, RFC 2578, Version 2 (SMIv2), STD 58, RFC 2578, April 1999.
April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, Textual Conventions for Rose, M. and S. Waldbusser, Textual Conventions for SMIv2, STD 58,
SMIv2, STD 58, RFC 2579, April 1999. RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, Conformance Statements Rose, M. and S. Waldbusser, Conformance Statements for SMIv2, STD 58,
for SMIv2, STD 58, RFC 2580, April 1999. RFC 2580, April 1999.
[RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in
Support in IPv6q RFC 3775, June 2004. IPv6q RFC 3775, June 2004.
[RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. [RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli,
Devarapalli, Network Mobility (NEMO) Basic Support Network Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan 2005.
Protocol, RFC 3963, Jan 2005.
[RFC4001] Daniele, M., Haberman, B., Routhier, S. and Schoenwaelder, [RFC4001] Daniele, M., Haberman, B., Routhier, S. and Schoenwaelder,
J., Textual Conventions for Internet Network J., Textual Conventions for Internet Network Addresses, RFC 4001,
Addresses, RFC 4001, February 2005. February 2005.
[RFC2011bis] Routhier, S., Management Information Base for the [RFC2011bis] Routhier, S., Management Information Base for the
Internet Protocol (IP), work in progress (currently Internet Protocol (IP), work in progress (currently
<draft-ietf-ipv6-rfc2011-update-10.txt>). draft-ietf-ipv6-rfc2011-update-10.txt).
[MIPv6MIB] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, [RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The
The Mobile IPv6 MIB, work in progress (currently Mobile IPv6 MIB, RFC 4295, April 2006.
<draft-ietf-mip6-mipv6-mib-07.txt>).
8.2. Informative References
8.2 Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
Introduction and Applicability Statements for Introduction and Applicability Statements for Internet-Standard
Internet-Standard Management Framework, RFC 3410, Management Framework, RFC 3410, December 2002.
December 2002.
[NEMOTERM] T. Ernst and H.-Y. Lach., Network Mobility Support [NEMOTERM] T. Ernst and H.-Y. Lach., Network Mobility Support
Terminology, work in progress (currently Terminology, work in progress (currently
<draft-ietf-nemo-terminology-01.txt>). draft-ietf-nemo-terminology-01.txt).
[NEMOGOAL] T. Ernst. Network Mobility Support Goals and [NEMOGOAL] T. Ernst. Network Mobility Support Goals and
Requirements, work in progress (currently Requirements, work in progress (currently
<draft-ietf-nemo-requirements-02.txt>). draft-ietf-nemo-requirements-02.txt).
9. Authors' Addresses Authors' Addresses
Sri Gundavelli Sri Gundavelli
Cisco Systems Cisco Systems
170 W.Tasman Drive, 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Phone: +1-408-527-6109 Phone: +1-408-527-6109
Email: sgundave@cisco.com Email: sgundave@cisco.com
Glenn Mansfield Keeni Glenn Mansfield Keeni
Cyber Solutions Inc. Cyber Solutions
6-6-3 Minami Yoshinari 6-6-3 Minami Yoshinari
Aoba-ku, Sendai 989-3204 Aoba-ku, Sendai 989-3204,
Japan Japan
Phone: +81-22-303-4012 Phone: +81-22-303-4012
EMail: glenn@cysols.com Email: glenn@cysols.com
Kenichi Nagami
INTEC NetCore Inc.
1-3-3, Shin-suna
Koto-ku, Tokyo, 135-0075
Japan
Phone: +81-3-5665-5069
E-mail: nagami@inetcore.com
Kazuhide Koide Kazuhide Koide
Tohoku University Tohoku University
Katahira Campus Katahira Campus
Sendai Sendai,
Japan Japan
Phone: +81-22-217-5454 Phone: +81-22-217-5454
E-mail: koide@shiratori.riec.tohoku.ac.jp Email: koide@shiratori.riec.tohoku.ac.jp
10. Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Kenichi Nagami
to the rights, licenses and restrictions contained in BCP 78, and INTEC NetCore
except as set forth therein, the authors retain all their rights. 1-3-3, Shin-suna
Koto-ku, Tokyo, 135-0075,
Japan
This document and the information contained herein are provided on an Phone: +81-3-5665-5069
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE Email: nagami@inetcore.com
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.
Intellectual Property Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed to
to pertain to the implementation or use of the technology pertain to the implementation or use of the technology described in
described in this document or the extent to which any license this document or the extent to which any license under such rights
under such rights might or might not be available; nor does it might or might not be available; nor does it represent that it has
represent that it has made any independent effort to identify any made any independent effort to identify any such rights. Information
such rights. Information on the procedures with respect to on the procedures with respect to rights in RFC documents can be
rights in RFC documents can be found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use of
of such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository specification can be obtained from the IETF on-line IPR repository at
at http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention The IETF invites any interested party to bring to its attention any
any copyrights, patents or patent applications, or other copyrights, patents or patent applications, or other proprietary
proprietary rights that may cover technology that may be required rights that may cover technology that may be required to implement
to implement this standard. Please address the information to the this standard. Please address the information to the IETF at
IETF at ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement 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 Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 109 change blocks. 
354 lines changed or deleted 268 lines changed or added

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