Re: [DNSOP] In a vacuum, nobody can hear you scream, was On the call for adoption on Special Use Names

"John Levine" <> Fri, 07 October 2016 01:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0989F1294F0 for <>; Thu, 6 Oct 2016 18:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TcVsgwddp2JK for <>; Thu, 6 Oct 2016 18:20:56 -0700 (PDT)
Received: from ( [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A8A901294EE for <>; Thu, 6 Oct 2016 18:20:56 -0700 (PDT)
Received: (qmail 94934 invoked from network); 7 Oct 2016 01:20:54 -0000
Received: from unknown ( by with QMQP; 7 Oct 2016 01:20:54 -0000
Date: Fri, 07 Oct 2016 01:20:33 -0000
Message-ID: <20161007012033.23623.qmail@ary.lan>
From: John Levine <>
In-Reply-To: <>
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <>
Subject: Re: [DNSOP] In a vacuum, nobody can hear you scream, was On the call for adoption on Special Use Names
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: Fri, 07 Oct 2016 01:20:58 -0000

> If someone can just start using a name and thus make it too hard
> to delegate we have a much a bigger problem.

That's been true approximately forever, viz. .onion, .belkin, .corp,
.local, .mail, and probably still .uucp that are too poisoned to allow
reliable delegation and new use.  That's why we're here.

The fundamental and I hope obvious problem, is that the IETF and ICANN
have no control over software that people write and the hardware they
embed it in.  If someone creates popular software leaking requests for
.PICKLE, we can grouse all we want but since we're not the Network
Police, there's not much we can do about it.