Re: [DNSOP] Last Call: <draft-ietf-dnsop-sutld-ps-05.txt> (Special-Use Domain Names Problem Statement) to Informational RFC

Stephane Bortzmeyer <> Mon, 12 June 2017 13:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9832C1286B1; Mon, 12 Jun 2017 06:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tcaiWkY04qyb; Mon, 12 Jun 2017 06:52:03 -0700 (PDT)
Received: from ( [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BDF66126D05; Mon, 12 Jun 2017 06:52:02 -0700 (PDT)
Received: from (localhost []) by (Postfix) with SMTP id 00E9A280589; Mon, 12 Jun 2017 15:52:01 +0200 (CEST)
Received: by (Postfix, from userid 500) id EF3CA280651; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Received: from ( [IPv6:2001:67c:2218:15::11]) by (Postfix) with ESMTP id E8655280589; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Received: from ( [IPv6:2001:67c:1348:7::86:133]) by (Postfix) with ESMTP id E516D6000082; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Received: by (Postfix, from userid 1000) id D673140E20; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Date: Mon, 12 Jun 2017 15:52:00 +0200
From: Stephane Bortzmeyer <>
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000001, version=1.2.2
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2017.6.12.134516
Archived-At: <>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-sutld-ps-05.txt> (Special-Use Domain Names Problem Statement) to Informational RFC
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 12 Jun 2017 13:52:07 -0000

On Tue, Jun 06, 2017 at 01:17:55PM -0700,
 The IESG <> wrote 
 a message of 42 lines which said:

> The IESG has received a request from the Domain Name System
> Operations WG (dnsop) to consider the following document: -
> 'Special-Use Domain Names Problem Statement'
> <draft-ietf-dnsop-sutld-ps-05.txt> as Informational RFC

For an issue which is quite contentious and sensitive, I think there
are some points in the document that deserve a change.

Biggest point: the IESG decided to freeze the RFC 6761 process
<> I regret this decision (RFC
6761 is still in force, it has not been deprecated or updated) and,
unfortunately, registration of new Special-Use Domain Names is now
impossible (pending an action on RFC 6761 that will probably never
come). So, de facto, a regular process has been shut down, leaving the
IETF without a possibility to register these domain names.

Now, on the draft:

* Section 3 says "No formal coordination process exists between the
IETF and ICANN" This is not true, there is a formal liaison
<> and it is even mentioned
laster, in section 4.1.4. This issue was mentioned during the WGLC

* Section 3 says "Use of the registry is inconsistent -- some
Special-Use Domain Name RFCs specify registry entries, some don't;
some specify delegation, some don't." There is no inconsistency
here. RFC 6761 says (in its section 5) that the reservation of a
Special-Use Domain Name is free to choose the rules regarding
resolution, as long as they are properly explained.

* Section 4.2.2 says "the fact of its unilateral use by The Tor
Project without following the RFC 6761 process" The onion TLD was in
use in Tor since 2004, nine years before the publication of RFC
6761. It is grossly unfair to reproach not following an unpublished
RFC. It was mentioned a long time ago

* Section 4.2.3 says "But it shares the problem that such names cannot
be assumed either to be unique or to be functional in all contexts for
all Internet-connected hosts." Unfortunately, because of the wide use
of censorship through lying DNS resolvers, this problem is now part of
our daily life. It would be nice if a name had the same global
signification, but it is no longer true.