Re: [ietf-dkim] SSP requirements

John L <johnl@iecc.com> Sat, 05 August 2006 22:30 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9Uel-0001WM-Be for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 18:30:07 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9Uej-00076e-WD for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 18:30:07 -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 k75MTUuH003685; Sat, 5 Aug 2006 15:29:30 -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 k75MTKoM003662 for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 15:29:21 -0700
Received: (qmail 26136 invoked from network); 5 Aug 2006 20:42:14 -0000
Received: from simone.iecc.com (208.31.42.47) by mail2.iecc.com with QMQP; 5 Aug 2006 20:42:14 -0000
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Aug 2006 20:42:14 -0000
Date: Sat, 05 Aug 2006 16:42:14 -0400
From: John L <johnl@iecc.com>
To: Michael Thomas <mike@mtcc.com>
Subject: Re: [ietf-dkim] SSP requirements
In-Reply-To: <44D4FB5A.5020704@mtcc.com>
Message-ID: <20060805163953.Q47527@simone.iecc.com>
References: <20060805034058.861.qmail@simone.iecc.com> <44D4FB5A.5020704@mtcc.com>
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
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.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

> That's a pretty reasonable question, frankly. The set of domains that 
> would actually benefit from SSP from the consensus I've seen seems like 
> it's a pretty tiny fraction of the internet at large and almost 
> certainly could be handled by third party dnsbl-like or accreditation 
> schemes as well.

Agreed.  That's what I've been thinking all along.

> But it may be worth it if for no other reason to provide the transport, 
> discovery, and syntax framework for putting goodies in for the 
> experiment.

If people want to do experiements, they should do experiments.  The IESG 
would never go for an SSP spec that was just a container for data yet to 
be invented.

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