Re: [ietf-dkim] Re: "I sign everything" yes/no

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 27 November 2006 13:07 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GogCZ-0001I8-2Z for ietf-dkim-archive@lists.ietf.org; Mon, 27 Nov 2006 08:07:15 -0500
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GogCT-0002A4-L5 for ietf-dkim-archive@lists.ietf.org; Mon, 27 Nov 2006 08:07:15 -0500
Received: from sb7.songbird.com (sb7.songbird.com [127.0.0.1]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id kARD6Sku005783; Mon, 27 Nov 2006 05:06:29 -0800
Received: from imx2.tcd.ie (imx2.tcd.ie [134.226.1.156]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id kARD6J0h005721 for <ietf-dkim@mipassoc.org>; Mon, 27 Nov 2006 05:06:20 -0800
Received: from Vams.imx2 (imx2.tcd.ie [134.226.1.156]) by imx2.tcd.ie (Postfix) with SMTP id 357E06824A; Mon, 27 Nov 2006 13:06:05 +0000 (GMT)
Received: from imx2.tcd.ie ([134.226.1.156]) by imx2.tcd.ie ([134.226.1.156]) with SMTP (gateway) id A00CF631E4D; Mon, 27 Nov 2006 13:06:05 +0000
Received: from [127.0.0.1] (cswireless62-26.cs.tcd.ie [134.226.62.26]) by imx2.tcd.ie (Postfix) with ESMTP id 2919A6824A; Mon, 27 Nov 2006 13:06:05 +0000 (GMT)
Message-ID: <456AE2F6.2040809@cs.tcd.ie>
Date: Mon, 27 Nov 2006 13:07:02 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Charles Lindsey <chl@clerew.man.ac.uk>
Subject: Re: [ietf-dkim] Re: "I sign everything" yes/no
References: <198A730C2044DE4A96749D13E167AD37E7E714@MOU1WNEXMB04.vcorp.ad.vrsn.com> <91A3FD7B-8B4A-4F78-9C5F-9BC66F86614D@mail-abuse.org> <4563C8D8.40909@santronics.com> <45647C86.36F3@xyzzy.claranet.de> <45648A1A.9030302@santronics.com> <op.tjg51tkv6hl8nm@clerew.man.ac.uk> <4567E1D7.6050002@cisco.com> <op.tjod3xh26hl8nm@clerew.man.ac.uk>
In-Reply-To: <op.tjod3xh26hl8nm@clerew.man.ac.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiVirus-Status: MessageID = A10CF631E4D
X-AntiVirus-Status: Host: imx2.tcd.ie
X-AntiVirus-Status: Action Taken:
X-AntiVirus-Status: NONE
X-AntiVirus-Status: Checked by TCD Vexira. (version=1.56.3 VDF=8.1414)
X-Songbird: Clean, Clean
Cc: DKIM <ietf-dkim@mipassoc.org>
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org
X-SongbirdInformation: support@songbird.com for more information
X-Songbird-From: ietf-dkim-bounces@mipassoc.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5


Charles Lindsey wrote:
> On Sat, 25 Nov 2006 06:25:27 -0000, Jim Fenton <fenton@cisco.com> wrote:
> 
>> It's not entirely forgotten; section 2.3 of draft-allman-dkim-ssp-02 
>> discusses multiple From addresses.  We thought about resolving the 
>> ambiguity by (1) arbitrarily picking the first address in the From 
>> header field, (2) picking the address in the Sender header field, or 
>> (3) querying SSP for all addresses in the From header field, and 
>> combining them somehow.  We picked (1), because we don't know whether 
>> the MUA is going to display the Sender address or not, and we felt 
>> that it is likely that it will display the first From address regardless.
> 
> And there I think you picked the wrong one. 

Fair enough that you disagree, but the main point though is that
the WG reached rough consensus.

> I have seen sufficient comments from others to the effect that the 
> Sender needs to be looked at in many situations that this matter 
> probably ought to be reviewed (does that mean raising an Issue?).

No. For base, Barry and I are using a scheme where re-opening a
decided issue (which is what you'd presumably like in this case)
requires N people supporting, for some informally defined, but
increasing, value of N (the value increases as we get closer to an
RFC). Absent an absolute storm of support, we're done on this
(and by a storm I mean >>1 voices).

So sorry but its just too late,
Stephen.

_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html