RFC 9081: Interoperation between Multicast Virtual Private Network (MVPN) and Multicast Source Directory Protocol (MSDP) Source-Active Routes
In plain English — editorial summary, not part of the RFC
This document specifies the procedures for interoperation between Multicast Virtual Private Network (MVPN) Source-Active (SA) routes and customer Multicast Source Discovery Protocol (MSDP) SA routes, which is useful for MVPN provider networks offering services to customers with an existing MSDP infrastructure. Without the procedures described in this document, VPN-specific MSDP sessions are required among the Provider Edge (PE) routers that are customer MSDP peers. This document updates RFC 6514.
Document record
- Document ID
- RFC9081
- Published
- July 2021
- Authors
- Z. Zhang; L. Giuliano
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 6514
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9079Source-Specific Routing in the Babel Routing ProtocolCurrent
August 2021
- RFC 9084OSPF Prefix Originator ExtensionsCurrent
August 2021
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 9086Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer EngineeringCurrent
August 2021
- RFC 9087Segment Routing Centralized BGP Egress Peer EngineeringCurrent
August 2021
- RFC 9088Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-ISCurrent
August 2021
- RFC 9089Signaling Entropy Label Capability and Entropy Readable Label Depth Using OSPFCurrent
August 2021
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
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?