draft-ietf-nemo-mib-02.txt   draft-ietf-nemo-mib-03.txt 
NEMO Working Group Sri Gundavelli NEMO Working Group Sri Gundavelli
Internet-Draft Cisco Systems Internet-Draft Cisco
Expires: April 24, 2007 Glenn M. Keeni Intended status: Standards Track Glenn M. Keeni
Cyber Solutions Expires: January 10, 2008 Cyber Solutions
Kazuhide Koide Kazuhide Koide
Tohoku University Tohoku University
Kenichi Nagami Kenichi Nagami
INTEC NetCore INTEC NetCore
October 21, 2006 July 09, 2007
NEMO Management Information Base NEMO Management Information Base
draft-ietf-nemo-mib-02 draft-ietf-nemo-mib-03
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 39 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 Internet-Draft will expire on April 24, 2007. This Internet-Draft will expire on January 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
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
2.1. The Mobile IPv6 Protocol and NEMO entities . . . . . . . . 3 2.1. The Mobile IPv6 Protocol and NEMO entities . . . . . . . . 3
2.2. Implementation Guidance . . . . . . . . . . . . . . . . . 3 2.2. Implementation Guidance . . . . . . . . . . . . . . . . . 3
2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
3. MIB Design . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. MIB Design . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. The NEMO MIB . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. The NEMO MIB . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 6. Security Considerations . . . . . . . . . . . . . . . . . . . 39
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.1. Normative References . . . . . . . . . . . . . . . . . . . 31 8.1. Normative References . . . . . . . . . . . . . . . . . . . 40
8.2. Informative References . . . . . . . . . . . . . . . . . . 32 8.2. Informative References . . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40
Intellectual Property and Copyright Statements . . . . . . . . . . 34 Intellectual Property and Copyright Statements . . . . . . . . . . 42
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 43 skipping to change at page 3, line 43
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 [RFC4295] 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 [RFC3963].
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:
skipping to change at page 4, line 42 skipping to change at page 4, line 42
registration 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. changes in the NEMO protocol.
The nemoConformance group identifies the managed objects that needs The nemoConformance group identifies the managed objects that needs
to be implemented for conforming to this draft. to be implemented for conforming to this draft.
4. The NEMO MIB 4. The NEMO MIB
NEMO-MIB DEFINITIONS ::= BEGIN NEMO-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32, Counter32, MODULE-IDENTITY, mib-2, Unsigned32, Counter32,
Gauge32, Counter64, Integer32, Gauge32,
-- Counter64,
OBJECT-TYPE, NOTIFICATION-TYPE OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, TEXTUAL-CONVENTION,
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 mip6BindingHomeAddressType, mip6BindingHomeAddress,
mip6HaListEntry, mip6MnBLEntry, mip6BindingCacheEntry
FROM MOBILEIPV6-MIB FROM MOBILEIPV6-MIB
; ;
nemoMIB MODULE-IDENTITY nemoMIB MODULE-IDENTITY
LAST-UPDATED "200507160000Z" -- 16th July, 2005 LAST-UPDATED "200703040000Z" -- 4th March, 2007
ORGANIZATION "IETF NEMO Working Group" ORGANIZATION "IETF NEMO Working Group"
CONTACT-INFO CONTACT-INFO
" Sri Gundavelli " Sri Gundavelli
Postal: Cisco Systems Postal: Cisco
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.
skipping to change at page 6, line 22 skipping to change at page 6, line 24
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 a NEMO entity. "The MIB module for monitoring a NEMO entity.
Copyright (C) The Internet Society 2004. This Copyright (C) The IETF Trust (2007). 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 and remove this -- RFC Ed.: replace XXXX with actual RFC number and remove this
-- note -- note
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number and remove this -- RFC Ed.: replace XXXX with actual RFC number and remove this
-- note -- note
::= { mib-2 XXX } -- will be assigned by IANA ::= { mib-2 YYY } -- will be assigned by IANA
-- IANA Reg.: Please assign a value for "XXX" under the 'mib-2' -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2'
-- subtree and record the assignment in the SMI Numbers -- subtree and record the assignment in the SMI Numbers
-- registry. -- 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 "YYY" 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 } nemoObjects OBJECT IDENTIFIER ::= { nemoMIB 1 }
nemoConfiguration OBJECT IDENTIFIER ::= { nemoMIB 2 } nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 3 }
nemoStats OBJECT IDENTIFIER ::= { nemoMIB 3 } nemoCore OBJECT IDENTIFIER ::= { nemoObjects 1 }
nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 4 } nemoMr OBJECT IDENTIFIER ::= { nemoObjects 2 }
nemoCn OBJECT IDENTIFIER ::= { nemoObjects 3 }
nemoHa OBJECT IDENTIFIER ::= { nemoObjects 4 }
-- The sub groups
nemoSystem OBJECT IDENTIFIER ::= { nemoCore 1 }
nemoBindings OBJECT IDENTIFIER ::= { nemoCore 2 }
nemoConfiguration OBJECT IDENTIFIER ::= { nemoCore 3 }
nemoStats OBJECT IDENTIFIER ::= { nemoCore 4 }
nemoMrSystem OBJECT IDENTIFIER ::= { nemoMr 1 }
nemoMrConf OBJECT IDENTIFIER ::= { nemoMr 2 }
nemoMrRegistration OBJECT IDENTIFIER ::= { nemoMr 3 }
nemoHaAdvertisement OBJECT IDENTIFIER ::= { nemoHa 1 }
-- 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 }
nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 2 } nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 2 }
nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 3 } nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 3 }
skipping to change at page 14, line 26 skipping to change at page 14, line 39
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast routable address assigned to the "The unicast routable address assigned to the
mobile router. This is used as the permanent mobile router. This is used as the permanent
address of the mobile router in the sense that it address of the mobile router in the sense that it
remains unchanged regardless of the mobile remains unchanged regardless of the mobile
router's current 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 is specified by the corresponding
nemoHomeAddressType object. nemoHomeAddressIdentifierInetType object.
" "
::= { nemoRegistration 8 } ::= { nemoRegistration 8 }
nemoHomeIfIndex OBJECT-TYPE nemoHomeIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-write 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.
skipping to change at page 14, line 37 skipping to change at page 15, line 4
" "
::= { nemoRegistration 8 } ::= { nemoRegistration 8 }
nemoHomeIfIndex OBJECT-TYPE nemoHomeIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-write 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), other (0),
explicitMode (1) implicitMode (1),
explicitMode (2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the mobile router will "This object indicates if the mobile router will
explicitly register all the prefixes. explicitly register all the prefixes.
" "
REFERENCE
"RFC 3963 : Section 5.2"
::= { nemoRegistration 10 } ::= { 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 if the mobile router will "This object indicates if the mobile router will
register all the connected prefixes. register all the connected prefixes.
" "
skipping to change at page 15, line 36 skipping to change at page 16, line 8
::= { 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 "An entry in the binding cache table. It represents
a single home network entry a single home network entry
Implementors need to be aware that if the total Implementers 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 }
::= { nemoHomeNetworkPrefixTable 1 } ::= { nemoHomeNetworkPrefixTable 1 }
skipping to change at page 17, line 19 skipping to change at page 17, line 35
-- 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.
" "
REFERENCE
"RFC 3963 : Section 6.1.2"
::= { 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 "An entry in the binding cache table. It represents
a single Binding Update. a single Binding Update.
Implementors need to be aware that if the total Implementers 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 { mip6BindingHomeAddressType, mip6BindingHomeAddress,
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
} }
nemoPrefixType OBJECT-TYPE nemoPrefixType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the nemoPrefix "The InetAddressType of the nemoPrefix
that follows. that follows.
" "
::= { nemoPrefixEntry 1 } ::= { nemoPrefixEntry 1 }
skipping to change at page 18, line 25 skipping to change at page 18, line 45
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 mobile router and advertised in the mobile
network. The type of the address represented by network. The type of the address represented by
this object is specified by the corresponding this object is specified by the corresponding
nemoPrefixType object. nemoPrefixType object.
" "
::= { nemoPrefixEntry 2 } REFERENCE
"RFC 3963 : Section 6.1.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.
" "
::= { nemoPrefixEntry 3 } ::= { nemoPrefixEntry 3 }
nemoPrefixLifeTime OBJECT-TYPE nemoPrefixLifeTime OBJECT-TYPE
skipping to change at page 19, line 14 skipping to change at page 19, line 35
-- 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 Each entry represents a configured roaming
interface with the roaming characterstics. interface with the roaming characteristics.
" "
::= { 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.
skipping to change at page 20, line 37 skipping to change at page 21, line 14
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 "This object indicates the time for which hold on
to the interface. This value is configured to to the interface. This value is configured to
avoid interface flapping. avoid interface flapping.
" "
::= { nemoRoamingIfEntry 4 } ::= { nemoRoamingIfEntry 4 }
nemoHaListTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoHaListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table models the Home Agents List that contains
the list of all routers that are acting as
home agents with NEMO functionality on
each of the interfaces on which the home agent service
is offered by this router.
"
REFERENCE
"RFC 3963 : Section 7.2, 7.3"
::= { nemoHaAdvertisement 1 }
nemoHaListEntry OBJECT-TYPE
SYNTAX NemoHaListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing additional information about a
home agent that is offering NEMO service.
"
AUGMENTS { mip6HaListEntry }
::= { nemoHaListTable 1 }
NemoHaListEntry ::= SEQUENCE {
nemoHaSupportsMr TruthValue
}
nemoHaSupportsMr OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) if the home agent supports mobile router and
sent the home agent information with Mobile Router
Flag.
false(0) implies that the home agent only supports
mobile node.
"
REFERENCE
"RFC 3963 : Section 7.3"
::= { nemoHaListEntry 1 }
nemoMrBLTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoMrBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table corresponds to the Binding Update List(BL)
that includes NEMO related information and
is maintained by the mobile router.
Entries from the table are deleted as
the lifetime of the binding expires.
"
REFERENCE
"RFC 3775 : Section 4.5, 11.1, RFC 3963 : Section 5.2"
::= { nemoMrRegistration 1 }
nemoMrBLEntry OBJECT-TYPE
SYNTAX NemoMrBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing additional information contained
in a Binding Update sent by a NEMO enabled mobile
router to its home agent.
"
AUGMENTS {mip6MnBLEntry}
::= { nemoMrBLTable 1 }
NemoMrBLEntry ::= SEQUENCE {
nemoMrBLMode BITS,
nemoMrBLMrFlag TruthValue
}
nemoMrBLMode OBJECT-TYPE
SYNTAX BITS {
implicitMode (0),
explicitMode (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the mode of mobile router
to tell the home agent to determine which prefixes
belong to the mobile router.
"
REFERENCE
"RFC 3963 : Section 5.2"
::= { nemoMrBLEntry 1 }
nemoMrBLMrFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) if the mobile router sent the binding update
with Mobile Router Flag that indicates to the home
agent that the binging update is from a mobile router.
false(0) implies that the mobile router is behaving
as a mobile node.
"
REFERENCE
"RFC 3963 : Section 4.1, 5.1"
::= { nemoMrBLEntry 2 }
nemoBindingCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoBindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table models the Binding Cache
that includes NEMO related information and
is maintained by the mobile router.
Entries in this table are not required to survive
a reboot of the Home Agent.
"
REFERENCE
"RFC 3775 : Section 4.5, 9.1, 10.1,
RFC 3963 : Section 6.1"
::= { nemoBindings 1 }
nemoBindingCacheEntry OBJECT-TYPE
SYNTAX NemoBindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing additional information related
to nemo-enabled entries in the binding cache table
of the Home Agent.
"
AUGMENTS {mip6BindingCacheEntry}
::= { nemoBindingCacheTable 1 }
NemoBindingCacheEntry ::= SEQUENCE {
nemoBindingMrFlag TruthValue,
nemoBindingMrMode BITS
}
nemoBindingMrFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) if the home agent accepted the binding update
with Mobile Router Flag from a mobile router.
false(0) implies that the binding cache is from
a mobile node.
"
REFERENCE
"RFC 3963 : Section 6.1.1, 6.2"
::= { nemoBindingCacheEntry 1 }
nemoBindingMrMode OBJECT-TYPE
SYNTAX BITS {
implicitMode(0),
explicitMode(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the mode of mobile router
to tell the home agent to determine which prefixes
belong to the mobile router.
"
REFERENCE
"RFC 3963 : Section 5.2, 6.1.1, 6.2"
::= { nemoBindingCacheEntry 2 }
nemoHaPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoHaPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the mobile network prefixes
that the home agent maintains for the Mobile Router.
"
REFERENCE
"RFC 3963 : Section 6.1"
::= { nemoMrRegistration 2 }
nemoHaPrefixEntry OBJECT-TYPE
SYNTAX NemoHaPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This entry represents the mobile network prefixes
that are maintained by the home agent.
There are two method that the home agent studies
the mobile network prefixes.
In implicit mode, the mobile network prefixes is
configured by any method(ex. pre-defined) for
corresponding Mobile Router.
In explicit mode, the binding update from the mobile
router contains the mobile network prefix list.
The home agent maintains Prefix Table that contains
the home address of the mobile router for verifying
the prefix list from the mobile router.
This entry contains only the mobile network prefixes
that are registered by the corresponding binding
update. It does not include the prefixes studied
through the dynamic routing process between the home
agent and the mobile router.
The instances of the columnar objects in this entry
pertain to an interface for a particular value of
mip6BindingHomeAddressType, mip6BindingHomeAddress,
and nemoHaPrefixSeqNo.
The nemoHaPrefixSeqNo object is used to
distinguish between multiple instances of
the mobile network prefix on the same binding update
for the same set of
mip6BindingHomeAddressType, mip6BindingHomeAddress.
There is no upper-bound on the maximum number of
mobile network prefixes on a binding update but, for
practical purposes, the upper bound of the value
nemoHaPrefixSeqNo is set to 1024.
Implementers need to be aware that if the total
number of octets in mip6BindingHomeAddress
exceeds 111, 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 { mip6BindingHomeAddressType,
mip6BindingHomeAddress,
nemoHaPrefixSeqNo
}
::= { nemoHaPrefixTable 1 }
NemoHaPrefixEntry ::= SEQUENCE {
nemoHaPrefixSeqNo Integer32,
nemoHaPrefixType InetAddressType,
nemoHaPrefix InetAddress,
nemoHaPrefixLength Unsigned32,
nemoHaPrefixSource BITS
}
nemoHaPrefixSeqNo OBJECT-TYPE
SYNTAX Integer32 (1..1024)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index that along with mip6BindingHomeAddressType,
and mip6BindingHomeAddress uniquely identifies this
row.
One binding update has some mobile network prefixes.
So when we describe the prefix list corresponding to
the binding cache, it will be needed as a sub index.
"
REFERENCE
"RFC 3963 : Section 6.1.1, 6.1.2"
::= { nemoHaPrefixEntry 1 }
nemoHaPrefixType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address type for the mobile network prefix
that follows.
"
REFERENCE
"RFC 3963 : Section 6.1, 6.2"
::= { nemoHaPrefixEntry 2 }
nemoHaPrefix OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A mobile network prefix related to the
corresponding Binding Update.
The type of the address represented by this object
is specified by the corresponding
nemoHaPrefixType object.
"
REFERENCE
"RFC 3963 : Section 6.1, 6.2"
::= { nemoHaPrefixEntry 3 }
nemoHaPrefixLength OBJECT-TYPE
SYNTAX Unsigned32 (0..128)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The length of the prefix specified by the corresponding
nemoHaPrefix Object.
"
REFERENCE
"RFC 3963 : Section 6.1, 6.2"
::= { nemoHaPrefixEntry 4 }
nemoHaPrefixSource OBJECT-TYPE
SYNTAX BITS{
configured (0),
bindingUpdate (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The information source of the mobile network prefix
configured with the binding update.
Configured(1) represents that the information is
introduced to the home agent without binding update.
Binding Update(2) represents that the information is
introduced to the home agent by the mobile network
prefix option in the binding update and verified
by the Prefix Table that the home agent maintains
for each home addresses of the mobile router.
"
REFERENCE
"RFC 3963 : Section 6.1, 6.2"
::= { nemoHaPrefixEntry 5 }
nemoMrDiscoveryRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Modified Dynamic Home Agent Address
Discovery Requests with Mobile Router Flag
sent by the mobile router.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.1"
::= { nemoMrConf 1 }
nemoMrDiscoveryReplies OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Modified Dynamic Home Agent Address
Discovery Replies with Mobile Router Flag is set to 1
received by the mobile router.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2"
::= { nemoMrConf 2 }
nemoMrDiscoveryRepliesRouterFlagZero OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Modified Dynamic Home Agent Address
Discovery Replies with Mobile Router Flag is set to 0
although the flag in the corresponding request
is set to 1.
It implies that there is no home agent that supports
Mobile Router in the home network.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.3"
::= { nemoMrConf 3 }
--- ---
--- ---
--- nemoStats group --- nemoStats group
--- ---
--- ---
-- --
-- Dynamic Home Agent discovery protocol related counters -- Dynamic Home Agent discovery protocol related counters
-- --
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
with the Mobile Router Support Flag (R) set.
" "
REFERENCE REFERENCE
"RFC3963 : Section 7.1." "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
support. Mobile Router Support Flag (R) set.
" "
REFERENCE REFERENCE
"RFC3963 : Section 7.2." "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 i.e the Mobile Router Support Flag
set to 0.
" "
REFERENCE REFERENCE
"RFC3963 : Section 7.2." "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 requests sent by the mobile router
was timeout. with the Mobile Router Support Flag (R) set,
that did not receive any response.
" "
::= { nemoHomeAgentDiscovery 4 } ::= { nemoHomeAgentDiscovery 4 }
-- --
-- nemoStats:nemoBindingRegcounters -- nemoStats:nemoBindingRegcounters
-- --
nemoBindingAcksWONemoSupport OBJECT-TYPE nemoBindingAcksWONemoSupport OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 25, line 27 skipping to change at page 33, line 44
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router.
" "
::= { nemoRoamingCounters 1 } ::= { nemoRoamingCounters 1 }
nemoMovedOutofHome OBJECT-TYPE nemoMovedOutofHome 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 to a foreign network from the home
network, has reconstructed its care-of address and network, has acquired a 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.
" "
REFERENCE
"RFC3963 : Section 3."
::= { 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 28, line 28 skipping to change at page 36, line 47
-- nemoHomeNetworkPrefixLength, -- nemoHomeNetworkPrefixLength,
nemoHomeNetworkPrefixLifeTime, nemoHomeNetworkPrefixLifeTime,
nemoPrefixLifeTime, nemoPrefixLifeTime,
-- nemoRoamingIfIndex, -- nemoRoamingIfIndex,
-- nemoRoamingIfPriority, -- nemoRoamingIfPriority,
nemoRoamingIfDescription, nemoRoamingIfDescription,
nemoRoamingIfRoamHoldDownTime, nemoRoamingIfRoamHoldDownTime,
nemoDHAADRequests, nemoDHAADRequests,
nemoDHAADRepliesWNemoSupport, nemoDHAADRepliesWNemoSupport,
nemoDHAADRepliesWONemoSupport, nemoDHAADRepliesWONemoSupport,
nemoDHAADDiscoveryTimeouts nemoDHAADDiscoveryTimeouts,
nemoHaSupportsMr,
nemoMrBLMode,
nemoMrBLMrFlag,
nemoBindingMrFlag,
nemoBindingMrMode,
nemoHaPrefixType,
nemoHaPrefix,
nemoHaPrefixLength,
nemoHaPrefixSource,
nemoMrDiscoveryRequests,
nemoMrDiscoveryReplies,
nemoMrDiscoveryRepliesRouterFlagZero
} }
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 {
nemoBindingUpdates,
nemoBindingAcks,
nemoBindingAcksWONemoSupport, nemoBindingAcksWONemoSupport,
nemoBindingAckNotHomeRegn, nemoBindingAckNotHomeRegn,
nemoBindingRegTypeChanged, nemoBindingRegTypeChanged,
nemoOpNotSupported, nemoOpNotSupported,
nemoInvalidPrefix, nemoInvalidPrefix,
nemoNotAuthorizedForPrefix, nemoNotAuthorizedForPrefix,
nemoForwardingSetupFailed, nemoForwardingSetupFailed,
nemoMovedHome, nemoMovedHome,
nemoMovedOutofHome, nemoMovedOutofHome,
nemoMovedFNtoFN, nemoMovedFNtoFN,
skipping to change at page 31, line 17 skipping to change at page 39, line 44
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.
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 review comments on this document.
and Pascal Thubert for their inputs on Mobile Router 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 Information Rose, M. and S. Waldbusser, Structure of Management Information
skipping to change at page 31, line 45 skipping to change at page 40, line 28
[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 for SMIv2, STD 58, Rose, M. and S. Waldbusser, Conformance Statements for SMIv2, STD 58,
RFC 2580, April 1999. RFC 2580, April 1999.
[RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in
IPv6q RFC 3775, June 2004. IPv6q RFC 3775, June 2004.
[RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli, [RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli,
Network Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan 2005. Network Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan 2005.
[RFC4001] Daniele, M., Haberman, B., Routhier, S. and Schoenwaelder,
J., Textual Conventions for Internet Network Addresses, RFC 4001,
February 2005.
[RFC2011bis] Routhier, S., Management Information Base for the
Internet Protocol (IP), work in progress (currently
draft-ietf-ipv6-rfc2011-update-10.txt).
[RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The [RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The
Mobile IPv6 MIB, RFC 4295, April 2006. Mobile IPv6 MIB, RFC 4295, April 2006.
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 Internet-Standard Introduction and Applicability Statements for Internet-Standard
Management Framework, RFC 3410, December 2002. Management Framework, RFC 3410, 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-06.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-06.txt).
Authors' Addresses Authors' Addresses
Sri Gundavelli Sri Gundavelli
Cisco Systems Cisco
170 West 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 Cyber Solutions
6-6-3 Minami Yoshinari 6-6-3 Minami Yoshinari
skipping to change at page 34, line 5 skipping to change at page 42, line 5
Kenichi Nagami Kenichi Nagami
INTEC NetCore INTEC NetCore
1-3-3, Shin-suna 1-3-3, Shin-suna
Koto-ku, Tokyo, 135-0075, Koto-ku, Tokyo, 135-0075,
Japan Japan
Phone: +81-3-5665-5069 Phone: +81-3-5665-5069
Email: nagami@inetcore.com Email: nagami@inetcore.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
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.
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, THE IETF TRUST 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
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 to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 34, line 29 skipping to change at page 42, line 45
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 at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 49 change blocks. 
82 lines changed or deleted 487 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/