draft-ietf-nemo-ro-space-analysis-02.txt   draft-ietf-nemo-ro-space-analysis-03.txt 
NEMO Working Group C. Ng NEMO Working Group C. Ng
Internet-Draft Panasonic Singapore Labs Internet-Draft Panasonic Singapore Labs
Expires: August 14, 2006 F. Zhao Intended status: Informational F. Zhao
UC Davis Expires: March 19, 2007 UC Davis
M. Watari M. Watari
KDDI R&D Labs KDDI R&D Labs
P. Thubert P. Thubert
Cisco Systems Cisco Systems
February 10, 2006 September 15, 2006
Network Mobility Route Optimization Solution Space Analysis Network Mobility Route Optimization Solution Space Analysis
draft-ietf-nemo-ro-space-analysis-02 draft-ietf-nemo-ro-space-analysis-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 August 14, 2006. This Internet-Draft will expire on March 19, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). 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
MRHA tunnel when the mobile network is away. This results in MRHA tunnel when the mobile network is away. This results in
skipping to change at page 35, line 11 skipping to change at page 35, line 11
Greg Daley, Thierry Ernst, T.J. Kniveton, Erik Nordmark, Alexandru Greg Daley, Thierry Ernst, T.J. Kniveton, Erik Nordmark, Alexandru
Petrescu, Hesham Soliman, Ryuji Wakikawa and Patrick Wetterwald for Petrescu, Hesham Soliman, Ryuji Wakikawa and Patrick Wetterwald for
their various contributions. their various contributions.
10. References 10. References
10.1. Normative References 10.1. Normative References
[1] Ng, C., Thubert, P., Watari, M., and F. Zhao, "Network Mobility [1] Ng, C., Thubert, P., Watari, M., and F. Zhao, "Network Mobility
Route Optimization Problem Statement", Route Optimization Problem Statement",
draft-ietf-nemo-ro-problem-statement-02 (work in progress), draft-ietf-nemo-ro-problem-statement-03 (work in progress),
December 2005. September 2006.
[2] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, [2] 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.
[3] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in [3] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
[4] Ernst, T., "Network Mobility Support Goals and Requirements", [4] 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.
[5] Manner, J. and M. Kojo, "Mobility Related Terminology", [5] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004. RFC 3753, June 2004.
[6] Ernst, T. and H. Lach, "Network Mobility Support Terminology", [6] 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.
10.2. Informative References 10.2. Informative References
[7] Wakikawa, R., Koshiba, S., Uehara, K., and J. Murai, "ORC: [7] Wakikawa, R., Koshiba, S., Uehara, K., and J. Murai, "ORC:
Optimized Route Cache Management Protocol for Network Optimized Route Cache Management Protocol for Network
Mobility", 10th International Conference on Telecommunications, Mobility", 10th International Conference on Telecommunications,
vol 2, pp 1194-1200, February 2003. vol 2, pp 1194-1200, February 2003.
[8] Wakikawa, R. and M. Watari, "Optimized Route Cache Protocol [8] Wakikawa, R. and M. Watari, "Optimized Route Cache Protocol
(ORC)", draft-wakikawa-nemo-orc-01 (work in progress), (ORC)", draft-wakikawa-nemo-orc-01 (work in progress),
skipping to change at page 38, line 5 skipping to change at page 38, line 5
[31] Takagi, Y., Ohnishi, H., Sakitani, K., Baba, K., and S. [31] Takagi, Y., Ohnishi, H., Sakitani, K., Baba, K., and S.
Shimojo, "Route Optimization Methods for Network Mobility with Shimojo, "Route Optimization Methods for Network Mobility with
Mobile IPv6", IEICE Trans. on Comms, vol E87-B, no 3, pp 480- Mobile IPv6", IEICE Trans. on Comms, vol E87-B, no 3, pp 480-
489, March 2004. 489, March 2004.
[32] Ohnishi, H., Sakitani, K., and Y. Takagi, "HMIP based Route [32] Ohnishi, H., Sakitani, K., and Y. Takagi, "HMIP based Route
optimization method in a mobile network", optimization method in a mobile network",
draft-ohnishi-nemo-ro-hmip-00 (work in progress), October 2003. draft-ohnishi-nemo-ro-hmip-00 (work in progress), October 2003.
[33] Lee, C., Zheng, J., and C. Huang, "SIP-based Network Mobility [33] Lee, C., Zheng, J., and C. HUang, "SIP-based Network Mobility
(SIP-NEMO) Route Optimization", draft-ming-nemo-sipnemo-00 (SIP-NEMO) Route Optimization", draft-ming-nemo-sipnemo-00
(work in progress), October 2005. (work in progress), October 2005.
[34] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 [34] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6
Specification", RFC 2473, December 1998. Specification", RFC 2473, December 1998.
[35] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H., [35] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H.,
Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le, K., Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le, K.,
Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, T., Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, T.,
Yoshimura, T., and H. Zheng, "RObust Header Compression (ROHC): Yoshimura, T., and H. Zheng, "RObust Header Compression (ROHC):
skipping to change at page 38, line 41 skipping to change at page 38, line 41
Neighbor Discovery (SEND)", RFC 3971, March 2005. Neighbor Discovery (SEND)", RFC 3971, March 2005.
[40] Aura, T., "Cryptographically Generated Addresses (CGA)", [40] Aura, T., "Cryptographically Generated Addresses (CGA)",
RFC 3972, March 2005. RFC 3972, March 2005.
[41] Zhao, F., "Extensions to Return Routability Test in MIP6", [41] Zhao, F., "Extensions to Return Routability Test in MIP6",
draft-zhao-mip6-rr-ext-01 (work in progress), February 2005. draft-zhao-mip6-rr-ext-01 (work in progress), February 2005.
[42] Arkko, J. and C. Vogt, "A Taxonomy and Analysis of Enhancements [42] Arkko, J. and C. Vogt, "A Taxonomy and Analysis of Enhancements
to Mobile IPv6 Route Optimization", to Mobile IPv6 Route Optimization",
draft-irtf-mobopts-ro-enhancements-04 (work in progress), draft-irtf-mobopts-ro-enhancements-08 (work in progress),
October 2005. May 2006.
[43] Bao, F., Deng, R., Qiu, Y., and J. Zhou, "Certificate-based [43] Bao, F., Deng, R., Qiu, Y., and J. Zhou, "Certificate-based
Binding Update Protocol (CBU)", Binding Update Protocol (CBU)",
draft-qiu-mip6-certificated-binding-update-03 (work in draft-qiu-mip6-certificated-binding-update-03 (work in
progress), March 2005. progress), March 2005.
[44] Moskowitz, R., Nikander, P., Jokela, P., and T. Henderson, [44] Moskowitz, R., "Host Identity Protocol", draft-ietf-hip-base-06
"Host Identity Protocol", draft-ietf-hip-base-04 (work in (work in progress), June 2006.
progress), October 2005.
[45] Henderson, T., "End-Host Mobility and Multihoming with the Host [45] Nikander, P., "End-Host Mobility and Multihoming with the Host
Identity Protocol", draft-ietf-hip-mm-02 (work in progress), Identity Protocol", draft-ietf-hip-mm-04 (work in progress),
July 2005. June 2006.
[46] Calderon, M., Bernardos, C., Bagnulo, M., and I. Soto, [46] Calderon, M., Bernardos, C., Bagnulo, M., and I. Soto,
"Securing Route Optimization in NEMO", Third International "Securing Route Optimization in NEMO", Third International
Symposium on Modeling and Optimization in Mobile, Ad Hoc, and Symposium on Modeling and Optimization in Mobile, Ad Hoc, and
Wireless Networks, WIOPT 2005, pages 248-254, April 2005. Wireless Networks, WIOPT 2005, pages 248-254, April 2005.
Appendix A. Change Log Appendix A. Change Log
o draft-ietf-nemo-ro-space-analysis-03:
* Keepalive release
o draft-ietf-nemo-ro-space-analysis-02: o draft-ietf-nemo-ro-space-analysis-02:
* Changed title of Sect 3.1 from "Basic NEMO Route Optimization" * Changed title of Sect 3.1 from "Basic NEMO Route Optimization"
to "Non-Nested NEMO Route Optimization" to "Non-Nested NEMO Route Optimization"
* Added "Terminology" Sub-section [Issue #17] * Added "Terminology" Sub-section [Issue #17]
* Modifications to Sect 3.1 and 5.1.1 [Issues #18, #20] * Modifications to Sect 3.1 and 5.1.1 [Issues #18, #20]
* Break "Mobility Transparency and Location Privacy" into Sect * Break "Mobility Transparency and Location Privacy" into Sect
skipping to change at page 43, line 5 skipping to change at page 43, line 5
Pascal Thubert Pascal Thubert
Cisco Systems Technology Center Cisco Systems Technology Center
Village d'Entreprises Green Side Village d'Entreprises Green Side
400, Avenue Roumanille 400, Avenue Roumanille
Biot - Sophia Antipolis 06410 Biot - Sophia Antipolis 06410
FRANCE FRANCE
Email: pthubert@cisco.com Email: pthubert@cisco.com
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 43, line 29 skipping to change at page 43, 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. 14 change blocks. 
34 lines changed or deleted 37 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/