Loop Free DODAG Local Repair
draft-guo-roll-loop-free-dodag-repair-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jianlin Guo, Philip Orlik, Ghulam Bhatti | ||
| Last updated | 2013-10-04 (Latest revision 2013-04-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
IETF has been developing IPv6 based standards for Low-power and Lossy Networks (LLNs) to meet requirements of constrained applications, such as field monitoring, inventory control and so on. IPv6 Routing Protocol for LLNs (RPL) has been published in [RFC6550]. Based on routing metrics and constraints [RFC6551], RPL builds Directed Acyclic Graph (DAG) topology to establish bidirectional routes for LLNs for traffic types of multipoint-to-point, point-to-multipoint, and point-to-point. RPL routes are optimized for traffic to or from one or more roots that act as sinks. As a result, a DAG is partitioned into one or more Destination Oriented DAGs (DODAGs), one DODAG per sink. RPL is widely considered as a feasible routing protocol for LLNs. However, DODAG loops caused by local DODAG repair mechanism is an issues to be addressed. This draft introduces a loop free local DODAG repair mechanism. This draft also introduces a piggybacked data option for transferring delay sensitive data during route repair process. The piggybacked data can be included in DODAG Repair Request (DRQ) message or DODAG Information Solicitation (DIS) message.
Authors
Jianlin Guo
Philip Orlik
Ghulam Bhatti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)