Re: [homenet] alternatives to .home

Ted Lemon <mellon@fugue.com> Fri, 17 June 2016 22:00 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A65212DBCA for <homenet@ietfa.amsl.com>; Fri, 17 Jun 2016 15:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=fugue-com.20150623.gappssmtp.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 eRH2rMuQbreN for <homenet@ietfa.amsl.com>; Fri, 17 Jun 2016 15:00:51 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 3CD6012DB2F for <homenet@ietf.org>; Fri, 17 Jun 2016 15:00:51 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id f6so6299768lfg.0 for <homenet@ietf.org>; Fri, 17 Jun 2016 15:00:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Lh0oSJznRWZWLb3wZKR6cE7sZWrMHS0UDGu/aiR8FBU=; b=M464067zE3N8F4BOxS6AptNRGMUgUowfuvNHDhQ9o2/GJl4AI++rXU1AknEHGhkpy2 Ol/6cdPR0wxYLfdmCgKkduO3C7nVdA95C9dqmhfxiGLVTsw52q6gdO/iyJPWEANee+8I P1oJWiKgV/jM/Ykp8iYtm26ulDkOZpeH47x+SoQp1pbWS0QlaLuP2rZjLj/4EiF+igoT cKH5baGpCfPCBmVPVcg5GmTLCdVbPaUt4UPrhKJPV9460lNrkAdBrKd+FMlgCwQum4kc Rqa/q3dPIGFvrcO/9yW9zdW839eLks8MVT6WbVAbqGePwk8fH7ma+6XFr/op4RqsPpZc U8Sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Lh0oSJznRWZWLb3wZKR6cE7sZWrMHS0UDGu/aiR8FBU=; b=hDPlGc2kTEl9H75Ei7JyjFbVFJ5D/q3uF25ebeK+J1E/y6br9+4m1gHboK8WO1ILla ZSswO8m83+h8rmDmzPwBWwWTfbe+f0A1s0DhnvYn5JM4LAPFjw68K9UhjT1iwWxQ1gBy +n2Dl5Q1ksY702XNiNWg0QRXKWgIXVUidcv5AueQnjFCYIHQKsLHtCgGNMKuKdsAevSL 3xmChQhN3+W2ehTQO6UWiaj0fmNy1ezXye4ji0aSTqGUEDEW1uJI7t5E9VoKpKTNy47v th6IEAEXVjCHMfdEltQq+PK7Fl/IWHVNRw2dWtNBuSj5QjAZkHobwJaa952xe3275QXl 0pTA==
X-Gm-Message-State: ALyK8tLGssjRAUqz+sGyjWlAElZHzSlrf7AIcgT3sNkL3W9IouO18a/xRlSHlXWcYYASjU2JcotCdIjqPUmj9w==
X-Received: by 10.25.91.76 with SMTP id p73mr991416lfb.181.1466200849183; Fri, 17 Jun 2016 15:00:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Fri, 17 Jun 2016 15:00:09 -0700 (PDT)
In-Reply-To: <27316.1466193170@obiwan.sandelman.ca>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <4598.1466104881@obiwan.sandelman.ca> <87porgafsq.wl-jch@pps.univ-paris-diderot.fr> <102a01d1c82a$f1e1e530$d5a5af90$@registry.asia> <7526.1466169795@obiwan.sandelman.ca> <CAPt1N1=7NAgfw=ZDX-S+Tc6RbYDMbuyUD-KXUwiLUyuDdEoF+A@mail.gmail.com> <11120.1466170772@obiwan.sandelman.ca> <CAPt1N1msC1XCEOR0vGvhLV9GF1-DrSNKWufZo=2PqtBb6UJdGA@mail.gmail.com> <27316.1466193170@obiwan.sandelman.ca>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 17 Jun 2016 18:00:09 -0400
Message-ID: <CAPt1N1=eu+X-onN-QkYdoyb1MzTf4vF9suTyjZXXKHvR1Q5AKQ@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="001a11411536c90ae00535807c1d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Wkd0-9MiEWAz-qKRiBuTzdAdWEs>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Edmon Chung <edmon@registry.asia>
Subject: Re: [homenet] alternatives to .home
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2016 22:00:53 -0000

You propose that .domus and .home both be possible presented names for the
same object: the home network.   Users will use many devices on the home
network; each of these devices will have to display the same name.   If the
actual name is the same, this is easy.   If the UI has to make it look like
it's the same, this will be hard, and will be gotten wrong.

Users will be expected to visit each others' homes.   Settings in each home
may be different.   Yet printer.domus in home A will reference printer.home
in home B, which will produce an unexpected error when that reference is
used.

The actual name of a thing should always be presented.   Whether it's
copy-and-pasteable is a UI detail, but if you are looking at a pointer, the
pointer should always look the same if it points to the same object, no
matter what device you are using.

Using the same name for every homenet that doesn't have its own global name
has the very nice quality that we don't have to do anything clever to make
it work.   That's why that's what I'm recommending.   I get that it would
be nicer to say .domus for homenets in the vatican, and .home for homenets
in english-speaking countries, but that's harder to achieve, and would have
to add a lot of value to be worth doing.   As Andrew says, answering a
slightly different question, we really don't want to have to do that.

On Fri, Jun 17, 2016 at 3:52 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Ted Lemon <mellon@fugue.com> wrote:
>     > model that the user forms will be wrong. If .home and .domus are
>
> I don't propose that they be the same.
>
> I'm suggesting that the HNCP will pick one or the other (or some other
> translation) is picked as the single choice.
>
>     > It's much better not to do this. I think that the model of hiding
>     > ".local" is wrong for just this reason.
>
> Please explain more. Is it that I should be able to copy and paste from the
> UI to my command line?  How is showing .local in the GUI important?
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>