RFC 6420: PIM Multi-Topology ID (MT-ID) Join Attribute
In plain English — editorial summary, not part of the RFC
This document introduces a new type of PIM Join Attribute that extends PIM signaling to identify a topology that should be used when constructing a particular multicast distribution tree. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6420
- Published
- November 2011
- Authors
- Y. Cai; H. Ou
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6423Using the Generic Associated Channel Label for Pseudowire in the MPLS Transport Profile (MPLS-TP)Current
November 2011
- RFC 6424Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS TunnelsObsoleted
November 2011
- RFC 6425Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP PingCurrent
November 2011
- RFC 6426MPLS On-Demand Connectivity Verification and Route TracingCurrent
November 2011
- RFC 6427MPLS Fault Management Operations, Administration, and Maintenance (OAM)Updated
November 2011
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
- RFC 6435MPLS Transport Profile Lock Instruct and Loopback FunctionsCurrent
November 2011
- RFC 6439Routing Bridges (RBridges): Appointed ForwardersObsoleted
November 2011
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?