[pim] STD 101, RFC 9777 on Multicast Listener Discovery Version 2 (MLDv2) for IPv6

rfc-editor@rfc-editor.org Fri, 28 March 2025 19:40 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 090EF13ED3D3; Fri, 28 Mar 2025 12:40:01 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id C171C1DF40A; Fri, 28 Mar 2025 12:40:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250328194000.C171C1DF40A@rfcpa.rfc-editor.org>
Date: Fri, 28 Mar 2025 12:40:00 -0700
Message-ID-Hash: 3ZSE3IDNF6O6XYJP65UKXLBOORN7D73G
X-Message-ID-Hash: 3ZSE3IDNF6O6XYJP65UKXLBOORN7D73G
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pim@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [pim] STD 101, RFC 9777 on Multicast Listener Discovery Version 2 (MLDv2) for IPv6
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/oQFo2MGMPMhUW8i3WfQwnf3DoqA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Owner: <mailto:pim-owner@ietf.org>
List-Post: <mailto:pim@ietf.org>
List-Subscribe: <mailto:pim-join@ietf.org>
List-Unsubscribe: <mailto:pim-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        STD 101        
        RFC 9777

        Title:      Multicast Listener Discovery Version 2 (MLDv2)
                    for IPv6 
        Author:     B. Haberman, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2025
        Mailbox:    brian@innovationslab.net
        Pages:      56
        Obsoletes:  RFC 3810
        Updates:    RFC 2710
        See Also:   STD 101

        I-D Tag:    draft-ietf-pim-3810bis-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9777

        DOI:        10.17487/RFC9777

This document specifies the Multicast Listener Discovery version 2
(MLDv2) protocol.  MLD is used by an IPv6 router to discover the
presence of multicast listeners on directly attached links and to
discover which multicast addresses are of interest to those
neighboring nodes.  MLDv2 is designed to be interoperable with MLDv1.
 MLDv2 adds the ability for a node to report interest in listening to
packets with a particular multicast address only from specific source
addresses or from all sources except for specific source addresses.

This document updates RFC 2710 and obsoletes RFC 3810.

This document is a product of the Protocols for IP Multicast Working Group of the IETF.

This is now an Internet Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team