Mikael Abrahamsson wrote:
On Fri, 20 Feb 2015, Teco Boot wrote:
Back to the subject: What are the requirements of a high performance
WiFi home network to the homenet routing protocol? I guess we don't
know.
Within the current framework to solve this problem with what exists
today when it comes to clients, I would say we need either:
1. HNCP helps set up an overlay L2 tunnel infrastructure connecting
all the APs using the same SSID, so the SSID can have the same L2
domain. This would probably mean we want to increase MTU on the
physical links to avoid fragmentation. Messy. Possibly we could
advertise lower MTU on the wifi network to minimize fragmentation if
we don't raise MTU.
2. We set up some kind of L2 switching domain between the APs. This
would require VLAN support in the HGWs, and something to set this up
with loop avoidance etc. Oh oh oh, we could use IEEE 802.1aq that
already uses ISIS as control plane, that way we could possibly run the
same IGP for both L2 and L3. Interconnecting APs over wifi seems weird
though. Oh, and messy sounds like an understatement.
Frankly, I don't know how to solve this without a lot of complication.
We need clients to be able to change IPv6 addresses without losing
existing connections. SHIM6 anyone? MP-TCP? Asking IEEE to make 802.11
keep two connections at once and inform the application that one
address is going away soon so it can do its thing to try to handle this?
I agree that WiFi roaming is a problem that needs addressing in Homenet.
One suggestion from my side for handling WiFi roaming is for these
clients to incorporate a software loopback interface that does not
renumber, and is always up, and these roaming clients also actively take
part in HNCP, and the Homenet routing protocol as "stub routers."
That way the devices can roam at L3, without all of the nasty side
effects of re-establishing TPC sessions, or updating dynamic naming
services, or having to run an L2 overlay network everywhere, or having
to support protocols that require a specialised partner in crime on the
server side (mTCP, shim6 et al).
YMMV.
--
Regards,
RayH
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
