In your previous mail you wrote:
> That's what I was aiming for; a short and simple advanced api socket
> extension doc as a guideline for MIPv6 compatible applications.
The default address selection draft contemplates about such an API:
Implementations should provide a mechanism allowing an application
to reverse the sense of this preference and prefer care-of addresses
over home addresses (e.g., via appropriate API extensions). Use of
the mechanism should only affect the selection rules for the
invoking application.
=> this suggests a setsockopt() API which is not usable.
What I suggest is:
- a better solution for address selection exceptions
- a get_the_care-of_which_shall_be_used for very special applications
(which need this information to explicitely bind sources)
I think we should work on a separate Mobile IP API, that can encompass
this and more.
=> no, only the second item should be in the Mobile IP API. The first one
has to go in an address selection control API.
[EMAIL PROTECTED]
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
