Load Balance for Distributed Home Agents in Mobile IPv6 Authors: R. ZhangChina Telecom X.L. Huang UCLA K. Zhang Tsinghua Univ. H. DengHitachi (China) draft-deng-mip6-ha-loadbalance-01.txt

Agenda Origination Solution Summary

Origination 1 Problem statement: Load Balancing draft-jfaizan-mipv6-ha-reliability-01.txt 2 DHAAD can be only used for stationary load balance among multiple HAs. 3 No proactive notification message used 4 HA still has a short time tentative traffic burden (Triangle routing)

Solution Not only the MN’s registration information, but also the tunneled data traffic information will be used for dynamic load balance. Proactive notification message from HA to MN about replacement

Solution (cont.1) Extended Home Agent List (Rough number, not precise, is used) 1.Registered rough MN Number at a HA 2.Queue Size

Solution (cont.2) New Load Balance Information Option Format | Type | Length | Reserved | | Queue Size | Registered MN Number |

Solution (cont.3) HA Reassignment 1.A timer is attached for each entry in the binding update cache at a HA. 2.HA will proactive select and notify the MN about replacement of a new HA. 3.Frequency of selecting new HA depends on HA reassignment algorithm.

Left issues for solution SA issue will be considered in next document How to define the rough number of registered number of MN and buffer size of HA will be explained in detail A home agent handover message should be defined? A common protocol for MIP4 is needed?

Summary Main target of our approach is to make dynamic load balance among distributed HAs. Our approach is useful for a specific case such as proactive notification of replacement of new HA. We believe it is still ongoing work so comments and feedback are appreciated. Thanks Brian Haley’s comments