In your previous mail you wrote:
A draft has been submitted to address source address selection at
the per-socket (and per apps) basis. Currently it discusses preferences
of source address selection by the application for privacy addresses,
mobileipv6 addresses and Cryptographically generated addresses.
Thus the application can reverse the sense of default source address
selection by using the proposed APIs.
=> I have a major concern about the style of the API: it is at the
socket level ([gs]etsockopt()) when it should be in the context of
applications:
- nobody wants to modify every applications in order to use the API
(an unfortunately many applications can want to toggle one of the
address selection knobs)
- at the opposite a global knob is not flexible again.
What I propose is to put the policy in the context of applications
(Unix user structure, environment, etc, even monitors have this kind
of things) so one can tune the address selection before launching
applications. When the context can be managed from applications
(the usual case), this makes [gs]etsockopt() no more necessary.
And global flags can be replaced by default values...
Regards
[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]
--------------------------------------------------------------------
