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

"Ray Hunter (v6ops)" <v6ops@globis.net> Thu, 12 May 2016 08:44 UTC

Return-Path: <v6ops@globis.net>
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 3736F12B04F for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 01:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level:
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, 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 chdwEeAnY4Sm for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 01:44:01 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 44B9512B02D for <homenet@ietf.org>; Thu, 12 May 2016 01:44:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 1E0554033E; Thu, 12 May 2016 10:44:00 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LhQNCkkDhHh5; Thu, 12 May 2016 10:43:54 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id E7B36402E4; Thu, 12 May 2016 10:43:53 +0200 (CEST)
Message-ID: <57344249.8070907@globis.net>
Date: Thu, 12 May 2016 10:43:53 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@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> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com>
In-Reply-To: <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080106090605030902030708"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/O9kzea0rrC4T4w0LyNVJzkXBpqs>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [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: Thu, 12 May 2016 08:44:03 -0000


> Ted Lemon <mailto:mellon@fugue.com>
> 11 May 2016 20:03
> DNS update is pretty simple.   Any problem with using that?
Not with the update mechanism itself
>
> I think you may be slightly conclusing "authoritative" and "primary." 
>   There is no need to elect authoritative servers--just make them 
> secondary to the elected primary.   You can't have two primaries with 
> stock DNS--that's probably the biggest fly in the ointment.
>
Exactly.

The challenge is the Homenet requirement to support network segmentation 
and remerging.

We have multiple independent address spaces (ULA per router + GUA per 
provider), so why not multiple namespaces?

If a new router is added, a new ULA is added, together with associated 
namespace, and infra.
If a router is removed or dies, the ULA prefix expires, together with 
associated namespace and infra.

If a new ISP uplink is added, a new GUA is added, together with 
associated (upstream) (globally resolvable) namespace and infra.
If an ISP is removed or dies, the GUA expires, together with associated 
namespace and infra.

Then the namespace infra/ update server could be tightly bound to the 
device that delegates/creates it (either the homenet router, homenet 
border router, or the ISP infra)

I know people don't like DNS search lists, but they do work, and are 
widely supported. Or else a recursive resolver running on the local 
homenet router could handle the search work for the end hosts.

I also realize this creates a new challenge of how to update all of 
these various namespaces.

> The reason to have a hybrid proxy is because we have to support 
> existing devices.   Clearly it's not the right long-term solution, but 
> we can't force vendors to implement something new if they don't want to.
>
>

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>