From owner-ietf-mxcomp@mail.imc.org Thu Sep 01 03:29:12 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAjVY-0003iD-IC
	for marid-archive@megatron.ietf.org; Thu, 01 Sep 2005 03:29:12 -0400
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01762
	for <marid-archive@lists.ietf.org>; Thu, 1 Sep 2005 03:29:10 -0400 (EDT)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j8171IsH098040;
	Thu, 1 Sep 2005 00:01:18 -0700 (PDT)
	(envelope-from owner-ietf-mxcomp@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j8171IiG098039;
	Thu, 1 Sep 2005 00:01:18 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mxcomp@mail.imc.org using -f
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j8171GeA098031
	for <ietf-mxcomp@imc.org>; Thu, 1 Sep 2005 00:01:16 -0700 (PDT)
	(envelope-from gim-ietf-mxcomp@gmane.org)
Received: from root by ciao.gmane.org with local (Exim 4.43)
	id 1EAj3y-0002h5-1c
	for ietf-mxcomp@imc.org; Thu, 01 Sep 2005 09:00:42 +0200
Received: from c-134-88-106.hh.dial.de.ignite.net ([62.134.88.106])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <ietf-mxcomp@imc.org>; Thu, 01 Sep 2005 09:00:42 +0200
Received: from nobody by c-134-88-106.hh.dial.de.ignite.net with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <ietf-mxcomp@imc.org>; Thu, 01 Sep 2005 09:00:42 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-mxcomp@imc.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject:  Resent-* oddities (was: Additional appeal against publication of draft-lyon-senderid-* [...])
Date:  Thu, 01 Sep 2005 08:45:03 +0200
Organization:  <URL:http://purl.net/xyzzy>
Lines: 39
Message-ID:  <4316A36F.762D@xyzzy.claranet.de>
References:  <Pine.LNX.4.62.0508290656240.16767@sokol.elan.net>
	 <43134EB0.300@xyzzy.claranet.de> <Pine.LNX.4.60.0508311833530.13347@hermes-1.csi.cam.ac.uk>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: c-134-88-106.hh.dial.de.ignite.net
X-Mailer: Mozilla 3.0 (OS/2; U)
Cc: spf-discuss@v2.listbox.com, ietf@ietf.org
Cc: spf-discuss@v2.listbox.com, ietf-mxcomp@imc.org
Sender: owner-ietf-mxcomp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mxcomp/mail-archive/>
List-Unsubscribe: <mailto:ietf-mxcomp-request@imc.org?body=unsubscribe>
List-ID: <ietf-mxcomp.imc.org>
Content-Transfer-Encoding: 7bit


Tony Finch wrote:

>> the author can't say "updates 2822", how should he fix it ? 
>> As you said the 822 issue is mentioned in the senderid-pra
>> draft.

> Regarding RFC 822, the S-ID draft doesn't mention the fact
> that a large proportion of software which does something
> useful with Resent- headers still implements the 822 syntax,
> not the 2822 syntax.

Except from all PRA-purposes and maybe MUAs displaying these
Resent-* header fields somehow (822 or 2822):  What other uses
do you have in mind ?

Maybe that was discussed somewhere in MARID last year, in that
case I either missed it or didn't get it.

A related issue, apparently 2822 twisted the syntax (more than
one Resent-* block allowed) _and_ the semantics.  Dave's "old"
822 concept could reflect "forwarding" (maybe - I'm not sure).

If that's true 822-Resent-* and PRA are semantically similar,
the only missing piece would be to either allow more than one
"block" (like 2822), or "invalidate" old Resent-* header fields
somehow, e.g. William's Original-* idea.

While I'm at it:  How's that supposed to work with RfC 2476bis
8.1 "MAY add Sender" ?  Apparently 2476bis 8.1 is still based
on the old 822-concept of Resent-* (?)

Or does it ignore the issue ?  Is this part of the PRA-mess in
fact "our" fault (for a definition of TINW including everybody
who reviewed the gellens-submit drafts) ?

Of course I watched 2476 6.1 (and also 8.1), it's essential for
stuff like draft-hutzler-spamops or "op=auth", but something
with Resent-* is very odd, and it's not necessarily PRA.  Bye





From owner-ietf-mxcomp@mail.imc.org Thu Sep 01 10:15:47 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EApr0-0008Mn-Ib
	for marid-archive@megatron.ietf.org; Thu, 01 Sep 2005 10:15:47 -0400
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06581
	for <marid-archive@lists.ietf.org>; Thu, 1 Sep 2005 10:15:44 -0400 (EDT)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j81DhFOH032895;
	Thu, 1 Sep 2005 06:43:15 -0700 (PDT)
	(envelope-from owner-ietf-mxcomp@mail.imc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j81DhFqX032894;
	Thu, 1 Sep 2005 06:43:15 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mxcomp@mail.imc.org using -f
Received: from ppsw-1.csi.cam.ac.uk (ppsw-1.csi.cam.ac.uk [131.111.8.131])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j81DhE4n032884
	for <ietf-mxcomp@imc.org>; Thu, 1 Sep 2005 06:43:14 -0700 (PDT)
	(envelope-from fanf2@hermes.cam.ac.uk)
X-Cam-SpamDetails: Not scanned
X-Cam-AntiVirus: No virus found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:36192)
	by ppsw-1.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.151]:25)
	with esmtpa (EXTERNAL:fanf2) id 1EApLS-0005IF-4S (Exim 4.51)
	(return-path <fanf2@hermes.cam.ac.uk>); Thu, 01 Sep 2005 14:43:10 +0100
