ietf-nntp NNTP and 16-bit charsets
Russ Allbery
rra at stanford.edu
Thu Apr 26 09:46:20 PDT 2001
Charles Lindsey <chl at clw.cs.man.ac.uk> writes:
> So I think the wording needs to be clarified. But first, we have to
> decide what we INTEND. I see the following possibilities:
> 1. We say that such an arbitrary octet stream is to be subjected to a
> transformation which does special things when any parts of adjacent (not
> necessarily part of the same 16-bit char) octets happen to look like
> CRLF, and maybe inserts an extra "." byte after such a pair, and maybe
> does other things with single bytes that happen to look like CR, LF or
> NULL. And then there is an inverse transformation at the client end
> which restores it all to the original octet stream. This all sounds
> horribly messy, but it might in fact actually work with little bother,
> even in existing implementations.
I believe that this is the intention, and it's certainly what people have
implemented (e.g. Diablo based on the long thread in news.software.nntp a
while back).
We do need to say something about whether the initial CRLF in CRLF.CRLF is
part of the message.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the ietf-nntp
mailing list