Re: [ietf-dkim] SSP requirements

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9T5M-0004pY-AI for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 16:49:28 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9T5K-00007e-TX for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 16:49:28 -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 k75KiEwx025743; Sat, 5 Aug 2006 13:44:15 -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 k75Ki9qf025722 for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 13:44:09 -0700
Received: by winserver.com (Wildcat! SMTP Router v6.1.451.8) for ietf-dkim@mipassoc.org; Sat, 05 Aug 2006 16:46:19 -0400
Received: from hdev1 ([72.144.82.177]) by winserver.com (Wildcat! SMTP v6.1.451.8) with ESMTP id 1564562844; Sat, 05 Aug 2006 16:46:18 -0400
Message-ID: <00e801c6b8cf$b4d7f230$0201a8c0@hdev1>
From: Hector Santos <hsantos@santronics.com>
To: Michael Thomas <mike@mtcc.com>, John Levine <johnl@iecc.com>
References: <20060805034058.861.qmail@simone.iecc.com> <44D4FB5A.5020704@mtcc.com>
Subject: Re: [ietf-dkim] SSP requirements
Date: Sat, 05 Aug 2006 16:42:42 -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: c1c65599517f9ac32519d043c37c5336

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


> John Levine wrote:
>
> >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 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.

This is complete hogwash and it is completely dumbfounding that a person who
was either commissioned, asked or had volunteered to write the design
requirements has already come to a own incorrect, highly subjective
conclusion about the need SSP without ever completing the work!!

This is completely unacceptable.  If you don't understand SSP and can't do
the job of writing the draft document, then it is probably best to  hand it
off to someone who does understand and is willing to be completely open
minded with ALL parties in mind and then allow chips fall where they may.

My apology to the WG chairs, but this is utterly ridiculous position coming
from a person who is suppose to write the SSP design requirements.  It reeks
badly with obvious signs of conflict of interest by specific individuals to
kill SSP.

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






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