Re: [ietf-dkim] A more fundamental SSP axiom

Michael Thomas <mike@mtcc.com> Fri, 04 August 2006 21:55 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G97dP-0001k4-7n for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 17:55:11 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G97dN-0005AM-RM for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 17:55:11 -0400
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 k74LnYoe026608; Fri, 4 Aug 2006 14:49:34 -0700
Received: from fasolt.mtcc.com (adsl-216-102-208-10.dsl.snfc21.pacbell.net [216.102.208.10]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74LnL3k026591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 14:49:22 -0700
DKIM-Signature: v=0.4; a=rsa-sha256; q=dns/txt; l=1367; t=1154728131; x=11 55592131; c=relaxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subj ect:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z= From:=20Michael=20Thomas=20<mike@mtcc.com>|Subject:=20Re=3A=20[ietf-dkim]=2 0A=20more=20fundamental=20SSP=20axiom|Sender:=20|To:=20John=20Levine=20<joh nl@iecc.com>|Cc:=20=20ietf-dkim@mipassoc.org|Content-Transfer-Encoding:=207 bit|MIME-Version:=201.0|Content-Type:=20text/plain=3B=20charset=3DISO-8859- 1=3B=20format=3Dflowe d; bh=LxgCWH5b28ND9nqiVZial9h9KCd+AXZcqOI4Weepnus=; b=QAySIHbGgIKMn1OgVc3fyJ/tYu6zbE4hdlOu6TbgfL7x6vmErnrg8ZD1XmOvoo43d2pvsAg7 KSGofADdBtUQ+dm6iiRiem7wM35KTGXIksSceTBUHH2KW8Yg3syjhmFj;
DKIM-Signature: a=rsa-sha1; q=dns; l=1367; t=1154728131; x=1155592131; c=r elaxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subject:Content-T ransfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:Michael= 20Thomas=20<mike@mtcc.com>|Subject:Re=3A=20[ietf-dkim]=20A=20more=20fundame ntal=20SSP=20axiom|Sender:|To:John=20Levine=20<johnl@iecc.com>|Cc:=20ietf-d kim@mipassoc.org|Content-Transfer-Encoding:7bit|MIME-Version:1.0|Content-Ty pe:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowe d; X=v=3Dcisco.com=3B=20h=3DTHgzsy76Cqx29/einu/PnNiEwmM=3D; b=Lzf8XJlFNQJwsaxmw011FQka79kLL2CqUU/o5vh/auTmPGCkLbDvK1SF8j/wxfkdIkP1P01F JPszTIVKPTMXtQv/I1FEtNYQw7RM2eMjHRCj63PzvF1GR5h8s3zKN4nU;
Received: from [192.168.0.102] (sj-natpool-220.cisco.com [128.107.248.220]) (authenticated bits=0) by fasolt.mtcc.com (8.13.6/8.13.1) with ESMTP id k74LmnEK007375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2006 14:48:51 -0700
Message-ID: <44D3C0BB.9000405@mtcc.com>
Date: Fri, 04 Aug 2006 14:48:43 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Thunderbird/0.8 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
References: <20060804173538.54245.qmail@simone.iecc.com>
In-Reply-To: <20060804173538.54245.qmail@simone.iecc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Authentication-Results: fasolt.mtcc.com; header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; ); header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; );
X-XIPE-SCORES: dispose=pass; ACD=1.00; CLAM=0.00; COMPLY=0.00; URL=0.00; SA=0.00; HONEY=0.00;
X-Songbird: Clean, Clean
Cc: 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.2 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

John Levine wrote:

>>What I have yet to hear is any sort of consituency for a monolithic
>>"i sign everything" beyond the statements@bigbank scenario. I really
>>don't buy John's small lawfirm scenario unless he can swear that none
>>of their users or correspondents use Yahoogroups;
>>    
>>
>
>Well, actually, since Yahoo will certainly be DKIM signing its mail,
>we can expect their reputation to be the one people use.  In the more
>general case, if they publish we sign everything and don't have a
>policy against using a work address to join mailing lists, they get
>what they get. Or if the only collateral damage is that people's
>posts to Yahoo groups about embroidered kittens get lost, they won't
>care.
>  
>

In other words, you really have no clue as to how these people use email
and what the collateral damage would be. The average small firm/company
doesn't even understand the difference between a mailing list, a blog
or a discussion board. And you expect them to be able to make an informed
decision?

>>In any case, I already outlined a scenario for which a receiver would
>>find the additional information very interesting.
>>    
>>
>
>Speaking as a receiver, I have to say I didn't find that info either
>useful or interesting.
>  
>
I wasn't aware that you wrote spam filters for a living.

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