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

Matt Larson <matt@kahlerlarson.org> Fri, 10 November 2017 13:53 UTC

Return-Path: <matt@kahlerlarson.org>
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 EF5CA1242F7 for <dnsop@ietfa.amsl.com>; Fri, 10 Nov 2017 05:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.141
X-Spam-Level:
X-Spam-Status: No, score=-1.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.779] autolearn=no 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 MOE4PSnmWg16 for <dnsop@ietfa.amsl.com>; Fri, 10 Nov 2017 05:53:08 -0800 (PST)
Received: from smtp117.ord1d.emailsrvr.com (smtp117.ord1d.emailsrvr.com [184.106.54.117]) (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 11956120721 for <dnsop@ietf.org>; Fri, 10 Nov 2017 05:53:07 -0800 (PST)
Received: from smtp7.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp7.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 2F584C0075; Fri, 10 Nov 2017 08:53:07 -0500 (EST)
X-Auth-ID: matt@kahlerlarson.org
Received: by smtp7.relay.ord1d.emailsrvr.com (Authenticated sender: matt-AT-kahlerlarson.org) with ESMTPSA id 06CC0C0055; Fri, 10 Nov 2017 08:53:06 -0500 (EST)
X-Sender-Id: matt@kahlerlarson.org
Received: from [192.168.1.26] (static-71-178-167-85.washdc.fios.verizon.net [71.178.167.85]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:465 (trex/5.7.12); Fri, 10 Nov 2017 08:53:07 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Matt Larson <matt@kahlerlarson.org>
In-Reply-To: <20171110121241.GA2621@laperouse.bortzmeyer.org>
Date: Fri, 10 Nov 2017 08:53:06 -0500
Cc: dnsop@ietf.org
X-Mao-Original-Outgoing-Id: 532014786.265238-29707d637f57f2c3517c265f179cc869
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C063F76-BFBD-4E54-AFBE-51B00678020B@kahlerlarson.org>
References: <20171110121241.GA2621@laperouse.bortzmeyer.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ap9nPh4nA-UTLBiqpBQ1LLP354Q>
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 13:53:09 -0000

> On Nov 10, 2017, at 7:12 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>; wrote:
> 
> draft-wkumari-dnsop-internal-00 says "This document requests that the
> .internal TLD be assigned to the IANA (similar to the way that
> .example is) and a DNSSEC insecure delegation (that is, a delegation
> with no DS records) be inserted into the root-zone, delegated to
> blackhole-[12].iana.org."
> 
> This implies NS records in the root. Why not using the DNAMEs of RFC
> 7535 instead? I understand there is currently no ICANN process to add
> DNAME in the root zone but there is no process to add .internal
> either.

Without commenting on the contents of that particular draft, 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.

While you're correct about no existing process (that I'm aware of) to add either .internal or a DNAME to the root, at least with a delegation there is only process work, not technical work, as well.

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.

Matt