In your previous mail you wrote: > 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... Having per-application or per-process overrides of anything if rife with issues since an application isn't a single unit; it consists of several independently developped pieces (libraries being the main source of the many pieces). Thus while the developper know that the pieces s/he has written want to turn the knob to affect the sockets in that piece of code, making the knob be per-process means that it will also affect sockets in libraries. Thus turning the per-process knob can have unknown side effects. Hence the need to have a per-socket knob. => you have access to a per-socket knob when applications can locally tune their context. IMHO to affect sockets in libraries is a good point. For instance usually we'd like to use the local DNS but not always because of views/two heads... What I propose should provide the maximal flexibility.
Thanks [EMAIL PROTECTED] PS: it can be implemented with a [gs]etsockopt() and some kind of middleware. So our proposals are not really exclusive. In the case of home/care-of address, my concern from the beginning is that a knob is not enough, we need a smarter rule using the proximity (i.e., prefix matching length) of addresses in order to do the right choice. For instance usually with a destination in a prefix of the visited link, a care-of is better than the home address, and with a destination in the home site, the home address is nearly always better. -------------------------------------------------------------------- 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] --------------------------------------------------------------------
