usefor-article-06 November 2001

7.  Control Messages

   The following sections document the control messages.  "Message" is
   used herein as a synonym for "article" unless context indicates
   otherwise.

   The Newsgroups header of each control message SHOULD 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 may
   cause the control message to propagate also to places where it is
   unwanted, or even cause it not to progatate where it should, so it
   should not be used without good reason).

   The descriptions below set out REQUIREMENTS to be followed by sites
   that receive control messages and choose to honour them. However,
   nothing in these descriptions should be taken as overriding the right
   of any such site, in accordance with its local policy, to deny any
   particular control message, or to refer it to an administrator for
   approval (either as a class or on a case-by-case basis). In
   particular, sites Ought to deny messages not issued by the
   appropriate administrative agencies, and therefore SHOULD take such
   steps as are reasonably practicable to validate their authenticity
   (see, for example, section 7.1 below).
   Relaying Agents MUST propagate even control messages that they do not
   recognise.

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

--- ../usefor-article-05/Control_Messages.out          July 2001
+++ ../usefor-article-06/Control_Messages.out          November 2001
@@ -2,18 +2,7 @@
 
    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.14).  Moreover, in those hierarchies where appropriate
-   administrative agencies exist (see 1.1), group control messages Ought
-   Not to be issued except as authorized by those agencies.
-[They SHOULD also use one of the authentication mechanisms which we may
-define when we get a Round Tuit.]
+   otherwise.
 
    The Newsgroups header of each control message SHOULD include the
    newsgroup-name(s) for the group(s) affected (i.e. groups to be
@@ -22,22 +11,21 @@
    receive (or would receive) that group(s). It MAY include other
    newsgroup-names so as to improve propagation (but this practice may
    cause the control message to propagate also to places where it is
-   unwanted, so it should not be used without good reason).
-
-   For convenience, the descriptions below are phrased on the assumption
-   that control messages will be honoured by sites receiving them.
-   Naturally, this does not apply where they have not been issued by the
-   appropriate administrative agencies (and sites SHOULD take such steps
-   as are reasonable practicable to validate their authenticity).
-   Moreover, acceptance of such messages 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.
+   unwanted, or even cause it not to progatate where it should, so it
+   should not be used without good reason).
 
+   The descriptions below set out REQUIREMENTS to be followed by sites
+   that receive control messages and choose to honour them. However,
+   nothing in these descriptions should be taken as overriding the right
+   of any such site, in accordance with its local policy, to deny any
+   particular control message, or to refer it to an administrator for
+   approval (either as a class or on a case-by-case basis). In
+   particular, sites Ought to deny messages not issued by the
+   appropriate administrative agencies, and therefore SHOULD take such
+   steps as are reasonably practicable to validate their authenticity
+   (see, for example, section 7.1 below).
    Relaying Agents MUST propagate even control messages that they do not
-   understand.
+   recognise.
 
    In the following sections, each type of control message is defined
    syntactically by defining its verb, its arguments, and possibly its