In your previous mail you wrote: An alternative approach could be: If the application cares about the source address, it can use the Mobile IP API to figure out which ones are home address, which ones are care-of address, and than explicitly "bind" the socket to the desired address. IMO, this would also satisfy the needs of the Mobile IPv6 mobile node. => this is similar to what I implemented in the past. But a function giving the list of addresses with status is not enough, the best is to give the home address and the care-of address for a destination. As first info is getsockname() for bound sockets, I added a clone of getsockname() which returns the real source address after MIPv6 processing. Note this doesn't solve the need of a control for smarter choice between Co@/H@. I proposed some and implemented two: use always the H@ and use it but a Co@ when the destination is in the same link then a Co@. They were global (still better than none :-).
Thanks [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] --------------------------------------------------------------------
