RFC 5384: The Protocol Independent Multicast (PIM) Join Attribute Format
In plain English — editorial summary, not part of the RFC
A "Protocol Independent Multicast - Sparse Mode" Join message sent by a given node identifies one or more multicast distribution trees that that node wishes to join. Each tree is identified by the combination of a multicast group address and a source address (where the source address is possibly a "wild card"). Under certain conditions it can be useful, when joining a tree, to specify additional information related to the construction of the tree. However, there has been no way to do so until now. This document describes a modification of the Join message that allows a node to associate attributes with a particular tree. The attributes are encoded in Type-Length-Value format. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5384
- Published
- November 2008
- Authors
- A. Boers; I. Wijnands; E. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 7887
Topics
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 5060Protocol Independent Multicast MIBCurrent
January 2008
- RFC 5796Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local MessagesCurrent
March 2010
- RFC 4601Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)Obsoleted
August 2006
- RFC 3618Multicast Source Discovery Protocol (MSDP)Current
October 2003
- RFC 2362Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol SpecificationObsoleted
June 1998
- RFC 9186Fast Failover in Protocol Independent Multicast - Sparse Mode (PIM-SM) Using Bidirectional Forwarding Detection (BFD) for Multipoint NetworksCurrent
January 2022
- RFC 4611Multicast Source Discovery Protocol (MSDP) Deployment ScenariosCurrent
August 2006
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
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?