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

Edward Lewis <edward.lewis@icann.org> Thu, 29 September 2016 05:42 UTC

Return-Path: <edward.lewis@icann.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 CE78212B05B for <dnsop@ietfa.amsl.com>; Wed, 28 Sep 2016 22:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level:
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 BIkJPPNExzPE for <dnsop@ietfa.amsl.com>; Wed, 28 Sep 2016 22:42:50 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADE6A12B057 for <dnsop@ietf.org>; Wed, 28 Sep 2016 22:42:49 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 28 Sep 2016 22:42:47 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Wed, 28 Sep 2016 22:42:47 -0700
From: Edward Lewis <edward.lewis@icann.org>
To: John Levine <johnl@taugh.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] Tell me about the ISO 3166 user assigned two-letter codes and TLDs
Thread-Index: AQHSGhROJFcYT01sQEW7jP7ft+1SSg==
Date: Thu, 29 Sep 2016 05:42:46 +0000
Message-ID: <AEA063E3-0BA1-4F8B-A46F-38D06232C4A2@icann.org>
References: <20160928232720.9513.qmail@ary.lan>
In-Reply-To: <20160928232720.9513.qmail@ary.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1a.1.160916
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.236]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3557986965_886475814"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0QQBOPIMDqqs-DkQeA7uEhNJ0KU>
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 05:42:52 -0000

On 9/29/16, 03:27, "DNSOP on behalf of John Levine" <dnsop-bounces@ietf.org on behalf of johnl@taugh.com> wrote:

> Last year Ed Lewis wrote an I-D proposing that XA-XZ be made private use and the rest future use, but as far as I can tell it never went anywhere.

I'd been waiting for anyone else to show an interest in it before spending any time on it.  This is the first mention I've seen on a public list about the draft. ;)

As David wrote in a later message, the dam burst on Special Use Domain Name registry discussions.
   
>I've been telling people that if they need a fake private TLD for their local network they should use one of those since it is exceedingly unlikely ever to collide with a real DNS name.  Am I right?
    
I'd have to say not right to be "telling people".  The one option you have is ".example", unfortunately (and in sympathy) I don't have a better suggestion.

Heuristically, you might be okay using these codes but it's that same-old-same-old problem of assuming the future.  My preference would be to put the appropriate codes in to the Special Use Domain Name registry before "telling people".  I stress the "telling people" because you using ".qy" isn't ever going to come to harm (because you can change that "if").

BTW, the user assigned two-letter codes are not the same as unassigned codes. These have been expressly set aside for local use, these codes aren't eligible for use in any other way, no matter what a new region might call itself.  That is, it's more likely some other novel use for one of these codes might be found than the code ever matching an economy's identifier.