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

Ralph Droms <> Thu, 29 September 2016 10:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9DF4512B498 for <>; Thu, 29 Sep 2016 03:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.218
X-Spam-Status: No, score=-2.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id f9GI6ynEf3rg for <>; Thu, 29 Sep 2016 03:38:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D528812B46F for <>; Thu, 29 Sep 2016 03:38:19 -0700 (PDT)
Received: by with SMTP id 38so34922444qte.1 for <>; Thu, 29 Sep 2016 03:38:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=08J0CbSmS8pdjJvgNpHPhzI+HY34/OHhmoDuUWuW+lg=; b=dMdYU9bZAV4PtGAhbsWISlYe8Os9PvCAuB23HtLSoReWhBgTvlK1kplAivKtpGOvn4 Z/WAn+EiSKFJjDUH68buIKrr+Nx5Zz62KxcUB5Mc5qzFk3bwCO28r0A3PxbZBWOWALfF rpaeRdfL9/V1EDRUaOCS7bmCTJgtBm7p5liUfISxmzLG8H20AF+B8+sKwLnV9JEkfcmU xun5OkqRI839p+/6rzhyO/o4mjB+YvyP+NRI4gHY1wKcD1m3oHYeP7ft4DA9HUn/Vkba S5P3CrTi/QGRJ3wq/pYNTfKub47Ajvubzi8hXbHJFkyLzx6HKhAwCRA5BCuzfBG3ps8/ GG5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=08J0CbSmS8pdjJvgNpHPhzI+HY34/OHhmoDuUWuW+lg=; b=XdVNgxzUnuSl4Q0yHWmxDHFvh4jLHMTM6+XtvS/4QKBLCgyOXBsixmZDrpg2UkYZX1 Ni5l+A2KN6VcLgaC7D//G2zf2aWFqmEKO2HEU/FCu2LjSCoVI7nvZn7sGqNoX+uCXwCX rq0kMSgirNGi+BsJMhs8ZTCZ7vWm7G/vw1iZQ8QYwbiX0W9myScnd5MyWg1esflkl5tD R3terv7Mc3Xxuwoe5znO2S1q0bYarKJ8xMvdJiUKPgnGMd0AHP/6p+RaVlCitygnvHwz u07kePiRz3UDtL6s1LWSZCsVkcH/K0Q69f9BhqQOe+TXbP3njaXV1G5zjPH1+DTaX4rN Wgvg==
X-Gm-Message-State: AA6/9Rl9cnwP9c2/RPIfHiiB5JMF4PhP9p1NbLsVqFPIhobmgZYeZYATWMBMjsgyGkAkAg==
X-Received: by with SMTP id y51mr634550qty.83.1475145438776; Thu, 29 Sep 2016 03:37:18 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:d929:ef00:2270:a0bd? ([2601:18f:801:600:d929:ef00:2270:a0bd]) by with ESMTPSA id b14sm6219724qte.19.2016. for <> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 29 Sep 2016 03:37:17 -0700 (PDT)
From: Ralph Droms <>
Content-Type: multipart/alternative; boundary=Apple-Mail-21842C35-BA35-4387-9DAC-9F051629E6EF
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Thu, 29 Sep 2016 06:37:16 -0400
Message-Id: <>
References: <20160928232720.9513.qmail@ary.lan> <> <>
In-Reply-To: <>
X-Mailer: iPad Mail (14A403)
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 10:38:21 -0000

> On Sep 29, 2016, at 2:56 AM, hellekin <> wrote:
>> 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)?

Good question, not (as far as I know) explicitly addressed in RFC 6761.

Because there is no explicit prohibition on removal of a name from the SUNR, publication of an appropriate RFC directing IANA to take such an action would be the appropriate action, at least. In my opinion.

The question might actually apply to many IANA registries.  Do the "Registration Procedures" apply to "unregistration" as well?  I don't know if there is any precedent here.

- Ralph

> ==
> hk
> _______________________________________________
> DNSOP mailing list