usefor-usepro-03 February 2005

7.3.1.  Path-Header 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-usepro-02/Path-Header_Example.out          December 2004
+++ ../usefor-usepro-03/Path-Header_Example.out          February 2005
@@ -8,18 +8,19 @@
         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.
+        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
+        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.
+        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
@@ -32,7 +33,7 @@
         "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
+        <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