The IESG has approved the following document: - 'Zeroconf Multicast Address Allocation Problem Statement and Requirements' (draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-13.txt) as Informational RFC
This document is the product of the Protocols for IP Multicast Working Group. The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan Talaulikar. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps/ Technical Summary This document defines the problem space and associated requirements for automatically assigning multicast addresses in zero-configuration ("zeroconf") networking environments. It addresses key challenges, such as 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 protocol capable of 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 multicast address allocation protocols that operate autonomously within local networks. Working Group Summary Was there anything in the WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? No controversy at all, among the people interested in this topic there appears to be good support. Document Quality Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type, or other Expert Review, what was its course (briefly)? In the case of a Media Type Review, on what date was the request posted? This is an informational document. A problem statement. There are several protocols being developed based on this document Personnel The Document Shepherd for this document is Stig Venaas. The Responsible Area Director is Gunter Van de Velde. IANA Note no requirements for IANA on this informational track document _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
