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

Ralph Droms <rdroms.ietf@gmail.com> Wed, 14 December 2016 22:24 UTC

Return-Path: <rdroms.ietf@gmail.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 39A50129A8C for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 14:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3IQY9dHosOlf for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 14:24:44 -0800 (PST)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F9EA129B76 for <dnsop@ietf.org>; Wed, 14 Dec 2016 14:23:32 -0800 (PST)
Received: by mail-qt0-x22d.google.com with SMTP id c47so39585731qtc.2 for <dnsop@ietf.org>; Wed, 14 Dec 2016 14:23:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L+na3w2ewljwaCFlHbMcLOBUpEl+lQz+NhBlRR0nNXA=; b=umip0aF3Bu33/Xxoh8F4be26R7pSf2kad0k7pqTjLRWKGr8F0z2/PgGhk1GXRMzEet 2VWtmeGY/pdSjJDpi83E8efWetLSXTn+n0LY27zOx30wjl+naBP3kEfUWVDLKARCnxmv 4DCdgR4Di0/ONs4GrSIor+dEtqQLPL4cJCOWmNVc2xuRLi12YyG2ZnLBTJZ/9NVAKo7C 0nZqvoY+6wda81uyKG+Az+OK1/mVzeKYNIRto52lL2wTx917al/4AXyddgMDCHqU44zu Z8c5zfUtvIlPX0q9wLAQkQtffNPLrpPbGO5t30f8Gb6NlFQ/T7Ub1JZ14Z2SMeoASaCs Hziw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L+na3w2ewljwaCFlHbMcLOBUpEl+lQz+NhBlRR0nNXA=; b=GpH1Zi+uf/uZXpzO/tYonTVPs27v3XL5JVa2rqY3pGmW6R7k7E6rtNY21vdvzS8Xs1 RtzeZxoLSafGidPNte7t7RJP41l+cavhbjwiNP0Kr7L26BvoJnXMDfgB8mZaWiCM3Vu2 /ivc5VvJwxVcnJIPS2C4W6S0HntSNeUlNuqQSGmsU3xQU8xL9RFzbWS3YpFTjRQaP2/J BSLEA0ejc6cEoWhSVX0Mkm5GzS/Sv0BTDiolKxs1cRj9v8RtsEAj+4qgaLzhE5BxWrrV VSDFeu0qGRfMnIaJwHL2wuqkeGu0gkv2IGpPEVPZ8A9yAnOBUtBr5A8SQyePjGR9jirz NAqg==
X-Gm-Message-State: AKaTC00wvRkzB8idHd8zFF9e5cD7RRZGw/upUwssAVcxiTj2+hSPdD1IxIcH++TXSphVzg==
X-Received: by 10.200.39.51 with SMTP id g48mr89240562qtg.256.1481754211384; Wed, 14 Dec 2016 14:23:31 -0800 (PST)
Received: from ?IPv6:2601:18f:801:600:1ce1:3de5:853:8022? ([2601:18f:801:600:1ce1:3de5:853:8022]) by smtp.gmail.com with ESMTPSA id y17sm26193254qkb.24.2016.12.14.14.23.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Dec 2016 14:23:30 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <5bd3879c-2db6-2721-4edb-3cee44383411@bellis.me.uk>
Date: Wed, 14 Dec 2016 17:23:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB3F3181-8452-4A12-B4F4-914A8FE33BE9@gmail.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> <08F50BE9-6D78-4336-A14C-1F332BD8A12B@rfc1035.com> <5bd3879c-2db6-2721-4edb-3cee44383411@bellis.me.uk>
To: Ray Bellis <ray@bellis.me.uk>, Jim Reid <jim@rfc1035.com>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bov2fiCAFixM6LIbrAo98gmFebc>
Cc: dnsop <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 22:24:46 -0000

> On Dec 14, 2016, at 4:48 PM, Ray Bellis <ray@bellis.me.uk> wrote:
> 
> 
> 
> On 14/12/2016 21:16, Jim Reid wrote:
> 
>> 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?
> 
> Actually, yes, they are expected to see this thing.
> 
> It would be what would appear in their browser bar, for example, if
> accessing the web UI of various on-net devices or services.

I know the WG has decided that home network device names should be user-friendly, so I'll make something of a moot point..."seeing" isn't the issue, in my opinion.  I see ugly names and URLs in my browser bar all the time.  "typing" is the real issue ... any time a user has to know, remember and reproduce a name for manuaal text entry, user-friendliness is important.

- Ralph

> 
>> 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?
> 
> The arguments in favour of a pseudo-TLD are (AFAIK) entirely user
> orientated, and not technical.
> 
> Ray
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop