Hello Ted : Yes the millions I'm talking about are deployed in production. If that's so complicated then I guess we have has 2 small groups of magicians at Cisco alone ; ) I'm aware of competition as well. Plus my private pre-RPL implementation that took less than a month to code and test.
As the moment all deployed nodes are equally capable, meaning that the leaves are capable to be routers. They are all powered and always son. The second generation that we are preparing will have low-power leaves that - are duty cycled - do not need to understand any of RFC 6550. The WIP draft is https://tools.ietf.org/html/draft-ietf-roll-unaware-leaves We've made it so that the 6LoWPAN ND interface (RFC 8505) is enough to register to abstract connectivity services that can be ND proxy or routing. The unaware leaves spec redistributes addresses learned via ND into RPL; we have a similar operation in DC routing to inject virtual machines / containers addresses in RIFT. It should work with other IGPs as well, and even BGP/eVPN, why not? All the best Pascal From: Ted Lemon <mel...@fugue.com> Sent: lundi 7 octobre 2019 15:27 To: Pascal Thubert (pthubert) <pthub...@cisco.com> Cc: Ole Troan <otr...@employees.org>; Markus Stenberg <homenet@ietf.org>; 6MAN <6...@ietf.org> Subject: Re: [homenet] Support for RFC 7084 on shipping devices... On Oct 7, 2019, at 3:37 AM, Pascal Thubert (pthubert) <pthub...@cisco.com<mailto:pthub...@cisco.com>> wrote: Too bad then... I still fail to see why the model cannot be generalized to more powerful nodes. Because it is maximally complex? :] You say that RPL has scaled to millions of nodes. Where is this deployed in production? What are the leaf nodes doing? With what are they communicating?
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
