RFC 4609: Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and Enhancements
In plain English — editorial summary, not part of the RFC
This memo describes security threats for the larger (intra-domain or inter-domain) multicast routing infrastructures. Only Protocol Independent Multicast - Sparse Mode (PIM-SM) is analyzed, in its three main operational modes: the traditional Any-Source Multicast (ASM) model, the source-specific multicast (SSM) model, and the ASM model enhanced by the Embedded Rendezvous Point (Embedded-RP) group-to-RP mapping mechanism. This memo also describes enhancements to the protocol operations that mitigate the identified threats. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4609
- Published
- October 2006
- Authors
- P. Savola; R. Lehtonen; D. Meyer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 8115DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 PrefixesCurrent
March 2017
- RFC 6308Overview of the Internet Multicast Addressing ArchitectureCurrent
June 2011
- RFC 6450Multicast Ping ProtocolCurrent
December 2011
- RFC 7450Automatic Multicast TunnelingUpdated
February 2015
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
- RFC 4570Session Description Protocol (SDP) Source FiltersCurrent
July 2006
- RFC 4258Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON)Current
November 2005
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?