Re: new DNS classes or anything else

"John Levine" <johnl@taugh.com> Wed, 05 July 2017 01:39 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71B7126E3A for <ietf@ietfa.amsl.com>; Tue, 4 Jul 2017 18:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 KNag1E3_esOW for <ietf@ietfa.amsl.com>; Tue, 4 Jul 2017 18:39:55 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC6DE120227 for <ietf@ietf.org>; Tue, 4 Jul 2017 18:39:54 -0700 (PDT)
Received: (qmail 83981 invoked from network); 5 Jul 2017 01:39:53 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 5 Jul 2017 01:39:53 -0000
Date: 5 Jul 2017 01:39:31 -0000
Message-ID: <20170705013931.67812.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: john@jck.com
Subject: Re: new DNS classes or anything else
In-Reply-To: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-sNF78B5uFdQb1uMt5EiTy5Trh8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 01:39:57 -0000

In article <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> you write:
>Having enough of the world get aggravated enough at ICANN (or
>some other entity of one's choice) to make general adoption of
>an alternate root plausible is another matter and I don't think
>we are there, at least yet.

Here in the IETF we are so close to ICANN that we suffer from sample
bias.  To the extent the outside world is even aware of ICANN, they
see that .com, .org, .net, and the large ccTLDs all work, registering
in them is straightforward and not too expensive, and everything else
is noise.  One advantage of ICANN's turgid bureaucratic processes is
that it makes it unlikely that they will do anything seriously
destructive because it would be too hard.

We all know how to run our own roots if that's what we want to do, but
I continue to observe approximately none of us doing it.

R's,
John