draft-ietf-nemo-mib-00.txt   draft-ietf-nemo-mib-01.txt 
NEMO Working Group Sri Gundavelli
Nemo Working Group Sri Gundavelli
INTERNET-DRAFT Cisco Systems INTERNET-DRAFT Cisco Systems
Expires: April 15, 2005 Glenn M. Keeni Expires: January 15, 2006 Glenn M. Keeni
Cyber Solutions Cyber Solutions
Kazuhide Koide Kazuhide Koide
Tohoku University Tohoku University
Kenichi Nagami Kenichi Nagami
INTEC NetCore INTEC NetCore
October 16, 2004 July 16, 2005
NEMO Management Information Base NEMO Management Information Base
<draft-ietf-nemo-mib-00.txt> <draft-ietf-nemo-mib-01.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, we certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which we are aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
or will be disclosed, and any of which we become aware will be have been or will be disclosed, and any of which he or she becomes
disclosed, in accordance with RFC 3668. 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 other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months 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 a "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/1id-abstracts.html 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 mip6 Working Group. Comments should This document is a product of the nemo Working Group. Comments should
be addressed to the authors or the mailing list at mip6@ietf.org be addressed to the authors or the mailing list at nemo@ietf.org
This Internet-Draft will expire on April 15, 2005. This Internet-Draft will expire on January 15, 2006
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
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 management the network mobility support (NEMO) MIB, for use with network
protocols in the Internet community. In particular, the NEMO MIB will be management protocols in the Internet community. In particular, the
used to monitor and control a mobile IPv6 node with NEMO Basic Support NEMO MIB will be used to monitor and control a mobile ipv6 node with
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 3. MIB Design .................................................... 4
4. The NEMO MIB .................................................. 5 4. The NEMO MIB .................................................. 5
5. Security Considerations .......................................29 5. Security Considerations .......................................32
6. IANA Considerations ...........................................29 6. IANA Considerations ...........................................32
7. Acknowledgments ...............................................29 7. Acknowledgments ...............................................33
8. References ....................................................30 8. References ....................................................34
9. Authors' Addresses ............................................32 9. Authors' Addresses ............................................36
10. Full Copyright Statement ......................................33 10. Full Copyright Statement ......................................37
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).
skipping to change at page 3, line 27 skipping to change at page 3, line 27
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. Network
Mobility Basic Support (NEMO) [NEMOBASIC] is an extension to the Mobility Basic Support (NEMO) [RFC3963] is an extension to the Mobile
Mobile IPv6 protocol which facilitates the movement of an entire IPv6 protocol which facilitates the movement of an entire network.
network. The goals of Network Mobility support and related The goals of Network Mobility support and related terminology are
terminology are discussed in [NEMOGOAL] and [NEMOTERM], respectively. 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 entities that support NEMO function. 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 "OPTIONAL" in this document are to be interpreted as described in BCP
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 - nemoSystem
- nemoConfiguration - nemoConfiguration
- nemoStats - nemoStats
- nemoNotifications - nemoNotifications
- nemoConformance - nemoConformance
skipping to change at page 5, line 24 skipping to change at page 5, line 24
TruthValue, DateAndTime TruthValue, DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InetAddressType, InetAddress, InetAddressPrefixLength InetAddressType, InetAddress, InetAddressPrefixLength
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
InterfaceIndex InterfaceIndex
FROM IF-MIB FROM IF-MIB
-- mip6Mn mip6Mn
-- FROM MOBILEIPV6-MIB FROM MOBILEIPV6-MIB
; ;
nemoMIB MODULE-IDENTITY nemoMIB MODULE-IDENTITY
LAST-UPDATED "200410070000Z" -- 7th October, 2004 LAST-UPDATED "200507160000Z" -- 16th July, 2005
ORGANIZATION "IETF NEMO Working Group" ORGANIZATION "IETF NEMO Working Group"
CONTACT-INFO CONTACT-INFO
" Sri Gundavelli " Sri Gundavelli
Postal: Cisco Systems Postal: Cisco Systems
170 W.Tasman Drive, 170 W.Tasman Drive,
San Jose, CA 95134 San Jose, CA 95134
USA USA
Tel: +1-408-527-6109 Tel: +1-408-527-6109
Email: sgundave@cisco.com Email: sgundave@cisco.com
Glenn Mansfield Keeni Glenn Mansfield Keeni
Postal: Cyber Solutions Inc. Postal: Cyber Solutions Inc.
6-6-3, Minami Yoshinari 6-6-3, Minami Yoshinari
Aoba-ku, Sendai, Japan 989-3204. Aoba-ku, Sendai, Japan 989-3204.
Tel: +81-22-303-4012 Tel: +81-22-303-4012
Fax: +81-22-303-4015 Fax: +81-22-303-4015
E-mail: glenn@cysols.com E-mail: glenn@cysols.com
skipping to change at page 6, line 4 skipping to change at page 6, line 5
Tel: +1-408-527-6109 Tel: +1-408-527-6109
Email: sgundave@cisco.com Email: sgundave@cisco.com
Glenn Mansfield Keeni Glenn Mansfield Keeni
Postal: Cyber Solutions Inc. Postal: Cyber Solutions Inc.
6-6-3, Minami Yoshinari 6-6-3, Minami Yoshinari
Aoba-ku, Sendai, Japan 989-3204. Aoba-ku, Sendai, Japan 989-3204.
Tel: +81-22-303-4012 Tel: +81-22-303-4012
Fax: +81-22-303-4015 Fax: +81-22-303-4015
E-mail: glenn@cysols.com E-mail: glenn@cysols.com
Kenichi Nagami Kenichi Nagami
Postal: INTEC NetCore Inc. Postal: INTEC NetCore Inc.
1-3-3, Shin-suna 1-3-3, Shin-suna
Koto-ku, Tokyo, 135-0075 Koto-ku, Tokyo, 135-0075
Japan Japan
Tel: +81-3-5665-5069 Tel: +81-3-5665-5069
E-mail: nagami@inetcore.com E-mail: nagami@inetcore.com
Kazuhide Koide Kazuhide Koide
Postal: Tohoku University Postal: Tohoku University
Katahira Campus Katahira Campus
Sendai Sendai
Japan Japan
Tel: +81-22-217-5454 Tel: +81-22-217-5454
E-mail: koide@shiratori.riec.tohoku.ac.jp E-mail: koide@shiratori.riec.tohoku.ac.jp
Support Group E-mail: nemo@ietf.org" Support Group E-mail: nemo@ietf.org"
DESCRIPTION DESCRIPTION
"The MIB module for monitoring 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 & remove this note
REVISION "200410160000Z" -- 16th October 2004 REVISION "200507160000Z" -- 16th July 2005
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 & 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 'mip6Mn' -- 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 }
--nemoNetworksTable OBJECT IDENTIFIER ::= { nemoConfiguration 2 }
--nemoRoamingIfTable OBJECT IDENTIFIER ::= { nemoConfiguration 3 }
-- 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 } nemoTotalTraffic OBJECT IDENTIFIER ::= { nemoStats 2 }
nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 3 } nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 3 }
nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 4 } 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. The "This object represents the state of the NEMO entity.
entity could be at home, isolated, roaming or in unknown The entity could be at home, isolated, roaming or in
state. 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 NEMO entity. The "Indicates the current status of the mobile router.
status indicates if the NEMO entity is at home, roaming The status indicates if the mobile router is at home,
isolated or in unknown state. roaming isolated or in an unknown state.
" "
::= { 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 NEMO entity "The time (in seconds) for which the mobile router
up and registered with its home agent. has been up and registered with its home agent.
" "
::= { 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 accepted
with its home agent. by the home agent.
" "
::= { 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 rejected
with its home agent. by the home agent.
" "
::= { nemoSystem 4 } ::= { nemoSystem 4 }
nemoTimeSinceLastRoamed OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time elapsed (in seconds) since the last time the
mobile router roamed.
"
::= { 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 that
follows. follows.
" "
::= { nemoSystem 5 } ::= { 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 address of the mobile router which is used "The home agent address of the mobile router which
in the last accepted registration. was used in the last accepted registration.
" "
::= { nemoSystem 6 } ::= { nemoSystem 7 }
nemoRegHomeNetworkAddressType 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 nemoRegHomeNetworkAddress that "The address type of the nemoRegHomeAddress that
follows. follows.
" "
::= { nemoSystem 7 } ::= { nemoSystem 8 }
nemoRegHomeNetworkAddress OBJECT-TYPE nemoRegHomeAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix of the home network for which the mobile "The home address of the mobile router which is used
router is registered at last. in the last accepted registration.
" "
::= { nemoSystem 8 } ::= { nemoSystem 9 }
nemoRegHomeNetworkPrefixLength 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 network for which the "The prefix length of the home address that the
mobile router is registered at last. mobile router is using for roaming.
" "
::= { nemoSystem 9 } ::= { nemoSystem 10 }
nemoRegCareofAddressType OBJECT-TYPE nemoRegCareofAddressType OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddressType
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 address type of the nemoRegCareofAddress that
used in the last accepted registration. follows.
" "
::= { nemoSystem 10 } ::= { 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.
" "
::= { nemoSystem 11 } ::= { nemoSystem 12 }
nemoRegCareofAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The prefix length of the care-of Address that the
mobile router currently is using for roaming.
"
::= { 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 ifIndex of the current active roaming "The interface index of the current active
interface. roaming interface.
" "
::= { nemoSystem 12 } ::= { 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 ifIndex of the tunnel interface in the "The interface index of the tunnel established
mobile router which is established between the between the mobile router and the home agent
mobile router and the home agent for NEMO traffic. for NEMO traffic.
" "
::= { nemoSystem 13 } ::= { nemoSystem 15 }
-- --
-- --
-- nemoConfiguration group -- nemoConfiguration group
-- --
-- --
-- --
-- nemoRegistration sub group -- nemoRegistration sub group
-- --
skipping to change at page 11, line 18 skipping to change at page 12, line 24
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 between
4 and 262143 secs. 4 and 262143 secs.
" "
::= { nemoRegistration 1 } ::= { nemoRegistration 1 }
nemoHomeRegRetryCount OBJECT-TYPE nemoHomeRegRetryCount OBJECT-TYPE
SYNTAX Counter32 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.
" "
::= { nemoRegistration 2 } ::= { nemoRegistration 2 }
nemoHomeRegRetryDelay OBJECT-TYPE nemoHomeRegRetryDelay OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
skipping to change at page 11, line 47 skipping to change at page 13, line 11
nemoHomeRegExtendBeforeExpiry OBJECT-TYPE nemoHomeRegExtendBeforeExpiry OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time before the registration extension is "The time before the registration extension is
attempted (in seconds) by the mobile router. attempted (in seconds) by the mobile router.
" "
::= { nemoRegistration 4 } ::= { nemoRegistration 4 }
nemoDynamicHAAddressDiscovery OBJECT-TYPE nemoDynamicHADiscovery OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether or not the mobile "This object indicates whether or not the mobile
router should attempt to make dynamic home agent router should attempt to make dynamic home agent
address discovery(DHAAD). address discovery(DHAAD).
" "
::= { nemoRegistration 5 } ::= { nemoRegistration 5 }
nemoHomeNetworkPrefixType OBJECT-TYPE nemoHomeAddressIdentifierType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX BITS {
eui64 (0),
random (1)
}
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the nemoHomeNetworkPrefix "The type of the nemoHomeAddressIdentifier
that follows. that follows.
" "
::= { nemoRegistration 6 } ::= { nemoRegistration 6 }
nemoHomeNetworkPrefix OBJECT-TYPE nemoHomeAddressIdentifierInetType OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The prefix of the home network which is configured
for the mobile router.
"
::= { nemoRegistration 7 }
nemoHomeNetworkPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The length of the home network prefix which
is configured for the mobile router.
"
::= { nemoRegistration 8 }
nemoHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the nemoHomeAddress "The InetAddressType of the nemoHomeAddressIdentifier
that follows. that follows.
" "
::= { nemoRegistration 9 } ::= { nemoRegistration 7 }
nemoHomeAddress 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 mobile
router. This is used as the 'permanent address' of router. This is used as the permanent address of
the mobile router in the sense that it remains the mobile router in the sense that it remains
unchanged regardless of the mobile router's current unchanged regardless of the mobile router's current
point ofattachment. 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 nemoHomeAddressType
object. object.
" "
::= { nemoRegistration 10 } ::= { nemoRegistration 8 }
nemoHomeIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface index of the mobile router where the
home address is configured.
"
::= { nemoRegistration 9 }
nemoPrefixRegMode OBJECT-TYPE nemoPrefixRegMode OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
implicitMode (0), implicitMode (0),
explicitMode (1) explicitMode (1)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Two modes to instruct the Home Agent to determine "This object indicates if the mobile router will
the prefixes that belong to the mobile router. explicitly register all the prefixes.
" "
::= { nemoRegistration 11 } ::= { nemoRegistration 10 }
nemoRegisterConnectedPrefixes OBJECT-TYPE nemoRegisterConnectedPrefixes OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the mobile router will "This object indicates if the mobile router will
register all connected prefixes or not. register all the connected prefixes.
"
::= { nemoRegistration 11 }
nemoHomeNetworkPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoHomeNetworkPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table representing the potential home networks
that the mobile router can use
" "
::= { nemoRegistration 12 } ::= { nemoRegistration 12 }
nemoHomeNetworkPrefixEntry OBJECT-TYPE
SYNTAX NemoHomeNetworkPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the binding cache table. It represents a
single home network entry
Implementors need to be aware that if the total
number of octets in nemoHomeNetworkPrefix
exceeds 113 then OIDs of column
instances in this row will have more than 128
sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { nemoHomeNetworkPrefixType, nemoHomeNetworkPrefix,
nemoHomeNetworkPrefixLength }
::= { nemoHomeNetworkPrefixTable 1 }
NemoHomeNetworkPrefixEntry ::=
SEQUENCE {
nemoHomeNetworkPrefixType InetAddressType,
nemoHomeNetworkPrefix InetAddress,
nemoHomeNetworkPrefixLength InetAddressPrefixLength,
nemoHomeNetworkPrefixLifeTime Gauge32
}
nemoHomeNetworkPrefixType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the nemoHomeNetworkPrefix
that follows.
"
::= { nemoHomeNetworkPrefixEntry 1 }
nemoHomeNetworkPrefix OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The prefix of the home network which is configured
for the mobile router.
"
::= { nemoHomeNetworkPrefixEntry 2 }
nemoHomeNetworkPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The length of the home network prefix which
is configured for the mobile router.
"
::= { nemoHomeNetworkPrefixEntry 3 }
nemoHomeNetworkPrefixLifeTime OBJECT-TYPE
SYNTAX Gauge32 (4..262143)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The lifetime requested by the mobile router (in
seconds) in the Binding registration. It is between
4 and 262143 secs.
"
::= { 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
STATUS current STATUS current
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 a
single Binding Update. single Binding Update.
Implementors need to be aware that if the total
number of octets in nemoPrefix
exceeds 114 then OIDs of column
instances in this row will have more than 128
sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3.
" "
INDEX { nemoPrefixType, nemoPrefix, nemoPrefixLength } INDEX { nemoPrefixType, nemoPrefix, nemoPrefixLength }
::= { nemoPrefixTable 1 } ::= { nemoPrefixTable 1 }
NemoPrefixEntry ::= NemoPrefixEntry ::=
SEQUENCE { SEQUENCE {
nemoPrefixType InetAddressType, nemoPrefixType InetAddressType,
nemoPrefix InetAddress, nemoPrefix InetAddress,
nemoPrefixLength InetAddressPrefixLength, nemoPrefixLength InetAddressPrefixLength,
nemoPrefixLifeTime Gauge32 nemoPrefixLifeTime Gauge32
skipping to change at page 16, line 4 skipping to change at page 19, line 14
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 }
NemoRoamingIfEntry ::= NemoRoamingIfEntry ::=
SEQUENCE { SEQUENCE {
nemoRoamingIfIndex InterfaceIndex, nemoRoamingIfIndex InterfaceIndex,
nemoRoamingIfDescription SnmpAdminString,
nemoRoamingIfPriority Unsigned32, nemoRoamingIfPriority Unsigned32,
nemoRoamingIfDescription SnmpAdminString,
nemoRoamingIfRoamHoldDownTime Gauge32 nemoRoamingIfRoamHoldDownTime Gauge32
} }
nemoRoamingIfIndex OBJECT-TYPE nemoRoamingIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index of the interface that will be used for "The index of the interface that will be used for
roaming to foreign networks in the mobile router. roaming to foreign networks in the mobile router.
skipping to change at page 22, line 26 skipping to change at page 26, line 23
" "
::= { nemoBindingRegCounters 6 } ::= { nemoBindingRegCounters 6 }
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 rejected
by the home agent with status code in the Binding by the home agent with status code in the Binding
Acknowledgement indicating 'Invalid Prefix' (Code 141). Acknowledgement indicating 'Invalid 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 } ::= { nemoBindingRegCounters 7 }
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 rejected
by the home agent with status code in the Binding by the home agent with status code in the Binding
Acknowledgement indicating 'Not Authorized for Prefix' Acknowledgement indicating 'Not Authorized for
(Code 142). 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 } ::= { nemoBindingRegCounters 8 }
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 rejected
by the home agent with status code in the Binding by the home agent with status code in the Binding
Acknowledgement indicating 'Forwarding Setup failed' Acknowledgement indicating 'Forwarding Setup failed'
(Code 143). (Code 143).
skipping to change at page 23, line 46 skipping to change at page 28, line 4
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
movement from to a foreign network from the home movement from to a foreign network from the home
network, has reconstructed its care-of address and network, has reconstructed its care-of address and
has initiated the care-of address registration has initiated the care-of address registration
process. process.
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.
"
"
::= { nemoRoamingCounters 2 } ::= { nemoRoamingCounters 2 }
nemoMovedFNtoFN OBJECT-TYPE nemoMovedFNtoFN 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
movement from to a foreign network from the home movement from to a foreign network from the home
network, has reconstructed its care-of address and network, has reconstructed its care-of address and
skipping to change at page 24, line 45 skipping to change at page 29, line 5
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 HA every "This notification is sent by the mobile router every
time the NEMO entity establishes a MR-HA time the tunnel is established between the home agent
tunnel. and the mobile router.
" "
::= { 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 HA every "This notification is sent by the mobile router every
time the NEMO entity releases a MR-HA tunnel. time the tunnel is deleted between the home agent and
the mobile router.
" "
::= { 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,
nemoRegisteredUpTime, nemoRegisteredUpTime,
nemoLastAcceptedRegTime, nemoLastAcceptedRegTime,
skipping to change at page 26, line 15 skipping to change at page 29, line 37
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,
nemoRegisteredUpTime, nemoRegisteredUpTime,
nemoLastAcceptedRegTime, nemoLastAcceptedRegTime,
nemoLastRejectedRegTime, nemoLastRejectedRegTime,
nemoTimeSinceLastRoamed,
nemoRegHomeAgentAddressType, nemoRegHomeAgentAddressType,
nemoRegHomeAgentAddress, nemoRegHomeAgentAddress,
nemoRegHomeNetworkAddressType, nemoRegHomeAddressType,
nemoRegHomeNetworkAddress, nemoRegHomeAddress,
nemoRegHomeNetworkPrefixLength, nemoRegHomeAddressPrefixLength,
nemoRegCareofAddressType, nemoRegCareofAddressType,
nemoRegCareofAddress, nemoRegCareofAddress,
nemoRegCareofAddressPrefixLength,
nemoActiveRoamingIfIndex, nemoActiveRoamingIfIndex,
nemoEstablishedHomeTunnelIfIndex nemoEstablishedHomeTunnelIfIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A collection of objects for basic NEMO " A collection of objects for basic NEMO
monitoring." monitoring."
::= { nemoGroups 1 } ::= { nemoGroups 1 }
nemoConfigurationGroup OBJECT-GROUP nemoConfigurationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
nemoHomeRegLifeTime, nemoHomeRegLifeTime,
nemoHomeRegRetryCount, nemoHomeRegRetryCount,
nemoHomeRegRetryDelay, nemoHomeRegRetryDelay,
nemoHomeRegExtendBeforeExpiry, nemoHomeRegExtendBeforeExpiry,
nemoDynamicHAAddressDiscovery, nemoDynamicHADiscovery,
nemoHomeNetworkPrefixType, nemoHomeAddressIdentifierType,
nemoHomeNetworkPrefix, nemoHomeAddressIdentifierInetType,
nemoHomeNetworkPrefixLength, nemoHomeAddressIdentifier,
nemoHomeAddressType, nemoHomeIfIndex,
nemoHomeAddress,
nemoPrefixRegMode, nemoPrefixRegMode,
nemoRegisterConnectedPrefixes, nemoRegisterConnectedPrefixes,
-- nemoPrefixType, -- nemoHomeNetworkPrefixType,
-- nemoPrefix, -- nemoHomeNetworkPrefix,
-- nemoPrefixLength, -- nemoHomeNetworkPrefixLength,
nemoHomeNetworkPrefixLifeTime,
nemoPrefixLifeTime, nemoPrefixLifeTime,
-- nemoRoamingIfIndex, -- nemoRoamingIfIndex,
-- nemoRoamingIfPriority, -- nemoRoamingIfPriority,
nemoRoamingIfDescription, nemoRoamingIfDescription,
nemoRoamingIfRoamHoldDownTime, nemoRoamingIfRoamHoldDownTime,
nemoDHAADRequests, nemoDHAADRequests,
nemoDHAADRepliesWNemoSupport, nemoDHAADRepliesWNemoSupport,
nemoDHAADRepliesWONemoSupport, nemoDHAADRepliesWONemoSupport,
nemoDHAADDiscoveryTimeouts nemoDHAADDiscoveryTimeouts
} }
skipping to change at page 29, line 43 skipping to change at page 33, line 43
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 6. IANA Considerations
IANA should assign a base arc in the mip6Mn group of the 'mipv6MIB' IANA should assign a base arc in the mib-2 (standards track) OID tree
(standards track) OID tree for the 'nemoMIB' MODULE-IDENTITY defined for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB.
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 insight into Mobile Router v4 and v6 and Pascal Thubert for their discussions 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.,
skipping to change at page 31, line 28 skipping to change at page 35, line 28
Rose, M. and S. Waldbusser, Textual Conventions for Rose, M. and S. Waldbusser, Textual Conventions for
SMIv2, STD 58, RFC 2579, April 1999. SMIv2, STD 58, 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, RFC 2580, April 1999. for SMIv2, STD 58, RFC 2580, April 1999.
[RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility
Support in IPv6q RFC 3775, June 2004. Support in IPv6q RFC 3775, June 2004.
[RFC2011bis] Routhier, S., Management Information Base for the [RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V.
Internet Protocol (IP), work in progress (currently Devarapalli, Network Mobility (NEMO) Basic Support
<draft-ietf-ipv6-rfc2011-update-10.txt>). Protocol, RFC 3963, Jan 2005.
[RFC3291bis] 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, work in progress (currently Addresses, RFC 4001, February 2005.
<draft-ietf-ops-rfc3291bis-06.txt>).
[NEMOBASIC] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli, [RFC2011bis] Routhier, S., Management Information Base for the
Network Mobility (NEMO) Basic Support Protocol, Internet Protocol (IP), work in progress (currently
work in progress (currently <draft-ietf-ipv6-rfc2011-update-10.txt>).
<draft-ietf-nemo-basic-support-03.txt>.
[MIPv6MIB] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, [MIPv6MIB] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli,
The Mobile IPv6 MIB, work in progress (currently The Mobile IPv6 MIB, work in progress (currently
<draft-ietf-mip6-mipv6-mib-05.txt>). <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 Management Framework, RFC 3410, Internet-Standard 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
skipping to change at page 34, line 7 skipping to change at page 38, line 7
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 E-mail: koide@shiratori.riec.tohoku.ac.jp
10. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/