![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi Vijay, on 2006-04-21 00:59 Vijay Devarapalli said the following: > Hi George, > > Tsirtsis, George wrote: >> Raj, >> >> The purpose of DS-MIPv4 is slightly different than what you present >> below. Keep in mind that Mobile IPv4 (unlike Mobile IPv6) is deployed >> today in multiple networks, corporate and operator owned. >> >> What we are trying to do is to allow these operators to provide IPv6 to >> their customers with an incremental approach that fits their deployment >> scenario (mobility) and without having to replace their entire >> infrastructure. > > I already disputed this argument. whats incremental > about deploying IPv6? compared to deploying IPv6 > services, upgrading your home agent and mobile node > from MIPv4 to MIPv6 would be trivial. I don't buy > this argument. So I guess I'll have to repeat my refutation too. Whether you buy it or not, being able to deploy a MIPv6 agent on your client platform is vitally dependent on the commercial availability of fine client software for that platform. Whether you as an individual find it trivial to perform an upgrade is neither here nor there in this context. And furthermore, upgrading the client in thousands or millions of deployed low-end devices can hardly be considered 'trivial', even if the software is available and will fit in the flash memory of the device, which is not at all guaranteed. Henrik
Attachment:
signature.asc
Description: OpenPGP digital signature
--
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/