Re: [DNSOP] we already have a new version of this problem

Ray Bellis <> Thu, 05 November 2015 13:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5A9701B2B7D for <>; Thu, 5 Nov 2015 05:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NBzFF-s31yyZ for <>; Thu, 5 Nov 2015 05:24:22 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 64E791B2B8F for <>; Thu, 5 Nov 2015 05:24:21 -0800 (PST)
Received: from ([]:58714 helo=Rays-MacBook-Pro.local) by ([]:465) with esmtpsa ( (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1ZuKWX-0003te-T8 (Exim 4.72) (return-path <>); Thu, 05 Nov 2015 13:24:18 +0000
To: George Michaelson <>,
References: <>
From: Ray Bellis <>
X-Enigmail-Draft-Status: N1110
Message-ID: <>
Date: Thu, 5 Nov 2015 22:24:11 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [DNSOP] we already have a new version of this problem
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: Thu, 05 Nov 2015 13:24:24 -0000

On 05/11/2015 10:11, George Michaelson wrote:
> So can somebody explain to me what we are meant to do with a possible
> emerging homenet desire for .home?

This particular proposal was being discussed long before any of the
.onion et al proposals existed, but didn't get put into draft form until
slightly after.

> because I believe this isn't just the tail of odd requests from the tor
> people for various hash based names.. its another WG inside the IETF
> process thinking "oh.. .onion worked, so lets go do one"

Without my Homenet co-chair hat on, but as an interested party, my view
is that I'd like to see ".home" formally blocked from registration as a
new TLD [*] by putting it into the "locally served zones" list, and
perhaps sunk to AS112 to catch those queries that aren't caught via
locally served zones.


[*] AFAICR, ICANN have said that's their plan, but it's also the case
that ICANN plans and policies can change.