Last Call: <draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07.txt> (Zeroconf Multicast Address Allocation Problem Statement and Requirements) to Informational RFC
The IESG <iesg-secretary@ietf.org> Fri, 03 October 2025 13:37 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from [10.244.8.182] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id C9F326CE25B8; Fri, 3 Oct 2025 06:37:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07.txt> (Zeroconf Multicast Address Allocation Problem Statement and Requirements) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 12.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <175949867976.3085053.15585015642705203458@dt-datatracker-6c6cdf7f94-h6rnn>
Date: Fri, 03 Oct 2025 06:37:59 -0700
Message-ID-Hash: 6QBZSDECZTLYLYFFETTX4H2TOILVCJAB
X-Message-ID-Hash: 6QBZSDECZTLYLYFFETTX4H2TOILVCJAB
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps@ietf.org, gunter@vandevelde.cc, pim-chairs@ietf.org, pim@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: last-call@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lh5G4cYFv7TDByl8UEwmqbVbQbQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The IESG has received a request from the Protocols for IP Multicast WG (pim) to consider the following document: - 'Zeroconf Multicast Address Allocation Problem Statement and Requirements' <draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07.txt> as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2025-10-17. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps/ No IPR declarations have been submitted directly on this I-D.