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

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G93BG-0006P5-Vn for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 13:09:50 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G93BF-0004VU-JX for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 13:09:50 -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 k74H9b4U019723; Fri, 4 Aug 2006 10:09:37 -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 k74H9LZj019686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 10:09:21 -0700
DKIM-Signature: v=0.4; a=rsa-sha256; q=dns/txt; l=1262; t=1154711334; x=11 55575334; 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:=20Damon=20<deepvoice@g mail.com>|Cc:=20Steve=20Atkins=20<steve@blighty.com>, =20DKIM=20List=20<ietf -dkim@m ipassoc.org>|Content-Transfer-Encoding:=207bit|MIME-Version:=201.0|Conten t-Type:=20text/plain=3B=20charset=3DUTF-8=3B=20format=3Dflowed; bh=f+ri5xyD sOtrfB3Vhw+h6nv6HWL6GA3eBjuCdQBZ7i0=; b=FYSOYhxRyiCuMKOxh/rtZ3MQEJIStagzB9qTrN8F4SAX1xOpWpaFJjPFjqyfNoBHUchLvI1V qgh12G8CkXug44wz0QL+toscLZX82M3LRJKbrcCY+I8q+SkvKgELRyjV;
DKIM-Signature: a=rsa-sha1; q=dns; l=1262; t=1154711334; x=1155575334; 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:Damon=20<deepvoice@gmail.com>|Cc:Steve=20Atki ns=20<steve@blighty.com>,=20DKIM=20List=20<ietf-dkim@m ipassoc.org>|Content-Transfer-Encoding:7bit|MIME-Version:1.0|Content-Type :text/plain=3B=20charset=3DUTF-8=3B=20format=3Dflowed; X=v=3Dcisco.com=3B=2 0h=3D9J+1R8q3OVg0TDo2cZEg7LPE+qc=3D; b=QW/i3ZYYq/bv4hCEf1uS3QgTB5fozgkeaqE0XWSvm6n1cP1+z2qy95HYZJsIRoxcgw5X1zyi SoTruoDzUvFJ61QYUCwEaSuqJUMS6uv5kM4LPcOoLP64xsfQy5Dn/pRR;
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 k74H8r6J019638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2006 10:08:54 -0700
Message-ID: <44D37F1F.3040509@mtcc.com>
Date: Fri, 04 Aug 2006 10:08:47 -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: Damon <deepvoice@gmail.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
References: <20060802002353.U59653@simone.iecc.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> <44D37376.4020408@mtcc.com> <1F0984B3-DF97-43EB-B982-4272EC121D36@blighty.com> <62146370608040953i491e3926h1e44a90cd8456e2a@mail.gmail.com>
In-Reply-To: <62146370608040953i491e3926h1e44a90cd8456e2a@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; 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: 7aafa0432175920a4b3e118e16c5cb64

Damon wrote:

> On 8/4/06, Steve Atkins <steve@blighty.com> wrote:
>
>>
>> On Aug 4, 2006, at 9:19 AM, Michael Thomas wrote:
>>
>> > John L wrote:
>> >
>> >>   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."
>> >
>> > I assume that you'd complain if it boiled down to a single bit?
>> >
>> > 0: "mail from this domain may transit manglers, adjust accordingly"
>>
>> 0: "I sign some mail"
>
>
> A 0 _still_ means: I have a published a record just so you have
> to do more CPU/DNS work... because you are going to have to accept it
> anyway.


I'm sorry: how exactly is a protocol forcing a receiver to do anything?
If you can explain that, then maybe there really is hope for 
strangulation-over-ip.

       Mike

>
>
>>
>> > 1: "the signature should always be intact"
>> >
>>
>> 1: "I sign all mail"
>>
>> Cheers,
>>   Steve
>>
>>
>> _______________________________________________
>> NOTE WELL: This list operates according to
>> http://mipassoc.org/dkim/ietf-list-rules.html
>>
> _______________________________________________
> NOTE WELL: This list operates according to 
> http://mipassoc.org/dkim/ietf-list-rules.html


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