Re: [DNSOP] draft-wkumari-dnsop-internal and DNAME

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 10 November 2017 14:28 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207B81205F1 for <dnsop@ietfa.amsl.com>; Fri, 10 Nov 2017 06:28:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9jppE-pfMceN for <dnsop@ietfa.amsl.com>; Fri, 10 Nov 2017 06:28:39 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86BB61267BB for <dnsop@ietf.org>; Fri, 10 Nov 2017 06:28:39 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id F2B1731D05; Fri, 10 Nov 2017 15:28:36 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id 66249EC10C2; Fri, 10 Nov 2017 15:28:18 +0100 (CET)
Date: Fri, 10 Nov 2017 22:28:18 +0800
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Matt Larson <matt@kahlerlarson.org>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dnsop@ietf.org
Message-ID: <20171110142818.GB4062@laperouse.bortzmeyer.org>
References: <20171110121241.GA2621@laperouse.bortzmeyer.org> <0C063F76-BFBD-4E54-AFBE-51B00678020B@kahlerlarson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0C063F76-BFBD-4E54-AFBE-51B00678020B@kahlerlarson.org>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Dy20JnMRablZoqY99lcjXapYzMY>
Subject: Re: [DNSOP] draft-wkumari-dnsop-internal and DNAME
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Nov 2017 14:28:42 -0000

On Fri, Nov 10, 2017 at 08:53:06AM -0500,
 Matt Larson <matt@kahlerlarson.org>; wrote 
 a message of 32 lines which said:

> I'll note that from a technical/mechanical perspective, ICANN's and
> Verisign's root zone management systems already know how to deal
> with delegations. A DNAME in the root would require an unknown level
> of development by both parties.

I've never read the source code of the root zone management system,
but it seems surprising that it could be a non-trivial level of
development. I assume this system is complicated because it is highly
sensitive, and because it needs to incorporate a lot of defenses
against both mistakes and attacks, but they should be more or less the
same for DNAME and NS/A/AAAA, no?

> Adding new types of information to the root is certainly possible:
> I'm not trying to discourage that. But for planning and
> expectation-setting purposes, the community needs to take into
> account the long lead time that will be required for anything that
> requires technical modifications to the root zone management system.

Wild guess (and I pay beers if I'm wrong): the technical work will
take much less time than the process one.