Re: [DNSOP] On .ZZ

Jaap Akkerhuis <jaap@NLnetLabs.nl> Fri, 22 November 2019 09:52 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 AF7F9120106 for <dnsop@ietfa.amsl.com>; Fri, 22 Nov 2019 01:52:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 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, URIBL_BLOCKED=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=tf5T3nhn; dkim=pass (1024-bit key) header.d=nlnetlabs.nl header.b=G9lhKdGp
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 oNIy0CalkzoD for <dnsop@ietfa.amsl.com>; Fri, 22 Nov 2019 01:52:02 -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 12714120048 for <dnsop@ietf.org>; Fri, 22 Nov 2019 01:52:02 -0800 (PST)
Received: by dicht.nlnetlabs.nl (Postfix, from userid 58) id 041F017808; Fri, 22 Nov 2019 10:52:00 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1574416320; bh=72depgelosvv0TvpsB892OaHXsJfpta6dfPdHPxwyXQ=; h=To:Subject:From:In-reply-to:References:Date; b=tf5T3nhn0MmbIbDhIEpH38N38xDMdD2tSZpw7BHFl/Sa1LUgzN6i/L8+KvSshIQS0 zlAUE7jcBq0/ZHBzwGBRMYMATyZWrYMzHzeL6MaShFLlfN8CmwM3JP9XC0FaFELQ+5 Tlo2AYc1/oAnGiqgRJhVRpAr0RhuN59k0yRrgfsk=
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2a04:b900::1:0:0:15]) by dicht.nlnetlabs.nl (Postfix) with ESMTPS id 46F4E17806 for <dnsop@ietf.org>; Fri, 22 Nov 2019 10:51:59 +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=1574416319; bh=72depgelosvv0TvpsB892OaHXsJfpta6dfPdHPxwyXQ=; h=To:Subject:From:In-reply-to:References:Date; b=G9lhKdGpO/N4nHRpwVl5xFX6et+pPJhO0m+8lSW/KUZXTr/52PxjFR1oj95/zC28B yqWvgRKBbVxP0e2xt1I9J1Bx1k2Nqwnak7Wf6rxwmz+/1KJvYQptIMs9jLgLRHqaXE wGN0Q9Du41TKwkr6aTkx9T5XW1b3IqDCINnmwUiM=
Received: from bela.nlnetlabs.nl (localhost [127.0.0.1]) by bela.nlnetlabs.nl (8.15.2/8.15.2) with ESMTPS id xAM9pwMt097085 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <dnsop@ietf.org>; Fri, 22 Nov 2019 10:51:58 +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 xAM9pwo8097082 for <dnsop@ietf.org>; Fri, 22 Nov 2019 10:51:58 +0100 (CET) (envelope-from jaap@NLnetLabs.nl)
Message-Id: <201911220951.xAM9pwo8097082@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: <f4d32eb9-c073-463f-1914-bdc62ec372bf@time-travellers.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> <f4d32eb9-c073-463f-1914-bdc62ec372bf@time-travellers.org>
Comments: In-reply-to Shane Kerr <shane@time-travellers.org> message dated "Fri, 22 Nov 2019 09:20:42 +0100."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <97080.1574416318.1@bela.nlnetlabs.nl>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Nov 2019 10:51:58 +0100
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (bela.nlnetlabs.nl [127.0.0.1]); Fri, 22 Nov 2019 10:51:59 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FmByrvDAdicXYrFkjVgbWzHmn6g>
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 09:52:04 -0000

 Shane Kerr writes:

 > 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."

The glossary is not authoritative, but it is a reformulation of a
note to Section 8.1.3 in the standard (ISO 3166:1,Third edition,
2013-11-05):

       "NOTE Users are advised that the above series of codes are
	not universals, 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.)

It means what it says. In the context of the stamdard, these are
not garanteed to be unique. The 3166/MA get sometimes requests to
reserve/allocate/assign codes from these blocks to make them unique
and always says no. (There used to be a note somewhere asking to
send the secretary of the 3166/MA information which User Assigned
Code was used and for what, but hardly anybody ever did and when
they did, users expected their particular code to be unique. Therefore
the MA dropped the note and does not keep a record of the User
Assigned Codes).

 > 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).

Yes, that is the ia perfect legit use use. (Trivia tidbit: The
rumour is that in Argentinia these codes are used to brand mark
cows).

	jaap