IETF Logo Mail Archive

Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec-algo-imp-status-04.txt

Samuel Weiler <weiler@watson.org> Tue, 12 March 2013 14:18 UTC

Return-Path: <weiler@watson.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8179921F8B4C for <dnsext@ietfa.amsl.com>; Tue, 12 Mar 2013 07:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level:
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zsvC5qBI5hVt for <dnsext@ietfa.amsl.com>; Tue, 12 Mar 2013 07:18:04 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id CB80621F8B4A for <dnsext@ietf.org>; Tue, 12 Mar 2013 07:18:03 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.5/8.14.5) with ESMTP id r2CEGkoU030237; Tue, 12 Mar 2013 10:16:46 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.5/8.14.5/Submit) with ESMTP id r2CEGkXu030234; Tue, 12 Mar 2013 10:16:46 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Tue, 12 Mar 2013 10:16:46 -0400
From: Samuel Weiler <weiler@watson.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
In-Reply-To: <20130312133829.GB39133@crankycanuck.ca>
Message-ID: <alpine.BSF.2.00.1303121006250.27185@fledge.watson.org>
References: <20130311152035.4888.59295.idtracker@ietfa.amsl.com> <20130311191607.GF38303@crankycanuck.ca> <alpine.BSF.2.00.1303111558310.25246@fledge.watson.org> <20130312133829.GB39133@crankycanuck.ca>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Tue, 12 Mar 2013 10:16:46 -0400 (EDT)
Cc: dnsext@ietf.org
Subject: Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec-algo-imp-status-04.txt
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 14:18:04 -0000

On Tue, 12 Mar 2013, Andrew Sullivan wrote:

> It appears that we now agree that the table covers everything, and 
> that the text in section 2.2 is just rationale for some algorithms' 
> state.  If I understand your concern, you'd prefer to see the table 
> in section 2.2 to be expressed instead as running text.

Not quite.  I think the table in 2.3 is complete.  HOWEVER, the text 
in 2.2 sounds like it intends to be complete, and it differs from the 
table.

> Will that do?

That is clunky.

My suggestion:  add two sentences to 2.2 explaining the additional 
non-Optional entires in the table in 2.3: RSASHA1 and RSAMD5.

"RSASHA1 has an implementation status of Must Implement, consistent 
with [RFC4034].  RSAMD5 has an implementation status of Must Not 
Implement because of known weaknesses in MD5."

Or something like that.

-- Sam

v2.23.0 | Report a Bug | By Email