Re: [DNSOP] on private use TLDS

Jaap Akkerhuis <jaap@NLnetLabs.nl> Fri, 29 November 2019 11:14 UTC

Return-Path: <jaap@NLnetLabs.nl>
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 30C04120123 for <dnsop@ietfa.amsl.com>; Fri, 29 Nov 2019 03:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nlnetlabs.nl header.b=vNfkWH8d; dkim=pass (1024-bit key) header.d=nlnetlabs.nl header.b=qao3UI7w
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 VNGWJub2LFv1 for <dnsop@ietfa.amsl.com>; Fri, 29 Nov 2019 03:14:54 -0800 (PST)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [IPv6:2a04:b900::1:0:0:10]) (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 B65AC1200B8 for <dnsop@ietf.org>; Fri, 29 Nov 2019 03:14:54 -0800 (PST)
Received: by dicht.nlnetlabs.nl (Postfix, from userid 58) id 3CA9429B96; Fri, 29 Nov 2019 12:14:52 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1575026092; bh=VMqQTWYL8tw8av4QWT77XKmd1V5gvaFg3XAzN6k3of0=; h=To:Subject:From:In-reply-to:References:Date; b=vNfkWH8duXiJaT4URtWQdPzHp/nHpATeKGr8xwoT1Ko+YKgsrbIYrSWqghio6f7lS p6w2dkynTcPQyMrG0LLp2SQZJ9EfdAZm9QSEsIGezGykDu+GUC7nj+4IaOO9MJ+VJV QMcl/D8VyzRM+z/bj1Wv7fvK/nQnik2fREOBtzrw=
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2a04:b900::1:0:0:15]) by dicht.nlnetlabs.nl (Postfix) with ESMTPS id B45C229B94 for <dnsop@ietf.org>; Fri, 29 Nov 2019 12:14:51 +0100 (CET)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=pass (p=none dis=none) header.from=NLnetLabs.nl
Authentication-Results: dicht.nlnetlabs.nl; spf=pass smtp.mailfrom=jaap@NLnetLabs.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1575026091; bh=VMqQTWYL8tw8av4QWT77XKmd1V5gvaFg3XAzN6k3of0=; h=To:Subject:From:In-reply-to:References:Date; b=qao3UI7w6cR+rZkBY/pCIEzozeYgxhWAIceKetQULxPZBkAfVFoJhBIq9y5L2gR+n cZSmBYcluOvQ54z+4ysZb/k02NjCs1yN6Pjx2KbU3w+EQUb7JyA0OjHoex+gC8wIqk +D0XEbaAFd8BouSbhOR9RFQe6uawdWrnmEKCyj7Q=
Received: from bela.nlnetlabs.nl (localhost [127.0.0.1]) by bela.nlnetlabs.nl (8.15.2/8.15.2) with ESMTPS id xATBEo3S071844 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <dnsop@ietf.org>; Fri, 29 Nov 2019 12:14:50 +0100 (CET) (envelope-from jaap@NLnetLabs.nl)
Received: from bela.nlnetlabs.nl (jaap@localhost) by bela.nlnetlabs.nl (8.15.2/8.15.2/Submit) with ESMTP id xATBEoEL071841 for <dnsop@ietf.org>; Fri, 29 Nov 2019 12:14:50 +0100 (CET) (envelope-from jaap@NLnetLabs.nl)
Message-Id: <201911291114.xATBEoEL071841@bela.nlnetlabs.nl>
X-Authentication-Warning: bela.nlnetlabs.nl: jaap owned process doing -bs
To: dnsop@ietf.org
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
In-reply-to: <0de4b220-9035-3a0e-0630-fadf0365c9e8@dougbarton.us>
References: <20191128165507.2A60BFDF451@ary.qy> <fb307c7a-348a-03d3-3d8e-8e683cec603d@dougbarton.us> <alpine.OSX.2.21.99999.374.1911282000130.79305@ary.qy> <0de4b220-9035-3a0e-0630-fadf0365c9e8@dougbarton.us>
Comments: In-reply-to Doug Barton <dougb@dougbarton.us> message dated "Thu, 28 Nov 2019 17:37:13 -0800."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <71839.1575026090.1@bela.nlnetlabs.nl>
Date: Fri, 29 Nov 2019 12:14:50 +0100
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (bela.nlnetlabs.nl [127.0.0.1]); Fri, 29 Nov 2019 12:14:51 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lOd3dTiRjvQg0U9AQPEkZzQBZ1I>
Subject: Re: [DNSOP] on private use TLDS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Nov 2019 11:14:56 -0000

 Doug Barton writes:

 > I don't doubt Jaap.

Thank you.

 > What I doubt is that any organization as political 
 > as ISO (or ICANN) will hold preferences stable in the absence of a 
 > controlling policy.

Here are some more facts from the trivia corner.

The ISO was started from 1947. The first edition of the 3166 standard
is from 1974 and defined the User assigned codes as:

	The series of letters AA, XA to XZ, and ZZ, and the series AAA to AAZ, XAA
	to XZZ and ZZA to ZZZ respectively, are available for private use, and for
	provisional codes which should be recorded as soon as possible by the
	maintenance agency. An existing alpha-1 code which is in agreement with
	the first letter of the alpha-2 code may be used for an appropriate time
	to be fixed by the agency.

The second edition (1981) said:

	The series of letters AA, OM to QZ,XA to XZ, and ZZ,and the
	series AAA to AAZ, QMA to QZZ, XAA to XZZ, and ZZA to ZZZ
	respectively and the series of numbers 900 to 999, are
	available for individual use.

so it did add the ranges starting with a Q. 

The later editions are all defining the same name space (with sometimes
different wording).

A similar exercise can be done for ICANN en TLD name space but I
leave that up to the reader(s).

However, I cannot help noticing that for years I hear from various
ICANN stakeholders that ICANN should start to use alpha-2 codes as
well. Most recently in the meetings of the GNSO newgtld working
group, subgroup wt-5. The motivation is that then Volkswagen can
have its TLD ".vw" and the Bank of America (why not bank of Albania?)
".ba".

	jaap

PS. [Apparently proponents of ba for a bank don't realize that it
    is assigned to Bosnia and Herzegovina].