Re: [DNSOP] Some distinctions and a request - Have some class?

"John R Levine" <johnl@taugh.com> Sun, 05 July 2015 02:32 UTC

Return-Path: <johnl@taugh.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 1C4D61A9068 for <dnsop@ietfa.amsl.com>; Sat, 4 Jul 2015 19:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level:
X-Spam-Status: No, score=-1.137 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_PASS=-0.001] 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 YfsuLksM6Z-o for <dnsop@ietfa.amsl.com>; Sat, 4 Jul 2015 19:32:08 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3E571A9066 for <dnsop@ietf.org>; Sat, 4 Jul 2015 19:32:07 -0700 (PDT)
Received: (qmail 85892 invoked from network); 5 Jul 2015 02:32:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=14f82.55989734.k1507; bh=mJFDfZzzNXJZ//wOZHvhBz0a0bcmoYa8U8/puKFLRI0=; b=mveKvW9kLcGbu9LoI7GCrwox91UjzyQgTq3sHnB6n5IFVmY2Ey/zoF2ahi8yhysHB+gdYAWHpqGjZmfPbx2hRWtNlX2dbndklYOfDKJTyk0a4kVNY/W1zty82IQsOWXR/8tgrjcqHAPDLYYUdBP2cA5neCzn+wXB8xSlwSkaXyBcsZvMhj6vxoRnY5p0EFZrpVno4q+kyDtZ86oZyhVtrNTzul1ieGr/b+xPdGF4JSHDvdi7dzf0Av52HQd6lGm7
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=14f82.55989734.k1507; bh=mJFDfZzzNXJZ//wOZHvhBz0a0bcmoYa8U8/puKFLRI0=; b=GR3Esht1/GzsriNbZNE3x4MSbSpoAcQDgVCmVN3eORKM+q897CaAcKbiv4xrAcmOKlZPehY03+VLJO+3JjWrx2nO2IWVXsFJ6dMLgOMMHUbjWD7UUz8oWfM9I6klApvX1lAjTEZfdteps286iYlDhNJ0HniYLtRbZGotAr+dMI3Wnoy31M8hBs3J8MM13Wq1SNzbI/N0Qs3DiZIddbXiOiUYITSgVgHcbPAirrRd2mhsVoD1zPCbxfqZnlFmXqh4
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 05 Jul 2015 02:32:20 -0000
Date: Sun, 05 Jul 2015 14:32:03 +1200
Message-ID: <alpine.OSX.2.11.1507051423270.6609@ary.local>
From: John R Levine <johnl@taugh.com>
To: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <27B81BB7-B254-40CD-B245-F74C4F395229@gmail.com>
References: <20150704063120.2380.qmail@ary.lan> <017CF015-8A06-40D5-9ECF-B7B7E208C7AF@frobbit.se> <27B81BB7-B254-40CD-B245-F74C4F395229@gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-556257874-1436063530=:6609"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/tnchPX9p1qMSFBPzDUecHHQ7BmE>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Some distinctions and a request - Have some class?
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 05 Jul 2015 02:32:09 -0000

> Avoiding collisions between DNS and non-DNS use of domain names is 
> probably important to us (to some degree that’s what we’re trying to 
> decide). But I have thought, and continue to think, that we make a 
> serious mistake if we regard it as our purpose to “say what strings in 
> the name space should NOT be TLDs.” The IETF delegated that 
> responsibility long ago to someone else, and for good reason.

I thought we were heading toward a process to identify domain names that 
should not be in the DNS for engineering reasons.  In practice they're 
likely to be TLDs, but I can imagine hypothetical situations where someone 
invents a son-of-onion under .ARPA or somewhere else.

Regards,
John
j@m.183.57.64.in-addr.arpa (try it if you dare)