Challenging the IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL): A Survey
- Authors
- Kim, Hyung-Sin; Ko, Jeonggil; Culler, David E.; Paek, Jeongyeup
- Issue Date
- Sep-2017
- Publisher
- IEEE-INST ELECTRICAL ELECTRONICS ENGINEERS INC
- Keywords
- RPL; IPv6; routing protocol; Internet of Things (IoT); low-power and lossy networks (LLN)
- Citation
- IEEE COMMUNICATIONS SURVEYS AND TUTORIALS, v.19, no.4, pp 2502 - 2525
- Pages
- 24
- Journal Title
- IEEE COMMUNICATIONS SURVEYS AND TUTORIALS
- Volume
- 19
- Number
- 4
- Start Page
- 2502
- End Page
- 2525
- URI
- https://scholarworks.bwise.kr/cau/handle/2019.sw.cau/6299
- DOI
- 10.1109/COMST.2017.2751617
- ISSN
- 1553-877X
1553-877X
- Abstract
- RPL is the IPv6 routing protocol for low-power and lossy networks, standardized by IETF in 2012 as RFC6550. Specifically, RPL is designed to be a simple and inter-operable networking protocol for resource-constrained devices in industrial, home, and urban environments, intended to support the vision of the Internet of Things with thousands of devices interconnected through multihop mesh networks. More than four-years have passed since the standardization of RPL, and we believe that it is time to examine and understand its current state. In this paper, we review the history of research efforts in RPL; what aspects have been (and have not been) investigated and evaluated, how they have been studied, what was (and was not) implemented, and what remains for future investigation. We reviewed over 97 RPL-related academic research papers published by major academic publishers and present a topic-oriented survey for these research efforts. Our survey shows that only 40.2% of the papers evaluate RPL through experiments using implementations on real embedded devices, ContikiOS and TinyOS are the two most popular implementations (92.3%), and TelosB was the most frequently used hardware platform (69%) on testbeds that have average and median size of 49.4 and 30.5 nodes, respectively. Furthermore, unfortunately, despite it being approximately four years since its initial standardization, we are yet to see wide adoption of RPL as part of real-world systems and applications. We present our observations on the reasons behind this and suggest directions on which RPL should evolve.
- Files in This Item
- There are no files associated with this item.
- Appears in
Collections - College of Software > School of Computer Science and Engineering > 1. Journal Articles
Items in ScholarWorks are protected by copyright, with all rights reserved, unless otherwise indicated.