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

John L <johnl@iecc.com> Thu, 03 August 2006 07:05 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8XGW-000397-An for ietf-dkim-archive@lists.ietf.org; Thu, 03 Aug 2006 03:05:08 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8Nuk-0005D8-3J for ietf-dkim-archive@lists.ietf.org; Wed, 02 Aug 2006 17:06:02 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G8NnA-0001fF-47 for ietf-dkim-archive@lists.ietf.org; Wed, 02 Aug 2006 16:58:13 -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 k72Kv9H2007701; Wed, 2 Aug 2006 13:57:09 -0700
Received: from xuxa.iecc.com (xuxa.iecc.com [208.31.42.42]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with SMTP id k72Kv1ot007662 for <ietf-dkim@mipassoc.org>; Wed, 2 Aug 2006 13:57:01 -0700
Received: (qmail 27469 invoked from network); 2 Aug 2006 20:56:35 -0000
Received: from simone.iecc.com (208.31.42.47) by mail2.iecc.com with QMQP; 2 Aug 2006 20:56:35 -0000
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Aug 2006 20:56:35 -0000
Date: Wed, 02 Aug 2006 16:56:35 -0400
From: John L <johnl@iecc.com>
To: Michael Thomas <mike@mtcc.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <44D0E259.7040400@mtcc.com>
Message-ID: <20060802165510.X1168@simone.iecc.com>
References: <20060802002353.U59653@simone.iecc.com> <44D0E259.7040400@mtcc.com>
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
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: -3.1 (---)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

> 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.

R's,
John
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html