draft-ietf-mip4-rfc2006bis-05.txt   draft-ietf-mip4-rfc2006bis-06.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: February 7, 2009 H. Sjostrand Expires: October 6, 2009 H. Sjostrand
ipUnplugged Transmode
August 7, 2008 April 6, 2009
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-05.txt draft-ietf-mip4-rfc2006bis-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that This Internet-Draft is submitted to IETF in full conformance with the
any applicable patent or other IPR claims of which he or she is provisions of BCP 78 and BCP 79.
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
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. 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 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 February 7, 2009. This Internet-Draft will expire on October 6, 2009.
Copyright Notice Copyright and License Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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.................................... 6 4. Mobile IP MIB Definitions......................................6
5. Security Considerations.................................... 100 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...............................103
A.1. Changes in draft-ietf-mobileip-rfc2006bis-00.......... 102 A.1. Changes in draft-ietf-mobileip-rfc2006bis-00............103
A.2. Changes in draft-ietf-mobileip-rfc2006bis-02.......... 106 A.2. Changes in draft-ietf-mobileip-rfc2006bis-02............107
A.3. Changes in draft-ietf-mobileip-rfc2006bis-03.......... 107 A.3. Changes in draft-ietf-mobileip-rfc2006bis-03............108
A.4. Changes in draft-ietf-mip4-rfc2006bis-00.............. 107 A.4. Changes in draft-ietf-mip4-rfc2006bis-00................108
A.5. Changes in draft-ietf-mip4-rfc2006bis-01.............. 107 A.5. Changes in draft-ietf-mip4-rfc2006bis-01................108
A.6. Changes in draft-ietf-mip4-rfc2006bis-02.............. 107 A.6. Changes in draft-ietf-mip4-rfc2006bis-02................108
A.7. Changes in draft-ietf-mip4-rfc2006bis-03.............. 109 A.7. Changes in draft-ietf-mip4-rfc2006bis-03................110
A.8. Changes in draft-ietf-mip4-rfc2006bis-04.............. 109 A.8. Changes in draft-ietf-mip4-rfc2006bis-04................110
8. References ................................................ 109 A.9. Changes in draft-ietf-mip4-rfc2006bis-05................110
8.1. Normative References.................................. 109 A.10. Changes in draft-ietf-mip4-rfc2006bis-06...............110
8.2. Informative References................................ 110 8. References...................................................110
Author's Addresses ........................................... 111 8.1. Normative References....................................110
Intellectual Property Statement............................... 111 8.2. Informative References..................................111
Author's Addresses..............................................112
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 6, line 24 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 "200709260000Z" LAST-UPDATED "200904060000Z"
ORGANIZATION "IETF Mobile IP Working Group" ORGANIZATION "IETF Mobility for IPv4 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 Transmode
hans@ipunplugged.com" hans.sjostrand@transmode.com
Comments about this document should be emailed
directly to the Mip4 working group mailing list at
mip4@ietf.org"
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 (2009). 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 "200709260000Z" REVISION "200904060000Z"
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 9, line 19 skipping to change at page 9, line 23
ipaddress(2), ipaddress(2),
nai(3) nai(3)
} }
MipEntityIdentifier ::= TEXTUAL-CONVENTION MipEntityIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the generic identifier for Mobile IP "Represents the generic identifier for Mobile IP
entities. A MipEntityIdentifier value is always entities. A MipEntityIdentifier value is always
interpreted within the context of a interpreted within the context of a
MipEntityIdentifierType value. MipEntityIdentifierType value. Foreign agents and
Foreign agents and Home agents are Home agents are identified by the IP addresses.
identified by the IP addresses. Mobile nodes can be Mobile nodes can be identified in more than one
identified in more than one way e.g. IP addresses, way e.g. IP addresses, network access identifiers (NAI).
network access identifiers (NAI). If mobile node is If mobile node is identified by something other than
identified by something other than IP address say by IP address say by NAI and it gets IP address dynamically
NAI and it gets IP address dynamically from the home from the home agent then value of object of this type
agent then value of object of this type should be same should be same as NAI. This is because IP address is not
as NAI. This is because IP address is not tied with tied with mobile node and it can change across
mobile node and it can change across registrations over registrations over period of time. Note that the first
period of time. Note that the first 64 octets are used 64 octets are used as index element."
as index element."
SYNTAX OCTET STRING (SIZE (1..64)) SYNTAX OCTET STRING (SIZE (1..64))
MipEntityIdentifierNAI ::= TEXTUAL-CONVENTION MipEntityIdentifierNAI ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a Network Access Identifier (NAI). Mobile "Represents a Network Access Identifier (NAI). Mobile
nodes may use NAI to authenticate themselves to the nodes may use NAI to authenticate themselves to the
foreign agent and home agent and to get the home foreign agent and home agent and to get the home
address dynamically from the home agent. address dynamically from the home agent.
If there are no NAI assigned, a null octet string is If there are no NAI assigned, a null octet string is
used." used."
REFERENCE REFERENCE
"RFC2794 - Mobile IP Network Access Identifier "RFC2794 - Mobile IP Network Access Identifier
skipping to change at page 69, line 4 skipping to change at page 69, line 8
::= { haRegistration 28 } ::= { haRegistration 28 }
haRegCounterEntry OBJECT-TYPE haRegCounterEntry OBJECT-TYPE
SYNTAX HaRegCounterEntry SYNTAX HaRegCounterEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Registration statistics for one mobile node." "Registration statistics for one mobile node."
INDEX { haMobilityBindingMnIdType, haMobilityBindingMnId } INDEX { haMobilityBindingMnIdType, haMobilityBindingMnId }
::= { haRegCounterTable 1 } ::= { haRegCounterTable 1 }
HaRegCounterEntry ::= SEQUENCE { HaRegCounterEntry ::= SEQUENCE {
haRegServiceRequestsAccepted Counter32, haRegServiceRequestsAccepted Counter32,
haRegServiceRequestsDenied Counter32, haRegServiceRequestsDenied Counter32,
haRegOverallServiceTime Gauge32, haRegOverallServiceTime Gauge32,
haRegRecentServiceAcceptedTime TimeStamp, haRegRecentServiceAcceptedTime TimeStamp,
haRegRecentServiceDeniedTime TimeStamp, haRegRecentServiceDeniedTime TimeStamp,
haRegRecentServiceDeniedCode INTEGER haRegRecentServiceDeniedCode Integer32
} }
haRegServiceRequestsAccepted OBJECT-TYPE haRegServiceRequestsAccepted OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of service requests for the mobile node "Total number of service requests for the mobile node
accepted by the home agent (Code 0 + Code 1)." accepted by the home agent (Code 0 + Code 1)."
::= { haRegCounterEntry 1 } ::= { haRegCounterEntry 1 }
skipping to change at page 108, line 38 skipping to change at page 109, line 38
debug-tool, and is also practice in all comparable mibs. They should debug-tool, and is also practice in all comparable mibs. They should
be kept per registration sessson in the FA and HA. be kept per registration sessson in the FA and HA.
9) HA and NAI information is included in haMobilityBindingTable. 9) HA and NAI information is included in haMobilityBindingTable.
There could be many per snmp-agent, so which ha a particular ha There could be many per snmp-agent, so which ha a particular ha
session is pertaining to should be incluided in the table. Also, the session is pertaining to should be incluided in the table. Also, the
NAI (as described before) is included. NAI (as described before) is included.
10) haRegRecentServiceDeniedCode can't be enumerated. It's handled by 10) haRegRecentServiceDeniedCode can't be enumerated. It's handled by
IANA and should therefore be one of the IANA considerations, the IANA and should therefore be one of the IANA considerations, the
sytax is changed to open INTEGER. sytax is changed to open Integer32.
11) The mipAuthFailure2 notification needs additional objects. Traps 11) The mipAuthFailure2 notification needs additional objects. Traps
should be complete and don't require addditional read operations. the should be complete and don't require addditional read operations. the
mipAuthFailure2 trap adds objects from hte seviolation table. mipAuthFailure2 trap adds objects from hte seviolation table.
12) StorageType a'la rfc2579 is added to those tables where they are 12) StorageType a'la rfc2579 is added to those tables where they are
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.
skipping to change at page 109, line 22 skipping to change at page 110, line 22
mnAdvFlags object updated with I [RFC4857] and U [RFC3519] flags. New mnAdvFlags object updated with I [RFC4857] and U [RFC3519] flags. New
bits are allowed for MIB revision. (RFC 2578, section 10.2 and bits are allowed for MIB revision. (RFC 2578, section 10.2 and
RFC4181, section 4.9). RFC4181, section 4.9).
Updated security guidelines and reference sections. Updated security guidelines and reference sections.
A.9. Changes in draft-ietf-mip4-rfc2006bis-05 A.9. Changes in draft-ietf-mip4-rfc2006bis-05
Removed RFC 3978 Section 5.2(b) Derivative Works Limitation. Removed RFC 3978 Section 5.2(b) Derivative Works Limitation.
A.10. Changes in draft-ietf-mip4-rfc2006bis-06
Boilerplate updates for changes in legal provisions relating to IETF
documents.
Contact info updates
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.
[RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003,
October 1996. October 1996.
skipping to change at page 110, line 34 skipping to change at page 111, line 43
[RFC3519] H. Levkowetz and S. Vaarala, "Mobile IP Traversal of [RFC3519] H. Levkowetz and S. Vaarala, "Mobile IP Traversal of
Network Address Translation (NAT) Devices", RFC3519, April Network Address Translation (NAT) Devices", RFC3519, April
2003 2003
[RFC3846] F. Johansson and T. Johansson, "Mobile IPv4 Extension for [RFC3846] F. Johansson and T. Johansson, "Mobile IPv4 Extension for
[RFC4721] P. Calhoun,C. Perkins and J. Bharatia, "Mobile IPv4 [RFC4721] P. Calhoun,C. Perkins and J. Bharatia, "Mobile IPv4
Challenge/Response Extension (Revised)", RFC 4721, January Challenge/Response Extension (Revised)", RFC 4721, January
2007. 2007.
[RFC4857] E. Fogelstroem, A. Jonsson and C. Perkins, "Mobile IPv4 [RFC4857] E. Fogelstroem, A. Jonsson and C. Perkins, "Mobile IPv4
Regional Registration", RFC4857, June 2007.
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
Cisco Systems, Inc Cisco Systems, Inc. Cisco Systems, Inc
Cessna Business Park 170 West Tasman Drive Cessna Business Park
Sarjapur Outer Ring Road San Jose, CA. 95134 Sarjapur Outer Ring Road
Bangalore - 560 087 Bangalore - 560 087
India USA India
Phone: +91 80 4426 0131 Phone: +1 408 526 5030 Phone: +91 80 4426 2403
Email: rathi@cisco.com Email: kleung@cisco.com Email: rathi@cisco.com
Kent Leung
Cisco Systems, Inc
170 West Tasman Drive
San Jose, CA. 95134
USA
Phone: +1 408 526 5030
Email: kleung@cisco.com
Hans Sjostrand Hans Sjostrand
ipUnplugged Transmode
Arenavagen 21 Jakobsdalsvagen 17
121 29 Stockholm 126 53 Stockholm
Sweden Sweden
Phone: +46 8 725 5900 Phone: +46 8 410 88 000
Email: hans@ipunplugged.com Email: hans.sjostrand@transmode.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the IETF Funding for the RFC Editor function is currently provided by the IETF
Administrative Support Activity (IASA). Administrative Support Activity (IASA).
 End of changes. 22 change blocks. 
109 lines changed or deleted 95 lines changed or added

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