Re: [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-05.txt

Jim Reid <> Tue, 27 September 2016 18:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7F30312B322 for <>; Tue, 27 Sep 2016 11:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.216
X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.316] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Utbuk3wjss7c for <>; Tue, 27 Sep 2016 11:38:55 -0700 (PDT)
Received: from ( [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 000A012B31A for <>; Tue, 27 Sep 2016 11:38:54 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id ED6272421027; Tue, 27 Sep 2016 18:38:52 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jim Reid <>
In-Reply-To: <>
Date: Tue, 27 Sep 2016 19:38:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <>
To: Warren Kumari <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Cc: IETF dnsop WG <>, Moronic MUA Header Mangling <>, Ray Bellis <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-05.txt
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: Tue, 27 Sep 2016 18:38:58 -0000

> On 27 Sep 2016, at 18:52, Warren Kumari <> wrote:
>> Meh. I wish the WG could stop the shed-painting on a frankly pointless detail and concentrate its efforts on producing a viable problem statement.
> .... we have two of them --

Indeed Warren. That’s one too many.

They both come up short as problem statements IMO. I’m struggling to find words to succinctly describe what problem the WG is expected to solve - sorry about that -- since it appears to be a layer 9+ matter. Both drafts seem to be concerned with treating (some of?) the symptoms rather than the root cause(s). Excuse the pun.

> ALT doesn't solve any of the major issues, but it *does* create a safe
> place for those people who want to experiment and build alternate
> resolution systems -- and takes some of the pressure off while we
> discuss solutions....

True. But that seems to be putting the cart before the horse. Where’s the demand from experimenters and why do they need a dedicated TLD for their alterate resolution systems? That’s a rhetorical question BTW. Answering it may well distract the WG from its quest for that one true problem statement to rule them all. So please don’t do that. :-)

FWIW I’m sceptical about creating .alt as a playpen for experiments since it might undermine efforts to answer the question ICANN asked us, whatever that question might be, or be the start of a slippery slope. Maybe a TLD is needed for experiments. Maybe not. However that’s something to discuss once we’ve figured out what has to be done about special* TLDs in general. *For some as-yet-unclear definition of special.

I think the WG should step back from both drafts, take a deep breath and agree a problem statement. Once that’s done, we’ll be in a better place to decide what to do with both drafts.

Easier said than done I know...