[NNTP] Re: New NNTP drafts approaching IETF Last Call

Clive D.W. Feather clive at demon.net
Tue Mar 15 04:18:06 PST 2005


Charles Lindsey said:
>>    Note that texts using an encoding (such as UTF-16 or UTF-32) that may
>>    contain the octets NUL, LF, or CR other than a CRLF pair cannot be
>>    reliably conveyed in the above format (that is, they violate the MUST
>>    requirement above).

> However, the wording in the present draft is slightly misleading, since it
> seems to suggest that the arbitrary mixture of octets might contain NUL or
> naked CR or LF. So perhaps the second sentence would better say:

It doesn't need anything saying. This paragraph is a NOTE. The normative
text is item 1 of the numbered list immediately before it.

* There is a MUST requirement about NUL, CR, and LF.
* UTF-16 violates this requirement.
* The content of multi-line responses is NOT REQUIRED to be UTF-8.

What's so hard about this?

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:    +44 20 8495 6138
Internet Expert     | Home:  <clive at davros.org>  | Fax:    +44 870 051 9937
Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973 377646
Thus plc            |                            |



More information about the ietf-nntp mailing list