IETF Logo Mail Archive

Re: [homenet] alternatives to .home

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 17 June 2016 01:10 UTC

Return-Path: <ajs@anvilwalrusden.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 6C96012D82A for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 18:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 eLA-tkyWgii2 for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 18:10:42 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 02DFC12D8E3 for <homenet@ietf.org>; Thu, 16 Jun 2016 18:10:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 945F510CAE for <homenet@ietf.org>; Fri, 17 Jun 2016 01:10:41 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBfyYYDPhnwq for <homenet@ietf.org>; Fri, 17 Jun 2016 01:10:40 +0000 (UTC)
Received: from mx2.yitter.info (c-73-142-157-135.hsd1.nh.comcast.net [73.142.157.135]) by mx2.yitter.info (Postfix) with ESMTPSA id D72091067D for <homenet@ietf.org>; Fri, 17 Jun 2016 01:10:40 +0000 (UTC)
Date: Thu, 16 Jun 2016 21:10:39 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160617011039.GC22195@mx2.yitter.info>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <4598.1466104881@obiwan.sandelman.ca> <87porgafsq.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1=7XE0__mG9ckJc6hb0EGHK4QE93_+Eqi6Gg7Mf05cXdQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAPt1N1=7XE0__mG9ckJc6hb0EGHK4QE93_+Eqi6Gg7Mf05cXdQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/OKvcFbsvD-ko-AK-hswdAmhnAno>
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 01:10:43 -0000

On Thu, Jun 16, 2016 at 07:53:42PM -0400, Ted Lemon wrote:

>.local has worked

But mostly because ordinary humans never see it.  That's what's not
clear to me.

Is this a name that will mostly be hidden by user-interface sugar
(which is mostly how it works with mDNS -- please don't tell me about
ssh.  That's not our audience, I maintain)?  If so, then any domain
will do, and putting it under arpa would be fine.

Is it a name that we expect people often to use in you-type-it-in
contexts?  If so, then the story is very different.

In any case, I'd really like "translation" to be off the table.  We
are not competent to do that, and anyway we're specifying a permanent
part of infrastructure that will not be able to evolve as (say)
language evolves.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email