Re: [DNSOP] Tell me about the ISO 3166 user assigned two-letter codes and TLDs

hellekin <> Thu, 29 September 2016 07:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5FAE612B244 for <>; Thu, 29 Sep 2016 00:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.217
X-Spam-Status: No, score=-9.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JZ48upFs54eY for <>; Thu, 29 Sep 2016 00:01:09 -0700 (PDT)
Received: from ( [IPv6:2001:4830:134:3::10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DC2BD12B122 for <>; Thu, 29 Sep 2016 00:01:06 -0700 (PDT)
Received: from Debian-exim by with spam-scanned (Exim 4.71) (envelope-from <>) id 1bpVL1-0005GE-QB for; Thu, 29 Sep 2016 03:01:04 -0400
Received: from ([2001:4830:134:3::e]:43031) by with esmtp (Exim 4.71) (envelope-from <>) id 1bpVL1-0005G6-MT for; Thu, 29 Sep 2016 03:00:59 -0400
Received: from ([]:53226 helo=[]) by with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <>) id 1bpVL0-0007gc-N5 for; Thu, 29 Sep 2016 03:00:59 -0400
References: <20160928232720.9513.qmail@ary.lan> <>
From: hellekin <>
X-Enigmail-Draft-Status: N1110
Message-ID: <>
Date: Thu, 29 Sep 2016 06:56:51 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-detected-operating-system: by GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
Archived-At: <>
Subject: Re: [DNSOP] Tell me about the ISO 3166 user assigned two-letter codes and TLDs
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 29 Sep 2016 07:01:11 -0000

On 09/29/2016 05:42 AM, Edward Lewis wrote:
> The one option you have is ".example", unfortunately (and in sympathy)
> I don't have a better suggestion.

.example is for documentation.  You can use .invalid for "fake private
TLD", which makes it very clear that it's not a valid TLD. (Sorry for
the tautology.)

This list of two-letter TLDs sounds like a good candidate for
Special-Use Domain Names.  But then, it prompts another question: if,
e.g., XA-XZ are reserved for future use, how to handle their *removal*
from the Special-Use Name Registry once they're assigned again?  Which
prompts another question: if a name enters the Special-Use Name
Registry, is it parked (for an indefinite amount of time), or is it
engraved in stone (and won't move from that registry again)?  And can
the SUNR hold both types of names (parked and final)?