#1047 Path field delimiters - feed behaviour? (fwd)

[Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx>]

I haven't seen an answer to this question - would anyone else like to 
answer?

                  Harald

---------- Forwarded Message ----------
Date: fredag, juni 24, 2005 09:04:27 +0200
From: Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx>
To: John Stanley <stanley@xxxxxxxx>, ietf-usefor@xxxxxxx
Cc:
Subject: #1047 Path field delimiters - feed behaviour?


Attempting to return to the problem at hand, rather than the discussion on
how to discuss these things - John, can you educate me a little bit about
USENET feeds?

--On 23. juni 2005 17:05 -0700 John Stanley <stanley@xxxxxxxx> wrote:

> It would seem to be unwise to use it in IPV6 addresses as well, since
> ::FFFF:129.144.52.38 and ::FFFF:129.145.23.23 are clearly two different
> addresses but the same failure that would make the dead:beef admin an
> idiot would make both of these people idiots. (I.e., non-conforming
> servers would match the "path-identity" of FFFF for both systems and
> feeds  would be disrupted.)

If, in a message arriving at the old system "here", there is a Path: header
that says

Path: there!::FFFF:129.144.52.38!not-for-mail

and "here" does not know about any system named "FFFF", will any change in
handling happen?

Conversely, if a message arrives with a Path: header that says

Path: there!::FFFF:129.144.52.38!::FFFF:129.145.23.23!not-for-mail

will the two occurences of "FFFF" in the Path: cause anything bad to happen?

Or is there some third circumstance that I haven't guessed at yet that will
cause something bad to happen?

I'd like to understand what you mean when you say "feeds will be
disrupted".....

                  Harald








---------- End Forwarded Message ----------