Re: [ietf-dkim] SSP requirements

"william(at)elan.net" <william@elan.net> Sun, 06 August 2006 00:22 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9WPo-00042T-Re for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 20:22:48 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9WPn-0005KY-FJ for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 20:22:48 -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 k760HweW027768; Sat, 5 Aug 2006 17:17:59 -0700
Received: from sokol.elan.net (sokol.elan.net [216.151.192.200]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k760HtEX027728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 17:17:55 -0700
Received: from sokol.elan.net (sokol [127.0.0.1]) by sokol.elan.net (8.13.1/8.13.1) with ESMTP id k760HMYY006122; Sat, 5 Aug 2006 17:17:22 -0700
Received: from localhost (william@localhost) by sokol.elan.net (8.13.1/8.13.1/Submit) with ESMTP id k760HLFU006118; Sat, 5 Aug 2006 17:17:21 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Sat, 05 Aug 2006 17:17:21 -0700
From: "william(at)elan.net" <william@elan.net>
To: Hector Santos <hsantos@santronics.com>
Subject: Re: [ietf-dkim] SSP requirements
In-Reply-To: <015701c6b8e3$9f7d8c10$0201a8c0@hdev1>
Message-ID: <Pine.LNX.4.62.0608051701210.11690@sokol.elan.net>
References: <20060805034058.861.qmail@simone.iecc.com><44D4FB5A.5020704@mtcc.com> <20060805163953.Q47527@simone.iecc.com> <015701c6b8e3$9f7d8c10$0201a8c0@hdev1>
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.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

On Sat, 5 Aug 2006, Hector Santos wrote:

>> Agreed.  That's what I've been thinking all along.
>
> In other words, your 3rd party dnsbl-like DAC business venture with some
> highly exploitable VBR protocol, with $10,000, $5000 entry feeds, with
> absolutely no plans for SSP, is the right solution for everyone and will
> resolved all the security issued related to DKIM.   This wasn't about the
> your so called "SSP FOG" rethorical chaos but rather a conflict of interest.
> Having SSP still in play will not serve your business well.

Hector, calm down. John does have business interests in commercial
accreditation services, however I think he in general somehow does
not like policy records (probably something to do with his dislike
of SPF) and that has not seriously changed and probably would not
have had no matter if he was working on DAC or not. Besides that DAC
seems to be more like accreditation organizations' business group
and the above mentioned fees are such organizations' membership dues
rather then actual accreditation service fees (though I hear some
accreditation service charge a lot more...).

I do want to point out though that there does seem to be number of
people on this list heavily involved in commercial accreditation
services. As many of these organization's business plan can be in
conflict with having mature email policy record framework, it would
be good if these people attempt to either avoid policy record
discussions or make their best effect to look at the world from the
point of that their (and other) accreditation systems do not exist
and in such a way try to examine use of the email policy records.

-- 
William Leibzon
Elan Networks
william@elan.net
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html