RFC 2117: Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2362.
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 describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2117
- Published
- June 1997
- Authors
- D. Estrin; D. Farinacci; A. Helmy; D. Thaler; S. Deering; M. Handley; V. Jacobson; C. Liu; P. Sharma; L. Wei
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 66
- Also known as
- —
- Obsoleted by:
- RFC 2362
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2102Multicast Support for Nimrod : Requirements and Solution ApproachesCurrent
February 1997
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 2092Protocol Analysis for Triggered RIPCurrent
January 1997
- RFC 2091Triggered Extensions to RIP to Support Demand CircuitsCurrent
January 1997
- RFC 2082RIP-2 MD5 AuthenticationObsoleted
January 1997
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2080RIPng for IPv6Current
January 1997
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?