%% You should probably cite draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-13 instead of this revision.
@techreport{ietf-pim-zeroconf-mcast-addr-alloc-ps-03,
    number =    {draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-03},
    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-zeroconf-mcast-addr-alloc-ps/03/},
    author =    {Nathan Karstens and Dino Farinacci and Mike McBride},
    title =     {{Zeroconf Multicast Address Allocation Problem Statement and Requirements}},
    pagetotal = 7,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document describes a network that requires unique multicast addresses to distribute data. Various challenges are discussed, such as the use of multicast snooping to ensure efficient use of bandwidth, limitations of switch hardware, problems associated with address collisions, and the need to avoid user configuration. After all limitations were considered it was determined that multicast addresses need to be dynamically-assigned by a decentralized, zero- configuration protocol. Requirements and recommendations for suitable protocols are listed and specific considerations for assigning IPv4 and IPv6 addresses are reviewed. The document closes with several solutions that are precluded from consideration.},
}