> > The real question is whether this document should endorse the > > idea that the > > host can change existing APIs in such a way that it may alter > > the behavior of programs written to those APIs. The only > > reasonable answer is "no". > > And in fact, the document recommends (the SHOULD part) the "no" answer. > But I think there will be circumstances in which an implementor could > reasonably conclude to give priority to privacy over app-compat, and the > "escape clause" is really just pointing out the right to make an > informed decision that the implementor has anyway.
the implementor can do whatever it wants, whether or not it conforms to the standard. but it's not IETF's job to endorse implementors' poor decisions. 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] --------------------------------------------------------------------
