IETF Logo Mail Archive

Re: [homenet] alternatives to .home

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 17 June 2016 01:05 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 1B99F12D9F0 for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 18:05:01 -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 VUhCEc61MrCN for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 18:04:59 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 156BB12D17A for <homenet@ietf.org>; Thu, 16 Jun 2016 18:04:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id CAD3C10CB0 for <homenet@ietf.org>; Fri, 17 Jun 2016 01:04:58 +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 25nyiEtkghhD for <homenet@ietf.org>; Fri, 17 Jun 2016 01:04:58 +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 22D311067D for <homenet@ietf.org>; Fri, 17 Jun 2016 01:04:58 +0000 (UTC)
Date: Thu, 16 Jun 2016 21:04:56 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160617010456.GB22195@mx2.yitter.info>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <4598.1466104881@obiwan.sandelman.ca> <57630B75.9070807@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <57630B75.9070807@isi.edu>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/CV95GbemMwTVDEsxiauSIrftQ1A>
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:05:01 -0000

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.

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.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email