draft-ietf-mip4-rfc2006bis-03.txt   draft-ietf-mip4-rfc2006bis-04.txt 
MIP4 Working Group R. Rathi MIP4 Working Group R. Rathi
Internet Draft K. Leung Internet Draft K. Leung
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: July 18, 2007 H. Sjostrand Expires: March 26, 2008 H. Sjostrand
ipUnplugged ipUnplugged
January 18, 2007 September 26, 2007
The Definitions of Managed Objects for IP Mobility Support The Definitions of Managed Objects for IP Mobility Support
using SMIv2, revised using SMIv2, revised
draft-ietf-mip4-rfc2006bis-03.txt draft-ietf-mip4-rfc2006bis-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any 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 aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
This document may not be modified, and derivative works of it may not This document may not be modified, and derivative works of it may not
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 July 18, 2007. This Internet-Draft will expire on March 26, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). 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)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction.................................................3
2. The Internet-Standard Management Framework.....................3 2. The Internet-Standard Management Framework...................3
3. Structure of the MIB...........................................3 3. Structure of the MIB.........................................3
3.1. Structure of the Mobile IP................................3 3.1. Structure of the Mobile IP..............................3
3.2. MIB Groups................................................4 3.2. MIB Groups..............................................4
3.3. Protocol Extensions.......................................5 3.3. Protocol Extensions.....................................5
3.4. Textual Conventions.......................................5 3.4. Textual Conventions.....................................5
4. Mobile IP MIB Definitions......................................5 4. Mobile IP MIB Definitions....................................6
5. Security Considerations.......................................99 5. Security Considerations....................................100
6. IANA Considerations..........................................101 6. IANA Considerations........................................101
7. Acknowledgments..............................................101 7. Acknowledgments............................................101
APPENDIX A: Changes from RFC 2006...............................102 APPENDIX A: Changes from RFC 2006.............................102
A.1. Changes in draft-ietf-mobileip-rfc2006bis-00............102 A.1. Changes in draft-ietf-mobileip-rfc2006bis-00..........102
A.2. Changes in draft-ietf-mobileip-rfc2006bis-02............106 A.2. Changes in draft-ietf-mobileip-rfc2006bis-02..........106
A.3. Changes in draft-ietf-mobileip-rfc2006bis-03............107 A.3. Changes in draft-ietf-mobileip-rfc2006bis-03..........107
A.4. Changes in draft-ietf-mip4-rfc2006bis-00................107 A.4. Changes in draft-ietf-mip4-rfc2006bis-00..............107
A.5. Changes in draft-ietf-mip4-rfc2006bis-01................107 A.5. Changes in draft-ietf-mip4-rfc2006bis-01..............107
A.6. Changes in draft-ietf-mip4-rfc2006bis-02................107 A.6. Changes in draft-ietf-mip4-rfc2006bis-02..............107
A.7. Changes in draft-ietf-mip4-rfc2006bis-03................109 A.7. Changes in draft-ietf-mip4-rfc2006bis-03..............109
8. References...................................................109 A.8. Changes in draft-ietf-mip4-rfc2006bis-04..............109
8.1. Normative References....................................109 8. References.................................................109
8.2. Informative References..................................110 8.1. Normative References..................................109
Author's Addresses..............................................111 8.2. Informative References................................110
Intellectual Property Statement.................................111 Author's Addresses............................................111
Intellectual Property Statement...............................111
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol.
This memo is intended to update and possibly obsolete RFC 2006, This memo is intended to update and possibly obsolete RFC 2006,
however, it is designed to be backward compatible however, it is designed to be backward compatible
skipping to change at page 3, line 45 skipping to change at page 3, line 45
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for the use with network management protocols in the Internet for the use with network management protocols in the Internet
community. In particular, it describes managed objects for the community. In particular, it describes managed objects for the
Mobile IP Protocol (MIP), as defined in [RFC3344]. Mobile IP Protocol (MIP), as defined in [RFC3344].
3.1. Structure of the Mobile IP 3.1. Structure of the Mobile IP
This section describes the basic model of Mobile IP used in This section describes the basic model of Mobile IP used in
developing the Mobile IP MIB. This information should be useful to developing the Mobile IP MIB. This information should be useful to
the implementor in understanding some of the basic design decisions the implementer in understanding some of the basic design decisions
of the MIB. of the MIB.
The Mobile IP Protocol introduces these new functional entities: The Mobile IP Protocol introduces these new functional entities:
Mobile Node Mobile Node
A host or router that changes its point of attachment from one A host or router that changes its point of attachment from one
network or subnetwork to another. A mobile node may change its network or subnetwork to another. A mobile node may change its
location without losing connectivity and without changing its IP location without losing connectivity and without changing its IP
address; it may continue to communicate with other Internet nodes address; it may continue to communicate with other Internet nodes
at any location using its (constant) IP address, assuming link- at any location using its (constant) IP address, assuming link-
layer connectivity to a point of attachment is available. layer connectivity to a point of attachment is available.
Home Agent Home Agent
A router on a mobile node's home network which tunnels packets for A router on a mobile node's home network which tunnels packets for
skipping to change at page 5, line 15 skipping to change at page 5, line 17
3.3. Protocol Extensions 3.3. Protocol Extensions
Apart from changes to base specification of Mobile IP [RFC3344], it Apart from changes to base specification of Mobile IP [RFC3344], it
has been enhanced in number of ways through its ability for added has been enhanced in number of ways through its ability for added
capabilities. Implementations of those capabilities have not been capabilities. Implementations of those capabilities have not been
able to have any management capabilities present in RFC 2006 able to have any management capabilities present in RFC 2006
compliant [RFC2006] MIB module agents, since the capabilities compliant [RFC2006] MIB module agents, since the capabilities
themselves postdated the adoption of RFC 2006. For several themselves postdated the adoption of RFC 2006. For several
significant capabilities, in the form of NAI extension [RFC2794], significant capabilities, in the form of NAI extension [RFC2794],
Challenge/Response Extensions [RFC3012], Reverse Tunneling [RFC3024], Challenge/Response Extensions [RFC4721], Reverse Tunneling [RFC3024],
Vendor/Organization-Specific Extensions [RFC3115] and Extensions for Vendor/Organization-Specific Extensions [RFC3115] and Extensions for
carrying NAI [RFC3846], the MIB Module defined in this document carrying NAI [RFC3846], the MIB Module defined in this document
exposes object types to manage those extended capabilities and their exposes object types to manage those extended capabilities and their
operation. operation.
NAI extension requires a thorough redefinition of MIB table row NAI extension requires a thorough redefinition of MIB table row
indices from the RFC 2006 state since it provides a one more way to indices from the RFC 2006 state since it provides a one more way to
identify the mobile nodes apart from home address. The functional identify the mobile nodes apart from home address. The functional
differences between this memo and RFC 2006 [RFC2002] are explained in differences between this memo and RFC 2006 [RFC2006] are explained in
Appendix A. Appendix A.
3.4. Textual Conventions 3.4. Textual Conventions
The RegistrationFlags, MipEntityIdentifierType, MipEntityIdentifier, The RegistrationFlags, MipEntityIdentifierType, MipEntityIdentifier,
MipEntityIdentifierNAI and MipDeliveryStyle are used as textual MipEntityIdentifierNAI and MipDeliveryStyle are used as textual
conventions in this document. These textual conventions are used for conventions in this document. These textual conventions are used for
the convenience of humans reading the MIB. Objects defined using the convenience of humans reading the MIB. Objects defined using
these conventions are always encoded by means of the rules that these conventions are always encoded by means of the rules that
define their primitive type. However, the textual conventions define their primitive type. However, the textual conventions
skipping to change at page 6, line 13 skipping to change at page 6, line 24
RowStatus, TruthValue, TimeStamp, RowStatus, TruthValue, TimeStamp,
StorageType, TEXTUAL-CONVENTION StorageType, TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndex InterfaceIndex
FROM IF-MIB; -- [RFC2863] FROM IF-MIB; -- [RFC2863]
mipMIB MODULE-IDENTITY mipMIB MODULE-IDENTITY
LAST-UPDATED "200701160000Z" LAST-UPDATED "200709260000Z"
ORGANIZATION "IETF Mobile IP Working Group" ORGANIZATION "IETF Mobile IP Working Group"
CONTACT-INFO CONTACT-INFO
" Ravindra Rathi " Ravindra Rathi
Cisco Systems, Inc. Cisco Systems, Inc.
rathi@cisco.com rathi@cisco.com
Kent Leung Kent Leung
Cisco Systems, Inc. Cisco Systems, Inc.
kleung@cisco.com kleung@cisco.com
Hans Sjostrand Hans Sjostrand
ipUnplugged ipUnplugged
hans@ipunplugged.com" hans@ipunplugged.com"
DESCRIPTION DESCRIPTION
"The MIB module for configuring and displaying Mobile "The MIB module for configuring and displaying Mobile
IP Information. IP Information.
Copyright (C) IETF Trust (2007). This version Copyright (C) IETF Trust (2007). This version
of this MIB module is part of RFC yyyy; see the RFC of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200701160000Z" REVISION "200709260000Z"
DESCRIPTION DESCRIPTION
"Updated for latest changes to Mobile IP." "Updated for latest changes to Mobile IP."
REVISION "199606040000Z" REVISION "199606040000Z"
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC 2006." "Initial revision, published as part of RFC 2006."
::= { mib-2 44 } ::= { mib-2 44 }
mipMIBObjects OBJECT IDENTIFIER ::= { mipMIB 1 } mipMIBObjects OBJECT IDENTIFIER ::= { mipMIB 1 }
-- ================================================================= -- =================================================================
skipping to change at page 25, line 19 skipping to change at page 25, line 29
mnAdvFlags OBJECT-TYPE mnAdvFlags OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
reserved0(0), reserved0(0),
gre(1), gre(1),
minEnc(2), minEnc(2),
foreignAgent(3), foreignAgent(3),
homeAgent(4), homeAgent(4),
busy(5), busy(5),
regRequired(6), regRequired(6),
reverseTunnel(7) reverseTunnel(7),
udpTunnelling(8),
regionalRegistration(9)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The flags are contained in the 7th byte in the "The flags are contained in the 7th and 8th bytes in the
extension of the most recently received mobility agent extension of the most recently received mobility agent
advertisement: advertisement. :
gre gre
-- Agent offers Generic Routing Encapsulation -- Agent offers Generic Routing Encapsulation
minEnc, minEnc,
-- Agent offers Minimal Encapsulation -- Agent offers Minimal Encapsulation
foreignAgent, foreignAgent,
-- Agent is a Foreign Agent -- Agent is a Foreign Agent
homeAgent, homeAgent,
-- Agent is a Home Agent -- Agent is a Home Agent
busy, busy,
-- Foreign Agent is busy -- Foreign Agent is busy
regRequired, regRequired,
-- FA registration is required -- FA registration is required
reverseTunnel, reverseTunnel,
-- Agent supports reverse tunneling." -- Agent supports reverse tunneling.
udpTunnelling,
-- Agent supports MIP UDP Tunnelling.
regionalRegistration,
-- Domain supports regional registration.
Note that the order of the bits is different compared
to the 7th and 8th bytes of the Mobility Agent
Advertisement Extension. The bits construct is chosen
to be backwards compatible with RFC2006. Also note
that new bits may be defined after the publication of
this mib. "
::= { mnRecentAdvReceived 3 } ::= { mnRecentAdvReceived 3 }
mnAdvMaxRegLifetime OBJECT-TYPE mnAdvMaxRegLifetime OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The longest lifetime in seconds that the agent is "The longest lifetime in seconds that the agent is
willing to accept in any registration request." willing to accept in any registration request."
skipping to change at page 99, line 22 skipping to change at page 100, line 4
"A collection of objects providing management "A collection of objects providing management
information for counters related to the registration information for counters related to the registration
function within a home agent." function within a home agent."
::= { mipGroups 12 } ::= { mipGroups 12 }
mipSecNotificationsGroup NOTIFICATION-GROUP mipSecNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mipAuthFailure } NOTIFICATIONS { mipAuthFailure }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The notification related to security violations." "The notification related to security violations."
::= { mipGroups 13 } ::= { mipGroups 13 }
END END
5. Security Considerations 5. Security Considerations
Assuming that secure network management (such as SNMP v3) is
implemented, the objects represented in this MIB do not pose a threat
to the security of the network.
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
sensitive information. These are contained in the sensitive information. These are contained in the
mipSecurityAssocTable, mipSecurityViolationTable, faRegVisitorTable, mipSecurityAssocTable, mipSecurityViolationTable, faRegVisitorTable,
and haMobilityBindingTable. It is thus important to control even GET and haMobilityBindingTable. It is thus important to control even GET
access to these objects and possibly to even encrypt the values of and/or NOTIFY access to these objects and possibly to even encrypt
these object when sending them over the network via SNMP. Not all the values of these object when sending them over the network via
versions of SNMP provide features for such a secure environment. SNMP.
SNMPv1 by itself is not a secure environment. Even if the network SNMP versions prior to SNMPv3 did not include adequate security. Even
itself is secure (for example by using IPSec), even then, there is no if the network itself is secure (for example by using IPSec), even
control as to who on the secure network is allowed to access and then, there is no control as to who on the secure network is allowed
GET/SET (read/change/create/delete) the objects in this MIB. to access and GET/SET (read/change/create/delete) the objects in this
MIB.
The Mobile IP MIB affords the network operator the ability to The Mobile IP MIB affords the network operator the ability to
configure and control the Mobile IP links of a particular system, configure and control the Mobile IP links of a particular system,
including the Mobile IP authentication protocols, and shared secret including the Mobile IP authentication protocols, and shared secret
key. This represents a security risk. key. This represents a security risk.
These risks are addressed in the following manners: These risks are addressed in the following manners:
1. All variables which represent a significant security risk are 1. All variables which represent a significant security risk are
placed in separate MIB Groups. By providing Agent Capability placed in separate MIB Groups. By providing Agent Capability
skipping to change at page 100, line 38 skipping to change at page 101, line 14
3. The MIB defines a trap for Mobile IP entities to send a 3. The MIB defines a trap for Mobile IP entities to send a
notification to the manager station if there is a security notification to the manager station if there is a security
violation. In this way, the operator can notice the source of an violation. In this way, the operator can notice the source of an
intruder. intruder.
4. The MIB also defines a table to log the security violations in the 4. The MIB also defines a table to log the security violations in the
Mobile IP entities. The manager station can retrieve this log to Mobile IP entities. The manager station can retrieve this log to
analyze the security violation instances in the system. analyze the security violation instances in the system.
It is recommended that the implementers consider the security It is RECOMMENDED that implementers consider the security features as
features as provided by the SNMPv3 framework. Specifically, the use provided by the SNMPv3 framework (see [RFC3410], section 8),
of the User-based Security Model RFC 2574 [RFC2574] and the View- including full support for the SNMPv3 cryptographic mechanisms (for
based Access Control Model RFC 2575 [RFC2575] is recommended. authentication and privacy).
It is then a customer/user responsibility to ensure that the SNMP Further, deployment of SNMP versions prior to SNMPv3 is NOT
entity giving access to an instance of this MIB, is properly RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
configured to give access to the objects only to those principals enable cryptographic security. It is then a customer/operator
(users) that have legitimate rights to indeed GET or SET responsibility to ensure that the SNMP entity giving access to an
(change/create/delete) them. instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
mipMIB { mib-2 44 } mipMIB { mib-2 44 }
skipping to change at page 109, line 10 skipping to change at page 109, line 10
needed. needed.
13) Updated template stuff, such as mib boiler plate, security 13) Updated template stuff, such as mib boiler plate, security
considerations, references and TC conventions. considerations, references and TC conventions.
A.7. Changes in draft-ietf-mip4-rfc2006bis-03 A.7. Changes in draft-ietf-mip4-rfc2006bis-03
1) No functional changes at all. Updated boilerplate, dates and 1) No functional changes at all. Updated boilerplate, dates and
address information. address information.
A.8. Changes in draft-ietf-mip4-rfc2006bis-04
mnAdvFlags object updated with I [RFC4857] and U [RFC3519] flags. New
bits are allowed for MIB revision. (RFC 2578, section 10.2 and
RFC4181, section 4.9).
Updated security guidelines and reference sections.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC1701] Hanks S. et. al., "Generic Routing Encapsulation (GRE)", [RFC1701] Hanks S. et. al., "Generic Routing Encapsulation (GRE)",
RFC1701, October 1994. RFC1701, October 1994.
[RFC2002] Perkins C., "IP Mobility Support", RFC 2002, Octoer 1996.
[RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003,
October 1996. October 1996.
[RFC2004] Perkins, C., "Minimal Encapsulation within IP", RFC 2004, [RFC2004] Perkins, C., "Minimal Encapsulation within IP", RFC 2004,
October 1996. October 1996.
[RFC2006] Cong, D., Hamlen, M., and Perkins, C., "The Definitions of [RFC2006] Cong, D., Hamlen, M., and Perkins, C., "The Definitions of
Managed Objects for IP Mobility Support using SMIv2", RFC Managed Objects for IP Mobility Support using SMIv2", RFC
2006, October 1996. 2006, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2574] Blumenthal U., "User-based Security Model (USM) for version
3 of the Simple Network Management Protocol (SNMPv3)", RFC
2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, 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 for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2794] Calhoun, P., and Perkins, C., "Mobile IP Network Access [RFC2794] Calhoun, P., and Perkins, C., "Mobile IP Network Access
Identifier Extension for IPv4", RFC 2794, January 2000. Identifier Extension for IPv4", RFC 2794, January 2000.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB" RFC 2863, June 2000. MIB" RFC 2863, June 2000.
[RFC3012] Calhoun, P., and Perkins, C., "Mobile IPv4
Challenge/Response Extension", RFC 3012, November 2000.
[RFC3024] Montenegro, G., "Reverse Tunneling for Mobile IP", RFC [RFC3024] Montenegro, G., "Reverse Tunneling for Mobile IP", RFC
3024, January 2001. 3024, January 2001.
[RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/Organization [RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/Organization
Specific Extensions", RFC 3115, April 2001. Specific Extensions", RFC 3115, April 2001.
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002. August 2002.
[RFC3519] H. Levkowetz and S. Vaarala, "Mobile IP Traversal of [RFC3519] H. Levkowetz and S. Vaarala, "Mobile IP Traversal of
[RFC3846] F. Johansson and T. Johansson, Mobile IPv4 Extension for Network Address Translation (NAT) Devices", RFC3519, April
2003
[RFC3846] F. Johansson and T. Johansson, "Mobile IPv4 Extension for
[RFC4721] P. Calhoun,C. Perkins and J. Bharatia, "Mobile IPv4
Challenge/Response Extension (Revised)", RFC 4721, January
2007.
[RFC4857] E. Fogelstroem, A. Jonsson and C. Perkins, "Mobile IPv4
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- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
Author's Addresses Author's Addresses
Ravindra Rathi Kent Leung Ravindra Rathi Kent Leung
Cisco Systems, Inc Cisco Systems, Inc. Cisco Systems, Inc Cisco Systems, Inc.
12, Bannerghatta Road 170 West Tasman Drive Cessna Business Park 170 West Tasman Drive
Subramanya Arcade Block San Jose, CA. 95134 Sarjapur Outer Ring Road San Jose, CA. 95134
Bangalore - 560 029 Bangalore - 560 087
India USA India USA
Phone: +91 80 4154 1000 Phone: +1 408 526 5030 Phone: +91 80 4426 0131 Phone: +1 408 526 5030
Email: rathi@cisco.com Email: kleung@cisco.com Email: rathi@cisco.com Email: kleung@cisco.com
Hans Sjostrand Hans Sjostrand
ipUnplugged ipUnplugged
Arenavagen 21 Arenavagen 21
121 29 Stockholm 121 29 Stockholm
Sweden Sweden
Phone: +46 8 725 5900 Phone: +46 8 725 5900
Email: hans@ipunplugged.com Email: hans@ipunplugged.com
 End of changes. 28 change blocks. 
74 lines changed or deleted 91 lines changed or added

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