RFC 6517: Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN Solution
In plain English — editorial summary, not part of the RFC
More that one set of mechanisms to support multicast in a layer 3 BGP/MPLS VPN has been defined. These are presented in the documents that define them as optional building blocks. To enable interoperability between implementations, this document defines a subset of features that is considered mandatory for a multicast BGP/MPLS VPN implementation. This will help implementers and deployers understand which L3VPN multicast requirements are best satisfied by each option. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6517
- Published
- February 2012
- Authors
- T. Morin; B. Niven-Jenkins; Y. Kamite; R. Zhang; N. Leymann; N. Bitar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6348Requirements for Point-to-Multipoint Extensions to the Label Distribution ProtocolCurrent
September 2011
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 7611BGP ACCEPT_OWN Community AttributeCurrent
August 2015
- RFC 6565OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing ProtocolCurrent
June 2012
- RFC 7438Multipoint LDP (mLDP) In-Band Signaling with WildcardsCurrent
January 2015
- RFC 5561LDP CapabilitiesCurrent
July 2009
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?