metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 7582: Multicast Virtual Private Network (MVPN): Using Bidirectional P-Tunnels

Still current, but amended. Parts of this document are changed or extended by RFC 8534, RFC 9573. Read both.

In plain English — editorial summary, not part of the RFC

A set of prior RFCs specify procedures for supporting multicast in BGP/MPLS IP VPNs. These procedures allow customer multicast data to travel across a service provider's backbone network through a set of multicast tunnels. The tunnels are advertised in certain BGP multicast auto-discovery routes, by means of a BGP attribute known as the "Provider Multicast Service Interface (PMSI) Tunnel" attribute. Encodings have been defined that allow the PMSI Tunnel attribute to identify bidirectional (multipoint-to-multipoint) multicast distribution trees. However, the prior RFCs do not provide all the necessary procedures for using bidirectional tunnels to support multicast VPNs. This document updates RFCs 6513, 6514, and 6625 by specifying those procedures. In particular, it specifies the procedures for assigning customer multicast flows (unidirectional or bidirectional) to specific bidirectional tunnels in the provider backbone, for advertising such assignments, and for determining which flows have been assigned to which tunnels.

Document record

Document ID
RFC7582
Published
July 2015
Authors
E. Rosen; IJ. Wijnands; Y. Cai; A. Boers
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
34
Also known as
—
Updates:
RFC 6513, RFC 6514, RFC 6625
Updated by:
RFC 8534, RFC 9573

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/7582-multicast-virtual-private-network-mvpn-using-bidirectional-p-tunnels