[homenet] Multiple routers in the home

Jan Newmarch <jan@newmarch.name> Sat, 11 May 2019 07:32 UTC

Return-Path: <jan.newmarch@gmail.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 B580A1200F3 for <homenet@ietfa.amsl.com>; Sat, 11 May 2019 00:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 BsfaOlUKaVsZ for <homenet@ietfa.amsl.com>; Sat, 11 May 2019 00:32:05 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 1F349120048 for <homenet@ietf.org>; Sat, 11 May 2019 00:32:05 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id z26so4422286pfg.6 for <homenet@ietf.org>; Sat, 11 May 2019 00:32:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:message-id:subject:from:to:date:mime-version :content-transfer-encoding; bh=l296CkBq7mufkhlPvkweFwkR9uNDF2jjhKx+QiKfUwY=; b=tzZvBegYhaXlyHpwM0YFUlilAlsRVJYix0UkopED7bMlvFIjYiXIQufzNREEUpc8kJ WhdRexFSD1w7Tjji5JBZA4OF3+RoTHM9C8Gn7sK8So9Jlg+db6XtY8pzAHOWDcXpPLms H/celtUVUDewX3DQTRRkWNT6GYsImShXrBU9tcywYl39bk0Fx57QMg2xqIl1IWRCZ38v P8jOnxTV5L37izoFfzrfLVljKPFsX1XZ3vEFv1IIm4e5m81fPcMfWP5DHyXHFOefSors veAOrmdAb9QHi+5f+UZQEgyTuwvQaM4NAR3r/sjHf3sVIFlpah4bnnXUbd9CtbSzKQFm Anqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:message-id:subject:from:to:date :mime-version:content-transfer-encoding; bh=l296CkBq7mufkhlPvkweFwkR9uNDF2jjhKx+QiKfUwY=; b=tSKJYZRDVeX2T5jgSmrsQeQLycxLAgJxjSNiSocjKDVOvnCewtG4tMpOi0HGFU6a3E Pp82vUiwXBOQ0P8I7qRmUENo0B0iVwHKQJVfEIf39fEcIR6RCGT2ikMmiKubvfpRvF3s PnCcRexVw/wPHd2y1ynPtjBLuS3RZwd/e1f+KFDoK7DopHh9Si2/dJ+BSJMFE2F6CYJI Wzbo+/e1LJIyrY3JAphbyf/2imLnk5SwIf45ZRiMoB/jzaT7R5VViyQJkld0A5UqBAuC miNAK3oaswGMs6qoLCNarc62TNsyjasKIuralgOGN78g5HJepkR+KcdgN1HwNDrR8VcZ RyRA==
X-Gm-Message-State: APjAAAUBAcqsPrKHLJ2hSASzxVHGIpZzFVpuX/WsbZtUc9GirLzPpyq6 nnGuDzDi+soV4nFUpMnZl7QUQ7FjGqc=
X-Google-Smtp-Source: APXvYqw+nzZoPd2/bBWqMxVbuqRsHDYIOGz29IS6ocTiFy8W+gdP8D4ULTHY5KLE42g+z8Ao1bmPJQ==
X-Received: by 2002:aa7:95bb:: with SMTP id a27mr8203249pfk.30.1557559922964; Sat, 11 May 2019 00:32:02 -0700 (PDT)
Received: from Desktop ([103.79.105.27]) by smtp.gmail.com with ESMTPSA id r9sm7711134pfc.173.2019.05.11.00.32.00 for <homenet@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 11 May 2019 00:32:01 -0700 (PDT)
Sender: Jan Newmarch <jan.newmarch@gmail.com>
Message-ID: <bd3d7018c790d3316e67ceace8560af375849035.camel@newmarch.name>
From: Jan Newmarch <jan@newmarch.name>
To: 'homenet' <homenet@ietf.org>
Date: Sat, 11 May 2019 17:31:57 +1000
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/AAcBHCcSeLqKHQgsjEGnzW-hGdM>
Subject: [homenet] Multiple routers in the home
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
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, 11 May 2019 07:32:07 -0000

I'm new to this list so may cover old ground, be off topic, etc. Feel
free to shoot me down!

Barbara Stark writes [homenet rechartering, meetings, and code}

   Multiple routers just for the purpose of having multiple (general
   purpose) routers may not be a common use case?

I would suggest that's because the use cases discussed so far seem to
be almost limited to guest networks and work vlans. I know the IETF is
about technical issues, but that isn't selling the idea to the home
market. So how about talking about the way the home network might be
divided up:

Social: work networks for mum and dad; teenager network filled with RAP
music; young child network, very protected; family network with the TV,
web server with family photos, etc

Location: kitchen network with recipe server linked to cookers,
microwaves etc; family room with lots of PCs, tablets etc with lots of
games and shared resources

Function: lighting network(s) with 100 bulbs*; low-power garden
network; air con.

So these would suggest multiple purposes even in the home, and subnets
for each would be a good way of managing it. Yes, many nodes would be
on multiple subnets, but that isn't a problem.

When IPv6 talks about everything having an address, people jump up and
down about their microwave being on the internet. We know that isn't
true: addressability is not accessibility, and firewalls are in common
use block global accessibility. 

Homenet adds to addressability, with household-wide naming and service
discovery. I suggest Homenet needs to bring the discussion about
accessability inside the home to manage these different subnets, and
not just at the internet gateway. So the young child network should be
in a tightly controlled domain. Similarly, I would want my work servers
protected against viruses and ransomware brought into the network by
others. When the teenager has a party with 30 curious, technically
savvy and possibly socially immature friends, I want to be able to wall
them off from playing party games with the lights in my bedroom, say.

I'm on more shaky ground here, but I don't see much about L2 firewalls.
I see Eero has Family profiles for its mesh networks, but I guess this
is done in a non-standard way and is probably not as well-developed as
L3 firewalls. On the other hand, L3 firewalls are well understood and
supported by all routers (and OpenWRT, of course).

* looking at e.g. the LIFX forum ("Maximum/many bulbs on a single
network"), reports are that most home routers fail at handling more
than 30 nodes on a single SSID, and other reports are that 30 nodes per
home will the _average_ number within a year or two in Australia at
least. Multiple (or expensive) routers seem to  be the only solution
anyway.

Cheers

Jan
-- 
Dr Jan Newmarch,
Associate Professor, Box Hill Institute

Adjunct Professor, University of Canberra
Adjunct Lecturer, Charles Sturt University

P 03 9286 9971
M +61 4 0117 0509
W jan.newmarch.name
E jan@newmarch.name