> => in order to use the API, an application needs to be changed.
> So with only the API, the only way to influence the Co@/H@ choice
> is to change all common applications... So the API will get only
> very limited use and the smart user should still wait for a device
> to fulfill his needs.
>
Yes, the applications need to change to accomodate MobileIP. The goal
should be to change them minimally. Thus a API would help in this case,
as it may turn the knob to tell the kernel which address to use instead
of a default address. The application may not need to specify the exact
COA, the kernel can choose the correct one corresponding to the default
homeaddress ( assuming application has knowledge about the correct home
address). This will be useful for multi-homed mobile nodes as well.
> they need to use COA for local cases in the visited link.
>
> => yes, all the short term not bound to the home applications
> could like to use a Co@. There are a lot of situations where
> to get communications killed by movements is not a problem...
>
It will not be desirable to restart common applications upon movement,
however small their numbers may be.
Then we will loose essence of MobileIP.
> some existing apps would have to be modified or written for
> MIPv6 anyway.
>
> => we have to keep the number of such applications as low as possible.
>
I don't know how many apps fall in this category, may be we should think
about that. Off the top of my head, they could be dns-client, printer-client,
or any application that requests service discovery in the local network.
-Samita
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
