Re: [homenet] (no subject)

Ted Lemon <mellon@fugue.com> Tue, 24 July 2018 04:58 UTC

Return-Path: <mellon@fugue.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 CA381130FDF for <homenet@ietfa.amsl.com>; Mon, 23 Jul 2018 21:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Mx3h84az3bVS for <homenet@ietfa.amsl.com>; Mon, 23 Jul 2018 21:58:55 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 EDF36130DDA for <homenet@ietf.org>; Mon, 23 Jul 2018 21:58:54 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id d16-v6so4800464itj.0 for <homenet@ietf.org>; Mon, 23 Jul 2018 21:58:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RjzszJChMQAhk7EZ1fOQS0/Zp0a9QfwwZo43IDkKUh4=; b=aZHUNmHGkeNQWcsymynWI6qYik3o79nDvve1oosGBhKJrpxgT9Y6CsWcHvFQ7IdjU4 Y6u4aJEwlPNgabfBQYbFq9+LNaN4azzMku7JjHhl28J2jie0YBo5Vjo7X/JwI4MrR1hm Q8ORcoQOcldhTVfcgtXx+4EAdIzhb/s093vQpBp3uu+Qrrj/EHujMy/MV8VemOMfoGTj 2ViEa50S7qFWhDDGFSjh5mHgDXXta+Csav+W31yJ1OZRzbyi/cvcWFkZ3jfb6W6MDYvb pg87C3+Hai9FKCCgQ9wyh21j3JfbQqpRxF6afg5LwI4EZzuLpGAzh40FmmpbNz21oWg3 oNRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RjzszJChMQAhk7EZ1fOQS0/Zp0a9QfwwZo43IDkKUh4=; b=klsEvb0EkTrIN/Cqkafft+nBgNSU2GRsyx6a72ik1e+iejwbjXDjlpruHEk90YStdO 2xrK5zsY9Ed58UKUqDa/XEhGj+WdvI7ga7tRw9HXdO/zQuaI5qRqw974N54EijJAJnwd LsD5e5hG999BetV30LjgRBjHLdDdu3c84zCzA5NrqL5Wu1BgJw44u8qVag7UWYlMyf9z ft8/ch36XzNYBAwjJaBQ/PyAio69fo+5WcTo84VJ+SUNAm5X8rHofTLAS5VMwHPeDp7Y j2b5Ef6DW2aAmi/N2saro7fLwJzoOwC3Ok1CDcQtHyP6okTXr7F5Y9I1dh125El2auOw kk2Q==
X-Gm-Message-State: AOUpUlHSGCBZ33UjCTYtlm8Vmt087MH5wvoSDzhAdSnW2HY8hZEYRkfc PL0sIqdVyD5BAIPxwBvPUautW6clzzjF8GfjZjVZFwIe
X-Google-Smtp-Source: AAOMgpeyQkeCYMzd81x41kYn8znj8M214XMDm75I/jAYO8iZGFqRpJGon7CunHsbiXWmHDz37lYGt70qciV5FxEq9B4=
X-Received: by 2002:a24:8a85:: with SMTP id v127-v6mr1493085itd.98.1532408334264; Mon, 23 Jul 2018 21:58:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:b442:0:0:0:0:0 with HTTP; Mon, 23 Jul 2018 21:58:13 -0700 (PDT)
In-Reply-To: <CADyWQ+EtHqSF6Q2ubFcuo4=vEE02J=_6_3HSmQFiokAez=bz=Q@mail.gmail.com>
References: <87sh4g1bqe.wl-jch@irif.fr> <249918E0-8E8F-44A9-B1ED-0D4F91104B20@isc.org> <877elsovmq.wl-jch@irif.fr> <CAPt1N1msXi1BG9RTDr2sWnn8J6F45CnESJCg4LTP-4jP9mVJxw@mail.gmail.com> <87tvovd0jp.wl-jch@irif.fr> <f70a8ff8-fb99-115d-ec33-d0ffa9ae8f13@cs.tcd.ie> <CAPt1N1=hpR81cBrs1zFKux6JAXQxn6g0==DiSWYVbW0hdSxbww@mail.gmail.com> <87k1prarme.wl-jch@irif.fr> <bc700dd55f654447a02cd93226f6aba5@cira.ca> <87sh496bnb.wl-jch@irif.fr> <87va953hx1.fsf@toke.dk> <87pnzd6a7m.wl-jch@irif.fr> <87sh493g6f.fsf@toke.dk> <87in5567fp.wl-jch@irif.fr> <CAPt1N1khPUk2pKeLnmyLhnUegh-w4PtSMwsH-auYXnL5aaqS5Q@mail.gmail.com> <87fu0961to.wl-jch@irif.fr> <A04ADE38-76E9-4203-A88E-F3826A6B8B93@fugue.com> <b6d4dcab-6c98-642b-9e85-17c1ccd90a6a@mtcc.com> <2D09D61DDFA73D4C884805CC7865E6114DE4F271@GAALPA1MSGUSRBF.ITServices.sbc.com> <382e4f04-14c4-6954-4195-f1f0429d8445@mtcc.com> <CAPt1N1=oqHObdzEqFGfap=Z_+Wi5z49xRy-Z=7PxKVCCATiQ0w@mail.gmail.com> <CADyWQ+EtHqSF6Q2ubFcuo4=vEE02J=_6_3HSmQFiokAez=bz=Q@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 24 Jul 2018 00:58:13 -0400
Message-ID: <CAPt1N1nVZS9EcaeYoOn1Vq=khpoG2m1B9G2THzpYYX6aMYxBRQ@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: Michael Thomas <mike@mtcc.com>, HOMENET <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a431b0571b79e59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/5_B91ljziwdBtDqk-Ol7MmKk0-8>
Subject: Re: [homenet] (no subject)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 24 Jul 2018 04:58:58 -0000

