usefor-article-10 April 2003

6.19.  Injector-Info

   The Injector-Info-header SHOULD be added to each article by the
   injecting agent in order to provide information as to how that
   article entered the Netnews system and to assist in tracing its true
   origin.

      header          =/ Injector-Info-header
      Injector-Info-header
            = "Injector-Info" ":" SP Injector-Info-content
                 *( ";" ( Injector-Info-parameter /
                          extension-parameter ) )
      Injector-Info-content
            = [CFWS] path-identity [CFWS]
      Injector-Info-parameter
            = posting-host-parameter /
              posting-account-parameter /
              posting-sender-parameter /
              posting-logging-parameter /
              posting-date-parameter
              ; for {USENET}-parameters see 4.1
      posting-host-parameter
            = <a parameter with attribute "posting-host"
               and value some host-value>
      host-value      = dot-atom /
              [ dot-atom ":" ]
                ( IPv4address / IPv6address ); see [RFC 2373]
      posting-account-parameter
            = <a parameter with attribute "posting-account"
               and any value>
      posting-sender-parameter
            = <a parameter with attribute "sender"
               and value some sender-value>
      sender-value    = mailbox / "verified"
      posting-logging-parameter
            = <a parameter with attribute "logging-data"
               and any value>
      posting-date-parameter
            = <a parameter with attribute "posting-date"
               and value some date-time>

   An Injector-Info-header MUST NOT be added to an article by any agent
   other than an injecting agent. Any Injector-Info-header present when
   an article arrives at an injecting agent MUST be removed. In
   particular if, for some exceptional reason (8.2.2), an article gets
   injected twice, the Injector-Info-header will always relate to the
   second injection.

   The path-identity MUST be the same as the path-identity prepended to
   the Path-header by that same injecting agent which, following section
   5.6.2, MUST therefore be a fully qualified domain name (FQDN)
   mailable address.

   Although comments and folding of white space are permitted throughout
   the Injector-Info-content specification, it is RECOMMENDED that
   folding is not used within any parameter (but only before or after
   the ";" separating those parameters), and that comments are only used
   following the last parameter. It is also RECOMMENDED that such
   parameters as are present are included in the order in which they
   have been defined in the syntax above.  An injecting agent SHOULD use
   a consistent form of this header for all articles emanating from the
   same or similar origins.

        NOTE: The effect of those recommendations is to facilitate the
        recognition of articles arising from certain designated origins
        (as in the so-called "killfiles" which are available in some
        reading agents). Observe that the order within the syntax has
        been chosen to place last those parameters which are most likely
        to change between successive articles posted from the same
        origin.

        NOTE:  To comply with the overall "attribute = value" syntax of
        parameters, any value containing an IPv6address, a date-time, a
        mailbox, any UTF8-xtra-char, or any CFWS MUST be quoted using
        <DQUOTE>s (the quoting is optional in other cases).

        NOTE: This header is intended to replace various currently-used
        but nowhere-documented headers such as "NNTP-Posting-Host",
        "NNTP-Posting-Date" and "X-Trace". These headers are now
        deprecated, and any of them present when an article arrives at
        an injecting agent SHOULD also be removed as above.

--- ../usefor-article-09/Injector-Info.out          February 2003
+++ ../usefor-article-10/Injector-Info.out          April 2003
@@ -60,6 +60,7 @@
    have been defined in the syntax above.  An injecting agent SHOULD use
    a consistent form of this header for all articles emanating from the
    same or similar origins.
+
         NOTE: The effect of those recommendations is to facilitate the
         recognition of articles arising from certain designated origins
         (as in the so-called "killfiles" which are available in some