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

Suzanne Woolf <> Mon, 15 June 2020 21:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A86313A122B; Mon, 15 Jun 2020 14:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 qhCq3qzXGuv5; Mon, 15 Jun 2020 14:32:02 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CC7BE3A1226; Mon, 15 Jun 2020 14:32:01 -0700 (PDT)
Received: by with SMTP id e2so8499176qvw.7; Mon, 15 Jun 2020 14:32:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=18SjPcpAGFdNszAumKZjnAcbIuJVyJtQnl6gZDmtYNU=; b=KmuP/k1Tsatzihcs8COiMC2irKNY4iB/guoGxUSoFCFD4cfGOOjugwJyqwoLcVM73M u5zGkAlJb3MtGootoDM+IfiCk7CGPCVWqAPK7obBNqrjIxarKh8//f7ydYUFZg94WA2b qE1EXDy3xH6HxhFMBb+dr3RDNIqRV2V9gguLClcKGtpIMJnxkM6R7oCgfsuSKBTK8zoA 8+2FPfJZLQkozaOGBay/NgpPn79ZXqCAiQ7l/ECib75IxBYyeNrethL+zAfLAyZSANmh FSI79uRtBCy+BHyFLSTHYEHMzUFAgrmZdJ0/gZ6jZGeDgUMDtCtHmCSs7Ngk9BYjbpHD tG7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=18SjPcpAGFdNszAumKZjnAcbIuJVyJtQnl6gZDmtYNU=; b=pK3fHY1P50btPqqjNkqJrtIxl9zcsHBdnU1ac7cnwaRjVdPn4pRyo0HgdHnzbu7M6T Qm+j6vsqHC4xcl0c2OneZ5qlVXT2uKKNqkTPz++IAgZtUulADO2zYjTX9TmlOVNaa8aU KFLTOIQhZn55rB2YB2i1nfZpf7x7qKyZ4h/5cV3J71mHpcqe1oHm+bU859lWwojs6r/2 vFIAp3vNUFEAnCdWWqwp2384TPm8TG8uq5CZTcyIOwOLbNWaIapn7GzRmi7LGctjyY5K AZ/+N7eDaXiNXHVvp15obiM/qZkKceHs0qF4Ww6D1U6Op8NfdcLdohRXFwPVpx1BwUGU N5UA==
X-Gm-Message-State: AOAM533fQsDDGPZTsEdhQ35hiRYsqZ/PQzKg13P59Vx+V2aAYCJJN88H No543EZwE1EW26uhmlj87mBDrzP7ORE=
X-Google-Smtp-Source: ABdhPJwxu5M0Ua1QjZKrSCnd7k961KnVauA6+YmwDWZO5McW312d0TdT5o6cdlN7HsIUMujkIhLZSQ==
X-Received: by 2002:a0c:ba0e:: with SMTP id w14mr16235043qvf.222.1592256720065; Mon, 15 Jun 2020 14:32:00 -0700 (PDT)
Received: from ?IPv6:2601:181:c381:c700:ed79:4f04:1418:39a6? ([2601:181:c381:c700:ed79:4f04:1418:39a6]) by with ESMTPSA id p13sm13312363qtk.24.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Jun 2020 14:31:59 -0700 (PDT)
From: Suzanne Woolf <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A38A9B13-4A60-4A14-885D-FD547B1AFD10"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 15 Jun 2020 17:31:54 -0400
In-Reply-To: <>
Cc: dnsop-chairs <>
To: dnsop <>
References: <>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <>
Subject: Re: [DNSOP] Call for Adoption: draft-arends-private-use-tld
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 15 Jun 2020 21:32:04 -0000

Dear colleagues,

It will be helpful to the chairs in considering the future of this draft if folks could keep a few things in mind as we discuss it.

1. This draft as written takes no formal action to reserve anything for any particular purpose. It makes some observations about the administration of ISO 3166 and its use in the ICANN context, and suggests to operators and implementers that the ISO3166 user-assigned 2-letter strings could be suitable for local use in domain names. It does not include any IANA actions to update any registry or protocol element. So claims that this draft reserves names or attempts to override ICANN policy about “TLDs” seem premature.

We’ve heard concerns that by encouraging people to use these strings in local DNS contexts, an RFC with no IANA actions could have the effect of constraining future ICANN policy. This brings us to:

2. If we want to know what ICANN-the-organization thinks of this proposal, there is a mechanism for asking that question. The IAB, on behalf of the IETF, maintains a liaison relationship with ICANN, in the form of a non-voting liaison to the ICANN Board of Directors, who can be asked to convey a question or statement about an issue of mutual interest. We’ve used this capability before, and intend to ask the IAB to make use of this liaison relationship again if the WG wants to proceed on this draft. 

As one of the draft authors already wrote to the list, the draft does not offer an official position or commitment by ICANN as an organization. (Under our process, affiliation of a draft author can’t be used to infer such statements, either.) That’s literally what liaisons are for: to allow the IETF to interact with a standards or policy body as an organization.

3. When several proposals came to the IETF more or less at once regarding “special use domain names”, which proponents were insisting had to be single-label names (“TLDs”), the DNSOP chairs — in consultation with the IAB and IESG — set those proposals aside in hopes of finding a less time-consuming, more scalable, and less dramatic way of considering changes to the special use names registry than having an open-ended IETF Last Call, since there’s almost no technical guidance in RFC 6761 to determine whether a specific request is useful or even valid. 

This did not happen. RFC 8244 was published in 2017, but several drafts attempting to solve parts of the problem it described met with very little interest from the WG.

The chairs are reluctant to spend WG time in this area unless there’s reasonably clear benefit.  If there is, we’re happy to work with the WG, the IAB, ICANN liaison, et. al. to manage any governance issues.

Suzanne, Tim, and Benno

> On Jun 12, 2020, at 11:12 AM, Tim Wicinski <> wrote:
> All,
> As we stated in the meeting and in our chairs actions, we're going to run regular calls for adoptions over the next few months.   We are looking for *explicit* support for adoption.
> This starts a Call for Adoption for draft-arends-private-use-tld
> The draft is available here: <>
> Please review this draft to see if you think it is suitable for adoption by DNSOP, and comments to the list, clearly stating your view.
> Please also indicate if you are willing to contribute text, review, etc.
> This call for adoption ends: 26 June 2020
> Thanks,
> tim wicinski
> DNSOP co-chair