Re: [Mip4] FW: I-D ACTION:draft-tsirtsis-v4v6-mipv4-01.txt

[Basavaraj Patil <basavaraj.patil at nokia.com>]

Kent,

There is obviously some degree of reuse with using MIP4 as a tunnel setup
mechanism for carrying IPv6 packets. But it comes at the cost of upgrading
your HA as well as existing clients. And given that an operator/enterprise
has decided to deploy IPv6 (which is the reason for having the MIP4 client
access this network), I believe the deployment has already taken the plunge
towards IPv6. But as someone said given the incremental nature of v6
deployments that we are likely to see, such a solution would address a gap.

But I agree that a solution that enables IPv6 access for (M)IPv4 enabled
devices and vice-versa would be a good thing. And if operators/enterprises
feel the need for such access, at least the IETF would have a solution. It
is better than having all kinds of hacks.

-Raj


On 4/20/06 6:58 PM, "ext Kent Leung (kleung)" <kleung at cisco.com> wrote:

> Hi Vijay.  It's not just the client, but the network infrastructure such
> as HA, AAA, provisioning system, logging, accounting, OAM, etc. that can
> be leveraged to support IPv6 with minimum change.  What's wrong with
> MIPv4 to support IPv6/IPv4 and MIPv6 to support IPv/IPv4 depending on
> the environment of deployment?
> 
> Kent
> 
>> 
>> the clients are being upgraded for IPv6 services anyway.
>> whats special about upgrading the clients from MIPv4 to MIPv6?
>> 
>> Vijay
>> 


-- 
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/