Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec-algo-imp-status-04.txt
Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 12 March 2013 13:38 UTC
Return-Path: <ajs@anvilwalrusden.com>
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 EEA1B21F8A99 for <dnsext@ietfa.amsl.com>; Tue, 12 Mar 2013 06:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.803
X-Spam-Level:
X-Spam-Status: No, score=-0.803 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 t7pXgB23MVdU for <dnsext@ietfa.amsl.com>; Tue, 12 Mar 2013 06:38:54 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id D23B521F8BA2 for <dnsext@ietf.org>; Tue, 12 Mar 2013 06:38:53 -0700 (PDT)
Received: from crankycanuck.ca (dhcp-2430.meeting.ietf.org [130.129.36.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 4E6D18A031 for <dnsext@ietf.org>; Tue, 12 Mar 2013 13:38:53 +0000 (UTC)
Date: Tue, 12 Mar 2013 09:38:30 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsext@ietf.org
Message-ID: <20130312133829.GB39133@crankycanuck.ca>
References: <20130311152035.4888.59295.idtracker@ietfa.amsl.com> <20130311191607.GF38303@crankycanuck.ca> <alpine.BSF.2.00.1303111558310.25246@fledge.watson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1303111558310.25246@fledge.watson.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
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 13:38:55 -0000
Sam, Thanks for your conversation in the hall. More below. On Mon, Mar 11, 2013 at 04:13:17PM -0400, Samuel Weiler wrote: > I think something needs to change. Most likely, we just need to > restate in the text (not just the table) the status of RSASHA1 and > RSAMD5. 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. Note that, if we do this, we pass through the IESG changeover, so this document will need to be processed by a new IESG (with the additional snags that might imply). Given that the definitions in previous drafts were _also_ in the table, I'm a little concerned that this is now being offered as a substantive reason to override prior consensus. Would it be sufficient to extend the sentence in section 1 to make clearer that the table is the official line here? That is OLD, sec 1 para 3: This document defines the current implementation status for all registered algorithms. NEW, sec 1 para 3: This document defines the current implementation status for all registered algorithms; the definitions are found in the table in Section 2.3. Will that do? Best, A (as shepherd) -- Andrew Sullivan ajs@anvilwalrusden.com
- [dnsext] I-D Action: draft-ietf-dnsext-dnssec-alg… internet-drafts
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Joe Abley
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Joe Abley
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Samuel Weiler
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Joe Abley
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Samuel Weiler
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Ralph Droms (rdroms)
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Joe Abley
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Andrew Sullivan
- Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec… Ralph Droms (rdroms)