> RPL had to address multiple IOT GWs from the start, say one for the > power utility, one for cloud access, etc... to address this is that it > creates multiple instances which are as many logical topologies. By > selecting the instance applied to a packet, the source or the first RPL > router will force which GW is used.
Multiple instances of RPL are supported, but I don't see any explicit support for source-specific routing. In concrete terms, there's no way to associate a given source address to an instance ID, so you need to do that by means outside the protocol. (That's a little like saying that BGP has support for source-specific routing because you can use communities to encode source-specific routes.) > RPL extends the hop count to include more information, including that > instance ID. This is done by a HbH option Modifying the data plane so that it supports new IPv6 options is certainly something that's reasonable in a sensor network. -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
