> > The psychological benefit of the two flags is that we don't have to choose > > the default; we can say that any application which has an explicit preference > > should always invoke the API to state that preference. > > I don't follow. This is true regardless of whether there is one bit or > two. If an application doesn't care, it doesn't invoke the API at all.
My point is that you have a socket option to say "FOO" it is very easy for app writers to assume that "FOO" isn't set by default; that is the case for all the existing socket options I can think of. But in this case the system admin is free to change the default. Thus how do we make this departure from existing practise clear to the app programmers? They need to turn off "FOO" is they don't want it since "FOO" might be the default set my the system admin. Having socket options that you use to set "FOO" or "NOTFOO" with no hard default I think makes the departure from existing practise more clear. Erik -------------------------------------------------------------------- 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] --------------------------------------------------------------------
