draft-ietf-nemo-ro-problem-statement-02.txt   draft-ietf-nemo-ro-problem-statement-03.txt 
NEMO Working Group C. Ng NEMO Working Group C. Ng
Internet-Draft Panasonic Singapore Labs Internet-Draft Panasonic Singapore Labs
Expires: July 1, 2006 P. Thubert Intended status: Informational P. Thubert
Cisco Systems Expires: March 19, 2007 Cisco Systems
M. Watari M. Watari
KDDI R&D Labs KDDI R&D Labs
F. Zhao F. Zhao
UC Davis UC Davis
December 28, 2005 September 15, 2006
Network Mobility Route Optimization Problem Statement Network Mobility Route Optimization Problem Statement
draft-ietf-nemo-ro-problem-statement-02 draft-ietf-nemo-ro-problem-statement-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 July 1, 2006. This Internet-Draft will expire on March 19, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
With current Network Mobility (NEMO) Basic Support, all With current Network Mobility (NEMO) Basic Support, all
communications to and from Mobile Network Nodes must go through the communications to and from Mobile Network Nodes must go through the
bi-directional tunnel established between the Mobile Router and Home bi-directional tunnel established between the Mobile Router and Home
Agent when the mobile network is away. This sub-optimal routing Agent when the mobile network is away. This sub-optimal routing
results in various inefficiencies associated with packet delivery, results in various inefficiencies associated with packet delivery,
such as increased delay and bottleneck links leading to traffic such as increased delay and bottleneck links leading to traffic
congestion, which can ultimately disrupt all communications to and congestion, which can ultimately disrupt all communications to and
skipping to change at page 14, line 17 skipping to change at page 14, line 17
7.1. Normative Reference 7.1. Normative Reference
[1] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, [1] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,
"Network Mobility (NEMO) Basic Support Protocol", RFC 3963, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963,
January 2005. January 2005.
[2] Manner, J. and M. Kojo, "Mobility Related Terminology", [2] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004. RFC 3753, June 2004.
[3] Ernst, T. and H. Lach, "Network Mobility Support Terminology", [3] Ernst, T. and H. Lach, "Network Mobility Support Terminology",
draft-ietf-nemo-terminology-04 (work in progress), October 2005. draft-ietf-nemo-terminology-05 (work in progress), March 2006.
7.2. Informative Reference 7.2. Informative Reference
[4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in [4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
[5] Ernst, T., "Network Mobility Support Goals and Requirements", [5] Ernst, T., "Network Mobility Support Goals and Requirements",
draft-ietf-nemo-requirements-05 (work in progress), draft-ietf-nemo-requirements-05 (work in progress),
October 2005. October 2005.
skipping to change at page 14, line 41 skipping to change at page 14, line 41
November 2001. November 2001.
[7] Petrescu, A., Olivereau, A., Janneteau, C., and H-Y. Lach, [7] Petrescu, A., Olivereau, A., Janneteau, C., and H-Y. Lach,
"Threats for Basic Network Mobility Support (NEMO threats)", "Threats for Basic Network Mobility Support (NEMO threats)",
draft-petrescu-nemo-threats-01 (work in progress), draft-petrescu-nemo-threats-01 (work in progress),
January 2004. January 2004.
[8] Jung, S., Zhao, F., Wu, S., Kim, H-G., and S-W. Sohn, "Threat [8] Jung, S., Zhao, F., Wu, S., Kim, H-G., and S-W. Sohn, "Threat
Analysis on NEMO Basic Operations", Analysis on NEMO Basic Operations",
draft-jung-nemo-threat-analysis-02 (work in progress), draft-jung-nemo-threat-analysis-02 (work in progress),
February 2004. July 2004.
[9] Thubert, P., Wakikawa, R., and V. Devarapalli, "NEMO Home [9] Thubert, P., Wakikawa, R., and V. Devarapalli, "NEMO Home
Network models", draft-ietf-nemo-home-network-models-05 (work Network models", draft-ietf-nemo-home-network-models-06 (work
in progress), October 2005. in progress), February 2006.
[10] Draves, R., "Default Address Selection for Internet Protocol [10] Draves, R., "Default Address Selection for Internet Protocol
version 6 (IPv6)", RFC 3484, February 2003. version 6 (IPv6)", RFC 3484, February 2003.
Appendix A. Change Log Appendix A. Change Log
o draft-ietf-nemo-ro-problem-statement-03:
* Keepalive release
o draft-ietf-nemo-ro-problem-statement-02: o draft-ietf-nemo-ro-problem-statement-02:
* Added Appendix C to illustrate the formation of stalemate * Added Appendix C to illustrate the formation of stalemate
situation in Section 2.7 situation in Section 2.7
* Editorial changes to the Abstract to better reflect the * Editorial changes to the Abstract to better reflect the
document contents document contents
* Minor editorial changes throughout Section 2 * Minor editorial changes throughout Section 2
skipping to change at page 29, line 5 skipping to change at page 29, line 5
Fan Zhao Fan Zhao
University of California Davis University of California Davis
One Shields Avenue One Shields Avenue
Davis, CA 95616 Davis, CA 95616
US US
Phone: +1 530 752 3128 Phone: +1 530 752 3128
Email: fanzhao@ucdavis.edu Email: fanzhao@ucdavis.edu
Intellectual Property Statement Full 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.
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.
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 29, line 29 skipping to change at page 29, 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 (2005). 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. 12 change blocks. 
27 lines changed or deleted 31 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/