review of draft-ietf-dnsext-dnssec-experiments-02

Andrew Sullivan <andrew@ca.afilias.info> Fri, 10 March 2006 19:06 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHmwT-0004sl-Ib for dnsext-archive@lists.ietf.org; Fri, 10 Mar 2006 14:06:25 -0500
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHmwT-0000xF-7v for dnsext-archive@lists.ietf.org; Fri, 10 Mar 2006 14:06:25 -0500
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1FHmr6-0004Rt-3D for namedroppers-data@psg.com; Fri, 10 Mar 2006 19:00:52 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO,INFO_TLD autolearn=no version=3.1.0
Received: from [207.219.45.62] (helo=mail.libertyrms.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <andrew@ca.afilias.info>) id 1FHmr5-0004Rf-9M for namedroppers@ops.ietf.org; Fri, 10 Mar 2006 19:00:51 +0000
Received: from wormhole2.int.libertyrms.com ([10.1.2.130] helo=trilby.local) by mail.libertyrms.com with esmtp (Exim 4.22) id 1FHmr4-0005mQ-1l for namedroppers@ops.ietf.org; Fri, 10 Mar 2006 14:00:50 -0500
Received: by trilby.local (Postfix, from userid 1019) id 27E301914DE; Fri, 10 Mar 2006 14:00:21 -0500 (EST)
Date: Fri, 10 Mar 2006 14:00:21 -0500
From: Andrew Sullivan <andrew@ca.afilias.info>
To: namedroppers@ops.ietf.org
Subject: review of draft-ietf-dnsext-dnssec-experiments-02
Message-ID: <20060310190020.GA1027@afilias.info>
Reply-To: Andrew Sullivan <andrew@ca.afilias.info>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.11
X-SA-Exim-Mail-From: andrew@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.5 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4

Dear colleagues,

I have reviewed the document draft-ietf-dnsext-dnssec-experiments-02. 
Here are my comments.

First, I strongly support the goal of this document.  I think it's a
good idea to have a well-defined methodology for these experiments. 

It seems to me that the first bit under 4 could be clarified:

   The core of the methodology is the use of strictly "unknown"
   algorithms to sign the experimental zone

isn't strictly true, if I'm reading this right, because it isn't the
_algorithm_ that is unknown, but its identifier (that seems to be
what the clarification in paragraph 6 actually says).  I don't think
this is a big deal, but it might be worth altering if other changes
are being made.  

Even without the above clarification, however, I would support the
document going forward.

Nits
====

Section 1, 1st paragraph:

   Throughout this document, familiarity with the DNS system (RFC1035
   [4]) and the DNS security extensions ([1], [2], and [3].

	* this doesn't seem to be a sentence.  Maybe
   
   This document assumes the reader's familiarity with RFC1035 ([4])
   and the DNS security extensions ([1], [2], and [3]).

Section 9

   IANA may need to allocate new DNSSEC algorithm numbers if that
   transition approach is taken, or the experiment decides to use
   allocated numbers to begin with.

	* the antecedent of the "that transition" was a little muddy
		to me.  Here's a suggested replacement, a little
		verbose:

   IANA may need to allocate new DNSSEC algorithm numbers in two
   cases: in case of a successful experiment that elects to move to 
   standards track by the adoption of newly allocated algorithm
   numbers (as outlined in section 7); and in case the experiment
   uses allocated numbers to begin with.


Best regards,
A

-- 
----
Andrew Sullivan                         204-4141 Yonge Street
Afilias Canada                        Toronto, Ontario Canada
<andrew@ca.afilias.info>                              M2P 2A8
                                        +1 416 646 3304 x4110


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>