%% You should probably cite rfc6754 instead of this I-D.
@techreport{ietf-pim-ecmp-04,
    number =    {draft-ietf-pim-ecmp-04},
    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-pim-ecmp/04/},
    author =    {Yiqun Cai and Liming Wei and Heidi Ou and Vishal Arya and Sunil Jethwani},
    title =     {{Protocol Independent Multicast ECMP Redirect}},
    pagetotal = 12,
    year =      2012,
    month =     jun,
    day =       28,
    abstract =  {A Protocol Independent Multicast (PIM) router uses the Reverse Path Forwarding (RPF) procedure to select an upstream interface and router to build forwarding state. When there are equal cost multiple paths (ECMP), existing implementations often use hash algorithms to select a path. Such algorithms do not allow the spread of traffic among the ECMPs according to administrative metrics. This usually leads to inefficient or ineffective use of network resources. This document introduces the ECMP Redirect, a mechanism to improve the RPF procedure over ECMPs. It allows ECMP path selection to be based on administratively selected metrics, such as data transmission delays, path preferences and routing metrics.},
}