IETF Logo Mail Archive

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

Jim Reid <jim@rfc1035.com> Wed, 14 December 2016 21:16 UTC

Return-Path: <jim@rfc1035.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 DCC6212950C for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 13:16:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level:
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.896] 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 4fvRbXWYXw5h for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 13:16:21 -0800 (PST)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 864EA1294D4 for <dnsop@ietf.org>; Wed, 14 Dec 2016 13:16:12 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id A3FDE242125E; Wed, 14 Dec 2016 21:16:10 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <2b2d2cd1-9f88-ec81-14bd-e87c033cca8d@bellis.me.uk>
Date: Wed, 14 Dec 2016 21:16:10 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <08F50BE9-6D78-4336-A14C-1F332BD8A12B@rfc1035.com>
References: <4ab2a538-603e-4e7a-3be9-ad75ed459006@bellis.me.uk> <E773C5B4-BA00-488C-9854-C729B671DFBD@gmail.com> <95E95A61-2079-498B-91C6-E98B50B84044@shinkuro.com> <CAPt1N1nCWgEtsMY4s669CHicWppyz9wCVYA9HR0QR_rGOPXSfA@mail.gmail.com> <CE36578B-780B-4222-B5A8-F6A252259234@shinkuro.com> <CAPt1N1n+PcuJ+AU-6U4TFiJvjNWz1PRNNp+y=zbnMSxZVKZ57A@mail.gmail.com> <201612142014.uBEKE0KA022671@bela.nlnetlabs.nl> <2b2d2cd1-9f88-ec81-14bd-e87c033cca8d@bellis.me.uk>
To: Ray Bellis <ray@bellis.me.uk>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-VFXdMHFaxAsOPdOqvO3rRF2qwo>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] [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 21:16:23 -0000

> On 14 Dec 2016, at 20:43, Ray Bellis <ray@bellis.me.uk> wrote:
> 
> On 14/12/2016 20:14, Jaap Akkerhuis wrote:
>> Any reason why homenet shuld use a TLD? What is wrong with something
>> like homenet.arpa (or thuisnet.arpa, or bob.arpa).
> 
> <hat partly-on>
> 
> It's not considered user-friendly enough.

So what? End users are not expected to see this string, far less care about it, are they? Surely this string is primarily, if not exclusively, for CPE firmware?

> The historic meaning of ARPA is considered by some to be problematic in
> the consumer space that Homenet is targeting.

Perhaps the way to resolve that is to tackle those misunderstandings and any FUD around them. The self-same issue was discussed ad nauseam ~15 years ago over ENUM.

IMO, the question here for the advocates of a TLD for home networks (for some definition of that term) is “what specifically can you do with .homenet (say) that you can’t do with homenet.arpa (say)?” ie What are the use case(s) and problem statement(s) that need to be addressed? And, as a logical followup, are those issues valid?

v2.23.0 | Report a Bug | By Email