Re: [DNSOP] .arpa

Ray Bellis <ray@bellis.me.uk> Wed, 22 March 2017 16:19 UTC

Return-Path: <ray@bellis.me.uk>
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 34AA1129A41 for <dnsop@ietfa.amsl.com>; Wed, 22 Mar 2017 09:19:34 -0700 (PDT)
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 1tGu6ykL-SfK for <dnsop@ietfa.amsl.com>; Wed, 22 Mar 2017 09:19:32 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C03B1299CF for <dnsop@ietf.org>; Wed, 22 Mar 2017 09:19:29 -0700 (PDT)
Received: from dhcp-wifi-246.sql1.isc.org ([149.20.50.246]:52077) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1cqiyr-0004Nn-95 (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Wed, 22 Mar 2017 16:19:25 +0000
To: dnsop <dnsop@ietf.org>
References: <E07AFAEB-2B84-4610-87E7-94CF32CF3761@fugue.com> <m1cqKPa-0000FeC@stereo.hq.phicoh.net> <71F88034-72C5-4AEE-9ACE-3493A1173634@gmail.com> <alpine.LRH.2.20.999.1703211011170.30281@bofh.nohats.ca> <0A544BEC-F719-4A7B-99E4-DC878EBE7B0C@gmail.com> <63DEB599-B4CD-4664-9AB6-9F505D81EDA7@rfc1035.com> <4DC4999E-CB4D-4F72-93BC-FDDC9A26A195@gmail.com> <5B809E6D-8C23-4B41-B142-5706316775C6@ecs.soton.ac.uk> <EMEW3|7748a271060e43ad02f4e918d6bc04f1y2LBoG03tjc|ecs.soton.ac.uk|5B809E6D-8C23-4B41-B142-5706316775C6@ecs.soton.ac.uk> <EAAB7CAC-7887-4C24-A597-6291E7196EEF@fugue.com> <E05606DF-7C9F-48A6-9191-36B689CF6B40@ecs.soton.ac.uk> <EMEW3|60cdac3fad8ea0f5d9c8144322c5e9ddy2LEom03tjc|ecs.soton.ac.uk|E05606DF-7C9F-48A6-9191-36B689CF6B40@ecs.soton.ac.uk> <C770AA35-126D-440D-96EA-7196DDA79877@fugue.com> <D89D8E26-B5A2-44DE-8E64-06D4B044C0A4@ecs.soton.ac.uk> <EMEW3|1770685f3047d9d32676cafa683d64b2y2LFBj03tjc|ecs.soton.ac.uk|D89D8E26-B5A2-44DE-8E64-06D4B044C0A4@ecs.soton.ac.uk>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <ad05e57a-6f43-7403-5e3d-58038b69d784@bellis.me.uk>
Date: Wed, 22 Mar 2017 09:19:24 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <EMEW3|1770685f3047d9d32676cafa683d64b2y2LFBj03tjc|ecs.soton.ac.uk|D89D8E26-B5A2-44DE-8E64-06D4B044C0A4@ecs.soton.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wEg5WrXHBn_JSvIDhDwEchU-BPU>
Subject: Re: [DNSOP] .arpa
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 22 Mar 2017 16:19:34 -0000


On 22/03/2017 08:11, Tim Chown wrote:

> I’d like to think such uses are largely all GUI/icon driven.  Or perhaps
> increasingly voice driven, like Alexa. How often will foo.homenet.arpa,
> or foo.homenet be used in typical cases? 

I use ".local" to access several devices in my home network that are not
hidden behind a UI "discovery client", including my ADSB receiver and my
NAS.

I also use it for SSH access to devices that announce that service via
Bonjour rather than having to put their IPs in /etc/hosts everywhere.

Arguably I'm not "typical", but IMHO we shouldn't be designing for the
lowest common denominator.

Either way, the Homenet WG has reached its consensus decision to request
".homenet" rather than ".homenet.arpa".

I personally don't mind if it takes longer for the requested insecure
delegation to happen than for the special-use reservation to happen -
the former shouldn't be a blocker for the latter.

To those that say "no insecure delegations in the root zone" because
"DNSSEC is good", my argument is that in this particular case blocking
the request would *inhibit* use of DNSSEC in edge networks and on stub
resolvers.  The whole point of the insecure delegation is to
*facilitate* correct use of DNSSEC within Homenets.

Ray (no hat)