%% You should probably cite draft-sami-pim-ng-14 instead of this revision.
@techreport{sami-pim-ng-00,
    number =    {draft-sami-pim-ng-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-sami-pim-ng/00/},
    author =    {saeed sami},
    title =     {{Protocol independent multicast- Next Generation (PIM-NG): Protocol Specifications}},
    pagetotal = 165,
    year =      2013,
    month =     dec,
    day =       7,
    abstract =  {This document specifies protocol independent multicast-Next Generation or simply called PIM-NG. like PIM-SM ,PIM-NG uses the underlying unicast routing information , but unlike PIM-SM it doesn't necessarily need to build unidirectional shared trees rooted at a Rendezvous Point (RP) per group ,due to the fact that the processes through which a source registers with the Rendezvous Point and a host finds the source of the multicast destination groups it needs are done in a whole new way. So at some points PIM-NG works faster than its predecessor. Also the new Domain concept, unique to PIM-NG, along the RPF check method used in PIM-NG specifications provides many features along a robust a flexible control and administration over multicast networks.},
}