usefor-usepro-00 August 2004

7.2.  Duties of an Injecting Agent

   An Injecting Agent is responsible for taking a proto-article from a
   posting agent and either forwarding it to a moderator or injecting it
   into the relaying system for access by readers.

   As such, an injecting agent is considered responsible for ensuring
   that any article it injects conforms with the rules of [USEFOR].

   In the normal course of events, an article that has already been
   injected into a Netnews network will never pass through another
   injecting agent.  So, if an injecting agent receives an otherwise
   valid article that has already been injected (as evidenced by the
   presence of an Injection-Date-header, an Injection-Info-header, or
   more thath one '%' path-delimiter in a Path-header) it MAY choose to
   reject it, but otherwise SHOULD cause it to be relayed, as it stands,
   by a relaying agent (7.3).

   In exceptional circumstances (e.g. as part of some complex gatewaying
   process, or where a relaying agent considers it essential for
   fulfilling its responsibility towards the rest of the network) an
   already injected article MAY be "reinjected" into the network.  This
   standard does not prescribe any such circumstance; rather this is a
   matter of policy to be determined by the administrators of each
   injecting agent, who have the responsibility to ensure that no harm
   arises. In all other circumstances, unintented reinjection is to be
   avoided (see 7.8).  Nevertheless, in order to preserve the integrity
   of the network in these special cases, this standard sets out the
   correct way to reinject.

   It is usual for an injecting agent to be closely associated with a
   serving agent, thus giving it access to the list (7.4) showing the
   moderation status of the newsgroups it is likely to handle. In the
   event that it does not have such an associated serving agent, it MUST
   maintain that list itself.

--- ../usefor-article-13/Duties_of_an_Injecting_Agent.out          May 2004
+++ ../usefor-usepro-00/Duties_of_an_Injecting_Agent.out          August 2004
@@ -1,14 +1,11 @@
-8.2.  Duties of an Injecting Agent
+7.2.  Duties of an Injecting Agent
 
    An Injecting Agent is responsible for taking a proto-article from a
    posting agent and either forwarding it to a moderator or injecting it
    into the relaying system for access by readers.
 
    As such, an injecting agent is considered responsible for ensuring
-   that any article it injects conforms with the rules of this standard.
-   It is also expected to bear some responsibility towards the rest of
-   the network for the behaviour of its posters (and provision is
-   therefore made for it to be easily contactable by email).
+   that any article it injects conforms with the rules of [USEFOR].
 
    In the normal course of events, an article that has already been
    injected into a Netnews network will never pass through another
@@ -17,9 +14,9 @@
    presence of an Injection-Date-header, an Injection-Info-header, or
    more thath one '%' path-delimiter in a Path-header) it MAY choose to
    reject it, but otherwise SHOULD cause it to be relayed, as it stands,
-   by a relaying agent (8.3).
+   by a relaying agent (7.3).
 
-   In exceptional circumstances (e.g. as part of come complex gatewaying
+   In exceptional circumstances (e.g. as part of some complex gatewaying
    process, or where a relaying agent considers it essential for
    fulfilling its responsibility towards the rest of the network) an
    already injected article MAY be "reinjected" into the network.  This
@@ -27,7 +24,13 @@
    matter of policy to be determined by the administrators of each
    injecting agent, who have the responsibility to ensure that no harm
    arises. In all other circumstances, unintented reinjection is to be
-   avoided (see 8.8).  Nevertheless, in order to preserve the integrity
-   of the network in those special cases, this standard does set out the
-   proper way to reinject.
+   avoided (see 7.8).  Nevertheless, in order to preserve the integrity
+   of the network in these special cases, this standard sets out the
+   correct way to reinject.
+
+   It is usual for an injecting agent to be closely associated with a
+   serving agent, thus giving it access to the list (7.4) showing the
+   moderation status of the newsgroups it is likely to handle. In the
+   event that it does not have such an associated serving agent, it MUST
+   maintain that list itself.