%% 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-12,
    number =    {draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-12},
    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/12/},
    author =    {Nathan Karstens and Dino Farinacci and Mike McBride},
    title =     {{Zeroconf Multicast Address Allocation Problem Statement and Requirements}},
    pagetotal = 11,
    year =      2026,
    month =     feb,
    day =       16,
    abstract =  {This document surveys current problems with existing protocols for automatically assigning multicast IP addresses in zero-configuration ("zeroconf") networking environments. It addresses key challenges, such as link-layer address collisions, hardware limitations, multicast snooping inefficiencies, and the need to avoid manual configuration. Based on these challenges, it derives requirements for a lightweight, decentralized solution for dynamically allocating unique multicast group addresses without central coordination. The document presents explicit requirements covering discovery, allocation, conflict detection and resolution, and lease management. It also evaluates considerations specific to IPv6 and IPv4 multicast address ranges, and identifies approaches that are unsuited for zeroconf deployment. This foundation serves as a reference for developing future solutions for multicast address allocation that operate autonomously within local networks.},
}