Re: [DNSOP] Tell me about the ISO 3166 user assigned two-letter codes and TLDs
hellekin <hellekin@gnu.org> Thu, 29 September 2016 07:01 UTC
Return-Path: <hellekin@gnu.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 5FAE612B244 for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 00:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.217
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZ48upFs54eY for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 00:01:09 -0700 (PDT)
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:4830:134:3::10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC2BD12B122 for <dnsop@ietf.org>; Thu, 29 Sep 2016 00:01:06 -0700 (PDT)
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1bpVL1-0005GE-QB for dnsop@ietf.org; Thu, 29 Sep 2016 03:01:04 -0400
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43031) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1bpVL1-0005G6-MT for dnsop@ietf.org; Thu, 29 Sep 2016 03:00:59 -0400
Received: from tor-exit7-readme.dfri.se ([171.25.193.131]:53226 helo=[0.0.0.0]) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <hellekin@gnu.org>) id 1bpVL0-0007gc-N5 for dnsop@ietf.org; Thu, 29 Sep 2016 03:00:59 -0400
To: dnsop@ietf.org
References: <20160928232720.9513.qmail@ary.lan> <AEA063E3-0BA1-4F8B-A46F-38D06232C4A2@icann.org>
From: hellekin <hellekin@gnu.org>
X-Enigmail-Draft-Status: N1110
Organization: https://gnu.org/consensus
Message-ID: <50f84b42-c1c8-0eef-4776-e1183cd21c1d@gnu.org>
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: <AEA063E3-0BA1-4F8B-A46F-38D06232C4A2@icann.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/89P_ngOfs6B2jVcAMxbQ43egq-Y>
Subject: Re: [DNSOP] Tell me about the ISO 3166 user assigned two-letter codes and TLDs
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: 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)? == hk
- [DNSOP] Tell me about the ISO 3166 user assigned … John Levine
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Mark Andrews
- Re: [DNSOP] Tell me about the ISO 3166 user assig… David Conrad
- Re: [DNSOP] Tell me about the ISO 3166 user assig… John R Levine
- Re: [DNSOP] Tell me about the ISO 3166 user assig… John Levine
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Mark Andrews
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Edward Lewis
- Re: [DNSOP] Tell me about the ISO 3166 user assig… hellekin
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Jaap Akkerhuis
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Jaap Akkerhuis
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Viktor Dukhovni
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Ralph Droms
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Donald Eastlake
- Re: [DNSOP] Tell me about the ISO 3166 user assig… David Conrad
- Re: [DNSOP] register and unregister, was Tell me … John Levine
- Re: [DNSOP] Tell me about the ISO 3166 user assig… David Conrad
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Warren Kumari
- Re: [DNSOP] Tell me about the ISO 3166 user assig… Michael StJohns
- Re: [DNSOP] Tell me about the ISO 3166 user assig… John R Levine
- Re: [DNSOP] Tell me about the ISO 3166 user assig… william manning
- Re: [DNSOP] Tell me about the ISO 3166 user assig… John R Levine
- Re: [DNSOP] Tell me about the ISO 3166 user assig… william manning