usefor-article-13 May 2004

8.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).

   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 (8.3).

   In exceptional circumstances (e.g. as part of come 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 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.

--- ../usefor-article-12/Duties_of_an_Injecting_Agent.out          November 2003
+++ ../usefor-article-13/Duties_of_an_Injecting_Agent.out          May 2004
@@ -9,4 +9,25 @@
    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).
+
+   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 (8.3).
+
+   In exceptional circumstances (e.g. as part of come 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 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.