RFC 10019: Zeroconf Multicast Address Allocation Problem Statement and Requirements
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC10019
- Published
- July 2026
- Authors
- N. Karstens; D. Farinacci; M. McBride
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 10018Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint (P2MP) and Ingress ReplicationCurrent
August 2026
- RFC 10028Updates to Dynamic IPv6 Multicast Address Group IDsCurrent
August 2026
- RFC 10005BGP Link Bandwidth Extended CommunityCurrent
June 2026
- RFC 9994MPLS Network Action (MNA) Sub-Stack Specification Including In-Stack Network Actions and DataCurrent
June 2026
- RFC 9992Routing in Fat Trees (RIFT) Key/Value Topology Information Elements Structure and ProcessingCurrent
June 2026
- RFC 9986Meticulous Keyed ISAAC for Bidirectional Forwarding Detection (BFD) Optimized AuthenticationCurrent
June 2026
- RFC 9985Optimizing Bidirectional Forwarding Detection (BFD) AuthenticationCurrent
June 2026
- RFC 9983OSPFv2 Anycast Property AdvertisementCurrent
May 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?