Re: [regext] EPP and DNAME records?

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 15 January 2018 11:16 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97B6112DA4B for <regext@ietfa.amsl.com>; Mon, 15 Jan 2018 03:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] 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 JSTrhPqXaZDH for <regext@ietfa.amsl.com>; Mon, 15 Jan 2018 03:16:43 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 60BF112DA69 for <regext@ietf.org>; Mon, 15 Jan 2018 03:16:43 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id E8AA12800FF; Mon, 15 Jan 2018 12:16:41 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id E237C2816DB; Mon, 15 Jan 2018 12:16:41 +0100 (CET)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id DB4D12800FF; Mon, 15 Jan 2018 12:16:41 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id D801F6423521; Mon, 15 Jan 2018 12:16:41 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 33E673FE08; Mon, 15 Jan 2018 12:16:37 +0100 (CET)
Date: Mon, 15 Jan 2018 12:16:37 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: John Levine <johnl@taugh.com>
Cc: regext@ietf.org, pm@dotandco.com
Message-ID: <20180115111637.ciriwoky3sdzlnlm@nic.fr>
References: <1515887413.808127.1234484296.080BABE2@webmail.messagingengine.com> <20180114193137.6E9801909ABD@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180114193137.6E9801909ABD@ary.qy>
X-Operating-System: Debian GNU/Linux 9.3
X-Kernel: Linux 4.9.0-5-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.1.15.110916
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/HZpVpO7Zf6pwWd72JaJdvR35-v4>
Subject: Re: [regext] EPP and DNAME records?
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 11:16:44 -0000

On Sun, Jan 14, 2018 at 02:31:37PM -0500,
 John Levine <johnl@taugh.com> wrote 
 a message of 38 lines which said:

> I continue to believe that allowing DNAMEs in TLDs is a bad idea,
> and so I see no reason to spend further effort on this extension.

Really, I do not understand, and I would appreciate explanations. The
original use case is not for DNAME in TLDs. So, whatever you think of
DNAME in TLDs does not mean the extension is useless.

> With respect to DNAMEs at the top level, someone else noted that the
> root zone isn't managed the same way as TLDs, so there's no obvious
> connection.

Already replied but see
<https://mailarchive.ietf.org/arch/msg/dnsop/lGdwGFO58iJ_dYYM9UR87Er9F5c>

> Since you can get the effect of a DNAME in the root zone by putting
> a DNAME at the apex of a TLD as Taiwan has done,

No, the goal here is to have no NS delegation (for reasons explained
in RFC 7535). So, this cannot work.

> it might be more productive to consider how to invent a policy to
> allow a DNAME-only TLD if you're not a ccTLD.

I'm not in policy, draft-bortzmeyer-dname-root and
draft-bortzmeyer-regext-epp-dname are purely technical.