usefor-usepro-00 August 2004

7.4.1.  Example

      Path: foo.isp.example/
         foo-server/bar.isp.example?10.123.12.2/old.site.example!
         barbaz/baz.isp.example%dialup123.baz.isp.example!not-for-mail

        NOTE: That article was injected into the news stream by
        baz.isp.example (complaints may be addressed to
        abuse@baz.isp.example). The injector has taken care to record
        that it got it from dialup123.baz.isp.example. "not-for-mail" is
        a dummy tail-entry, though sometimes a real userid is put there.

        The article was relayed, perhaps by UUCP, to the machine known,
        at least to old.site.example, as "barbaz".

        Barbaz relayed it to old.site.example, which does not yet
        conform to this standard (hence the '!' path-delimiter). So one
        cannot be sure that it really came from barbaz.

        Old.site.example relayed it to a site claiming to have the IP
        address [10.123.12.2], and claiming (by using the '/' path-
        delimiter) to have verified that it came from old.site.example.

        [10.123.12.2] relayed it to "foo-server" which, not being
        convinced that it truly came from [10.123.12.2], did a reverse
        lookup on the actual source and concluded it was known as
        bar.isp.example (that is not to say that [10.123.12.2] was not a
        correct IP address for bar.isp.example, but simply that that
        connection could not be substantiated by foo-server).  Observe
        that foo-server has now added two entries to the Path.

        "foo-server" is a locally significant name within the complex
        site of many machines run by foo.isp.example, so the latter
        should have no problem recognizing foo-server and using a '/'
        path-delimiter.  Presumably foo.isp.example then delivered the
        article to its direct clients.

        It appears that foo.isp.example and old.site.example decided to
        fold the line, on the grounds that it seemed to be getting a
        little too long.

--- ../usefor-article-13/3_Example.out          May 2004
+++ ../usefor-usepro-00/3_Example.out          August 2004
@@ -1,38 +1,41 @@
-7.2.1.4.  Example
+7.4.1.  Example
 
-   A "newgroup" with its charter:
-
-      From: "example.all Administrator" <admin@noc.example>
-      Newsgroups: example.admin.info,example.admin.announce
-      Date: 27 Feb 2002 12:50:22 +0200
-      Subject: cmsg newgroup example.admin.info moderated
-      Approved: admin@noc.example
-      Control: newgroup example.admin.info moderated
-      Message-ID: <ng-example.admin.info-20020227@noc.example>
-      MIME-Version: 1.0
-      Content-Type: multipart/mixed; boundary="nxtprt"
-      Content-Transfer-Encoding: 8bit
-
-      This is a MIME control message.
-      --nxtprt
-      Content-Type: application/news-groupinfo
-
-      For your newsgroups file:
-      example.admin.info      About the example.* groups (Moderated)
-
-      --nxtprt
-      Content-Type: application/news-transmission
-
-      Newsgroups: example.admin.info
-      From: "example.all Administrator" <admin@noc.example>
-      Subject: Charter for example.admin.info
-      Message-ID: <charter-example.admin.info-20020227@noc.example>
-      Distribution: local
-      Content-Type: text/plain; charset=us-ascii
-      Content-Transfer-Encoding: 7bit
-
-      The group example.admin.info contains regularly posted
-      information on the example.* hierarchy.
-
-      --nxtprt--
+      Path: foo.isp.example/
+         foo-server/bar.isp.example?10.123.12.2/old.site.example!
+         barbaz/baz.isp.example%dialup123.baz.isp.example!not-for-mail
+
+        NOTE: That article was injected into the news stream by
+        baz.isp.example (complaints may be addressed to
+        abuse@baz.isp.example). The injector has taken care to record
+        that it got it from dialup123.baz.isp.example. "not-for-mail" is
+        a dummy tail-entry, though sometimes a real userid is put there.
+
+        The article was relayed, perhaps by UUCP, to the machine known,
+        at least to old.site.example, as "barbaz".
+
+        Barbaz relayed it to old.site.example, which does not yet
+        conform to this standard (hence the '!' path-delimiter). So one
+        cannot be sure that it really came from barbaz.
+
+        Old.site.example relayed it to a site claiming to have the IP
+        address [10.123.12.2], and claiming (by using the '/' path-
+        delimiter) to have verified that it came from old.site.example.
+
+        [10.123.12.2] relayed it to "foo-server" which, not being
+        convinced that it truly came from [10.123.12.2], did a reverse
+        lookup on the actual source and concluded it was known as
+        bar.isp.example (that is not to say that [10.123.12.2] was not a
+        correct IP address for bar.isp.example, but simply that that
+        connection could not be substantiated by foo-server).  Observe
+        that foo-server has now added two entries to the Path.
+
+        "foo-server" is a locally significant name within the complex
+        site of many machines run by foo.isp.example, so the latter
+        should have no problem recognizing foo-server and using a '/'
+        path-delimiter.  Presumably foo.isp.example then delivered the
+        article to its direct clients.
+
+        It appears that foo.isp.example and old.site.example decided to
+        fold the line, on the grounds that it seemed to be getting a
+        little too long.