PE> Since the PATH is optional, no-one is required to generate
PE> it, and no-one on the way is required to update it.

RS> Fact remains, whatever was or was not required, it ended up with an
RS> out of spec PATH line, and THEN it was out of spec, and it didnt

PE> No Rod, it was NEVER out of spec.

RS> Oh bullshit, thats faking away like mad.

PE> Rod, you're completely out of your tree.
PE> You're "doing a Bill". Engage brain.

Make more smoke, we can see right thru this pathetic attempt.

PE> How do you implement an OPTIONAL kludge?

Soorree, you havent grasped the difference between one like say the
MSGID which is a single isolated optional kludge, and an optional
kludge which gets changed at each step along the way. With THOSE,
the optional concept falls down very badly when its FIRST used part
way along the chain. THEN what you have in the kludge is fucked.

Its just yet another example of when mindlessly attempting to
proclaim what is and is not 'in spec' blows up in your face, JUST
like it did on the embedded origin line between an SOT/EOT pair TOO.

Its nothing like as cut and dried as you are trying to claim.
@EOT:

---