Re: [secdir] secdir review of draft-ietf-dnsext-dnssec-alg-allocation-02

Samuel Weiler <weiler@watson.org> Wed, 03 March 2010 01:00 UTC

Return-Path: <weiler@watson.org>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC2F93A8863; Tue, 2 Mar 2010 17:00:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Vr84Ec4RCfjb; Tue, 2 Mar 2010 17:00:11 -0800 (PST)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by core3.amsl.com (Postfix) with ESMTP id 08B2D3A870E; Tue, 2 Mar 2010 17:00:10 -0800 (PST)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.3/8.14.3) with ESMTP id o2310Af9063070; Tue, 2 Mar 2010 20:00:10 -0500 (EST) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.3/8.14.3/Submit) with ESMTP id o23109Zn063065; Tue, 2 Mar 2010 20:00:09 -0500 (EST) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Tue, 2 Mar 2010 20:00:09 -0500 (EST)
From: Samuel Weiler <weiler@watson.org>
To: Andrew Sullivan <ajs@shinkuro.com>
In-Reply-To: <20100303000509.GR2901@shinkuro.com>
Message-ID: <alpine.BSF.2.00.1003021955090.62257@fledge.watson.org>
References: <9abf48a61003021143p6cef437fxb72fe0c3a58a684c@mail.gmail.com> <20100302203103.GJ2901@shinkuro.com> <6c9fcc2a1003021242p16379b6ai6d87f6cf497b37cb@mail.gmail.com> <20100302231204.GM2901@shinkuro.com> <alpine.BSF.2.00.1003021836230.46887@fledge.watson.org> <20100303000509.GR2901@shinkuro.com>
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, 02 Mar 2010 20:00:10 -0500 (EST)
Cc: draft-ietf-dnsext-dnssec-alg-allocation.all@tools.ietf.org, Barry Leiba <barryleiba@computer.org>, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] secdir review of draft-ietf-dnsext-dnssec-alg-allocation-02
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 01:00:11 -0000

> The -02 version of registry-fixes says
>
>   The requirement status for all new algorithms will be DISCRETIONARY
>   unless a Standards Track document changes that (possibly including
>   the Standards Track document defining the algorithm).  Only a
>   Standards Track document may make an algorithm ENCOURAGED or
>   MANDATORY or remove the MANDATORY or ENCOURAGED designation (to
>   DISCOURAGED or OBSOLETE for example).
>
> There is no reference from the current (alg-allocation) document to
> the registry-fixes doc because we were trying, very hard, to keep each
> document specific and focussed.
>
> Does that help?

No.  alg-allocation, read by itself, is still confusing.  Rather than 
cite the new metric for changing requirement status (as being 
defined/changed in registry-fixes), alg-allocation could instead cite 
the current metric.  Earlier in this thread you said that was to 
update 4034 (=standards action).

No matter what the metric is, I want alg-allocation to be explicit 
about the metric.

-- Sam