[homenet] Updating DNS [was: How many people have installed the homenet code?]

Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> Sat, 23 April 2016 17:35 UTC

Return-Path: <jch@pps.univ-paris-diderot.fr>
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 BD59812D660 for <homenet@ietfa.amsl.com>; Sat, 23 Apr 2016 10:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001] 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 XmF6tvWY1Nfr for <homenet@ietfa.amsl.com>; Sat, 23 Apr 2016 10:35:29 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35F2812D117 for <homenet@ietf.org>; Sat, 23 Apr 2016 10:35:28 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id u3NHZRRE000992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 23 Apr 2016 19:35:27 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id u3NHZRY6022086; Sat, 23 Apr 2016 19:35:27 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 367C161FE6; Sat, 23 Apr 2016 19:35:27 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 2D98HHZKePe9; Sat, 23 Apr 2016 19:35:25 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 62F1761FE5; Sat, 23 Apr 2016 19:35:25 +0200 (CEST)
Date: Sat, 23 Apr 2016 19:35:27 +0200
Message-ID: <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <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> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Sat, 23 Apr 2016 19:35:27 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sat, 23 Apr 2016 19:35:27 +0200 (CEST)
X-Miltered: at korolev with ID 571BB25F.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 571BB25F.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 571BB25F.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 571BB25F.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 571BB25F.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 571BB25F.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/AGTsc-JMCiqrt4ohQp9mGwbE35E>
Cc: homenet@ietf.org
Subject: [homenet] Updating DNS [was: 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:35:30 -0000

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

Yep.  Shncpd might learn to act as a DHCPv4 and DHCPv6-PD client at some
point.  (But first implement IPv4 edge router election, which is one of
the three missing features that I feel are necessary, security aside.)

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

Yes.  I'm not sure how shncpd should update the state, though, since it
doesn't act as a DNS resolver, it only passes the address of an existing
DNS resolver to clients, and I don't want to bind it to any specific
implementation of a DNS resolver.

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

Yeah, that's what I gathered.

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

Quoting Stephen:

   I agree with you as well, initially odhcpd did only do RAs and
   stateless DHCPv6 however the user community liked their stateful
   (v4isms) all too much so I had to give in. ;)

   -- https://github.com/sbyx/odhcpd/issues/55

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

I haven't looked at it, but my instinct would be to agree with you --
proxying in the presence of merging sounds like a can of worms that we
don't want to open.

Do any of the Wise People on this list have opinions about RFC 2136?

-- Juliusz