usefor-usepro-00 August 2004

4.  Transport

   As in this standard's predecessors, the exact means used to transmit
   articles from one host to another is not specified. NNTP [NNTP] is
   the most common transmission method on the Internet, but much
   transmission takes place entirely independent of the Internet. Other
   methods in use include the UUCP protocol [RFC 976] extensively used
   in the early days of Usenet, FTP, downloading via satellite, tape
   archives, and physically delivered magnetic and optical media.

   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 corresponds 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.


   In particular, transmission paths MUST convey all headers (including
   body part headers and headers within message/rfc822 objects) intact,
   even if they contain octets in the range 128 to 255.  These
   requirements include the transmissiom paths between posting agents,
   injecting agents, relaying agents, serving agents and reading agents,
   but NOT the paths traversed by Netnews articles that have been
   gatewayed into Email (7.8.1).
[At some point it will be necessary for the IMAP standards to catch up
with these requirements.]

--- ../usefor-article-13/Transport.out          May 2004
+++ ../usefor-usepro-00/Transport.out          August 2004
@@ -1,4 +1,4 @@
-1.4.  Transport
+4.  Transport
 
    As in this standard's predecessors, the exact means used to transmit
    articles from one host to another is not specified. NNTP [NNTP] is
@@ -7,4 +7,25 @@
    methods in use include the UUCP protocol [RFC 976] extensively used
    in the early days of Usenet, FTP, downloading via satellite, tape
    archives, and physically delivered magnetic and optical media.
+
+   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 corresponds 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.
+
+
+   In particular, transmission paths MUST convey all headers (including
+   body part headers and headers within message/rfc822 objects) intact,
+   even if they contain octets in the range 128 to 255.  These
+   requirements include the transmissiom paths between posting agents,
+   injecting agents, relaying agents, serving agents and reading agents,
+   but NOT the paths traversed by Netnews articles that have been
+   gatewayed into Email (7.8.1).
+[At some point it will be necessary for the IMAP standards to catch up
+with these requirements.]