everyone--
After just now finding the root cause of yet another stupid interoperability
problem to be an interaction between a client not choosing a sufficiently
unique host/session identifier and a server being overly clever about using
said identifiers for purposes other than intended in the protocol
specification...
WHEREAS the IETF has no document category for dealing with material that is
unfit for Standards Track, that does not in any way describe Best Current
Practice, provides Information of questionable utility, which is neither yet
limited to Historical interest nor of merely Experimental nature...
BE IT HEREBY RESOLVED that IETF should create a new document category for
Disinformation, and that RFC 2516 should immediately and with extreme prejudice
be reclassified as such without further discussion.
--
james woodyatt <jhw(_at_)apple(_dot_)com>
member of technical staff, communications engineering
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf