RFC 4602: Protocol Independent Multicast - Sparse Mode (PIM-SM) IETF Proposed Standard Requirements Analysis
In plain English — editorial summary, not part of the RFC
This document provides supporting documentation to advance the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing protocol from IETF Experimental status to Proposed Standard. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4602
- Published
- August 2006
- Authors
- T. Pusateri
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4601Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)Obsoleted
August 2006
- RFC 4606Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) ControlUpdated
August 2006
- RFC 4607Source-Specific Multicast for IPCurrent
August 2006
- RFC 4610Anycast-RP Using Protocol Independent Multicast (PIM)Current
August 2006
- RFC 4593Generic Threats to Routing ProtocolsCurrent
October 2006
- RFC 4591Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3)Updated
August 2006
- RFC 4618Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS NetworksCurrent
September 2006
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
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?