usefor-article-04 April 2001

[< Prev] [TOC]
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.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.]
   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.
[< Prev] [TOC]
#Diff to first older
NewerOlder
usefor-usepro February 2005
usefor-usepro December 2004
usefor-usepro September 2004
usefor-usepro August 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 February 2000
Son of 1036 June 1994
RFC 1036 December 1987

--- ../usefor-article-03/Control_Messages.out          February 2000
+++ ../usefor-article-04/Control_Messages.out          April 2001
@@ -9,12 +9,11 @@
    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.]
-
+   (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.]
    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).


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