usefor-usefor-01 September 2004

1.2  Scope

   This document specifies the syntax of network news articles in the
   context of the "Internet Message Format" [RFC2822] and "Multipurpose
   Internet Mail Extensions (MIME)" [RFC2045].  This document supersedes
   [RFC1036], updating it to reflect current practice and incorporating
   incremental changes specified in other documents such as
   [Son-of-1036].

   This is the first in a set of documents that obsolete [RFC1036].
   This document focuses on the syntax and semantics of network news
   articles.  [USEPRO] is also a standards-track document, and describes
   the protocol issues of network news articles, independent of
   transmission protocols such as NNTP [RFC0977].  An informational
   document, [USEAGE], describes implementation recommendations to
   improve interoperability and usability.

   This specification is intended as a definition of what article
   content format is to be passed between systems.  Though some news
   systems locally store articles in this format (which eliminates the
   need for translation between formats) and others use formats that
   differ from the one specified in this standard, local storage is
   outside of the scope of this standard.

   Note: This standard is not intended to dictate the internal formats
   used by sites, the specific news system features that they are
   expected to support, or any of the characteristics of user interface
   programs that create or read articles.  In addition, this standard
   does not specify an encoding of the characters for either transport
   or storage; that is, it does not specify the number of bits used or
   how those bits are specifically transferred over the wire or stored
   on disk.

--- ../rfc2822/Scope.out          April 2001
+++ ../usefor-usefor-01/Scope.out          September 2004
@@ -1,45 +1,31 @@
-1.1. Scope
+1.2  Scope
 
-   This standard specifies a syntax for text messages that are sent
-   between computer users, within the framework of "electronic mail"
-   messages.  This standard supersedes the one specified in Request For
-   Comments (RFC) 822, "Standard for the Format of ARPA Internet Text
-   Messages" [RFC822], updating it to reflect current practice and
-   incorporating incremental changes that were specified in other RFCs
-   [STD3].
+   This document specifies the syntax of network news articles in the
+   context of the "Internet Message Format" [RFC2822] and "Multipurpose
+   Internet Mail Extensions (MIME)" [RFC2045].  This document supersedes
+   [RFC1036], updating it to reflect current practice and incorporating
+   incremental changes specified in other documents such as
+   [Son-of-1036].
 
-   This standard specifies a syntax only for text messages.  In
-   particular, it makes no provision for the transmission of images,
-   audio, or other sorts of structured data in electronic mail messages.
-   There are several extensions published, such as the MIME document
-   series [RFC2045, RFC2046, RFC2049], which describe mechanisms for the
-   transmission of such data through electronic mail, either by
-   extending the syntax provided here or by structuring such messages to
-   conform to this syntax.  Those mechanisms are outside of the scope of
-   this standard.
+   This is the first in a set of documents that obsolete [RFC1036].
+   This document focuses on the syntax and semantics of network news
+   articles.  [USEPRO] is also a standards-track document, and describes
+   the protocol issues of network news articles, independent of
+   transmission protocols such as NNTP [RFC0977].  An informational
+   document, [USEAGE], describes implementation recommendations to
+   improve interoperability and usability.
 
-   In the context of electronic mail, messages are viewed as having an
-   envelope and contents.  The envelope contains whatever information is
-   needed to accomplish transmission and delivery.  (See [RFC2821] for a
-   discussion of the envelope.)  The contents comprise the object to be
-   delivered to the recipient.  This standard applies only to the format
-   and some of the semantics of message contents.  It contains no
-   specification of the information in the envelope.
-
-   However, some message systems may use information from the contents
-   to create the envelope.  It is intended that this standard facilitate
-   the acquisition of such information by programs.
-
-   This specification is intended as a definition of what message
-   content format is to be passed between systems.  Though some message
-   systems locally store messages in this format (which eliminates the
+   This specification is intended as a definition of what article
+   content format is to be passed between systems.  Though some news
+   systems locally store articles in this format (which eliminates the
    need for translation between formats) and others use formats that
    differ from the one specified in this standard, local storage is
    outside of the scope of this standard.
+
    Note: This standard is not intended to dictate the internal formats
-   used by sites, the specific message system features that they are
+   used by sites, the specific news system features that they are
    expected to support, or any of the characteristics of user interface
-   programs that create or read messages.  In addition, this standard
+   programs that create or read articles.  In addition, this standard
    does not specify an encoding of the characters for either transport
    or storage; that is, it does not specify the number of bits used or
    how those bits are specifically transferred over the wire or stored