metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4601: Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7761.

Current document in this lineage: RFC 5059 — Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM); RFC 7761 — Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)

In plain English — editorial summary, not part of the RFC

This document specifies Protocol Independent Multicast - Sparse Mode (PIM-SM). PIM-SM is a multicast routing protocol that can use the underlying unicast routing information base or a separate multicast-capable routing information base. It builds unidirectional shared trees rooted at a Rendezvous Point (RP) per group, and optionally creates shortest-path trees per source. This document obsoletes RFC 2362, an Experimental version of PIM-SM. [STANDARDS-TRACK]

Document record

Document ID
RFC4601
Published
August 2006
Authors
B. Fenner; M. Handley; H. Holbrook; I. Kouvelas
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
150
Also known as
—
Obsoletes:
RFC 2362
Obsoleted by:
RFC 7761
Updated by:
RFC 5059, RFC 5796, RFC 6226

Topics

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 2117 (1997)
  2. RFC 2362 (1998)
  3. RFC 4601 (2006)
  4. RFC 5059 (2008)
  5. RFC 7761 (2016) ✓

Read the full history of Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised) →

Referenced by

4 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4601-protocol-independent-multicast-sparse-mode-pim-sm-protocol-specification-revised