In message <17359.1424897...@sandelman.ca> Michael Richardson writes: > Ray Hunter <v6...@globis.net> wrote: > > I agree that WiFi roaming is a problem that needs addressing in > > Homenet. > > Yes, but can we rule it out of scope for now? > > Can we agree that it's not strictly a routing problem, and that the set of > solutions that we are considering could be used, and that we could also > explain how to do something like automatically setup capwap using HNCP for > discovery, but that we don't have the head-of-queue block on this item for > now? > > -- > Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =-
Perhaps consider it two problems, roaming within an administrative domain and roaming into another administrative doamin. The latter is harder to solve. Other than bridging all of the AP within an administrative domain, there is no way to support the former without at least some host change. As I mentioned before, I favor putting a /128 on the loopback and having the routers/APs forward to the interface address of the moment to that /128. Curtis _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
