RE: [mobile-ip] FW: I-D ACTION:draft-tsirtsis-dsmip-problem-00.tx t

Pekka, 

Thanks for the comments. Response below.

 > Thanks for putting up this draft.  I think it is very useful
 > in defining the problem.
 > 
 > However, unfortunately I do not personally agree at all with
 > the recommendations in the draft:
 > 
 > To me, it looks like such a solution might be workable, but the
 > resulting protocols might be very complex.  Too complex, in my
 > humble opinion.

=> This week we plan on submitting at least one solution
and we can assess complexity from there. But I'd like to 
emphasise that we are not aiming to have one protocol that
will solve everything. Even now, MIPv4 cannot provide all
of the features in MIPv6. I'd completely agree with the 
complexity argument if that were our goal, but we only
aim to have a transitional solution. 

 > 
 > HIP provides already now an implemented, demonstrated alternativity.
 > It does not only allow seamless mobility between IPv4 and IPv6, but
 > it also integrates multi-address multi-homing with mobility.
 > 
 > For an early draft describing what has been implemented, see
 > draft-nikander-hip-mm-00.txt.  While that requires much more work,
 > for example, to determine how to deal with NAT devices etc, the
 > basic approach has been implemented and demonstrated.
 > 
 > Hence, I would request that you drop the Mobile IP specific
 > recommendations from the problem statement draft, or at least
 > acknowledge that there are other approaches that may be able
 > to solve the problem in a different and perhaps better way.

=> Sure there are other approaches. However, our limiting factor
is existing deployment. We want to deal with existing problems
on the Internet that can be solved gradually. HIP does not do
that now because a) it does not exist in standards or products,
b) clearly not deployed, c) it has difficult problems that
have not begun to be addressed (e.g. hierarchical name space ...etc).
At this moment in time it is an idea that was prototyped and
we all know the time it takes from conception to deployment. 
Look at v6 which was introduced for a much more tangible problem
than the problems HIP is intended to solve, yet, 10 years later, 
deployment is still in its infancy (on a global level). So we need
to realise these issues (in fact they are _the_ issues to
think about) and not only look at the technical challenges.

Hesham

 > 
 > --Pekka Nikander
 > 
 >