draft-ietf-mip4-rfc2006bis-04.txt   draft-ietf-mip4-rfc2006bis-05.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: March 26, 2008 H. Sjostrand Expires: February 7, 2009 H. Sjostrand
ipUnplugged ipUnplugged
September 26, 2007 August 7, 2008
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-04.txt draft-ietf-mip4-rfc2006bis-05.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
be created, other than to extract section "Mobile IP MIP definitions"
as-is for separate use.
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 March 26, 2008. This Internet-Draft will expire on February 7, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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.............................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
A.8. Changes in draft-ietf-mip4-rfc2006bis-04..............109 A.8. Changes in draft-ietf-mip4-rfc2006bis-04..............109
8. References.................................................109 8. References ................................................ 109
8.1. Normative References..................................109 8.1. Normative References..................................109
8.2. Informative References................................110 8.2. Informative References................................110
Author's Addresses............................................111 Author's Addresses ........................................... 111
Intellectual Property Statement...............................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,
skipping to change at page 109, line 18 skipping to change at page 109, line 18
address information. address information.
A.8. Changes in draft-ietf-mip4-rfc2006bis-04 A.8. Changes in draft-ietf-mip4-rfc2006bis-04
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
Removed RFC 3978 Section 5.2(b) Derivative Works Limitation.
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 112, line 7 skipping to change at page 112, line 7
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.
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 13 change blocks. 
16 lines changed or deleted 16 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/