Re: [dnsext] CDS RRTYPE review - Comments period end Mar 29th

Olafur Gudmundsson <ogud@ogud.com> Wed, 09 March 2011 18:46 UTC

Return-Path: <ogud@ogud.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11CBA3A6928 for <dnsext@core3.amsl.com>; Wed, 9 Mar 2011 10:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level:
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Z17RdXHBuDq2 for <dnsext@core3.amsl.com>; Wed, 9 Mar 2011 10:46:40 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 909A33A692A for <dnsext@ietf.org>; Wed, 9 Mar 2011 10:46:39 -0800 (PST)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p29IltDf046842 for <dnsext@ietf.org>; Wed, 9 Mar 2011 13:47:55 -0500 (EST) (envelope-from ogud@ogud.com)
Message-ID: <4D77CB55.40407@ogud.com>
Date: Wed, 09 Mar 2011 13:47:49 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: dnsext@ietf.org
References: <C99C3502.72B1%roy@nominet.org.uk> <alpine.LSU.2.00.1103082030190.5244@hermes-1.csi.cam.ac.uk> <72A22513B1644CFE9023189F93BFDD32@local> <20110309080006.GA23957@miek.nl> <758260B7B5B34599BA80D9BA5A3840C0@local> <20110309090536.GA9578@miek.nl>
In-Reply-To: <20110309090536.GA9578@miek.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Subject: Re: [dnsext] CDS RRTYPE review - Comments period end Mar 29th
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 09 Mar 2011 18:46:42 -0000

On 09/03/2011 4:05 AM, Miek Gieben wrote:
> [ Quoting George Barwood in "Re: [dnsext] CDS RRTYPE review - Co"... ]
>>>>> Why not just use the child zone's SEP DNSKEY RRs for this purpose?
>>>>
>>>>  From the draft http://tools.ietf.org/html/draft-barwood-dnsop-ds-publish-01
>>>>
>>>>    key, delaying the time at which an attacker can start cryptanalysis;
>>
>>> So this is the sole reason for adding this new type?
>>
>> There are 4 reasons given, why do you quote only one?
>> Please don't quote selectively.
>
> it is the first reason you give in the introduction in the draft.
>
>> One could probably add yet more reasons, e.g.
>> It gives the child control over which Digest Type is used.
>> It allows new Digest types to be deployed easily.
>> It allows easy verification (by humans) as to whether the parent and child zones are in sync.
>>
>> But these are really just examples, fundamentally it's just proper design.
>> It gives the child zone proper control of the parent DS RRset.
>
> ...if the parent cooperates...
>
> Is this proposal aimed at TLDs or at smaller zones? Because for .nl we
> are just going to use EPP and let the registrar send in a DNSKEY which
> we will convert to a DS (so you can not even choose your own hash
> algo).
>

DNS >> TLD's  and even in among your registrars when do you expect the 
last one to support DNSSEC updating of DS records?

This mechanism can be used anywhere in the tree, and all it needs for 
use is a simple DNS lookup.
How the parent is told to perform the lookup or how frequently the 
parent does the lookup is outside the scope of this application.

	Olafur
PS: