usefor-usepro-00 August 2004

7.5.  Duties of a Serving Agent

   A Serving Agent takes an article from a relaying or injecting agent
   and files it in a "news database". It also provides an interface for
   reading agents to access the news database. This database is normally
   indexed by newsgroup with articles in each newsgroup identified by an
   article-locator (usually in the form of a decimal number - see a-
   6.16).

   A serving agent MUST maintain a list showing the moderation status
   (see 6.2.1) of the newsgroups it stores in the news database, and
   SHOULD include in that list all groups likely to be crossposted to
   from those groups (e.g. all other groups in the same hierarchy(ies)).

        NOTE: Since control messages are often of interest, but should
        not be displayed as normal articles in regular newsgroups, it is
        common for serving agents to make them available in a pseudo-
        newsgroup named "control" or in a pseudo-newsgroup in a sub-
        hierarchy under "control." (e.g. "control.cancel").

   A serving agent processes articles as follows:

   1.  It MUST establish the trusted identity of the source of the
      article and modify the Path-header as for a relaying agent (7.3).

   2. It MUST examine the Injection-Date-header (or, if that is absent,
      the Date-header) and reject the article as stale (a-5.7) if that
      predates the earliest articles of which it normally keeps record,
      or if it is more than 24 hours into the future (the margin MAY be
      less than that 24 hours).

   3. It MUST reject any article that does not have the correct
      mandatory headers (section a-5) present, or which contains any
      header that does not have legal contents.

   4. It SHOULD reject any article that has already been sent to it (a
      database of message identifiers of recent messages is usually kept
      and matched against).

   5. It SHOULD reject any article that matches an already received
      cancel message (or an equivalent Supersedes-header) issued by its
      poster or by some other trusted entity.

   6. It MUST reject any article without an Approved-header posted to
      any newsgroup listed as moderated.

   7. It MUST remove any Xref-header (a-6.16) from each article.  It
      then MAY (and usually will) generate a fresh Xref-header.

   8. Finally, it stores the article in its news database.

--- ../usefor-article-13/Duties_of_a_Serving_Agent.out          May 2004
+++ ../usefor-usepro-00/Duties_of_a_Serving_Agent.out          August 2004
@@ -1,10 +1,16 @@
-8.4.  Duties of a Serving Agent
+7.5.  Duties of a Serving Agent
 
    A Serving Agent takes an article from a relaying or injecting agent
    and files it in a "news database". It also provides an interface for
    reading agents to access the news database. This database is normally
    indexed by newsgroup with articles in each newsgroup identified by an
-   article-locator (usually in the form of a decimal number - see 6.16).
+   article-locator (usually in the form of a decimal number - see a-
+   6.16).
+
+   A serving agent MUST maintain a list showing the moderation status
+   (see 6.2.1) of the newsgroups it stores in the news database, and
+   SHOULD include in that list all groups likely to be crossposted to
+   from those groups (e.g. all other groups in the same hierarchy(ies)).
 
         NOTE: Since control messages are often of interest, but should
         not be displayed as normal articles in regular newsgroups, it is
@@ -14,22 +20,19 @@
 
    A serving agent processes articles as follows:
 
-   1. It MUST verify the leftmost entry in the Path-header and then
-      prepend its own path-identity with a '/' path-delimiter, and
-      possibly also the verified path-identity of its source with a '?'
-      path-delimiter (5.6.2).
+   1.  It MUST establish the trusted identity of the source of the
+      article and modify the Path-header as for a relaying agent (7.3).
 
    2. It MUST examine the Injection-Date-header (or, if that is absent,
-      the Date-header) and reject the article as stale (5.7) if that
+      the Date-header) and reject the article as stale (a-5.7) if that
       predates the earliest articles of which it normally keeps record,
       or if it is more than 24 hours into the future (the margin MAY be
       less than that 24 hours).
 
    3. It MUST reject any article that does not have the correct
-      mandatory headers (section 5) present, or which contains any
+      mandatory headers (section a-5) present, or which contains any
       header that does not have legal contents.
 
-
    4. It SHOULD reject any article that has already been sent to it (a
       database of message identifiers of recent messages is usually kept
       and matched against).
@@ -39,12 +42,10 @@
       poster or by some other trusted entity.
 
    6. It MUST reject any article without an Approved-header posted to
-      any moderated newsgroup which it is configured to receive, and it
-      MAY reject such articles for any newsgroup it knows to be
-      moderated.
+      any newsgroup listed as moderated.
 
-   7. It MUST remove any Xref-header (6.16) from each article.  It then
-      MAY (and usually will) generate a fresh Xref-header.
+   7. It MUST remove any Xref-header (a-6.16) from each article.  It
+      then MAY (and usually will) generate a fresh Xref-header.
 
    8. Finally, it stores the article in its news database.