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

Andrew Sullivan <ajs@shinkuro.com> Wed, 09 March 2011 13:56 UTC

Return-Path: <ajs@shinkuro.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 8A6B43A6821 for <dnsext@core3.amsl.com>; Wed, 9 Mar 2011 05:56:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level:
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 D2CjegPAx112 for <dnsext@core3.amsl.com>; Wed, 9 Mar 2011 05:55:46 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 288093A6881 for <dnsext@ietf.org>; Wed, 9 Mar 2011 05:55:46 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 05FDB1ECB408 for <dnsext@ietf.org>; Wed, 9 Mar 2011 13:57:01 +0000 (UTC)
Date: Wed, 9 Mar 2011 08:57:00 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsext@ietf.org
Message-ID: <20110309135700.GI32629@shinkuro.com>
References: <C99C3502.72B1%roy@nominet.org.uk> <alpine.LSU.2.00.1103082030190.5244@hermes-1.csi.cam.ac.uk> <20110309133017.GA19809@odin.mars.sol>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110309133017.GA19809@odin.mars.sol>
User-Agent: Mutt/1.5.18 (2008-05-17)
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 13:56:02 -0000

No hat.

On Wed, Mar 09, 2011 at 08:30:17AM -0500, Scott Schmit wrote:

> I'm inclined to agree with this, but even if it's decided that the
> DNSKEY RRs aren't sufficient, why not just use DS on the client side? I
> see that RFC 3658 forbids it, but I'm not sure I understand why.

I do not think this is the time to debate that design decision.  The
design of DNSSEC uses different RRTYPEs at the parent side of the cut
and the child side.  It is true that we use the same RRTYPE at the
parent and child sides for the NS record.  But even if you think that
was a good design (though I happen not to), the fact is that DNSSEC
did not follow that direction, and it has rules stating that the DS
isn't allowed on the child side.  We can't unmake that decision, and
we can't change it now without introducing a backward incompatible
change; so that is not an option open to us.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.