IETF Logo Mail Archive

Re: [homenet] alternatives to .home

Michael Richardson <mcr@sandelman.ca> Mon, 20 June 2016 14:23 UTC

Return-Path: <mcr@sandelman.ca>
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 A54B012D0DD for <homenet@ietfa.amsl.com>; Mon, 20 Jun 2016 07:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level:
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] 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 DA0uRnUm40df for <homenet@ietfa.amsl.com>; Mon, 20 Jun 2016 07:23:57 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40B5712D0C1 for <homenet@ietf.org>; Mon, 20 Jun 2016 07:23:57 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 327DE2009E for <homenet@ietf.org>; Mon, 20 Jun 2016 10:31:46 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2B84C638BF for <homenet@ietf.org>; Mon, 20 Jun 2016 10:23:52 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: HOMENET <homenet@ietf.org>
In-Reply-To: <87ziqjfpyf.wl-jch@pps.univ-paris-diderot.fr>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <4598.1466104881@obiwan.sandelman.ca> <87porgafsq.wl-jch@pps.univ-paris-diderot.fr> <6068.1466169439@obiwan.sandelman.ca> <87ziqjfpyf.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14829.1466432632.1@obiwan.sandelman.ca>
Date: Mon, 20 Jun 2016 10:23:52 -0400
Message-ID: <14830.1466432632@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ivq1fELvslPWan-D0FDmmpdvHaE>
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: Mon, 20 Jun 2016 14:24:00 -0000

Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    >>> - how does software running on my laptop, which just connected to an
    >>> unknown network, find out what is the local translation of "home"?

    >> It doesn't. It uses HNCP.

    > Please describe exactly how my laptop (which doesn't run HNCP) finds
    > out the right domain.  Please describe how an HNCP router that joins an

I think that it's in the DHCP.  You could ignore it.
DHCP/SearchPath is fraught with issues.

AFAIK, ".local" is not used on the wire with mDNS.
The .local is a clue from the end-user to the resolver that you should
use mDNS to resolve the name.

But, we aren't talking about mDNS, we are talking about names which are
resolved using standard DNS mechanisms, probably via search-path like thing,
which are split-horizon DNS and with return (mostly) ULA IPv6 names for parts
which are (possibly) more than one hop away.

We do need a special name with special treatment (whether it is localized or
not) because we need to teach tools like SSH and HTTPS that the name
"printer.home" can not be permanently bound to the same public key all the
time.  In particular, it needs to be qualified by the attachment point
(probably DHCP Server's DUID is best is available).


--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email