Benjamin Damm <[email protected]> wrote: > Michael's assumptions regarding why are mostly correct. There are many > versions of the SSNI network, but the standard model is where the > continuously powered devices (CPDs) which are firmware-upgradable form > the core canopy and the majority of the device population, and various > battery-powered devices hang off of the canopy using whatever CPD > signals they can get. The CPDs are typically not significantly > constrained (they aren't constrained at all per rfc7228) but the BPDs > typically are, and they aren't all the same rfc7228 class. The > evolution is to allow standard Wi-SUN (route-over) devices join the > mesh, and potentially use some of the same RPL data structures, > messages, and algorithms where possible to reduce the private burden of > having non-standard routing structures and the various tooling and > expertise challenges that go with that.
Would you expect the the wi-sun devices to only link to the CPDs, or do they also need to connect to the BPDs? If the former (just CPDs), then you just need to incrementally upgrade the CPDs in the field, and when they discover upstream CPDs that speak RPL they join both PANIDs. Then they just send DAOs for all their L2 connected BPDs. There are probably some ND issues to sort out, and maybe an (efficient!) ND proxy is in order. Basically the RPL becomes the "backbone" for the mesh-under networks. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ 6lo mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lo
