INTERNET-DRAFT                               Charles H. Lindsey
Usenet Format Working Group                  University of Manchester
                                             July 2001

4.4. Characters and Character Sets

4.4.  Characters and Character Sets
   Transmission paths for news articles MUST treat news articles as
   uninterpreted sequences of octets, excluding the values 0 (US-ASCII
   NUL) and 13 and 10 (US-ASCII CR and LF, which MUST ONLY appear in the
   combination CRLF which denotes a line separator).

        NOTE: this correspponds to the range of octets permitted for
        MIME "8bit data" [RFC 2045].  Thus raw binary data cannot be
        transmitted in an article body except by the use of a Content-
        Transfer-Encoding such as base64.

   Character data is represented by octets in accordance with some
   encoding scheme (UTF-8 for headers, and determined by the Content-
   Type and Content-Transfer-Encoding headers for bodies).

   If it comes to a relaying agent's attention that it is being asked to
   pass an article using the Content-Transfer-Encoding "8bit" to a
   relaying agent that does not support it, it SHOULD report this error
   to its administrator. It MUST refuse to pass the article and MUST NOT
   re-encode it with different MIME encodings.

        NOTE: This strategy will do little harm. The target relaying
        agent is unlikely to be able to make use of the article on its
        own servers, and the usual flooding algorithm will likely find
        some alternative route to get the article to destinations where
        it is needed.

Diffs to previous draft

--- {draft-04}	Wed Jul 11 21:55:15 2001
+++ {draft-05}	Wed Jul 11 21:55:15 2001
@@ -1,11 +1,11 @@
 
4.4.  Characters and Character Sets
    Transmission paths for news articles MUST treat news articles as
-   uninterpreted sequences of octets, excluding the values 0 (ASCII NUL)
-   and 13 and 10 (ASCII CR and LF, which MUST ONLY appear in the
+   uninterpreted sequences of octets, excluding the values 0 (US-ASCII
+   NUL) and 13 and 10 (US-ASCII CR and LF, which MUST ONLY appear in the
    combination CRLF which denotes a line separator).
 
         NOTE: this correspponds to the range of octets permitted for
-        Mime "8bit data" [RFC 2045].  Thus raw binary data cannot be
+        MIME "8bit data" [RFC 2045].  Thus raw binary data cannot be
         transmitted in an article body except by the use of a Content-
         Transfer-Encoding such as base64.
 
@@ -17,7 +17,7 @@
    pass an article using the Content-Transfer-Encoding "8bit" to a
    relaying agent that does not support it, it SHOULD report this error
    to its administrator. It MUST refuse to pass the article and MUST NOT
-   re-encode it with different Mime encodings.
+   re-encode it with different MIME encodings.
 
         NOTE: This strategy will do little harm. The target relaying
         agent is unlikely to be able to make use of the article on its