Recommendations for Efficient Implementation of RPL

Document Type Expired Internet-Draft (individual)
Last updated 2013-09-15 (latest revision 2013-03-14)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


RPL is a flexible routing protocol applicable to a wide range of Low Power and Lossy Networks. To enable this wide applicability, RPL provides many configuration options and gives implementers choices on how to implement various components of RPL. Drawing on our experiences, we distill the design choices and configuration parameters that lead to efficient RPL implementations and operations.


Omprakash Gnawali (
P Levis (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)