Analysis of Multihoming in Mobile IPv6

1
Analysis of Multihoming in Mobile IPv6

• draft-montavont-mobileip-multihoming-pb-statement-
  04.txt
• N. Montavont (NIST)
• R. Wakikawa (Keio University)
• T. Ernst (Keio University)
• C. Ng (Panasonic Singapore Labs )
• K. Kuladinithi (University of Bremen )

2
Multihomed MIP6 node
A MIP6 nodes with several HoAs/CoAs
HA1
HA2
GPRS
Ethernet
802.11
CoA1/CoA2
CoA3
CoA4
HoA2
HoA1
Mobile Node
3
Structure of the draft

• Multihoming / MIP6 related terminology
• Requirements
• Taxonomy
• Scenarios
• Issues
• IPv6 related issues
• MIPv6 related issues
• Implementation related issues

4
Taxonomy

• x number of active interfaces
• y number of Home Addresses (HoAs)
• z number of Care-of Addresses (CoAs)
• End up with 9 scenarios
• (1,1,1) is not a multihoming configuration
• (n,1,1) is a very special case
• (1,,) and (n,,) are often very close
• Remove the xnumber of interfaces parameter from
  this taxonomy
• This taxonomy does not highlight the difference
  between
• Paths between MN and HAs
• Paths between HAs and CNs

5
MIPv6 related issues (6.2.1) Binding multiple
CoAs to a given HoA

• Scenarios (,,n)
• Provide
• Redundancy
• Fault recovery
• Allows to set policies
• Load balancing
• Load sharing

6
MIPv6 related issues (6.2.2) Using a HoA as a CoA

• Scenarios (,n,)

New binding HoA2 lt-gt HoA1
HA1
HA2
MN
HoA1 becomes the CoA of HoA2
7
MIPv6 related issues (6.2.3) Simultaneous
locationin home and foreign networks

• Scenarios (,,)

How to bind CoA1 to HoA1, for redundancy purpose
for example?
Visited network
HA1
How to use interface 1, in such a way that if you
change CoA1, your data traffic has not to be
re-initiated
interface 1
interface 2
MN
8
Summary of issues