Re: [dnsext] I-D Action: draft-ietf-dnsext-dnssec-algo-imp-status-04.txt
Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 11 March 2013 20:12 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 0552821F8F7A for <dnsext@ietfa.amsl.com>; Mon, 11 Mar 2013 13:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.807
X-Spam-Level:
X-Spam-Status: No, score=-0.807 tagged_above=-999 required=5 tests=[AWL=0.033, 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 g6JQdL1UVz9C for <dnsext@ietfa.amsl.com>; Mon, 11 Mar 2013 13:12:34 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 69DB421F8F5C for <dnsext@ietf.org>; Mon, 11 Mar 2013 13:12:34 -0700 (PDT)
Received: from mx1.yitter.info (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 7D9058A031 for <dnsext@ietf.org>; Mon, 11 Mar 2013 20:12:33 +0000 (UTC)
Date: Mon, 11 Mar 2013 16:12:01 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsext@ietf.org
Message-ID: <20130311201201.GD38441@mx1.yitter.info>
References: <20130311152035.4888.59295.idtracker@ietfa.amsl.com> <20130311191607.GF38303@crankycanuck.ca> <E99C99C9-73E1-43F8-B09E-B28CA138F526@hopcount.ca> <20130311194317.GA38441@crankycanuck.ca> <FBCCECBD-43DC-46F1-911F-B06ED43E10C3@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <FBCCECBD-43DC-46F1-911F-B06ED43E10C3@hopcount.ca>
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: Mon, 11 Mar 2013 20:12:35 -0000
On Mon, Mar 11, 2013 at 04:01:04PM -0400, Joe Abley wrote: > > That seems like it would have eliminated my confusion. Perhaps also > explicitly state that this document aims to classify existing and > all future algorithms that might be standardised, until replaced. This paragraph in 2.4 doesn't do: [RFC6014] establishes a parallel procedure for adding a registry entry for a new algorithm other than a standards track document. Because any algorithm not listed in the foregoing table is Optional, algorithms entered into the registry using the [RFC6014] procedure are automatically Optional. ? > ECC-GOST are not recommended, although I believe they have the same > advantages. Arguably ECC-GOST has been around for longer, and hence > has an advantage over ECDSA. Both have stable references, in > English, in the RFC series. What is the reason for appearing to > promote one over the other? I don't know; that's what the WG said before. This is the first time this question came up. I think that would be a substantive change to the intent of the document, and would require a new WGLC, but I think yours is a fair question. Best, A -- 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)