Re: draft-zhang-mip6-find-reg-ha-00.txt

In the future deployment of mobile IPv6, there may be several home agent 
in home network simultaneously for load balancing and reliability. So, some 
mobile nodes may select home agent A to register its mobility service, and 
some mobile nodes select home agent B to register its mobility service.
When the operator of home network wants to know the status of some 
service associated with mobile node, he don't know which home agent that
the mobile node is registered to.  He can not retrieve the needed 
information of mobile node. So, I think that there should be a general 
mechanism to provide.
This mechanism mainly provides to carriers for operation and maintenance
of their networks. It complements the basic mobile IPv6 specification.

Jian

----- Original Message ----- 
From: "Basavaraj Patil" <basavaraj.patil@xxxxxxxxx>
To: <hwzhj@xxxxxxxxxx>; <mip6@xxxxxxxx>
Cc: "Gopal Dommety" <gdommety@xxxxxxxxx>
Sent: Thursday, March 09, 2006 4:31 AM
Subject: I-D: draft-zhang-mip6-find-reg-ha-00.txt


> 
> After reviewing this I-D, I do not agree that there is a real problem in
> terms of determining which is the HA serving an MN.
> Hence I do not believe it makes sense to have it on the agenda at the MIP6
> WG meeting at IETF65.
> 
> Please discuss why the problem as stated in the I-D makes sense before we
> can consider it for including it in the final agenda.
> 
> -Basavaraj
>