Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

"John Levine" <johnl@taugh.com> Tue, 04 February 2014 06:39 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE2FE1A0373 for <dnsop@ietfa.amsl.com>; Mon, 3 Feb 2014 22:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level:
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 TAVzDoof5VQm for <dnsop@ietfa.amsl.com>; Mon, 3 Feb 2014 22:39:34 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDE81A0371 for <dnsop@ietf.org>; Mon, 3 Feb 2014 22:39:34 -0800 (PST)
Received: (qmail 33453 invoked from network); 4 Feb 2014 06:39:33 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Feb 2014 06:39:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f08b25.xn--3zv.k1402; i=johnl@user.iecc.com; bh=X7bnBTmokpDeTn2VolD357FKIUCiFe6eAJ1DXnMtAXc=; b=ICXgrTCF8kCcd8b5VD9ooOMSWFjsdeQCgVsM8zy5LRhNjhrwL7EeJanC9RPJQF9AVfyDUcHwsCKZf/xMZItRahu7YihVa5HXGGg6rxIO2Uua1Bqhyl4OLPpCFEkgXCTdaBC/gm22LWIBOqnu3wh0KB0kj0Oysj6yO50qu0UIuNF95BYhkGO3EqHpYNQr3s3ljkD2tuXgwVbBdz1b1yck0ganSNYXeH0YfgYcjp5CifNpjlDnqP5dkXdfm73gzCwe
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f08b25.xn--3zv.k1402; bh=X7bnBTmokpDeTn2VolD357FKIUCiFe6eAJ1DXnMtAXc=; b=jSYvIm9HhinxEMQXA3aO0ogeiOyR+FXNX3MN3nstTqlBq5ZCcYRHqChHqkBlx1sSZb5e4S04tsEz0GEmoSswYiC4qcXaFC0tVcR0AYodJrYdrgPgkASerKqD+bfHYeI2I5M/SViSFhr3etYgR2k5qRZ3D+W47AO7KG6rKl9PWP9/eIPkVCQwQPlxL68+VI+5NFO6Z0mlMFErvWZtI+tkZ0U7CQx/4cbGmQ3LHEi/ig10YaSfJWRLbsTANfR6344J
Date: 4 Feb 2014 06:39:11 -0000
Message-ID: <20140204063911.55905.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20140204001137.GA53095@mx1.yitter.info>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: ajs@anvilwalrusden.com
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 06:39:36 -0000

>> Not really, because what you get by squatting on a TLD is nothing like
>> what you get if you rent it from ICANN.  Squats are all local
>> (mis-)use, with names only leaking onto the public Internet by
>> accident. 

>That actually depends on what you're doing with the name.  In the case
>of the names discussed in the chapin draft, that is true.  It's less
>true in all cases.

I think that all we're talking about here is reserving domain names
and saying that they should never resolve on the global Internet.

If the IETF finds good technical reasons to reserve some other name
for some other reason, e.g., peer to peer exchange of crypto
credentials or something, so what?  It's one less name for ICANN to
sell but I don't see why that would be our problem.

I suppose the situation with .onion is slightly different, but in
concept it's not all that different from .arpa.  It's a domain that
people are using for special technical purposes, so it's not available
for normal delegation.  The only ICANN delegated name that's the least
bit interesting is .TEL, an attempt to create an online directory
using NAPTR that is a failure, so they're unlikely to do any more.

R's,
John

PS: Because I am not a good person, you can reply to me at
jl@m.183.57.64.in-addr.arpa.  Or, of course, johnl@taughannock.tel.