IETF Logo Mail Archive

Re: [regext] EPP and DNAME records?

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 09 January 2018 15:32 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 7D0A4126CD8 for <regext@ietfa.amsl.com>; Tue, 9 Jan 2018 07:32:26 -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 67l0GSFa5oVD for <regext@ietfa.amsl.com>; Tue, 9 Jan 2018 07:32:23 -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 2D54F1205F0 for <regext@ietf.org>; Tue, 9 Jan 2018 07:32:23 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 705ED281D14; Tue, 9 Jan 2018 16:32:21 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id 6AA10281DCD; Tue, 9 Jan 2018 16:32:21 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 63E1A281D14; Tue, 9 Jan 2018 16:32:21 +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 5DCD66427BE0; Tue, 9 Jan 2018 16:32:21 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 4F99D4003A; Tue, 9 Jan 2018 16:32:21 +0100 (CET)
Date: Tue, 09 Jan 2018 16:32:21 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: John Levine <johnl@taugh.com>
Cc: regext@ietf.org
Message-ID: <20180109153221.qlgtcarmz7jyirsk@nic.fr>
References: <20180108133402.mxwlqjxmljczt6bf@nic.fr> <20180109022417.2CB9518EC181@ary.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180109022417.2CB9518EC181@ary.local>
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.000257, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.1.9.152117
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/z_hUzGJWQlmcLGJf88fDjRzH7kc>
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: Tue, 09 Jan 2018 15:32:26 -0000

On Tue, Jan 09, 2018 at 10:24:16AM +0800,
 John Levine <johnl@taugh.com> wrote 
 a message of 28 lines which said:

> > it is draft-bortzmeyer-dname-root. Some people remarked that we
> > don't even have an EPP mapping for DNAME. It is not the biggest
> > obstacle to draft-bortzmeyer-dname-root but this new draft
> > draft-bortzmeyer-regext-epp-dname is an attempt to lift it.
> 
> Now I'm confused.  I can see the point of a DNAME from .local to
> empty.as112.arpa, and maybe a few poisoned 2LDs to empty.as112.arpa,
> but DNAME'ing anything else in a TLD or 2LD is asking for misery

Well, TLD which agree with you will simply don't implement or deploy
this service, that's all (like all other EPP extensions). The draft
draft-bortzmeyer-regext-epp-dname describes a XML schema, not a TLD
policy.

And, anyway, my first use case was only for the root but I don't see
the point of hardwiring this specificity in the draft

v2.23.0 | Report a Bug | By Email