On Mon, 03 Feb 2014, Vitus Zeel wrote to Benny Pedersen:

 BP>  VZ> @PATH: 240/8001 8001 1120

 BP> hmm 240/8001 is listed 3 times what happend ?

 VZ> thats may be a mystic bug. Well 240/8001 <- here is the .4 missing
 VZ> from my hotdoged point number i think,

true... the problem for the PATH is at the second processing system when it
added its (duplicate) address...

SEENBY and PATH are only 2D... net/node...

seenby are sorted by net and then node... path are not sorted at all...

in the PATH additional nodes within a net are "compressed" for space and do
not carry the "net/" portion...

  eg: path 123/123 456 789 234/345 123/321

the above example path shows the following...

  originating node 123/123 or a point of 123/123
         next node 123/456
         next node 123/789
         next node 234/345
         last node 123/321

the example message was processed by three net123 systems before being
processed by a system in net234 and then ending up back in net123 at node
321...

 VZ> the 2nd is incomplete and have to be 2:240/8001 without a point 
 VZ> number (my bbs)

it is fully complete but erroneously duplicated... 240/ in the first entry
applies to all following entries in PATH until another "net/" is encountered...

 VZ> and the 1120, the 3th have to be 2:240/1120 fidohub of my bbs.

see above... it is complete for the posted path and yes, it is for 240/1120...
we can only guess at the zone since zones, points and domains are not allowed
in the standard 2D SEENBY or PATH lines...


FWIW: 1D is node only
      2D is net/node
      3D is zone:net/node
      4D is zone:net/node.point
      5D is zone:net/node.point@FTNdomain

      net/node.point is 4D even without the zone

)\/(ark

One of the great tragedies of life is the murder of a beautiful theory by a
gang of brutal facts. --Benjamin Franklin

--- FMail/Win32 1.60
 * Origin:  (1:3634/12.71)