On Tue, 2003-03-25 at 14:17, Erik Nordmark wrote:
> > And if the application specifies both "X" and "not X"?
>
> That would be an error.
Exactly. The kernel needs to test this and return an error ==> bloat.
> So do we make the one bit PREFER_SRC_TMP or PREFER_SRC_PUBLIC?
PUBLIC is the obvious default since that is the current expected
behaviour, although the system administrator might decide to change it.
> Will applications that have a preference for either always explicitly state it
> by invoking the API?
They should. The system default might be configurable by the admin so
the apps can't rely on a particular default.
> 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.
MikaL
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
