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

Michael Thomas <mike@mtcc.com> Thu, 03 August 2006 02:40 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8T8V-0004Yw-5h for ietf-dkim-archive@lists.ietf.org; Wed, 02 Aug 2006 22:40:35 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8T4w-0005vM-7R for ietf-dkim-archive@lists.ietf.org; Wed, 02 Aug 2006 22:36:56 -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 k732ZGr8021584; Wed, 2 Aug 2006 19:35:17 -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 k732ZCe4021529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Wed, 2 Aug 2006 19:35:13 -0700
DKIM-Signature: v=0.4; a=rsa-sha256; q=dns/txt; l=818; t=1154572478; x=115 5436478; c=relaxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subje ct:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=F rom:=20Michael=20Thomas=20<mike@mtcc.com>|Subject:=20Re=3A=20[ietf-dkim]=20 A=20more=20fundamental=20SSP=20axiom|Sender:=20|To:=20John=20L=20<johnl@iec c.com>|Cc:=20DKIM=20List=20<ietf-dkim@mipassoc.org>|Content-Transfer-Encodi ng:=207bit|MIME-Version:=201.0|Content-Type:=20text/plain=3B=20charset=3DIS O-8859-1=3B=20format=3Dflowe d; bh=X11AbzaLqwOuHxrGIxTx0U/I/5TftAS7usWs7mrU14U=; b=lR3xlTQSnlEG3b77jX6OjxhM/mFwabfGaqkZru9sA/Gtbe6mEWOH2sI3YGWS0Fh5mKFbNimm dcdRdeO/4JsDE6HOpCV7HbgzDjQ/OkcjHkW/0PZg+7Qquw7qneb8XjnR;
DKIM-Signature: a=rsa-sha1; q=dns; l=818; t=1154572478; x=1155436478; c=re laxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subject:Content-Tr ansfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:Michael=2 0Thomas=20<mike@mtcc.com>|Subject:Re=3A=20[ietf-dkim]=20A=20more=20fundamen tal=20SSP=20axiom|Sender:|To:John=20L=20<johnl@iecc.com>|Cc:DKIM=20List=20< ietf-dkim@mipassoc.org>|Content-Transfer-Encoding:7bit|MIME-Version:1.0|Con tent-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowe d; X=v=3Dcisco.com=3B=20h=3DTHgzsy76Cqx29/einu/PnNiEwmM=3D; b=XdmbG5g++WAFlX6RMHWivIlzZDAzk0i4IcnYzpPO02IUtLaXfjmMx9uGRxEUrrAdaG5aki+1 F9OpgsLF4YBYXuINUTrCshCPFsJMuv8byQqbrmDg4oCS68SR81MwopBD;
Received: from [216.102.208.10] (IDENT:U2FsdGVkX1+G280z1W2yYz+XKUYU6ERnTV/glAwGqWA@fasolt.mtcc.com [216.102.208.10] (may be forged)) (authenticated bits=0) by fasolt.mtcc.com (8.13.6/8.13.1) with ESMTP id k732YbBN018215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Aug 2006 19:34:38 -0700
Message-ID: <44D160BD.7080209@mtcc.com>
Date: Wed, 02 Aug 2006 19:34:37 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Thunderbird/1.0.6 Fedora/1.0.6-1.1.fc3 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John L <johnl@iecc.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
References: <20060802002353.U59653@simone.iecc.com> <44D0E259.7040400@mtcc.com> <20060802165510.X1168@simone.iecc.com>
In-Reply-To: <20060802165510.X1168@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: 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.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

John L wrote:

>> I think a more fundamental question is who the consumers of SSP 
>> information
>> are.  I think that everybody agrees that DKIM receivers are an important
>> constituent, but are they the only ones? It doesn't seem very hard to 
>> envision other consumers.
>
>
> Usage scenarios would be very helpful.  As Dave noted, if people can 
> throw stuff into a protocol because it might be useful for something 
> nobody actually plans to do, you end up with terminal bloat.

Please don't shoot the messanger: I'm just asking. It's a fairly common 
occurrance
that a successful protocol will have many more uses/consumers than was 
originally envisioned.
Especially in the case of spam, it's not very clear what the mutations 
will be so it's
worth questioning, IMO.

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