Received: from fanf2 (helo=localhost) by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk)
	with local-esmtp id 1EApLS-0003jr-BN (Exim 4.43)
	(return-path <fanf2@hermes.cam.ac.uk>); Thu, 01 Sep 2005 14:43:10 +0100
Date: Thu, 1 Sep 2005 14:43:10 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Frank Ellermann <nobody@xyzzy.claranet.de>
cc: ietf@ietf.org, ietf-mxcomp@imc.org, spf-discuss@v2.listbox.com
Subject: Re: Resent-* oddities (was: Additional appeal against publication
 of	draft-lyon-senderid-* [...])
In-Reply-To: <4316A36F.762D@xyzzy.claranet.de>
Message-ID: <Pine.LNX.4.60.0509011420430.13347@hermes-1.csi.cam.ac.uk>
References: <Pine.LNX.4.62.0508290656240.16767@sokol.elan.net>
 <43134EB0.300@xyzzy.claranet.de> <Pine.LNX.4.60.0508311833530.13347@hermes-1.csi.cam.ac.uk>
 <4316A36F.762D@xyzzy.claranet.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-mxcomp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mxcomp/mail-archive/>
List-Unsubscribe: <mailto:ietf-mxcomp-request@imc.org?body=unsubscribe>
List-ID: <ietf-mxcomp.imc.org>


On Thu, 1 Sep 2005, Frank Ellermann wrote:
>
> > Regarding RFC 822, the S-ID draft doesn't mention the fact
> > that a large proportion of software which does something
> > useful with Resent- headers still implements the 822 syntax,
> > not the 2822 syntax.
>
> Except from all PRA-purposes and maybe MUAs displaying these
> Resent-* header fields somehow (822 or 2822):  What other uses
> do you have in mind ?

Ignoring PRA, there are two current sides to the handling of Resent-*:
message submission and message display. An 822 display end can probably
muddle along OK when presented by a 2822 message. An 822 message
submission server will probably do something wrong when fixing up a 2822
message that has been re-sent more than once. A 2822 submission server
will have to have some fairly good heuristics to gracefully handle 822
re-sent messages. Things get even more interesting if an 822-re-sent
message is then 2822-re-sent, because the header order of the original
re-sending has to be fixed.

Sender-ID effecively requires that this kind of submission server fix-up
must be implemented by MTAs and MDAs that do aliasing / redirecting /
forwarding.

> While I'm at it:  How's that supposed to work with RfC 2476bis
> 8.1 "MAY add Sender" ?  Apparently 2476bis 8.1 is still based
> on the old 822-concept of Resent-* (?)

It doesn't address Resent-* at all so one would have to work out for
oneself how a submission server should treat them. This is clearly a bug.
(Is it too late to fix submit-bis now it is in the RFC Editor queue?)
Specifying what to do with them is, however, tricky. Sender-ID lacks this
specification too.

Tony.
-- 
f.a.n.finch  <dot@dotat.at>  http://dotat.at/
BISCAY: WEST 5 OR 6 BECOMING VARIABLE 3 OR 4. SHOWERS AT FIRST. MODERATE OR
GOOD.




