usefor-article-03 February 2000
[< Prev]
[TOC] [ Next >]
6.11. 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 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 Replaces or
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
perform that control action (as may have occurred in some legacy
software). See also section 5.4.
[< Prev]
[TOC] [ Next >]
#Diff to first older
--- ../s-o-1036/Control.out June 1994
+++ ../usefor-article-03/Control.out February 2000
@@ -1,39 +1,32 @@
-6.6. Control
+6.11. Control
-The Control header content marks the article as a control
-message, and specifies the desired actions (other than the
-usual ones of filing and passing on the article):
-
- Control-content = verb *( space argument )
- verb = 1*( letter / digit )
- argument = 1*<ASCII printable character>
-
-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 the standard verbs. See also the Also-Control
-header (section 6.15).
-
- NOTE: Control messages are often processed and
- filed rather differently than normal articles.
-
- NOTE: The restriction of verbs to letters and dig-
- its is new, but is consistent with existing prac-
- tice and potentially simplifies implementation by
- avoiding characters significant to command inter-
- preters. Beware that the arguments are under no
- such restriction in general.
-
- NOTE: Two other conventions for distinguishing
- control messages from normal articles were for-
- merly in use: a three-component newsgroup name
- ending in ".ctl" or a subject beginning with
- "cmsg " was considered to imply that the article
- was a control message. These conventions are
- obsolete. Do not use them.
-
-An article with a Control header MUST not have an Also-
-Control or Supersedes header.
-
-INTERNET DRAFT to be NEWS sec. 6.7
+ 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 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 Replaces or
+ 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
+ perform that control action (as may have occurred in some legacy
+ software). See also section 5.4.