Re: [ietf-dkim] SSP requirements

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sun, 06 August 2006 11:04 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9gQp-0007Ay-Ap for ietf-dkim-archive@lists.ietf.org; Sun, 06 Aug 2006 07:04:31 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9gQn-0006et-VH for ietf-dkim-archive@lists.ietf.org; Sun, 06 Aug 2006 07:04:31 -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 k76B3I4P028452; Sun, 6 Aug 2006 04:03:19 -0700
Received: from relay.imagine.ie (relay.imagine.ie [87.232.1.41]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k76B36LB028421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Sun, 6 Aug 2006 04:03:07 -0700
Received: from mail2.int.imagine.ie (mail2 [87.232.1.153]) by relay.imagine.ie (Postfix) with ESMTP id 2C10F40AD; Sun, 6 Aug 2006 12:02:41 +0100 (IST)
Received: from [127.0.0.1] (dsl-102-234.cust.imagine.ie [87.232.102.234]) by mail2.int.imagine.ie (8.13.4/8.13.4/Debian-3) with ESMTP id k76B2dBP020466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 6 Aug 2006 12:02:40 +0100
Message-ID: <44D5CC6A.1080408@cs.tcd.ie>
Date: Sun, 06 Aug 2006 12:03:06 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Hector Santos <hsantos@santronics.com>
Subject: Re: [ietf-dkim] SSP requirements
References: <20060805034058.861.qmail@simone.iecc.com> <44D4FB5A.5020704@mtcc.com> <00e801c6b8cf$b4d7f230$0201a8c0@hdev1>
In-Reply-To: <00e801c6b8cf$b4d7f230$0201a8c0@hdev1>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Bayes-Prob: 0.0001 (Score 0)
X-Spam-Score: 0.00 () [Hold at 8.00]
X-Canit-Stats-ID: 1906031 - 59a961e4b26a (trained as not-spam)
X-CanItPRO-Stream: outgoing
X-Scanned-By: CanIt (www . roaringpenguin . com) on 87.232.1.53
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: d6b246023072368de71562c0ab503126

Hector,

I missed this one earlier.

Hector Santos wrote:
> 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.

This is also out of line. You're accusing someone of bad faith (which
is totally out-of-line) and without even waiting to see the I-D (which
is ridiculously premature).

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