Re: [Cfrg] [saag] [Fwd: I-D ACTION:draft-turner-sha0-sha1-seccon-00.txt]

Sean Turner <turners@ieca.com> Thu, 07 October 2010 01:19 UTC

Return-Path: <turners@ieca.com>
X-Original-To: cfrg@core3.amsl.com
Delivered-To: cfrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2B723A725E for <cfrg@core3.amsl.com>; Wed, 6 Oct 2010 18:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.264
X-Spam-Level:
X-Spam-Status: No, score=-102.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBgj6avA-H-p for <cfrg@core3.amsl.com>; Wed, 6 Oct 2010 18:19:31 -0700 (PDT)
Received: from smtp112.biz.mail.sp1.yahoo.com (smtp112.biz.mail.sp1.yahoo.com [69.147.92.225]) by core3.amsl.com (Postfix) with SMTP id 9F6723A7253 for <cfrg@irtf.org>; Wed, 6 Oct 2010 18:19:31 -0700 (PDT)
Received: (qmail 77862 invoked from network); 7 Oct 2010 01:20:30 -0000
Received: from thunderfish.local (turners@96.241.10.225 with plain) by smtp112.biz.mail.sp1.yahoo.com with SMTP; 06 Oct 2010 18:20:30 -0700 PDT
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: QKXUOusVM1nbuDREagTxys3aRke9JzhXZ5XaeNC3YpeXqyi wr8vsbqWjtb6es9GXpHSdjZrShr.lFVavc2XLLNYV95JuCY1vubjdrEst6D4 d_Pft0f3a4Z0tXZGRkeDTz6U.HT.iIi7EhwQG4EWiQz.3ELSDzImqvDw6O4S vU18SMs4hY4ZQSuylfhbrL2K_w1rR4yh1TA8GsSETBO16zGPdhJF3ZA1LCFa dSRnXJ6tQeKYMcWkuiAqmlm1rig255bxJoapqsF1i3uQO0AU-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4CAD205D.6090701@ieca.com>
Date: Wed, 06 Oct 2010 21:20:29 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: cfrg@irtf.org, saag@ietf.org
References: <4CA65AD7.80300@ieca.com> <p06240808c8cd060efcb4@[10.20.30.158]> <4CA8ECA9.9020201@gondrom.org> <p06240834c8cea6ec688d@[10.20.30.158]>
In-Reply-To: <p06240834c8cea6ec688d@[10.20.30.158]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Cfrg] [saag] [Fwd: I-D ACTION:draft-turner-sha0-sha1-seccon-00.txt]
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 01:19:31 -0000

Paul Hoffman wrote:
> At 9:50 PM +0100 10/3/10, Tobias Gondrom wrote:
>> Must say I agree with Paul's concerns below (and in particular
>> hesitated too when I read the intended "MUST NOT" effect of a guidance
>> informational draft on standards documents).
>> However, I think the general idea to write a guidance ID is a good idea
>>from Tim, et al.
> 
> Fully agree (certainly more useful than such guidance coming from you or I). However, it would be nice if the document said why they were the ones writing it.

The 2119 language should not have been included.  We're only trying to 
update the security considerations not provide mandates.  This draft 
should have followed the same format as the recent MD2/4/5 security 
consideration update drafts and those don't include 2119 language. 
I'm sorry for any confusion.

We wrote this draft because somebody asked for it as part of their 
comments on the MD2/4/5 drafts (and I thought it was low hanging 
fruit).  I assure you there is no sinister plan.

We'll update the draft with the Paul's wording, remove the 2119 
reference, and address off-list comments from Ran and Sheila.

spt