Mobile IPv6 and Vista

re: Mobile IPv6 and Vista

guirari mustapha — Sun, 03 Jun 2007 21:47:30 GMT

Even in non VOIP applications, node movement cannot be always transparent because TCP reconnection may force the user to go through a lengthy logon and authentication procedure.

In addition to unloading the application from processing events outside its scope, MIPv6 handles this movement more gracefully as there is no reconnection.

The home agent in MIPv6 has another role which is keeping a mobile node always reachable; without this feature, a node (being mobile or nomad) can be connected in a foreign network without being visible, this in my opinion the killing scenario mainly in a P2P networking application.

re: Mobile IPv6 and Vista

guirari mustapha — Sun, 03 Jun 2007 21:49:16 GMT

Even in non VOIP applications, node movement cannot be always transparent because TCP reconnection may force the user to go through a lengthy logon and authentication procedure.

In addition to unloading the application from processing events outside its scope, MIPv6 handles this movement more gracefully as there is no reconnection.

re: Mobile IPv6 and Vista

Motley — Fri, 08 Jun 2007 19:08:22 GMT

If you are uploading a large file via FTP, a 1-2 second drop would be bad.

The problem with Windows Mobile IPv6 ..

testman — Fri, 08 Jun 2007 20:23:41 GMT

is that Windows XP is not supporting it.

(plz, avoid the "yes, it support CN" answer, CN is usefull as long as MIPv6 is mainstream, but it is not)

Vista also have limited support of latest mobile IPv6 specifications (see NEMO).

This means MS customer only have one solution : go to linux to get a complete end-to-end mobile IPv6 solution (desktop to server).

Another fun is to see that almost none of the MS servers are IPv6 enabled, which shows also the MS "internal support" to the IPv6 technology.