From: Maurizio Codogno (mau@beatles.cselt.it)
Date: Mon Nov 17 1997 - 06:54:33 CST
% From: Chris Newman <Chris.Newman@innosoft.com>
% The problem is that 822bis has a strong backwards compatibility
% requirement since we're updating a full standard specification. A client
% which sticks comments in the middle of the date header is conformant to
% RFC 822. Making a previously conformant client non-conformant requires
% good justification (e.g., significantly better interoperability with
% installed base and few such clients exist). Making a previously
% conformant client non-interoperable is simply not an option. Can you
% prove that no client exists which generates a comment in the date header
% anywhere other than at the end? If not, 822bis has to at least accept
% comments in those places.
Is it possible to put in the specification of drums that such things
are deprecated, and therefore SHOULD NOT be used, adding a note that
using them would lead to problems with Usenet?
.mau.