Multiple Care-of Address Registration on Mobile IPv6 Ryuji Wakikawa Keisuke Uehara Thierry Ernst Keio University / WIDE

Motivation MN utilizes all the active interfaces simultaneously by dividing flows to each interfaces –MN should register all the active CoAs to HA and CNs, otherwise packets are dropped if MN uses an unregistered CoA –A lot of advantages in terms of QoS, Multihoming, Redundancy, Fault Tolerance, Fast Vertical Hand-off Upper layers are unaware of multiple CoAs because all the CoAs are bounded to the same HoA –Session continuance is guaranteed Any Policy Management to utilize all the registered CoAs should be accepted –This draft does not propose any new policy management, but multiple CoA registrations only!!!

Overview Interface Identification Number (IFID) –This randomly generated number is used to distinguish each interface on MN Interface Priority (IFPRI) –Priority value is used to select the primary CoA Care-of Address Information sub-option –The sub-option used in BU to notify IFID and IFPRI to either HA or CNs MN CN CoA1 IFID1 CoA2 IFID2 Binding Cache HoA + IFID1 – CoA1 HoA + IFID2 － CoA2 VoIP, DVTS smtp, pop

CoA1 IFID1 CoA2 IFID2 CoA Registration MN needs to send a different BU per each CoA HA updates a BC entry which matches HoA and IFID if a CoA sub-option is available MN can manage each CoA independently –If a CoA is changed, MN just updates the changed CoA Binding Cache HoA + IFID1 – CoA1 HoA + IFID2 － CoA2 MN/MR Internet HA 1. Binding Update 2. Binding Acknowledgement IP header HoABU (M)CoA InfoIPsec

CoA1 IFID1 CoA2 IFID2 Return Routability CN calculates Care-of Keygen Token with IFID and IFPRI Binding Cache HoA + IFID1 – CoA1 HoA + IFID2 － CoA2 MN Internet HA CN 1 CoT and CoTI with IFID + IFPRI 2. Binding Update with IFID+IFPRI Binding Cache HoA + IFID1– CoA1 HoA + IFID2 － CoA2

Binding Management Registration –BU with CoA sub-option a receiver updates only the corresponding binding cache entry –BU without CoA sub-option a receiver registers to a single binding as in current MIPv6 draft De-registration –BU with CoA sub-option a receiver deletes only the corresponding binding –BU without CoA sub-option a receiver deletes all the registered bindings –Returning Home When one of interfaces is attached to the home link, MN must delete all the bindings from CN and HA

How to select Binding? Any policy management and notification should be supported Priority Based Binding Selection –HA and CN can select the best binding by each priority value Policy Based Binding Selection –MN can notify own policy to HA and CN to select the most ideal binding –The policy can be notified and managed by either MIP signaling, applications, policy management daemon, static configuration –IFID can be used as an ID of each policy entry like SPI of IPsec