> The doc says that applications get to override the default, that's all
> that is needed.   The mechanism by which the application decides it should
> make that decision (and whether it occurs in the app code itself, or in
> some provided library routine) are way beyond the scope here.
> 

I don't think this is way beyond the scope here at all - this is 
fundamentally an API issue, and it seems like it would actually be 
useful and appropriate to talk about it in those terms.  Granted 
there are multiple APIs in use.  But the point is that either
having different implementations of the same API do the address 
selection/ordering in different ways, or having new implementations 
of an API do it differently than old versions, will degrade 
interoperability.

Keith
--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to