![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
on 2006-04-21 01:38 Vijay Devarapalli said the following: ... >>> 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. > > they are available. I don't see this as an issue. I understand that you don't see it as an issue. However, as you aren't the one who will have to upgrade your infrastructure, and some people who are deploying MIP4 are asking for this, I don't see that we can ignore them because this is not an issue for you... >> Whether you as an >> individual find it trivial to perform an upgrade is neither here >> nor there in this context. > > I am not talking about "myself". I am talking > about an enterprise upgrading their clients from > MIPv4 to MIPv6 while upgrading them to use IPv6 > services. You're assuming that the device which is running IPv6 apps is the same as the one with the MIPv4 client. This is not necessarily true. >> 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. > > the clients are being upgraded for IPv6 services > anyway. whats special about upgrading the clients > from MIPv4 to MIPv6? Nope. Think a phone model which may have just enough flash for MIPv4, but not enough flash for the additional IPsec and MIPv6 functionality. Things aren't necessarily as simple as you suggest for those who have MIPv4 deployed in small devices today, I believe. 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/