IETF Logo Mail Archive

Re: [regext] EPP and DNAME records?

"John Levine" <johnl@taugh.com> Tue, 09 January 2018 02:24 UTC

Return-Path: <johnl@iecc.com>
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 C5C63126C3D for <regext@ietfa.amsl.com>; Mon, 8 Jan 2018 18:24:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.76
X-Spam-Level:
X-Spam-Status: No, score=-1.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=2Y22OdJR; dkim=pass (1536-bit key) header.d=taugh.com header.b=Ekwk8y49
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 3knwFccpUCwm for <regext@ietfa.amsl.com>; Mon, 8 Jan 2018 18:24:20 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 39E2C124BE8 for <regext@ietf.org>; Mon, 8 Jan 2018 18:24:20 -0800 (PST)
Received: (qmail 62010 invoked from network); 9 Jan 2018 02:24:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=f235.5a5427d2.k1801; bh=Vf8YDOQW1tGq7xEBNfog0BrmvNFknRex1QWvzcNVKJg=; b=2Y22OdJRwaG8Rur28s646bna13ZAzWzzKqoI20fa3miwTS9H7TifRfRKBf+WLvpBp/7osoZky6WMGKuPorwDT5+oquU3dPwpa9UHZgvyI81iWKnIYtykEmWCZwDwwP5Brwe6A1S7D7+dBkulk9AAOWgQ0z+7sQw7vAVUuI2KM+kuql+tEoOLkO6HkFpdjkFZyMc78NaVpON15vcri0v8lwH+92v9jpcas2iqH+JrUqy2Rzlrv2cMHRyYnupZ104a
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=f235.5a5427d2.k1801; bh=Vf8YDOQW1tGq7xEBNfog0BrmvNFknRex1QWvzcNVKJg=; b=Ekwk8y49bj24iZuNvtNM3Jldj4DcxgK9m/G+7E06eN4/W+JpEHvSfgFdzLrJk0TWbNHe8bokqIYr4vZM+subVoDcI4kXoYlIOEFH7rOkimlQ0+UF69RyMXT4CgKg4SnLNPK3O/Bx/7b/bPqT46IHLVbs5NIeSi5fDpP6nkeYkUYtFv1LYCLBUtyTS5Vg1TzRcrnYS49EiwLmwhoPZ8pUdQlDIS5fK7fzwkAaJCsl72tYow8hxCuR78mzb5dxiXnO
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 09 Jan 2018 02:24:17 -0000
Received: by ary.local (Postfix, from userid 501) id 2CB9518EC181; Tue, 9 Jan 2018 10:24:16 +0800 (HKT)
Date: Tue, 09 Jan 2018 10:24:16 +0800
Message-Id: <20180109022417.2CB9518EC181@ary.local>
From: John Levine <johnl@taugh.com>
To: regext@ietf.org
Cc: bortzmeyer@nic.fr
In-Reply-To: <20180108133402.mxwlqjxmljczt6bf@nic.fr>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/h0Jxvay4cjAJsp2M9JuKLppJKVo>
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 02:24:22 -0000

In article <20180108133402.mxwlqjxmljczt6bf@nic.fr> you write:
>> 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.

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 since
the semantics of DNAME are a poor match for people who want two name
trees to be "the same."

I'm not sure how practical this is, but I'd be much more comfortable
with an EPP mapping that only mapped to empty.as112.arpa.

R's,
John

v2.23.0 | Report a Bug | By Email