[[File:contiki_stacks.jpg|200px|right|frame|Contiki Layers]]
 
[[File:contiki_stacks.jpg|200px|right|frame|Contiki Layers]]
   −
RPL was designed with the objective to meet the requirements spelled out in [RFC5867], [RFC5826], [RFC5673], and [RFC5548].
+
RPL was designed with the objective to meet the requirements spelled out in [https://tools.ietf.org/html/rfc5867 RFC5867], [https://tools.ietf.org/html/rfc5826 RFC5826], [https://tools.ietf.org/html/rfc5673 RFC5673], and [https://tools.ietf.org/html/rfc5548 RFC5548].
    
In order to be useful in a wide range of LLN application domains, RPL separates packet processing and forwarding from the routing optimization objective.  Examples of such objectives includes minimizing energy, minimizing latency, or satisfying constraints. A RPL implementation, in support of a particular LLN application, will include the necessary Objective Function(s) as required by the application.
 
In order to be useful in a wide range of LLN application domains, RPL separates packet processing and forwarding from the routing optimization objective.  Examples of such objectives includes minimizing energy, minimizing latency, or satisfying constraints. A RPL implementation, in support of a particular LLN application, will include the necessary Objective Function(s) as required by the application.
 
RPL also expects an external mechanism to access and transport some control information, referred to as the "RPL Packet Information", in data packets.  RPL provides a mechanism to disseminate information over the  dynamically formed network topology.  This dissemination enables minimal configuration in the nodes, allowing nodes to operate mostly  autonomously.   
 
RPL also expects an external mechanism to access and transport some control information, referred to as the "RPL Packet Information", in data packets.  RPL provides a mechanism to disseminate information over the  dynamically formed network topology.  This dissemination enables minimal configuration in the nodes, allowing nodes to operate mostly  autonomously.   
   Exception encountered, of type "Error"