Re: [ietf-dkim] SSP requirements

Mark Delany <MarkD+dkim@yahoo-inc.com> Sat, 05 August 2006 05:14 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9EUw-0007mJ-Q6 for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 01:14:54 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9EUs-0007xb-Ck for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 01:14:54 -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 k755A8Uq012481; Fri, 4 Aug 2006 22:10:08 -0700
Received: from snake.corp.yahoo.com (snake.corp.yahoo.com [216.145.52.229]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with SMTP id k7559tXn012454 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 22:09:55 -0700
Received: (qmail 74837 invoked by uid 6042); 5 Aug 2006 05:09:30 -0000
Delivered-To: markd-intercept-ietf-dkim@mipassoc.org
DomainKey-Trace: U=http://domainkeys.sourceforge.net; V=$Revision: 1.4 $; h=::::::::::12::::::::::::::::::::::34::::::::1:1::2:1:14:19:1:43:5:7:6:10:10:9:3:11:4:17:2:5:1:5::7:2::3:6::2:::2::::5:::1::4:4:4::1:::::1::1::::18:2:19:7:34:5:5:3:31:1:8:11:21:18:28:8:5:11:15:17:7:2:1:1:6; H=::::::::::12:::12:::::::::::::::::::34::::::::1:1::2:1:14:19:1:43:5:7:6:10:10:9:3:11:4:17:2:5:1:5::7:2::3:6::2:::2::::5:::1::4:4:4::1:::::1::1::::18:2:19:7:34:5:5:3:31:1:8:11:21:18:28:8:5:11:15:17:7:2:1:1:6; b=::::::::::28::::::::::::::::::::::187::4:::::16:1:1:::9:5:10::9::1:1:1:2:1::1::3::::8:::3:::::1:::9:1::1:2::1:1:::3:4:::::1::::::::77:11:14:21:104:15:20:32:54::8:35:22:67:65:20:2:56:66:94:26:7:16:1:15; B=::::::::::28:::28:::::::::::::::::::187::4:::::16:1:1:::9:5:10::9::1:1:1:2:1::1::3::::8:::3:::::1:::9:1::1:2::1:1:::3:4:::::1::::::::77:11:14:21:104:15:20:32:54::8:35:22:67:65:20:2:56:66:94:26:7:16:1:15;
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=snake; d=yahoo-inc.com; b=tC4FPJPE41EGuIEXXcHVSAjwvrOZZo61fifqmJt0IhKehzUCniDwP4dSv+Wnlan1
Received: (qmail 74831 invoked by uid 6042); 5 Aug 2006 05:09:30 -0000
Message-ID: <20060805050930.74829.qmail@snake.corp.yahoo.com>
Date: Sat, 05 Aug 2006 05:09:30 +0000
From: Mark Delany <MarkD+dkim@yahoo-inc.com>
To: ietf-dkim@mipassoc.org
Subject: Re: [ietf-dkim] SSP requirements
Mail-Followup-To: ietf-dkim@mipassoc.org
References: <44D404C8.6070401@mtcc.com> <20060805034058.861.qmail@simone.iecc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <20060805034058.861.qmail@simone.iecc.com>
X-Songbird: Clean, Clean
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.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

On Sat, Aug 05, 2006 at 03:40:58AM -0000, John Levine allegedly wrote:
> >I can't gather requirements if I can't make any sense of what you're saying.
> 
> That's a reasonable concern.
> 
> The fog around SSP is so opaque that I'm really wondering if it
> wouldn't make more sense to punt and wait for people to do enough
> experiments to understand what turns out to be useful.

That's a reasonable proposition. It's certainly the case that we're
dealing with parties who want to make bi-lateral "I sign all"
arrangements with us, but it's early days so measuring the value an
generality of that is some way off.

Their thinking is that they don't need Internet-wide support (or
perhaps they don't want to wait for it), all they need is enough
support to make the attackers move onto an easier target. Yes,
self-preservation is not pretty, but it's common.

As far as I recall, we have never been propositioned for any
bi-lateral that is less rigid than "I sign all" for a given
domain. From this list it's clear that senders must be clammering for
more subtle policies, but those senders aren't talking to us so I'm
not competent in those discussions.


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