Re: [homenet] (no subject)

Michael Thomas <mike@mtcc.com> Tue, 24 July 2018 01:02 UTC

Return-Path: <mike@mtcc.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 96440130EF4 for <homenet@ietfa.amsl.com>; Mon, 23 Jul 2018 18:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 alhwnuJijT0Q for <homenet@ietfa.amsl.com>; Mon, 23 Jul 2018 18:02:19 -0700 (PDT)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (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 EE6DE130F06 for <homenet@ietf.org>; Mon, 23 Jul 2018 18:02:18 -0700 (PDT)
Received: from takifugu.mtcc.com (mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.15.2/8.15.2/Debian-3) with ESMTPSA id w6O12IAK027216 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <homenet@ietf.org>; Mon, 23 Jul 2018 18:02:18 -0700
To: homenet@ietf.org
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>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <382e4f04-14c4-6954-4195-f1f0429d8445@mtcc.com>
Date: Mon, 23 Jul 2018 18:02:18 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DE4F271@GAALPA1MSGUSRBF.ITServices.sbc.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/tGjiylcVgqVnAGF-Q05WFE4_Wjw>
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 01:02:21 -0000

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