usefor-article-07 May 2002

6.13.  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).

      header              =/ Control-header
      Control-header      = "Control" ":" SP Control-content
                     *( ";" other-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 typical 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). See also section 5.4.

--- ../usefor-article-06/Control.out          November 2001
+++ ../usefor-article-07/Control.out          May 2002
@@ -1,32 +1,41 @@
 6.13.  Control
 
-   The Control header marks the article as a control message, and
-   specifies the desired actions (other than the usual ones of storing
-   and/or relaying the article).
-
-      Control-content     = CONTROL-verb CONTROL-argument
-      CONTROL-verb        = <the verb defined in this standard
-                     (or an extension of it) for a specific
-                     CONTROL message>
-      verb                = token
-      CONTROL-arguments   = <the argument defined in this standard
-                     (or an extension of it) for a specific
-                     CONTROL message>
-      arguments           = *( CFWS value )  ; see 4.1
-[Observe that <value> reqires the use of a quoted-string if any
-tspecials or non-ASCII characters are involved. This is a restriction on
-present usage, but follows MIME practice.]
+   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).
+
+      header              =/ Control-header
+      Control-header      = "Control" ":" SP Control-content
+                     *( ";" other-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 typical 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. Section 7 describes all of the standard verbs.
-
-   An article with a Control header MUST NOT also have a Supersedes
+   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-content MUST NOT be construed,
-        in the absence of a proper Control header, as a request to
+        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). See also section 5.4.