Re: [DNSOP] Call for Adoption: draft-arends-private-use-tld

Roy Arends <roy@dnss.ec> Mon, 15 June 2020 23:16 UTC

Return-Path: <roy@dnss.ec>
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 D69663A0EDF for <dnsop@ietfa.amsl.com>; Mon, 15 Jun 2020 16:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dnss.ec
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 PZXbWfwYwG2G for <dnsop@ietfa.amsl.com>; Mon, 15 Jun 2020 16:16:33 -0700 (PDT)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 B67CD3A0EDE for <dnsop@ietf.org>; Mon, 15 Jun 2020 16:16:33 -0700 (PDT)
Received: by mail-il1-x132.google.com with SMTP id i1so341010ils.11 for <dnsop@ietf.org>; Mon, 15 Jun 2020 16:16:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dnss.ec; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=28wdh11kkI0PcIveOJChtFqWl8jPWqVwtX67kInbyIU=; b=PGenV1LbLPGC7P0gmsP1nBbjuhF6uZumnKACDa3cA+bmWsbTZ3wpAvaAsAeliK2Hkb vhYPpHWuNrAHnhjQVCnNiHGuY7h9Ms8F/e/6cKCD5ZgbAEkpDG4X+9zlApemhL0LUS3M Wnn10mozpDEbmYAqQ7Osw97GB3HTvGUBP6VJs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=28wdh11kkI0PcIveOJChtFqWl8jPWqVwtX67kInbyIU=; b=NTegfPXOAXW3+MuJKNlFwnhfQ2q+uZh2qy6Zt1QYa9HwbxnJWJlxToia5qa8Anz0p7 AfZQAipZj2O5SJ80oyj3vZQFx3XjgZ/gngFPeoGwD7Mg9ZQCO8o3LBObWDywSWUT0vXc U6BhhllZ3y0lkS+Mk4PBVCVTL3VRn8aIXGgBtWXgZKtsWKGRrBWNKnH/ztrIKuFpL2Pl h5BhJWtTfy5ePvOrmXLMYcNQ6Dfw3xaQ8aJoy/UEyEYYDCfo5a0d2fiPeWft4njEGAsf 2x8jh8jLZdQcvpTqwXQtZwDBy0ByZbrU7a6BhTOpNKjOXQ/bjHB6J1pRiYNIaUoYReTe Fhvg==
X-Gm-Message-State: AOAM531NOZjCgBrjnKc0Y8M10gQiofRoVeEVG65Ts3BZce0igdRwjAs+ 0+UXHpxVKq5dxn1gJbpG2S9qGKKPzWGMxA==
X-Google-Smtp-Source: ABdhPJxVErJGEQGGoVOLotghFb7S5+lv64wYmCPps0yXFWcaKNyIcdx8kheAcsI0tpFMqiigd0L0wA==
X-Received: by 2002:a92:d704:: with SMTP id m4mr356407iln.248.1592262992388; Mon, 15 Jun 2020 16:16:32 -0700 (PDT)
Received: from [192.168.1.64] (host86-175-77-184.range86-175.btcentralplus.com. [86.175.77.184]) by smtp.gmail.com with ESMTPSA id t12sm8754397ilj.75.2020.06.15.16.16.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Jun 2020 16:16:31 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Roy Arends <roy@dnss.ec>
In-Reply-To: <1c60efc6-6c7b-232c-b2ba-aba30e355b55@nthpermutation.com>
Date: Tue, 16 Jun 2020 00:16:28 +0100
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBE97DBD-D21B-4C29-9D42-4DE923BB59C5@dnss.ec>
References: <CADyWQ+F=JA6fogcy_JGRJaZv=Hq52ozgmY5gmzfPm=1oHcJXKg@mail.gmail.com> <6.2.5.6.2.20200614060206.0b09c560@elandnews.com> <A4882CC1-1610-4456-A28C-CB4F8304C754@icann.org> <1c60efc6-6c7b-232c-b2ba-aba30e355b55@nthpermutation.com>
To: Michael StJohns <msj@nthpermutation.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/09tp66rCQN5RRvpO77VleW-xk5k>
Subject: Re: [DNSOP] Call for Adoption: draft-arends-private-use-tld
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 15 Jun 2020 23:16:36 -0000

Hi Mike,

> On 14 Jun 2020, at 21:12, Michael StJohns <msj@nthpermutation.com> wrote:
> 
> Roy et al - 
> 
> Is there a document from ICANN taking a position on the assignment of TLDs based on  ISO3166 assignments?   

Yes: https://www.icann.org/resources/pages/icann-iso-3166-2012-05-09-en

From that page:

"In 2000, the ICANN Board of Directors recognized the ISO 3166 Maintenance Agency as the authoritative entity for country code designations and officially adopted the use of ISO 3166-1 and the 3166-MA exceptional reserved list as the set of eligible designations for ccTLD assignment (September 2000)”

Please note that:

The ISO/TC46/WG2 “owns” ISO3166. Any substantial changes to it, need to go through TC46. The user-assigned two letter codes exist since the inception of the standard (15 december 1974).

TC46/WG2 has designated the User-Assigned two letter codes to users of the ISO3166-1 standard (not to the Maintenance Agency!)

TC46/WG2 refers the remaining codes to the Maintenance Agency for the assignment (Reserved, Assigned, Re-Assigned, Deleted, etc, etc) of two letter codes to country names.

The ISO3166/MA has no authority over the User-Assigned two letter codes.

It is naive to think that these policies, some of which pre-dates ICANN and even the Internet would be ignored by either ICANN or the ISO. 

I think it is safe to assume that these codes will never by delegated in the root zone.

> When Jon was doing this he was adamant about following their lead - rather than having to make political decisions about what was a country.  The main role he had was not the selection of the TLDs, but making sure that the delegations went to the right organizations related to the countries indicated by the TLD.   I would say that ICANN should probably have the same role.   

I agree.

> Given that ISO has indicated a range of specifically NOT issued 2 letter codes, and that these codes will never (should never?) be added to the root zone, I would suggest that it's probably not an ICANN role to weigh in on this interpretation.

I agree.

> That said, I'd prefer it if the document selected a few (<=10) codes from these ranges so that filtering may be built into various servers and clients to prevent leakage.  

With all due respect, I’ll wait with responding about specifics until the WG has adopted the document (if at all).

Warmly, 

Roy