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

Donald Eastlake <d3e3e3@gmail.com> Thu, 29 September 2016 13:28 UTC

Return-Path: <d3e3e3@gmail.com>
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 9A1E812B108 for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 06:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XM4Xcjjr07hA for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 06:28:41 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F78F12B00F for <dnsop@ietf.org>; Thu, 29 Sep 2016 06:28:41 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id r192so173459341ita.0 for <dnsop@ietf.org>; Thu, 29 Sep 2016 06:28:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=KvPofIwO3VDviCwt2kuxBIoYbhNo1bNZMYatu9kEVMw=; b=nf1KOt6p5UTixI1FE5Lq7VBb0aLTQZZn9ViMsfGp16qaYJoNYmlXofHTdcCXaNhD4y VbZSTyLhE7oD4EVHNG0T+ObOv0WOsEGO5Cuh0ya6OkGRGo737dg5X04ynOJC+Ubm3o2B UjtHQBU6VH0sWFPaBAn13Siin6Be5D71oz8LFX9XUzqij7Q7uzTbMN2zVvffifDnZ57J rAaQR5pqrZG+IrZ/okezefi/CekAzncVClqipAKB2HUV8JzCokh9uqql7gReCqjeOCXP Rxxxac0U9vPXCVCysQO693c+P0QwZGjXSTqH4WFNvGwN60lf5LcKhOM/xUIu2ti1NTp2 yBAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=KvPofIwO3VDviCwt2kuxBIoYbhNo1bNZMYatu9kEVMw=; b=jWs89Eel7DIJXW2BYwS18oRC7e89KT5qkrwrMmeMlVklxneNGf6PcHhAepwCuo5djl oDNPIKHdGQLpip7zKshxvJwFba05+SqRDXaUZH6YYr/5JwuFIKB23zRXSSZb2BESFQKs mVsGQspQ4sulsUoHjDBshC4+SPZCeu01jRJDJhbflr8LL9UueAYUtZ7ehZiVtIk/ksEy LqzYgl+bO/lsVW9qBHKb6k+i6zqz7fNwUqmhG/fg7RUuu0JpbGuYX4I0lCoLYSw8JmZn cJakemVJYn/Sj2SiontwJzb5gVSsctixNs+oB4DqLyhigosxFZVlp97628rCIYMFYHOb 9UMA==
X-Gm-Message-State: AA6/9Rk+gor/IIh0NxUsRBp4wKwOkPimD8F0FQUiutXu9Y9O3Hdur2PqJU3/M5LNyVR5qRu3OlFW+KqKNtXbGA==
X-Received: by 10.36.111.209 with SMTP id x200mr7848931itb.59.1475155720395; Thu, 29 Sep 2016 06:28:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.154.144 with HTTP; Thu, 29 Sep 2016 06:28:24 -0700 (PDT)
In-Reply-To: <20160928232720.9513.qmail@ary.lan>
References: <20160928232720.9513.qmail@ary.lan>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 29 Sep 2016 09:28:24 -0400
Message-ID: <CAF4+nEFv2OCqm-5AhHSrLEVBAMT+2Ckta91n31pdm0cjZ+0wBA@mail.gmail.com>
To: "<dnsop@ietf.org>" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a11450cacb4201f053da5740b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Or2ZR8wLOS2hHcSGEmlixpDXaKc>
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 13:28:45 -0000

It wasn't particularly clear which later message in this thread to respond
to so I'm replying to the first. If anyone is interested, I happen to know
John Postel's opinion on this matter. If you look at early drafts of RFC
2606, such as
https://www.ietf.org/archive/id/draft-ietf-dnsind-test-tlds-06.txt
you will see a lot more tld's including some of these reserved country
codes. John reject all those saying that, regardless of what the ISO
standards currently said, the IETF couldn't constrain any two letter tld's
without a clear prior agreement from ISO.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Wed, Sep 28, 2016 at 7:27 PM, John Levine <johnl@taugh.com> wrote:

> I don't think this has anything to do with RFC 6761, so ...
>
> For a very long time, two letter TLDs have been assigned to countries
> and other geographic entities per the ISO 3166 alpha-2 list.  The
> earliest mention I can find is in RFC 920 in 1984, and even then the
> wording suggests that the usage was well settled.
>
> The codes AA, QM-QZ, XA-XZ, and ZZ are "user assigned" and will never
> be used for countries.  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'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?
>
> R's,
> John
>
> PS: On my lan, I'm using .QY.
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>