Re: [ietf-dkim] draft-ietf-dkim-threats-02 nit//[various topics]

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 11 April 2006 20:13 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTPFH-0007pz-3p for ietf-dkim-archive@lists.ietf.org; Tue, 11 Apr 2006 16:13:51 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTPFF-0001BS-N5 for ietf-dkim-archive@lists.ietf.org; Tue, 11 Apr 2006 16:13:51 -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 k3BKDJm4023428; Tue, 11 Apr 2006 13:13:20 -0700
Received: from relay.imagine.ie (relay.imagine.ie [87.232.1.40]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k3BKDEnx023338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Tue, 11 Apr 2006 13:13:16 -0700
Received: from mail1.int.imagine.ie (mail1 [87.232.1.152]) by relay.imagine.ie (Postfix) with ESMTP id 1740432EA2; Tue, 11 Apr 2006 21:12:39 +0100 (IST)
Received: from [127.0.0.1] (dsl-102-234.cust.imagine.ie [87.232.102.234]) by mail1.int.imagine.ie (8.13.4/8.13.4/Debian-3) with ESMTP id k3BKCYch017814; Tue, 11 Apr 2006 21:12:36 +0100
Message-ID: <443C0DBB.5090606@cs.tcd.ie>
Date: Tue, 11 Apr 2006 21:12:43 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Douglas Otis <dotis@mail-abuse.org>
Subject: Re: [ietf-dkim] draft-ietf-dkim-threats-02 nit//[various topics]
References: <57DB790B-C4AF-4A30-846F-36BA3A07A356@mail-abuse.org> <44356870.8080808@cs.tcd.ie> <44385BCD.5090900@cisco.com> <43CAC409-0C4D-4260-A602-278E1CAD96A4@mail-abuse.org> <443AD0BD.6050200@cs.tcd.ie> <C42E422A-8B6D-40BA-B0F3-09781D99C3A5@mail-abuse.org>
In-Reply-To: <C42E422A-8B6D-40BA-B0F3-09781D99C3A5@mail-abuse.org>
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: 823402 - e430610d03e6 (trained as not-spam)
X-CanItPRO-Stream: outgoing
X-Scanned-By: CanIt (www . roaringpenguin . com) on 87.232.1.52
X-Songbird: Clean, Clean
Cc: IETF-DKIM <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: 538aad3a3c4f01d8b6a6477ca4248793

Doug,

Douglas Otis wrote:
> 
> On Apr 10, 2006, at 2:40 PM, Stephen Farrell wrote:
> 
>>
>> Doug,
>>
>> I'm not clear if you're saying that these comments are on parts of
>> the document that changed between -01 and -02, or on parts that
>> remained the same.
>>
>> If the former, then it is fair to bring them up, *iff* your comment
>> is to the effect that the change doesn't match the resolution of
>> some specific (i.e. referenced) last call issue(s).
>>
>> If the latter, then sorry, we've had last call. Everyone got their
>> chance to raise issues. Other cases are treated the same, unless
>> compelling.
>>
>> Its too late here for me to check tonight, but I will tomorrow,
>> unless someone else on the list does that for me in the meantime
>> (he hinted:-)
> 
> http://www.sonic.net/~dougotis/dkim/ietf-dkim-threat-02-diff.html

Thanks for that. Always takes me ages to find that tool for
some reason :-(

> In the prior message, I recalled the wrong version of the threat draft.  
> Sorry for the inaccurate statement regarding the extent of the changes 
> in two sections regarding network amplification and the cryptographic 
> weaknesses.  The other suggestions do not attempt to change the meaning 
> of the draft, but were intended to improve clarity.  The existing text 
> appears to be technically in error, where corrections should be helpful 
> for future work.

Ok, so this is therefore wordsmithing in which case I guess its best
to make no change now. But if (say in response to IESG comments), we do
re-work the document, perhaps you can make your suggestions again.
I'd guess there's a fair likelihood of that, and I assume that if
this is important enough for you, you'll remember to bring it back
to the WG's attention at that point.

Cheers,
Stephen.


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