I'll restate it in context; if we are going to support interoperability with broken and non-compliant systems this must be made available as a configuration option and preferably OFF as default.
What's the value of turning this off? <snarky>So that sysadmin's who don't have any users can turn on enforcement?</snarky>
To add support for non-compliant systems as default behaviour is to condone non-compliance. Condoning non-compliance devalues the standard and leads to the existence of an undocumented de-facto standard which is very much harder to research, implement, and test. It raises the bar to effective new implementations of the system.
The bar is already really really high. How about instead publishing all the spec violations we've had to made, and the servers and clients that prompted us to do it? That would probably be a popular page.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
