{'fraction_non_alphanumeric': 0.024539877300613498, 'fraction_numerical': 0.0043821209465381246, 'mean_word_length': 5.451977401129944, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Towards full RPL interoperability: addressing the case with downwards routing interoperability

In this work we point out the issue of the IETF RPL routing protocol's two different downwards routing schemes not being able to interoperate with each other. This problem is less of an issue when low-power and lossy networks (LLNs) are deployed homogeneously but with the industrial kickoff and large scale deployments, the interoperability of heterogeneous, standards-compliant implementations will become a significant issue. To address this, we suggest two major changes to IETF RPL (RFC 6550). First we suggest that all storing mode nodes should hold the capability to understand and attach source routing headers that the non-storing mode nodes require to forward packets. Next, we suggest that RPL's non-storing mode nodes should send their destination advertisement messages hop-by-hop, rather than the current end-to-end approach. We show, with two different IPv6 implementations in TinyOS and NanoQplus, that our suggestions high achieve high interoperability performance among different implementations for downwards traffic patterns.