> > prplMesh solves the wifi broadcast domain issue. > > <url mauled by corporate policy> > > >From their website: « prplMesh is an open-source, carrier-grade and > certifiable implementation of the WiFi Alliance’s Multi-AP specification. » > > That's a purely layer 2 solution that relies on a central controller. > It depends on IEEE 1905: > <url mauled by corporate policy>
You can get the Wi-Fi Alliance MAP (branded EasyMesh) spec that prpl is implementing from the WFA website (after providing your name and contact info if you aren't a member): https://www.wi-fi.org/file/multi-ap-specification-v10 You can also see the prplMesh code in its current (incomplete -- the project is still underway) state at: https://github.com/prplfoundation/prplMesh I am involved in the joint BBF effort that they mentioned. If someone wanted to join that project (it's free to join -- just requires agreeing to IPR policy and BSD+Patent open source license) and suggest and provide code for HNCP, they could. But since this is a purely Layer 2 network (routers will break it), the HNCP would really only be for other routers (e.g., IoT gateways attaching a Thread network) that aren't part of the Multi AP L2 network. If you'd like more info for joining the joint BBF/prpl project, let me know. Barbara _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
