Re: [homenet] How many people have installed the homenet code?

Markus Stenberg <markus.stenberg@iki.fi> Sat, 23 April 2016 17:09 UTC

Return-Path: <markus.stenberg@iki.fi>
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 97A5212D161 for <homenet@ietfa.amsl.com>; Sat, 23 Apr 2016 10:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.048
X-Spam-Level:
X-Spam-Status: No, score=-0.048 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.652] 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 W8Fk9BOjSHfA for <homenet@ietfa.amsl.com>; Sat, 23 Apr 2016 10:09:23 -0700 (PDT)
Received: from johanna4.inet.fi (mta-out1.inet.fi [62.71.2.232]) by ietfa.amsl.com (Postfix) with ESMTP id 5260212D0BA for <homenet@ietf.org>; Sat, 23 Apr 2016 10:09:23 -0700 (PDT)
RazorGate-KAS: Status: not_detected
RazorGate-KAS: Rate: 0
RazorGate-KAS: Envelope from:
RazorGate-KAS: Version: 5.5.3
RazorGate-KAS: LuaCore: 215 2015-05-29_17-31-22 60ae4a1b4d01d14f868b20a55aced8d7df7b2e28
RazorGate-KAS: Lua profiles 78662 [Jun 02 2015]
RazorGate-KAS: Method: none
Received: from poro.lan (80.220.86.47) by johanna4.inet.fi (9.0.002.03-2-gbe5d057) (authenticated as stenma-47) id 570CF19A00E974F2; Sat, 23 Apr 2016 20:08:50 +0300
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr>
Date: Sat, 23 Apr 2016 20:08:49 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jGqybDGSj3RMXh5o64yLyDl0KoE>
Cc: homenet@ietf.org, Tim Coote <tim+ietf.org@coote.org>
Subject: Re: [homenet] How many people have installed the homenet code?
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: Sat, 23 Apr 2016 17:09:25 -0000

On 23.4.2016, at 19.39, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>; wrote:
>> I’m starting by running shncpd on a boundary router and tried a trivial
>> installation.
> Excellent, thanks.
> 
>> I don’t see how dns gets updated. Are such updates out of scope of
>> shncpd?
> 
> Do you mean, (1) how is a DNS resolver advertised to clients, or
> (2) how clients are registered in DNS ?
> 
> (1) is done by using the -N flag on the router advertising an external
> connection (-E).  This flag can be repeated multiple times.

hnetd grabs this automatically from wan-facing DHCP client, but again, requires integration to work nicely (odhcp6c glue script supported on most Linux platforms). Clients on the other hand are given always just first-hop router address.

> (2) is a host issue, so I believe it is better handled outside of shncpd,
> but I'm quite willing to be convinced otherwise.  (The obvious alternative
> would be to have shncpd update DNS when it gives out a DHCP lease, but
> that would mean giving up on stateless autoconf.)

Well, DHCPv4 is stateful anyway, and you could in theory bind state from there as well (at least if you do IPv4).

>> Are they in scope for the other homenet protocols?
> Markus, Steven, Ted?  What's the plan here?  Do we count on mDNS proxying,
> or should we be advertising an RFC 2136 server over HNCP?

I think the plan varies ;-)

hnetd (and current HNCP + my expired autoconf draft) are based on the idea of using mDNS _and/or stateful DHCPv4 and/or stateful DHCPv6 to determine what’s on each link, and advertise the routers responsible for each link across the homenet. It does work with ‘current stuff’ for some relatively high % of likelihood.

Ted’s draft proposes either learn-from-mDNS (=proxy DNS-update) and/or (manually/automatically configured client-sourced) DNS-update scheme. I am worried about zone merging + conflict resolution, although if it works out it sounds like a good solution. 

(Zone merging + plain hybrid proxy is at least very problematic, if you want hybrid proxies to remain stateless. I have looked at it and it is neither pretty nor efficient.)

Cheers,

-Markus