%% You should probably cite rfc6554 instead of this I-D. @techreport{ietf-6man-rpl-routing-header-07, number = {draft-ietf-6man-rpl-routing-header-07}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-6man-rpl-routing-header/07/}, author = {David Culler and Jonathan Hui and JP Vasseur and Vishwas Manral}, title = {{An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL)}}, pagetotal = 13, year = 2011, month = dec, day = 15, abstract = {In Low-Power and Lossy Networks (LLNs), memory constraints on routers may limit them to maintaining, at most, a few routes. In some configurations, it is necessary to use these memory-constrained routers to deliver datagrams to nodes within the LLN. The Routing Protocol for Low-Power and Lossy Networks (RPL) can be used in some deployments to store most, if not all, routes on one (e.g., the Directed Acyclic Graph (DAG) root) or a few routers and forward the IPv6 datagram using a source routing technique to avoid large routing tables on memory-constrained routers. This document specifies a new IPv6 Routing header type for delivering datagrams within a RPL routing domain. {[}STANDARDS-TRACK{]}}, }