usefor-article-03 February 2000

7.  Control Messages

   The following sections document the control messages.  "Message" is
   used herein as a synonym for "article" unless context indicates
   otherwise.  Group control messages are the sub-class of control
   messages that request some update to the configuration of the groups
   known to a serving agent, namely "newgroup".  "rmgroup", "mvgroup"
   and "checkgroups", plus any others created by extensions to this
   standard.

   All of the group control messages MUST have an Approved header
   (6.12).  Moreover, in those hierarchies where appropriate
   administrative agencies exist (see 1.1), group control messages
   SHOULD NOT be issued except as authorized by those agencies.
[They SHOULD also use one of the authentication mechanisms which we
shall define when we get a Round Tuit.]

   The Newsgroups header of each control message MUST include the
   newsgroup-name(s) for the group(s) affected (i.e. groups to be
   created, modified or removed, or containing articles to be canceled).
   This is to ensure that the message progagates to all sites which
   receive (or would receive) that group(s). It MAY include other
   newsgroup-names so as to improve propagation (but this practice
   should be regarded as exceptional rather than normal).

   The descriptions below are generally phrased in terms suggesting
   mandatory actions, but any or all of these MAY be subject to local
   administrative restrictions, and MAY be denied or referred to an
   administrator for approval (either as a class or on a case-by-case
   basis). Analogously, where the description below specifies that a
   message or portion thereof is to be ignored, this action MAY include
   reporting it to an administrator.

   Relaying Agents MUST propagate even control messages that they do not
   understand.

   In the following sections, each type of control message is defined
   syntactically by defining its verb, its arguments, and possibly its
   body.

--- ../s-o-1036/Control_Messages.out          June 1994
+++ ../usefor-article-03/Control_Messages.out          February 2000
@@ -1,42 +1,40 @@
 7. Control Messages
 
-The following sections document the  currently-defined  con-
-trol  messages.   "Message"  is used herein as a synonym for
-"article" unless context indicates otherwise.
-
-Posting agents are warned that since  certain  control  mes-
-sages require article bodies in quite specific formats, sig-
-natures SHOULD not be appended to such articles, and it  may
-be  wise to take greater care than usual to avoid unintended
-(although perhaps well-meaning) alterations to text supplied
-
-INTERNET DRAFT to be        NEWS                      sec. 7
-
-
-by  the  poster.  Relayers MUST assume that control messages
-mean what they say; they MAY be obeyed as  is  or  rejected,
-but MUST not be reinterpreted.
-
-The  execution  of the actions requested by control messages
-is subject to local administrative restrictions,  which  MAY
-deny   requests  or  refer  them  to  an  administrator  for
-approval.  The descriptions below are generally  phrased  in
-terms  suggesting mandatory actions, but any or all of these
-MAY be subject to local administrative approval (either as a
-class  or case-by-case).  Analogously, where the description
-below specifies that a message or portion thereof is  to  be
-ignored, this action MAY include reporting it to an adminis-
-trator.
-
-     NOTE: The  exact  choice  of  local  action  might
-     depend   on   what   action  the  control  message
-     requests, who it claims to come from, etc.
+   The following sections document the control messages.  "Message" is
+   used herein as a synonym for "article" unless context indicates
+   otherwise.  Group control messages are the sub-class of control
+   messages that request some update to the configuration of the groups
+   known to a serving agent, namely "newgroup".  "rmgroup", "mvgroup"
+   and "checkgroups", plus any others created by extensions to this
+   standard.
+
+   All of the group control messages MUST have an Approved header
+   (6.12).  Moreover, in those hierarchies where appropriate
+   administrative agencies exist (see 1.1), group control messages
+   SHOULD NOT be issued except as authorized by those agencies.
+[They SHOULD also use one of the authentication mechanisms which we
+shall define when we get a Round Tuit.]
+
+   The Newsgroups header of each control message MUST include the
+   newsgroup-name(s) for the group(s) affected (i.e. groups to be
+   created, modified or removed, or containing articles to be canceled).
+   This is to ensure that the message progagates to all sites which
+   receive (or would receive) that group(s). It MAY include other
+   newsgroup-names so as to improve propagation (but this practice
+   should be regarded as exceptional rather than normal).
+
+   The descriptions below are generally phrased in terms suggesting
+   mandatory actions, but any or all of these MAY be subject to local
+   administrative restrictions, and MAY be denied or referred to an
+   administrator for approval (either as a class or on a case-by-case
+   basis). Analogously, where the description below specifies that a
+   message or portion thereof is to be ignored, this action MAY include
+   reporting it to an administrator.
 
-Relayers MUST propagate even control messages  they  do  not
+   Relaying Agents MUST propagate even control messages that they do not
 understand.
 
-In  the  following sections, each type of control message is
-defined syntactically by  defining  its  arguments  and  its
-body.   For example, "cancel" is defined by defining cancel-
-arguments and cancel-body.
+   In the following sections, each type of control message is defined
+   syntactically by defining its verb, its arguments, and possibly its
+   body.