IETF Logo Mail Archive

Re: [ietf-dkim] A more fundamental SSP axiom

Scott Kitterman <ietf-dkim@kitterman.com> Sun, 06 August 2006 15:15 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9kLI-0005iD-El for ietf-dkim-archive@lists.ietf.org; Sun, 06 Aug 2006 11:15:04 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9kLH-0008EG-34 for ietf-dkim-archive@lists.ietf.org; Sun, 06 Aug 2006 11:15:04 -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 k76F9ZGB026185; Sun, 6 Aug 2006 08:09:35 -0700
Received: from mailout00.controlledmail.com (mailout00.controlledmail.com [70.91.79.101]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k76F87YG026026 for <ietf-dkim@mipassoc.org>; Sun, 6 Aug 2006 08:08:08 -0700
Received: from mailout00.controlledmail.com (localhost [127.0.0.1]) by mailout00.controlledmail.com (Postfix) with ESMTP id A06245CC595; Sun, 6 Aug 2006 15:07:30 +0000 (UTC)
Received: from [70.218.235.43] (43.sub-70-218-235.myvzw.com [70.218.235.43]) (using SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mailout00.controlledmail.com (Postfix) with ESMTP; Sun, 6 Aug 2006 15:07:28 +0000 (UTC)
Mime-Version: 1.0
X-Mailer: SnapperMail 1.9.5.01 by Snapperfish, www.snappermail.com
To: ietf-dkim@mipassoc.org
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
From: Scott Kitterman <ietf-dkim@kitterman.com>
Date: Sun, 06 Aug 2006 08:06:00 -0600
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Message-Id: <20060806150730.A06245CC595@mailout00.controlledmail.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.2 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a

On Wed, 02 Aug 2006 10:07:52 -0700 Dave Crocker <dhc@dcrocker.net> wrote:

>Bottom Line:
>
>     Although it is essential that a protocol specification be deployed 
only
>after due deliberation, it is equally essential that it be concise, 
coherent and
>compelling.
>
>     In other words the market needs to understand it and needs to believe 
its
>adoption is important... for the near term.
>
>All of this argues strongly for the criterion I suggested.
>
OK, but that's all fodder for the final design.  We are currently 
discussing requirements.  Prematurely cutting off requirements discussion 
has its own risks.

I agree the what we deliver in the end must be as simple as reasoanbly 
possible, but the time to decide what that is has not yet arrived.

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

v2.23.0 | Report a Bug | By Email