%% You should probably cite draft-ietf-roll-dao-projection-34 instead of this revision.
@techreport{ietf-roll-dao-projection-09,
    number =    {draft-ietf-roll-dao-projection-09},
    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-roll-dao-projection/09/},
    author =    {Pascal Thubert and Rahul Jadhav and Matthew Gillmore},
    title =     {{Root initiated routing state in RPL}},
    pagetotal = 31,
    year =      2019,
    month =     nov,
    day =       18,
    abstract =  {This document enables a RPL Root to install and maintain Projected Routes within its DODAG, along a selected set of nodes that may or may not include self, for a chosen duration. This potentially enables routes that are more optimized or resilient than those obtained with the classical distributed operation of RPL, either in terms of the size of a source-route header or in terms of path length, which impacts both the latency and the packet delivery ratio. Projected Routes may be installed in either Storing and Non-Storing Modes Instances of the classical RPL operation, resulting in potentially hybrid situations where the mode of some Projected Routes is different from that of the other routes in the RPL Instance.},
}