Mikael, >> 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.
why do you think this has to be solved at L2? > 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? at least you can do: L3 - route injection (got a routing protocol there already, use it) L3.5 - SHIM6. not deployable L4/L5 - MP-TCP L5/L7 - MOSH cheers, Ole
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
