@techreport{zzhang-pim-bidir-rpl-resiliency-00,
    number =    {draft-zzhang-pim-bidir-rpl-resiliency-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-zzhang-pim-bidir-rpl-resiliency/00/},
    author =    {Zhaohui (Jeffrey) Zhang and Kurt Windisch and Jaroslaw Adam Gralak},
    title =     {{PIM-Bidir RPL Resiliency}},
    pagetotal = 10,
    year =      2013,
    month =     oct,
    day =       16,
    abstract =  {With PIM-Bidir, the RPA does not have to be associated with a router. Rather, it only needs to be a routable address on a RPL (typically a multi-access network). Such a scenario is commonly referred as Phantom RPA. This achieves RP resiliency to some extent, because the "RP" will not fail. However, if the RPL itself partitions, traffic converged to one partition will not be able to reach other parts of the network where joins converge to the other partitions of the RPL. This document proposes simple procedures, which does not require signaling extensions, to achieve RPL resiliency.},
}