[pim] RFC 9466 on PIM Assert Message Packing
rfc-editor@rfc-editor.org Fri, 13 October 2023 23:25 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF50FC14CF0D; Fri, 13 Oct 2023 16:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.467
X-Spam-Level:
X-Spam-Status: No, score=-4.467 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hqohXfaKfyIp; Fri, 13 Oct 2023 16:25:55 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA79DC14F738; Fri, 13 Oct 2023 16:25:07 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 86C3E13BB4C3; Fri, 13 Oct 2023 16:25:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pim@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231013232507.86C3E13BB4C3@rfcpa.amsl.com>
Date: Fri, 13 Oct 2023 16:25:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/rjaIQIbeec3-jmcwnDOcgL3X1Sk>
Subject: [pim] RFC 9466 on PIM Assert Message Packing
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2023 23:25:58 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9466
Title: PIM Assert Message Packing
Author: Y. Liu, Ed.,
T. Eckert, Ed.,
M. McBride,
Z. Zhang
Status: Standards Track
Stream: IETF
Date: October 2023
Mailbox: liuyisong@chinamobile.com,
tte@cs.fau.de,
michael.mcbride@futurewei.com,
zhang.zheng@zte.com.cn
Pages: 20
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pim-assert-packing-12.txt
URL: https://www.rfc-editor.org/info/rfc9466
DOI: 10.17487/RFC9466
When PIM Sparse Mode (PIM-SM), including PIM Source-Specific
Multicast (PIM-SSM), is used in shared LAN networks, there is often
more than one upstream router. This can lead to duplicate IP
multicast packets being forwarded by these PIM routers. PIM Assert
messages are used to elect a single forwarder for each IP multicast
traffic flow between these routers.
This document defines a mechanism to send and receive information for
multiple IP multicast flows in a single PackedAssert message. This
optimization reduces the total number of PIM packets on the LAN and
can therefore speed up the election of the single forwarder, reducing
the number of duplicate IP multicast packets incurred.
This document is a product of the Protocols for IP Multicast Working Group of the IETF.
This is now a Proposed 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
Association Management Solutions, LLC
- [pim] RFC 9466 on PIM Assert Message Packing rfc-editor