Re: [DNSOP] WGLC for draft-ietf-dnsop-sutld-ps

"John R Levine" <johnl@taugh.com> Wed, 08 February 2017 16:40 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD10129C4C for <dnsop@ietfa.amsl.com>; Wed, 8 Feb 2017 08:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=ozEAYRsG; dkim=pass (1536-bit key) header.d=taugh.com header.b=JBihkntf
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 AtCFJYa5YLvK for <dnsop@ietfa.amsl.com>; Wed, 8 Feb 2017 08:40:18 -0800 (PST)
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-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32404129C33 for <dnsop@ietf.org>; Wed, 8 Feb 2017 08:40:18 -0800 (PST)
Received: (qmail 1293 invoked from network); 8 Feb 2017 16:40:16 -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=50b.589b49f0.k1702; bh=a2lhFd58VZ024czf0W+bioM/42KUJ7O5IKraaEqG7DA=; b=ozEAYRsGzxMSyDgRS6LeAiOZ279JFKZVRhswV7CJJREn3ub/w5itbJhp8zJwY1d+ZwCE1WBHpC2ABG/wkZZO70ZrVYa6ZyInTVionbYpG+Ip0MDoJSPMCS270QCzLUXv4uplYeu7j+eP/CY3u2KbzZDE+rM4ehsEiErGnofSlbfwKirh5Nig5t5L6eMnTsxJS4Z+vE7N6XQnVggVeJcbKeYSYuPHYtfS4ya+Ksw69G8IZiUwudzCjBNtTP8J8p67
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=50b.589b49f0.k1702; bh=a2lhFd58VZ024czf0W+bioM/42KUJ7O5IKraaEqG7DA=; b=JBihkntf4FhlxPp02Z2W7VyySLun13hU9Q+btknpkt76vJmAnKsMMzqAHJy48g33LzlbT9CQR2vLMho2rdfE1X3WOc6wlrswXKTuqsNC/j9sv/WQxc2rNPwQk1oX1MQHlMhfryasVHJxUu6mojZ1+SnujmbvFsIlnFFT8xb3Z8DnCIIbskTVS5m+OUGCG2fDaD8Nhp6HHu7x4Ey4l+ETRzPpnV+at8KOG/4Yp2EbrrXFwKTfCxZkN8Gpt309M7YL
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.2/X.509/AEAD) via TCP6; 08 Feb 2017 16:40:16 -0000
Date: Wed, 08 Feb 2017 11:40:16 -0500
Message-ID: <alpine.OSX.2.20.1702081129500.51298@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20170208162718.jxaesl23jc6frykl@nic.fr>
References: <20170208091536.vqwftrhpole33opl@nic.fr> <20170208151101.14753.qmail@ary.lan> <20170208162718.jxaesl23jc6frykl@nic.fr>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dr_0k-F51NRJKQOYijMjq_TXHPQ>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] WGLC for draft-ietf-dnsop-sutld-ps
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 08 Feb 2017 16:40:19 -0000

>> to come along (.homenet?) will likely be different from any of the
>> existing ones, this strikes me as akin to asking for a pony.
>
> Some people in the discussion wanted ICANN to do something. This is
> akin to asking for an unicorn (at least, ponies do exist).

I wouldn't disagree.

>> If you just want a list of the names so your recursive resolver can
>> stub them out, we already have that, of course.
>
> URL, please, with the expected behavior of the resolver when queried
> for the domain.

It's the IANA list of special use domains:

http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xml 
also available as CSV for the traditionally inclined.

As I said, you might want to have your resolver stub these out to prevent 
leakage if it doesn't know how to handle them.  I use unbound, where it's 
easy to turn them into "local-zone <name> always_nxdomain" which won't 
make applications very happy, but at least they won't leak.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly