[dnsext] draft-srose-dnssec-algo-imp-status-00 (was: Re: Follow up on draft-ietf-dnsext-dnssec-registry-fixes)

Samuel Weiler <weiler@watson.org> Fri, 13 January 2012 11:55 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 423C021F8522 for <dnsext@ietfa.amsl.com>; Fri, 13 Jan 2012 03:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325, 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 GAt5NsLMbr1z for <dnsext@ietfa.amsl.com>; Fri, 13 Jan 2012 03:55:47 -0800 (PST)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id B414921F850C for <dnsext@ietf.org>; Fri, 13 Jan 2012 03:55:47 -0800 (PST)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.4/8.14.4) with ESMTP id q0DBtiXV012207; Fri, 13 Jan 2012 06:55:44 -0500 (EST) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id q0DBthr3012200; Fri, 13 Jan 2012 06:55:43 -0500 (EST) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Fri, 13 Jan 2012 06:55:43 -0500
From: Samuel Weiler <weiler@watson.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
In-Reply-To: <20120109222905.GW1820@crankycanuck.ca>
Message-ID: <alpine.BSF.2.00.1201130645500.8349@fledge.watson.org>
References: <20120109222905.GW1820@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]); Fri, 13 Jan 2012 06:55:44 -0500 (EST)
Cc: dnsext@ietf.org
Subject: [dnsext] draft-srose-dnssec-algo-imp-status-00 (was: Re: Follow up on draft-ietf-dnsext-dnssec-registry-fixes)
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: Fri, 13 Jan 2012 11:55:48 -0000

I generally support the idea behind this draft (putting current 
recommendation state in an RFC), but I have some minor concerns about 
the specific content:

"The status of RSASHA1-NSEC3-SHA1 is set to RECOMMENDED TO 
IMPLEMENT.  This is due to the fact that RSA/SHA-1 is a MUST 
IMPLEMENT."

I don't follow the logic in the above.  Why does A follow from B?

"Adding a newly specified algorithm to the registry with a compliance 
status SHALL entail obsolescing this document and replacing the 
registry table (with the new algorithm entry)."

I suggest: "Adding...with an implementation status other than OPTIONAL 
SHALL....and publishing a new document with a new complete registry 
table."

Throughout this document, "implementation status", "compliance 
status", and "implementations compliance status" appear.  I don't 
understand the difference between the three.  If there is none, pick 
one and stick to it.

In security considerations: "This document replaces the Domain Name 
System (DNS) Security Algorithm Numbers registry."  I don't think you 
intended to write that in this document.

-- Sam