draft-ietf-nemo-home-network-models-03.txt   draft-ietf-nemo-home-network-models-04.txt 
Network Mobility P. Thubert Network Mobility P. Thubert
Internet-Draft Cisco Internet-Draft Cisco
Expires: September 16, 2005 R. Wakikawa Expires: December 26, 2005 R. Wakikawa
Keio University Keio University
V. Devarapalli V. Devarapalli
Nokia Nokia
March 18, 2005 June 24, 2005
NEMO Home Network models NEMO Home Network models
draft-ietf-nemo-home-network-models-03 draft-ietf-nemo-home-network-models-04
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance with have been or will be disclosed, and any of which he or she becomes
RFC 3668. 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 other groups may also distribute working documents as Internet-
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 September 16, 2005. This Internet-Draft will expire on December 26, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
This paper documents some usage patterns and the associated issues This paper documents some usage patterns and the associated issues
when deploying a Home Network for NEMO-enabled Mobile Routers, when deploying a Home Network for NEMO-enabled Mobile Routers,
conforming the NEMO Basic Support draft [8]. The aim here is conforming the NEMO Basic Support draft [8]. The aim here is
specifically to provide some examples of organization of the Home specifically to provide some examples of organization of the Home
Network, as they were discussed in NEMO related mailing lists. Network, as they were discussed in NEMO related mailing lists.
Table of Contents Table of Contents
skipping to change at page 2, line 33 skipping to change at page 2, line 33
6.3 Applicability . . . . . . . . . . . . . . . . . . . . . . 13 6.3 Applicability . . . . . . . . . . . . . . . . . . . . . . 13
6.4 Deployment Caveats . . . . . . . . . . . . . . . . . . . . 13 6.4 Deployment Caveats . . . . . . . . . . . . . . . . . . . . 13
6.4.1 Home Agent Side . . . . . . . . . . . . . . . . . . . 13 6.4.1 Home Agent Side . . . . . . . . . . . . . . . . . . . 13
6.4.2 Mobile Router side . . . . . . . . . . . . . . . . . . 14 6.4.2 Mobile Router side . . . . . . . . . . . . . . . . . . 14
7. Virtual Home Network . . . . . . . . . . . . . . . . . . . . . 15 7. Virtual Home Network . . . . . . . . . . . . . . . . . . . . . 15
7.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 15 7.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 15
7.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 16 7.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 16
8. Mobile Home . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. Mobile Home . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 17 8.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 17
8.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 18 8.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 18
9. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 9. IANA considerations . . . . . . . . . . . . . . . . . . . . . 19
9.1 Changes from version 00 to 01 . . . . . . . . . . . . . . 20 10. Security Considerations . . . . . . . . . . . . . . . . . . 19
9.2 Changes from version 01 to 02 . . . . . . . . . . . . . . 20 11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.3 Changes from version 02 to 03 . . . . . . . . . . . . . . 20 11.1 Changes from version 00 to 01 . . . . . . . . . . . . . . 20
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 11.2 Changes from version 01 to 02 . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 11.3 Changes from version 02 to 03 . . . . . . . . . . . . . . 20
11.4 Changes from version 03 to 04 . . . . . . . . . . . . . . 20
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
13.1 normative reference . . . . . . . . . . . . . . . . . . . 21
13.2 informative reference . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22
A. Returning Home emulation in the virtual case . . . . . . . . . 23 A. Returning Home emulation in the virtual case . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . 24 Intellectual Property and Copyright Statements . . . . . . . . 24
1. Introduction 1. Introduction
This document assumes that the reader is familiar with IPv6 Mobility This document assumes that the reader is familiar with IPv6 Mobility
as defined in [7], with the NEMO Basic Support [8] and with the NEMO as defined in [7], with the NEMO Basic Support [8] and with the NEMO
terminology document [9]. terminology document [9].
skipping to change at page 17, line 30 skipping to change at page 17, line 30
An example of that is the Cab Co configuration. When a Taxi Company An example of that is the Cab Co configuration. When a Taxi Company
owns a /32 prefix, this prefix is advertised at a fixed point in the owns a /32 prefix, this prefix is advertised at a fixed point in the
Head Quarters. Regional offices are deployed around the world. Even Head Quarters. Regional offices are deployed around the world. Even
though these regional offices are relatively stable in terms of though these regional offices are relatively stable in terms of
location and prefix requirement -say this changes every few years- location and prefix requirement -say this changes every few years-
making them mobile allows a simpler management when a move has to making them mobile allows a simpler management when a move has to
take place, or should the ISP service change. take place, or should the ISP service change.
global Home Network CAB:C0::/32 owned by HQ global Home Network CAB:C0::/32 owned by HQ
<-------------------------------------------------------------------> <------------------------------------------------------------------>
HQ extended Home Net Mobile Home for SFO office HQ extended Home Net Mobile Home for SFO office
(casa) (casa)
CAB:C0:CA5A::/48 CAB:C0:5F0::/48 CAB:C0:CA5A::/48 CAB:C0:5F0::/48
<----------------------------> ... <--------------------------------> <----------------------------> ... <------------------------------->
| |
Home for offices HQ | Home for offices HQ |
CAB:C0:CA5A:CA5A::/64 MN | CAB:C0:CA5A:CA5A::/64 MN |
<----------------------><----> | <----------------------><----> |
CAB:C0:CA5A:CA5A::CA5A | CAB:C0:CA5A:CA5A::CA5A |
CAB:C0:CA5A:CA5A::CA5B | CAB:C0:CA5A:CA5A::CA5B |
are HAs on link with for each office a route like | are HAs on link with for each office a route like |
| |
CAB:C0:CA5A:CA5A::5F0 <---------------------- via CAB:C0:CA5A:CA5A::5F0 <---------------------- via
is the Home addr is the Home addr
skipping to change at page 19, line 9 skipping to change at page 19, line 9
8.2 Applicability 8.2 Applicability
This complex topology applies to large distributed fleet, mostly if This complex topology applies to large distributed fleet, mostly if
there is a single interchange point with the internet (e.g. a NAT or there is a single interchange point with the internet (e.g. a NAT or
a socks farm) where the super Home Agent could be located. a socks farm) where the super Home Agent could be located.
One specific benefit is that when 2 Mobile Routers travel together One specific benefit is that when 2 Mobile Routers travel together
with a common Home Agent, the traffic between the 2 is not with a common Home Agent, the traffic between the 2 is not
necessarily routed via the infrastructure, but can stay confined necessarily routed via the infrastructure, but can stay confined
within the mobile cloud, the Mobile Home Agent acting as a within the mobile cloud, the Mobile Home Agent acting as a rendez-
rendez-vous point between the Mobile Routers. This applies vous point between the Mobile Routers. This applies particularly
particularly well for a fleet at sea when the long haul access may be well for a fleet at sea when the long haul access may be as expensive
as expensive as a satellite link. as a satellite link.
9. Changes 9. IANA considerations
An issue list is maintained at This document does not require any IANA action.
http://www.mobilenetworks.org/~pthubert/draft-ietf-nemo-home-network-models-issues.html .
9.1 Changes from version 00 to 01 10. Security Considerations
This document only explains how a home network can be deployed to
support Mobile Routers and does not introduce any additional security
concerns. Please see [RFC3963] for security considerations for the
NEMO Basic Support protocol.
11. Changes
An issue list is maintained at http://www.mobilenetworks.org/
~pthubert/draft-ietf-nemo-home-network-models-issues.html .
11.1 Changes from version 00 to 01
Removed terminology (moved to the Nemo terminology draft). Removed terminology (moved to the Nemo terminology draft).
Added an applicability statement for all documented cases Added an applicability statement for all documented cases
9.2 Changes from version 01 to 02 11.2 Changes from version 01 to 02
Issue 1: Editorial Issue 1: Editorial
Issue 2: Added a caveat part in extended and aggregated sections. Issue 2: Added a caveat part in extended and aggregated sections.
Also added a MIP Home Network section prior to those. Also added a MIP Home Network section prior to those.
Issue 4: Added a subsection to the extended case for the case when Issue 4: Added a subsection to the extended case for the case when
the mr takes a home address from its MNP the mr takes a home address from its MNP
9.3 Changes from version 02 to 03 11.3 Changes from version 02 to 03
Issue 5: Editorial fixes. Issue 5: Editorial fixes.
10. Acknowledgements 11.4 Changes from version 03 to 04
Issue 6: Pass idnits. Thanks Henrik for this great tool :)
12. Acknowledgements
The authors wish to thank: The authors wish to thank:
Erik Nordmark, Kent Leung, Thierry Ernst, TJ Kniveton, Patrick Erik Nordmark, Kent Leung, Thierry Ernst, TJ Kniveton, Patrick
Wetterwald, Alexandru Petrescu and David Binet. for their Wetterwald, Alexandru Petrescu and David Binet. for their
contributions. contributions.
11 References 13. References
13.1 normative reference
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) [2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification", RFC 2460, December 1998. Specification", RFC 2460, December 1998.
[3] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery [3] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery
for IP Version 6 (IPv6)", RFC 2461, December 1998. for IP Version 6 (IPv6)", RFC 2461, December 1998.
[4] Thomson, S. and T. Narten, "IPv6 Stateless Address [4] Thomson, S. and T. Narten, "IPv6 Stateless Address
Autoconfiguration", RFC 2462, December 1998. Autoconfiguration", RFC 2462, December 1998.
[5] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) [5] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
Addressing Architecture", RFC 3513, April 2003. Addressing Architecture", RFC 3513, April 2003.
[6] Manner, J. and M. Kojo, "Mobility Related Terminology", RFC [6] Manner, J. and M. Kojo, "Mobility Related Terminology",
3753, June 2004. RFC 3753, June 2004.
[7] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support in [7] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
[8] Devarapalli, V., Wakikawa, R., Petrescu, A. and P. Thubert, [8] 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.
[9] Ernst, T. and H. Lach, "Network Mobility Support Terminology", [9] Ernst, T. and H. Lach, "Network Mobility Support Terminology",
draft-ietf-nemo-terminology-03 (work in progress), February draft-ietf-nemo-terminology-03 (work in progress),
2005. February 2005.
[10] Ernst, T., "Network Mobility Support Goals and Requirements", [10] Ernst, T., "Network Mobility Support Goals and Requirements",
draft-ietf-nemo-requirements-04 (work in progress), February draft-ietf-nemo-requirements-04 (work in progress),
2005. February 2005.
13.2 informative reference
[11] Thubert, P., "Global HA to HA protocol", [11] Thubert, P., "Global HA to HA protocol",
draft-thubert-nemo-global-haha-00 (work in progress), October draft-thubert-nemo-global-haha-00 (work in progress),
2004. October 2004.
[12] Ernst, T., "Analysis of Multihoming in Network Mobility [12] Ernst, T., "Analysis of Multihoming in Network Mobility
Support", draft-ietf-nemo-multihoming-issues-02 (work in Support", draft-ietf-nemo-multihoming-issues-02 (work in
progress), February 2005. progress), February 2005.
Authors' Addresses Authors' Addresses
Pascal Thubert Pascal Thubert
Cisco Systems Cisco Systems
Village d'Entreprises Green Side Village d'Entreprises Green Side
400, Avenue de Roumanille 400, Avenue de Roumanille
Batiment T3 Batiment T3
Biot - Sophia Antipolis 06410 Biot - Sophia Antipolis 06410
FRANCE FRANCE
Phone: +33 4 97 23 26 34 Phone: +33 4 97 23 26 34
EMail: pthubert@cisco.com Email: pthubert@cisco.com
Ryuji Wakikawa Ryuji Wakikawa
Keio University and WIDE Keio University and WIDE
5322 Endo Fujisawa Kanagawa 5322 Endo Fujisawa Kanagawa
252-8520 252-8520
JAPAN JAPAN
EMail: ryuji@sfc.wide.ad.jp Email: ryuji@sfc.wide.ad.jp
Vijay Devarapalli Vijay Devarapalli
Nokia Research Center Nokia Research Center
313 Fairchild Drive 313 Fairchild Drive
Mountain View, CA 94043 Mountain View, CA 94043
USA USA
EMail: vijay.devarapalli@nokia.com Email: vijay.devarapalli@nokia.com
Appendix A. Returning Home emulation in the virtual case Appendix A. Returning Home emulation in the virtual case
When a Home Link is virtual, all traffic to and from the Mobile When a Home Link is virtual, all traffic to and from the Mobile
Network is sent through the bi-directional tunnel even at the Home Network is sent through the bi-directional tunnel even at the Home
Link. This section describes one possible mechanism that extends Link. This section describes one possible mechanism that extends
NEMO Basic Support to eliminate this tunneling overhead. NEMO Basic Support to eliminate this tunneling overhead.
Although the Home Link is virtual, the Home Agent has at least one Although the Home Link is virtual, the Home Agent has at least one
physical link to communicate with the external world. One or several physical link to communicate with the external world. One or several
 End of changes. 

This html diff was produced by rfcdiff 1.24, available from http://www.levkowetz.com/ietf/tools/rfcdiff/