Re: [DNSOP] Fwd: [homenet] WGLC on "redact" and "homenet-dot"

"John Levine" <johnl@taugh.com> Wed, 14 December 2016 22:17 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 B92B2129E9D for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 14:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 nyOd2RxDdavG for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 14:17:16 -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 09786129F3C for <dnsop@ietf.org>; Wed, 14 Dec 2016 14:13:52 -0800 (PST)
Received: (qmail 37679 invoked from network); 14 Dec 2016 22:13:52 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 14 Dec 2016 22:13:52 -0000
Date: Wed, 14 Dec 2016 22:13:25 -0000
Message-ID: <20161214221325.1725.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20161214220428.1688.qmail@ary.lan>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/suTvCBz3ZAWYsd5afNxAZt_WRhY>
Cc: homenet@ietf.org
Subject: Re: [DNSOP] Fwd: [homenet] WGLC on "redact" and "homenet-dot"
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, 14 Dec 2016 22:17:18 -0000

>But it's worse than that -- if your client software does DNSSEC
>validation it needs to understand that homenet is a special case and
>it's OK not to validate.  This brings us to one of the knottiest parts
>of special use names, which is that they're all handled differently.
>For .onion, it's generally handled in a SOCKS proxy in the
>application, for .local it's handled by mDNS, and for .localhost it's
>special cased in the stub client library.  (There are of course other
>ways one could do it, e.g., a .onion proxy on a LAN could intercept
>AAAA lookups, and return link-local addresses it serves.)

Forgot to mention: homenet is a fourth model, special cased in the
cache, which is an occasional but I think infrequent alternate
implementation for .localhost.  There's implicitly a fifth for
.example, .test, and .invalid which are expected to get a normal
NXDOMAIN.  

I expect when the next 6761 candidate comes along, it'll be handled in
yet another grotty way.

But still:

>So having said all this, I agree with Steve that an unsigned delegation
>is a bad idea, not because all unsigned delegations are necessarily
>bad, but because this one wouldn't solve enough problems to be worth
>the ugly and ambiguous precedent it'd set.

R's,
John