IETF Logo Mail Archive

Re: [DNSOP] ALT-TLD and (insecure) delgations.

"John Levine" <johnl@taugh.com> Fri, 03 February 2017 20:44 UTC

Return-Path: <johnl@taugh.com>
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 2A0DB12997E for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 12:44:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 WlDvB_a9rUS3 for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 12:44:53 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1EE129973 for <dnsop@ietf.org>; Fri, 3 Feb 2017 12:44:52 -0800 (PST)
Received: (qmail 31124 invoked from network); 3 Feb 2017 20:44:51 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 3 Feb 2017 20:44:51 -0000
Date: Fri, 03 Feb 2017 20:44:29 -0000
Message-ID: <20170203204429.14153.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <A519902D-8B90-44A7-84BD-8A5FD1D15978@gmail.com>
Organization:
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/dnsop/1BdI_ghT-c-jJHwv0uaW0kFP81k>
Cc: steve.crocker@gmail.com
Subject: Re: [DNSOP] ALT-TLD and (insecure) delgations.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 03 Feb 2017 20:44:54 -0000

In article <A519902D-8B90-44A7-84BD-8A5FD1D15978@gmail.com> you write:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>We (ICANN) have no mechanism or process for inserting a DNAME record into the root.  We do have a
>process for considering the general issue, but, so far as I know, no one has yet brought that idea
>into the ICANN/PTI arena.

There are ccTLDs that contain nothing but a DNAME (along with the
mandatory SOA and NS).  Maybe that's close enough.

R's,
John

v2.23.0 | Report a Bug | By Email