Re: [homenet] Homenet market gap analysis...

Toke Høiland-Jørgensen <toke@toke.dk> Wed, 13 March 2019 21:27 UTC

Return-Path: <toke@toke.dk>
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 8DA0112423B for <homenet@ietfa.amsl.com>; Wed, 13 Mar 2019 14:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 mHNWCkg7w1EF for <homenet@ietfa.amsl.com>; Wed, 13 Mar 2019 14:27:28 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [IPv6:2a00:7660:6da:2001::664]) (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 4E0A8120106 for <homenet@ietf.org>; Wed, 13 Mar 2019 14:27:28 -0700 (PDT)
From: Toke Høiland-Jørgensen <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1552512445; bh=tEVUHUl+ASNaHyagoKWxvEmKcZrvBCW8yZo12s0dYjw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=p+r/p0MV7LS2w9z7X/P2nwZNwkM7D0WLjkUwER+fBNo16d++OPrhohicVLRGBLyrG pKrRlzJhHfAbaD9MxeQrnzSI5Hdyfb+bXIhB9Qp3XfRjevvlsjqp9n7+Vcfts5qj71 AA79WtOh3DDx+nRjAV7GYsx5Vv/lPQYdcwoBd/k0x1P7MGVkLvRoOp4w2V2EngANdK Ajpmig3cBxADXWaFxrI/u0KQLnEVFia30Qst1mhcrELCrKnKN71+6whXi1pmgLGAWf Gyi7zE7BAaSgnBVOXCNNYnVdN5GMNRRZ6jyNarji8y+gDrnBplrtGv9W6xgkq0iUSD tNAwFwtHr3IAQ==
To: Mikael Abrahamsson <swmike@swm.pp.se>, Ted Lemon <mellon@fugue.com>
Cc: HOMENET <homenet@ietf.org>
In-Reply-To: <alpine.DEB.2.20.1903132134500.3161@uplift.swm.pp.se>
References: <ACFF8ADB-BC7F-4A12-BE14-E7655F1C82E2@fugue.com> <alpine.DEB.2.20.1903132134500.3161@uplift.swm.pp.se>
Date: Wed, 13 Mar 2019 22:27:25 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87a7hy1n42.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/qZitv-GlHEQnnHHUjnYYVGrfmEk>
Subject: Re: [homenet] Homenet market gap analysis...
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: Wed, 13 Mar 2019 21:27:31 -0000

Mikael Abrahamsson <swmike@swm.pp.se> writes:

> I especially agree with the statement on wifi roaming between APs does
> require shared L2, and there has been discussions about this and how
> to solve that, and I think it's a requirement for homenet to become a
> useful solution in that space. This would probably require some kind
> of tunneling or vlan encapsuatlion between homenet devices to be
> controlled somehow. There are routing protocols out there that already
> do this, can perhaps be used as inspiration.

You don't actually need encapsulation or VLANs if all access points
participate in the routing protocol. You can just announce routes for
each of the clients' IP addresses on roaming. You'll need some mechanism
for discovering those IP addresses of course; one option is something
like l3roamd[0] (which more or less just sniffs the addresses used by
the client), but others are certainly possible. I remember discussing
other approaches with Juliusz at some point, but I guess none of us ever
got around to implementing something.

Either way, I guess this is something homenet could conceivably specify
a solution for if there was sufficient interest... :)

-Toke

[0] https://github.com/freifunk-gluon/l3roamd