RFC 7900: Extranet Multicast in BGP/IP MPLS VPNs
In plain English — editorial summary, not part of the RFC
Previous RFCs specify the procedures necessary to allow IP multicast traffic to travel from one site to another within a BGP/MPLS IP VPN (Virtual Private Network). However, it is sometimes desirable to allow multicast traffic whose source is in one VPN to be received by systems that are in another VPN. This is known as a "Multicast VPN (MVPN) extranet". This document updates RFCs 6513, 6514, and 6625 by specifying the procedures that are necessary in order to provide extranet MVPN service.
Document record
- Document ID
- RFC7900
- Published
- June 2016
- Authors
- Y. Rekhter; E. Rosen; R. Aggarwal; Y. Cai; T. Morin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 65
- Also known as
- —
- Updated by:
- RFC 8534
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 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7887Hierarchical Join/Prune AttributesCurrent
June 2016
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 7716Global Table Multicast with BGP Multicast VPN (BGP-MVPN) ProceduresCurrent
December 2015
- RFC 8220Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)Current
September 2017
- RFC 8279Multicast Using Bit Index Explicit Replication (BIER)Current
November 2017
- RFC 8296Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS NetworksCurrent
January 2018
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?