usefor-usefor-01 September 2004

[< Prev] [TOC] [ Next >]
3.2.4  Control

   The Control header marks the article as a control message, and
   specifies the desired actions (additional to the usual ones of
   storing and/or relaying the article).
   control         =  "Control:" SP [CFWS] control-message [CFWS] CRLF

   control-message = <empty>

   The control-message indicates what action should be taken.  The exact
   syntax for control-message is specified in the companion document,
   [USEPRO].
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usefor May 2005
usefor-usefor April 2005
usefor-usefor November 2004
News Article Format and Transmission May 2004
News Article Format and Transmission November 2003
News Article Format June 2003
News Article Format April 2003
News Article Format February 2003
News Article Format August 2002
News Article Format May 2002
News Article Format November 2001
News Article Format July 2001
News Article Format April 2001
News Article Format February 2000
Son of 1036 June 1994
RFC 1036 December 1987

--- ../usefor-article-13/Control.out          May 2004
+++ ../usefor-usefor-01/Control.out          September 2004
@@ -1,42 +1,13 @@
-6.13.  Control
+3.2.4  Control
 
-   The Control-header marks the article as a control message, and
+   The Control header marks the article as a control message, and
    specifies the desired actions (additional to the usual ones of
    storing and/or relaying the article).
+   control         =  "Control:" SP [CFWS] control-message [CFWS] CRLF
 
-      header              =/ Control-header
-      Control-header      = "Control" ":" SP Control-content
-                     *( ";" extension-parameter )
-      Control-content     = [CFWS] control-message [CFWS]
       control-message     = <empty>
 
-   However, the rule given above for control-message is incomplete.
-   Further alternatives will be added incrementally as the various
-   control-messages are introduced in section 7, or in extensions to
-   this standard, using the "=/" notation defined in [RFC 2234].  For
-   example, a putative "Control-message" would be defined as follows:
-
-      control-message     =/ Control-message
-      Control-message     = "Control" Control-arguments
-      Control-arguments   = <the argument(s) specific to that
-                   Control-message>
-
-   where "Control" is a "verb" which is (and MUST be) of the syntactic
-   form of a token and Control-arguments MUST be of the syntactic form
-   of a CFWS-separated list of values (which may require the use of
-   quoted-strings if any tspecials or non-ASCII characters are
-   involved).
-
-   The verb indicates what action should be taken, and the argument(s)
-   (if any) supply details. In some cases, the body of the article may
-   also contain details.
-
-   An article with a Control-header MUST NOT also have a Supersedes-
-   header.
-
-        NOTE: The presence of a Subject-header starting with the string
-        "cmsg " and followed by a Control-message MUST NOT be construed,
-        in the absence of a proper Control-header, as a request to
-        perform that control action (as may have occurred in some legacy
-        software).
+   The control-message indicates what action should be taken.  The exact
+   syntax for control-message is specified in the companion document,
+   [USEPRO].
 

Documents were processed to this format by Forrest J. Cavalier III