Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names

Andrew Sullivan <> Mon, 06 January 2014 20:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 644A41AE120 for <>; Mon, 6 Jan 2014 12:54:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CBzLd5j9oagC for <>; Mon, 6 Jan 2014 12:54:27 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id B65BB1AE14D for <>; Mon, 6 Jan 2014 12:54:27 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 19A088A031 for <>; Mon, 6 Jan 2014 20:54:19 +0000 (UTC)
Date: Mon, 6 Jan 2014 15:54:17 -0500
From: Andrew Sullivan <>
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 06 Jan 2014 20:54:29 -0000

On Mon, Jan 06, 2014 at 01:48:04PM -0500, Ted Lemon wrote:
> It seems to me that TOR is a pretty vital application, even if it's
> not as popular as .local (which, let's be honest, is almost never
> seen, much less typed, by an end user). 

   Addresses in ".onion" are opaque, non-mnemonic, alpha-semi-numeric
   hashes corresponding to an 80-bit truncated SHA1 hash over a given
   Tor hidden service's public key. 

I'm pretty sure things in .onion are never supposed to be seen, much
less typed, by an end user too.

> I am deeply skeptical of
> the idea that the only relevant factor here is how widespread the
> squatting is on a particular top-level special-use domain.

I have never suggested that's the only relevant factor.  But I have
suggested that the argument, "This needs to be a TLD that steps on the
standard ICANN allocation mecahnism because it's already widely
deployed," needs some evidence of that wide deployment.  In the case
of .onion, for instance, it is very far from obvious to me that the
name needed to have been allocated directly beneath the root (as
opposed to, say, inside .arpa); but if Tor is already widely deployed,
the argument in favour of allocating that string in the root due to
practical side effects is made stronger.

Best regards,


Andrew Sullivan