Re: [DNSOP] On .ZZ

Shane Kerr <shane@time-travellers.org> Fri, 22 November 2019 08:20 UTC

Return-Path: <shane@time-travellers.org>
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 B9B35120143 for <dnsop@ietfa.amsl.com>; Fri, 22 Nov 2019 00:20:49 -0800 (PST)
X-Quarantine-ID: <ou9ECgm5YCoe>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...T_ADDRESS@@ for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ou9ECgm5YCoe for <dnsop@ietfa.amsl.com>; Fri, 22 Nov 2019 00:20:47 -0800 (PST)
Received: from saturn.zonnestelsel.tk (tunnel317214-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:77a::2]) (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 96E6512003E for <dnsop@ietf.org>; Fri, 22 Nov 2019 00:20:46 -0800 (PST)
Received: from earth.zonnestelsel.tk ([2001:470:78c8:2::9]) by saturn.zonnestelsel.tk with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <shane@time-travellers.org>) id 1iY4BG-0006t0-G3 for dnsop@ietf.org; Fri, 22 Nov 2019 08:20:44 +0000
To: dnsop@ietf.org
References: <CAHXf=0pOVM_MHypgL7uV88242ciBUXGpx6waUetxBbZhvth1gA@mail.gmail.com> <35F0456A-2BA5-4021-AA9D-A86889E74AE6@nohats.ca> <8a5833d5-192f-fdbf-2862-e3f144be80cc@nic.cz> <CAH1iCirfeaD5pJ1_Tm5PaATQ9_zmrj2PbSnPGyL8z40L-_z3nw@mail.gmail.com> <D7475E63-1047-4622-B7EE-DEEA1A891825@pch.net>
From: Shane Kerr <shane@time-travellers.org>
Message-ID: <f4d32eb9-c073-463f-1914-bdc62ec372bf@time-travellers.org>
Date: Fri, 22 Nov 2019 09:20:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2
MIME-Version: 1.0
In-Reply-To: <D7475E63-1047-4622-B7EE-DEEA1A891825@pch.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Spam-Score-Int: -28
X-Spam-Bar: --
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yKEnWJ3xz6yOEb40Skc95QXb3PY>
Subject: Re: [DNSOP] On .ZZ
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, 22 Nov 2019 08:20:50 -0000

Bill and all,

On 21/11/2019 16.25, Bill Woodcock wrote:
> 
>> On Nov 21, 2019, at 12:18 AM, Brian Dickson <brian.peter.dickson@gmail.com> wrote:
>> IMHO, there is *no* reason not to advance .zz
> 
> For the record, I think it’s a really bad idea to start re-purposing the ISO user-assigned codes.  Just as bad an idea as if they started re-purposing 1918 space.

Hm... this is an interesting point.

I just checked the ISO 3166 glossary:

https://www.iso.org/glossary-for-iso-3166.html

And it says:

"User-assigned codes - If users need code elements to represent country 
names not included in ISO 3166-1, the series of letters AA, QM 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.
NOTE: Please be advised that the above series of codes are not 
universal, those code elements are not compatible between different 
entities."

So the intention of the ISO at least is that these codes are used by 
users. (I'm not sure what the scary warning means.) Certainly I have 
made heavy use of .Q* and .X* in my own testing, with the assumption 
that these would never be assigned (and yes, there is .TEST but 
sometimes you need more than one one TLD).

Cheers,

--
Shane