RFC 9026: Multicast VPN Fast Upstream Failover
In plain English — editorial summary, not part of the RFC
This document defines Multicast Virtual Private Network (VPN) extensions and procedures that allow fast failover for upstream failures by allowing downstream Provider Edges (PEs) to consider the status of Provider-Tunnels (P-tunnels) when selecting the Upstream PE for a VPN multicast flow. The fast failover is enabled by using "Bidirectional Forwarding Detection (BFD) for Multipoint Networks" (RFC 8562) and the new BGP Attribute, BFD Discriminator. Also, this document introduces a new BGP Community, Standby PE, extending BGP Multicast VPN (MVPN) routing so that a C-multicast route can be advertised toward a Standby Upstream PE.
Document record
- Document ID
- RFC9026
- Published
- April 2021
- Authors
- T. Morin; R. Kebler; G. Mirsky
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8971Bidirectional Forwarding Detection (BFD) for Virtual eXtensible Local Area Network (VXLAN)Current
December 2020
- RFC 9186Fast Failover in Protocol Independent Multicast - Sparse Mode (PIM-SM) Using Bidirectional Forwarding Detection (BFD) for Multipoint NetworksCurrent
January 2022
- RFC 9247BGP - Link State (BGP-LS) Extensions for Seamless Bidirectional Forwarding Detection (S-BFD)Current
June 2022
- RFC 8562Bidirectional Forwarding Detection (BFD) for Multipoint NetworksUpdated
April 2019
- RFC 9612Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)Current
July 2024
- RFC 9780Bidirectional Forwarding Detection (BFD) for Multipoint Networks over Point-to-Multipoint MPLS Label Switched Paths (LSPs)Current
May 2025
- RFC 9985Optimizing Bidirectional Forwarding Detection (BFD) AuthenticationCurrent
June 2026
- RFC 7884OSPF Extensions to Advertise Seamless Bidirectional Forwarding Detection (S-BFD) Target DiscriminatorsCurrent
July 2016
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?