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

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G92Zu-0004RP-IB for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 12:31:14 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G92Zt-0002Fk-5S for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 12:31:14 -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 k74GV3u9013533; Fri, 4 Aug 2006 09:31:03 -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 k74GUvvt013477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 09:30:57 -0700
DKIM-Signature: v=0.4; a=rsa-sha256; q=dns/txt; l=1455; t=1154709031; x=11 55573031; 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:=20=20dcrocker@bbiw.net |Cc:=20DKIM=20List=20<ietf-dkim@mipassoc.org>|Content-Transfer-Encoding:=20 7bit|MIME-Version:=201.0|Content-Type:=20text/plain=3B=20charset=3DISO-8859 -1=3B=20format=3Dflowe d; bh=VctVrOeT5DguIEVCLRTeWYTX+L8Esxjj1orUZF90eto=; b=Zc49EfFgUsvKxP4yV/jcb3oP1/TsGQ5YNcDuV5f+192If/yVY5ZKLJMt4QPOTL8V1bX6EPNX IbtkniN5bbNTTFlv5vUuxCh22zpvN5MjeaKHj0LOQaH0SmDpunLxGwAJ;
DKIM-Signature: a=rsa-sha1; q=dns; l=1455; t=1154709031; x=1155573031; 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:=20dcrocker@bbiw.net|Cc:DKIM=20List=20<ietf-d kim@mipassoc.org>|Content-Transfer-Encoding:7bit|MIME-Version:1.0|Content-T ype:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowe d; X=v=3Dcisco.com=3B=20h=3DTHgzsy76Cqx29/einu/PnNiEwmM=3D; b=QeoJPYAeFCeru0cYEjg0Z2/svGb4VSwjMsmEQbFeEZU1F6d6hd20C7PeVJSYr1YCpfZINRmD bQw83W8cy/hJbfRCtZD2LVkAQREzWEEkgUrSE9z9V7Nyc0XOiEI6Wmx/;
Received: from [216.102.208.13] (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 k74GUUu0016724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2006 09:30:31 -0700
Message-ID: <44D37621.2020905@mtcc.com>
Date: Fri, 04 Aug 2006 09:30:25 -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: dcrocker@bbiw.net
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
References: <20060802002353.U59653@simone.iecc.com> <44D0E259.7040400@mtcc.com> <20060802165510.X1168@simone.iecc.com> <44D160BD.7080209@mtcc.com> <20060802223619.E86316@simone.iecc.com> <44D24A20.6050109@mtcc.com> <20060803153457.X33570@simone.iecc.com> <44D36203.2060803@mtcc.com> <20060804112731.I21459@simone.iecc.com> <44D36B4A.2050903@mtcc.com> <20060804114527.Y27352@simone.iecc.com> <44D37206.7070209@dcrocker.net>
In-Reply-To: <44D37206.7070209@dcrocker.net>
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: DKIM List <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: 69a74e02bbee44ab4f8eafdbcedd94a1

Dave Crocker wrote:

>John L wrote:
>  
>
>>I'm trying to think about what I'll do when DKIM is in wide use, I get
>>mail from thousands of sources that publish SSP info.  If SSP says "I
>>sign everything" I have trouble figuring a use for it other than a flat
>>reject of unsigned messages or at least 4.9 points in a five point
>>scoring spam filter.  I REALLY do not want an SSP that says "I sign
>>everything, and here is my estimate on a 0 to 10 scale of how much you
>>should care."
>>    
>>
>
>
>Right.   SSP stands a much greater chance of being useful if it a) answers
>questions we believe the receivers will want to have answered, and b) the
>questions pertain to *simple* statements about signer/sender behaviors.
>
>Certainly this kind of minimal model is essential for initial adoption and use.
>  
>
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; nobody is going to
tolerate the false positives except for a narrow class of transactional
mail. As such SSP would be extremely narrow and unuseful for the vast email
population to the point of being: why bother?

In any case, I already outlined a scenario for which a receiver would
find the additional information very interesting.

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