Re: [homenet] alternatives to .home

Joe Touch <touch@isi.edu> Fri, 17 June 2016 04:32 UTC

Return-Path: <touch@isi.edu>
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 424D212DD8C for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 21:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level:
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 x-UV-C_YbRiI for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 21:32:58 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 685BF12DD63 for <homenet@ietf.org>; Thu, 16 Jun 2016 21:32:58 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u5H4WgGV025668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Jun 2016 21:32:43 -0700 (PDT)
To: Andrew Sullivan <ajs@anvilwalrusden.com>, homenet@ietf.org
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <4598.1466104881@obiwan.sandelman.ca> <57630B75.9070807@isi.edu> <20160617010456.GB22195@mx2.yitter.info>
From: Joe Touch <touch@isi.edu>
Message-ID: <57637D69.1050000@isi.edu>
Date: Thu, 16 Jun 2016 21:32:41 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160617010456.GB22195@mx2.yitter.info>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/nmv0NepUrUpTaZWMM77eDL9jhf8>
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 04:32:59 -0000


On 6/16/2016 6:04 PM, Andrew Sullivan wrote:
> On Thu, Jun 16, 2016 at 01:26:29PM -0700, Joe Touch wrote:
>> See RFC3172.
>>
>> I don't think .arpa is the correct place for this sort of stuff.
> Why?  "[T]his domain name undertakes a role as a limited use domain
> for Internet infrastructure applications," and
>
>    This domain is termed an "infrastructure domain", as its role is to
>    support the operating infrastructure of the Internet.  In particular,
>    the "arpa" domain is not to be used in the same manner (e.g., for
>    naming hosts) as other generic Top Level Domains are commonly used.
The use of .home is a lot more like a conventional TLD than it is like
any other use in .arpa (e.g., reverse lookups based on IP addresses,
telephone number mapping, etc.).

> If the names beneath this special-use name are supposed to cause
> software to do something differently than it would with any other
> domain name, then that sounds like "infrastructure" to me.  That's why
> we used it for the special IPv4 only name in dns64, for instance.

The software does exactly the same thing. Having a response is based on
a local database, such that the same query in different places gives
different results, is not uncommon in other TLD lookups.

Joe