Sure, it *could*, but it's probably easier to implement it as a
split-horizon DNS server that only talks to the homenet.

On Tue, Jul 24, 2018 at 12:31 AM, Tim Wicinski <tjw.ietf@gmail.com> wrote:

> Instead of calling it a "DNS Server" perhaps call it the "declarative data
> store"?  it could be a git repo,
>
> tim
>
> On Mon, Jul 23, 2018 at 10:43 PM, Ted Lemon <mellon@fugue.com> wrote:
>
>> The DNS server in the cloud doesn't have to answer queries.   Indeed, it
>> probably shouldn't.   It's really just a backing store.   The
>> public/private primary with selective publication is just a functional
>> block—you can put it where it makes the most sense.   Juliusz is saying
>> that he wants a nearly stateless homenet; for him, putting the
>> public/primary functional block in the cloud makes sense because it keeps
>> his homenet stateless.   I would not want that configuration because it
>> exposes the internals of my network to the cloud provider (unless it's also
>> encrypted, but then you have a keying problem).
>>
>> On Mon, Jul 23, 2018 at 9:02 PM, Michael Thomas <mike@mtcc.com> wrote:
>>
>>> On 07/23/2018 05:45 PM, STARK, BARBARA H wrote:
>>>
>>>> You're concerned with the homenet losing state when the master is
>>>>>> unplugged.   By having the master in the cloud, this problem is eliminated.
>>>>>>
>>>>> I can't speak for Juliusz, but my first question was "what if i don't
>>>>> want it in the cloud"? For one thing, what if it's a cloudless day?
>>>>>
>>>> I was starting to accept the idea that selecting a subset of my devices
>>>> to exist in global DNS. But absolutely, positively, not all. Any design I
>>>> could buy into will *not* push all my DNS into the cloud.
>>>>
>>>
>>> As usual i'm probably behind, but I kind of thought this was more about
>>> provisioning/configs. The way I've thought
>>> about this is that where I decide is the ultimate repository for truth
>>> for my configs is really a deeply personal
>>> decision. The easy case is when i delegate it to "the cloud" since it
>>> then becomes somebody else's $DAYJOB to
>>> figure out how to back it up, etc. But if I want to keep things local --
>>> for whatever reason, including tin foil hats --
>>> i'd really like my homenet to have the property that i can take one
>>> router and throw it in the trash, and plug in
>>> another, and with minimal fuss it takes over for the old one.
>>>
>>> For naming, that implies that i want to distribute the naming database
>>> such that there isn't a single point of failure.
>>> While this isn't exactly new territory, it is in the context of my home
>>> networking. Better would be to use already
>>> standardized mechanisms so that everybody's sanity is preserved, if only
>>> a little bit.
>>>
>>> Mike
>>>
>>>
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homenet
>>>
>>
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>
>>
>