IETF Logo Mail Archive

Re: [homenet] alternatives to .home

Ralph Droms <rdroms.ietf@gmail.com> Mon, 20 June 2016 15:01 UTC

Return-Path: <rdroms.ietf@gmail.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 ED79E12D17A for <homenet@ietfa.amsl.com>; Mon, 20 Jun 2016 08:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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=gmail.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 5D5kY11IXwON for <homenet@ietfa.amsl.com>; Mon, 20 Jun 2016 08:01:48 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 DDDCE12D181 for <homenet@ietf.org>; Mon, 20 Jun 2016 08:01:44 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id t127so43622874qkf.1 for <homenet@ietf.org>; Mon, 20 Jun 2016 08:01:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=ln0hOJoPiUdSRGfTbHlQYo9F+OW8cqCqD35F9hYDnn0=; b=mxndTp8HfJfH06BOaFonoKFvC9qOHudnJsZ5oUnKerFJjC+wQz3hn27Rli06xJW0Yi Y04fXtdGbuvAgAWo9JYeh5aHtWJP37BCH5PcXCbuBe74DkPYmg2PdOolKRw6KATiR3Fu /5A3r08ciyoG7taogXZTqLoy07Ev/nQ9ZIVd6jM5R/irck58yaw2P+qOOeEBGobxE9T+ LfdTvS2aDzh3UAtRq4G2hNeiSdnu56DN9X/Fe8ZXXuNMDsw2hxcmIF0HpRfjCFcd679R LU+A2gY69r81KJs/1FhMBm5vE+siR2bjy01d0W3aAMS1vzOd3RUhM4vMkwkcJ49bwk0z z/Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=ln0hOJoPiUdSRGfTbHlQYo9F+OW8cqCqD35F9hYDnn0=; b=Us3m9PO8XYPE3isqZWTkPh+XKuBqLHndq+oQ9U/9kuAnfK/MC56C/LSq3v046+5qpi VtnYmj9UVYoWRT0fujks0fewycJZnjwb6mGvKgSgzYIH166/XI/OGyxaajyDtzBg6763 T3qgHkbWZJ8zPc9obb1af4KLyQU7BgMSVbd1KT3NTWYOvyJ5M5CdXRAI2PKDPKidcz/u W4+SaiHhzkHdvijXrgwx3JsBLbU3/ffbfcurnXwbhwxTnJAiITPdzUtnBT/FbMULf2P5 OR6STL82mFMgiDYvgDPrwHR8DhgU/eHUldYmsj8Mwazx2Ex4wv4P/W4iToMlrriJNfoW K9vA==
X-Gm-Message-State: ALyK8tKoE4wM3E+yIAQChjfeyIbwo5sKQA5r+bz98L2bUEhfqU4G9xb1EAclLsK7FEHJTg==
X-Received: by 10.200.50.37 with SMTP id x34mr22376864qta.42.1466434903953; Mon, 20 Jun 2016 08:01:43 -0700 (PDT)
Received: from [10.131.118.123] ([173.38.117.71]) by smtp.gmail.com with ESMTPSA id z94sm20104215qtc.49.2016.06.20.08.01.42 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 20 Jun 2016 08:01:42 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3825C332-55F2-4A19-8877-C829479913D2"; protocol="application/pgp-signature"; micalg="pgp-sha256"
X-Pgp-Agent: GPGMail 2.6b2
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <14830.1466432632@obiwan.sandelman.ca>
Date: Mon, 20 Jun 2016 11:01:40 -0400
Message-Id: <F4C771C6-F149-4E7B-AFAE-14CD19C3D697@gmail.com>
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> <14830.1466432632@obiwan.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/g_Q8-hfFZTdwOnmo_yBbxacyU_c>
Cc: HOMENET <homenet@ietf.org>
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 15:01:51 -0000

> On Jun 20, 2016, at 10:23 AM 6/20/16, Michael Richardson <mcr@sandelman.ca> wrote:
> 
> 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.

wireshark seems to indicate .local is included on the wire with mDNS requests.

> 
> 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.

Is this architecture documented somewhere?  I ask because I'm a little surprised by:

* standard DNS mechanisms
* split-horizon DNS
* (mostly) ULA IPv6

I'll admit to not having paid close attention and I might have missed this discussion.  And telling me to reread Ted's homenet naming architecture document is a fine response.

> 
> 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).

Personally, I think there will be broader scope to the special treatment of homenet-relative names, but won't know for sure until the details are nailed down.

- Ralph

> 
> 
> --
> ]               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    [
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

v2.23.0 | Report a Bug | By Email