IETF Logo Mail Archive

Re: [regext] EPP and DNAME records?

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 08 January 2018 13:34 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 4368312895E for <regext@ietfa.amsl.com>; Mon, 8 Jan 2018 05:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 QmO6d836Tpvv for <regext@ietfa.amsl.com>; Mon, 8 Jan 2018 05:34:05 -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 2033B128896 for <regext@ietf.org>; Mon, 8 Jan 2018 05:34:05 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 324FE2828D9; Mon, 8 Jan 2018 14:34:02 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id 2C59B282909; Mon, 8 Jan 2018 14:34:02 +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 259E22828D9; Mon, 8 Jan 2018 14:34:02 +0100 (CET)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 223AA61083F1; Mon, 8 Jan 2018 14:34:02 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 1CEED400DC; Mon, 8 Jan 2018 14:34:02 +0100 (CET)
Date: Mon, 08 Jan 2018 14:34:02 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: John Levine <johnl@taugh.com>
Cc: regext@ietf.org
Message-ID: <20180108133402.mxwlqjxmljczt6bf@nic.fr>
References: <20180106163022.ffo4wqah2i7l34v2@sources.org> <20180107132647.57B8A18E70D1@ary.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180107132647.57B8A18E70D1@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.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.1.8.132116
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/TXg8_8q3amqMIiFVufBmVMuhytw>
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, 08 Jan 2018 13:34:11 -0000

On Sun, Jan 07, 2018 at 08:26:46AM -0500,
 John Levine <johnl@taugh.com> wrote 
 a message of 20 lines which said:

> It can coexist with anything other than CNAME, NS/DS, or another
> DNAME, and you need A, AAAA, and MX records at the DNAME to do what
> many people wrongly believe that DNAME does.  See RFC 6672, sec 2.4.

You're right, of course. Sorry for the mistake. It may be because I
thought of only one use case (see below).

> Not to be oversnarky, but I'd want a field to upload a picture of
> the user shooting himself in the foot to demonstrate that he
> understands what DNAMEs will do.

Right. Warnings added
<https://framagit.org/bortzmeyer/ietf-epp-dname/commit/bc4f697946848861ec62e14e710f10ef73f1241b>

> I assume I missed a discussion of what problem this solves -- is it
> in the list archives?

Yes. Added to the future version of the draft but, basically, 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.

v2.23.0 | Report a Bug | By Email