IETF Logo Mail Archive

Re: [ietf-dkim] SSP requirements

"Hector Santos" <hsantos@santronics.com> Sat, 05 August 2006 23:07 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9VEX-0007Oh-JH for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 19:07:05 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9VEW-0005ah-5I for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 19:07:05 -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 k75N6l53007176; Sat, 5 Aug 2006 16:06:48 -0700
Received: from winserver.com (catinthebox.net [208.247.131.9]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k75N6iDR007152 for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 16:06:44 -0700
Received: by winserver.com (Wildcat! SMTP Router v6.1.451.8) for ietf-dkim@mipassoc.org; Sat, 05 Aug 2006 19:08:53 -0400
Received: from hdev1 ([72.144.82.177]) by winserver.com (Wildcat! SMTP v6.1.451.8) with ESMTP id 1573117250; Sat, 05 Aug 2006 19:08:52 -0400
Message-ID: <015701c6b8e3$9f7d8c10$0201a8c0@hdev1>
From: Hector Santos <hsantos@santronics.com>
To: John L <johnl@iecc.com>, Michael Thomas <mike@mtcc.com>
References: <20060805034058.861.qmail@simone.iecc.com><44D4FB5A.5020704@mtcc.com> <20060805163953.Q47527@simone.iecc.com>
Subject: Re: [ietf-dkim] SSP requirements
Date: Sat, 05 Aug 2006 19:05:16 -0400
Organization: Santronics Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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: 8abaac9e10c826e8252866cbe6766464

----- Original Message -----
From: "John L" <johnl@iecc.com>
To: "Michael Thomas" <mike@mtcc.com>


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

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.

Wonderful.

--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com



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

v2.23.0 | Report a Bug | By Email