<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pim-zeroconf-mcast-addr-alloc-ps" target="https://datatracker.ietf.org/doc/html/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-03">
   <front>
      <title>Zeroconf Multicast Address Allocation Problem Statement and Requirements</title>
      <author initials="N." surname="Karstens" fullname="Nathan Karstens">
         <organization>Garmin International</organization>
      </author>
      <author initials="D." surname="Farinacci" fullname="Dino Farinacci">
         <organization>lispers.net</organization>
      </author>
      <author initials="M." surname="McBride" fullname="Mike McBride">
         <organization>Futurewei</organization>
      </author>
      <date month="February" day="16" year="2025" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-03" />
   
</reference>
