Analysis of Multihoming in Network Mobility Support
RFC 4980

 
Document Type RFC - Informational (October 2007; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4980 (Informational)
Telechat date
Responsible AD Jari Arkko
Send notices to nemo-chairs@ietf.org,chanwah.ng@sg.panasonic.com,euna@kt.co.kr,marcelo@it.uc3m.es
Network Working Group                                              C. Ng
Request for Comments: 4980                      Panasonic Singapore Labs
Category: Informational                                         T. Ernst
                                                                   INRIA
                                                                 E. Paik
                                                                      KT
                                                              M. Bagnulo
                                                                    UC3M
                                                            October 2007

          Analysis of Multihoming in Network Mobility Support

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Abstract

   This document is an analysis of multihoming in the context of network
   mobility (NEMO) in IPv6.  As there are many situations in which
   mobile networks may be multihomed, a taxonomy is proposed to classify
   the possible configurations.  The possible deployment scenarios of
   multihomed mobile networks are described together with the associated
   issues when network mobility is supported by RFC 3963 (NEMO Basic
   Support).  Recommendations are offered on how to address these
   issues.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Classification . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  (1,1,1): Single MR, Single HA, Single MNP  . . . . . . . .  6
     2.2.  (1,1,n): Single MR, Single HA, Multiple MNPs . . . . . . .  6
     2.3.  (1,n,1): Single MR, Multiple HAs, Single MNP . . . . . . .  7
     2.4.  (1,n,n): Single MR, Multiple HAs, Multiple MNPs  . . . . .  8
     2.5.  (n,1,1): Multiple MRs, Single HA, Single MNP . . . . . . .  8
     2.6.  (n,1,n): Multiple MRs, Single HA, Multiple MNPs  . . . . .  9
     2.7.  (n,n,1): Multiple MRs, Multiple HAs, Single MNP  . . . . .  9
     2.8.  (n,n,n): Multiple MRs, Multiple HAs, Multiple MNPs . . . . 10

Ng, et al.                   Informational                      [Page 1]
RFC 4980            Analysis of Multihoming in NEMO         October 2007

   3.  Deployment Scenarios and Prerequisites . . . . . . . . . . . . 11
     3.1.  Deployment Scenarios . . . . . . . . . . . . . . . . . . . 11
     3.2.  Prerequisites  . . . . . . . . . . . . . . . . . . . . . . 13
   4.  Multihoming Issues . . . . . . . . . . . . . . . . . . . . . . 14
     4.1.  Fault Tolerance  . . . . . . . . . . . . . . . . . . . . . 14
       4.1.1.  Failure Detection  . . . . . . . . . . . . . . . . . . 15
       4.1.2.  Path Exploration . . . . . . . . . . . . . . . . . . . 16
       4.1.3.  Path Selection . . . . . . . . . . . . . . . . . . . . 17
       4.1.4.  Re-Homing  . . . . . . . . . . . . . . . . . . . . . . 19
     4.2.  Ingress Filtering  . . . . . . . . . . . . . . . . . . . . 19
     4.3.  HA Synchronization . . . . . . . . . . . . . . . . . . . . 21
     4.4.  MR Synchronization . . . . . . . . . . . . . . . . . . . . 22
     4.5.  Prefix Delegation  . . . . . . . . . . . . . . . . . . . . 23
     4.6.  Multiple Bindings/Registrations  . . . . . . . . . . . . . 23
     4.7.  Source Address Selection . . . . . . . . . . . . . . . . . 23
     4.8.  Loop Prevention in Nested Mobile Networks  . . . . . . . . 24
     4.9.  Prefix Ownership . . . . . . . . . . . . . . . . . . . . . 24
     4.10. Preference Settings  . . . . . . . . . . . . . . . . . . . 25
   5.  Recommendations to the Working Group . . . . . . . . . . . . . 26
   6.  Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 28
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 28
   8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 29
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 29
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 29
   Appendix A.  Alternative Classifications Approach  . . . . . . . . 32
     A.1.  Ownership-Oriented Approach  . . . . . . . . . . . . . . . 32
       A.1.1.  ISP Model  . . . . . . . . . . . . . . . . . . . . . . 32
       A.1.2.  Subscriber/Provider Model  . . . . . . . . . . . . . . 33
     A.2.  Problem-Oriented Approach  . . . . . . . . . . . . . . . . 34
   Appendix B.  Nested Tunneling for Fault Tolerance  . . . . . . . . 35
     B.1.  Detecting Presence of Alternate Routes . . . . . . . . . . 35
     B.2.  Re-Establishment of Bi-Directional Tunnels . . . . . . . . 36
       B.2.1.  Using Alternate Egress Interface . . . . . . . . . . . 36
       B.2.2.  Using Alternate Mobile Router  . . . . . . . . . . . . 36
Show full document text