RFC 6550 - RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
- Status: Proposed Standard
- Published: March 2012
- Stream: IETF
- Errata: No Errata
Abstract
Low-Power and Lossy Networks (LLNs) are a class of network in which both the routers and their interconnect are constrained. LLN routers typically operate with constraints on processing power, memory, and energy (battery power). Their interconnects are characterized by high loss rates, low data rates, and instability. LLNs are comprised of anything from a few dozen to thousands of routers. Supported traffic flows include point-to-point (between devices inside the LLN), point-to-multipoint (from a central control point to a subset of devices inside the LLN), and multipoint-to-point (from devices inside the LLN towards a central control point). This document specifies the IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL), which provides a mechanism whereby multipoint-to-point traffic from devices inside the LLN towards a central control point as well as point-to-multipoint traffic from the central control point to the devices inside the LLN are supported. Support for point-to-point traffic is also available.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6550.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Table of Contents
- 1. Introduction
- 2. Terminology
- 3. Protocol Overview
- 4. Traffic Flows Supported by RPL
- 5. RPL Instance
- 6. ICMPv6 RPL Control Message
- 7. Sequence Counters
- 8. Upward Routes
- 9. Downward Routes
- 9.1. Destination Advertisement Parents
- 9.2. Downward Route Discovery and Maintenance
- 9.3. DAO Base Rules
- 9.4. Structure of DAO Messages
- 9.5. DAO Transmission Scheduling
- 9.6. Triggering DAO Messages
- 9.7. Non-Storing Mode
- 9.8. Storing Mode
- 9.9. Path Control
- 9.10. Multicast Destination Advertisement Messages
- 10. Security Mechanisms
- 11. Packet Forwarding and Loop Avoidance/Detection
- 12. Multicast Operation
- 13. Maintenance of Routing Adjacency
- 14. Guidelines for Objective Functions
- 15. Suggestions for Interoperation with Neighbor Discovery
- 16. Summary of Requirements for Interoperable Implementations
- 17. RPL Constants and Variables
- 18. Manageability Considerations
- 18.1. Introduction
- 18.2. Configuration Management
- 18.2.1. Initialization Mode
- 18.2.2. DIO and DAO Base Message and Options Configuration
- 18.2.3. Protocol Parameters to Be Configured on Every Router in the LLN
- 18.2.4. Protocol Parameters to Be Configured on Every Non-DODAG-Root Router in the LLN
- 18.2.5. Parameters to Be Configured on the DODAG Root
- 18.2.6. Configuration of RPL Parameters Related to DAO-Based Mechanisms
- 18.2.7. Configuration of RPL Parameters Related to Security Mechanisms
- 18.2.8. Default Values
- 18.3. Monitoring of RPL Operation
- 18.4. Monitoring of the RPL Data Structures
- 18.5. Fault Management
- 18.6. Policy
- 18.7. Fault Isolation
- 18.8. Impact on Other Protocols
- 18.9. Performance Management
- 18.10. Diagnostics
- 19. Security Considerations
- 20. IANA Considerations
- 20.1. RPL Control Message
- 20.2. New Registry for RPL Control Codes
- 20.3. New Registry for the Mode of Operation (MOP)
- 20.4. RPL Control Message Options
- 20.5. Objective Code Point (OCP) Registry
- 20.6. New Registry for the Security Section Algorithm
- 20.7. New Registry for the Security Section Flags
- 20.8. New Registry for Per-KIM Security Levels
- 20.9. New Registry for DODAG Informational Solicitation (DIS) Flags
- 20.10. New Registry for the DODAG Information Object (DIO) Flags
- 20.11. New Registry for the Destination Advertisement Object (DAO) Flags
- 20.12. New Registry for the Destination Advertisement Object (DAO) Acknowledgement Flags
- 20.13. New Registry for the Consistency Check (CC) Flags
- 20.14. New Registry for the DODAG Configuration Option Flags
- 20.15. New Registry for the RPL Target Option Flags
- 20.16. New Registry for the Transit Information Option Flags
- 20.17. New Registry for the Solicited Information Option Flags
- 20.18. ICMPv6: Error in Source Routing Header
- 20.19. Link-Local Scope Multicast Address
- 21. Acknowledgements
- 22. Contributors
- 23. References
- Appendix A. Example Operation
- Authors' Addresses