RFC 6516: IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join Messages
In plain English — editorial summary, not part of the RFC
The specification for Multicast Virtual Private Networks (MVPNs) contains an option that allows the use of PIM as the control protocol between provider edge routers. It also contains an option that allows UDP-based messages, known as Selective Provider Multicast Service Interface (S-PMSI) Join messages, to be used to bind particular customer multicast flows to particular tunnels through a service provider's network. This document extends the MVPN specification (RFC 6513) so that these options can be used when the customer multicast flows are IPv6 flows. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6516
- Published
- February 2012
- Authors
- Y. Cai; E. Rosen; I. Wijnands
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6515IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNCurrent
February 2012
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 6514BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNsUpdated
February 2012
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 6513Multicast in MPLS/BGP IP VPNsUpdated
February 2012
- RFC 6512Using Multipoint LDP When the Backbone Has No Route to the RootCurrent
February 2012
- RFC 6511Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched PathsCurrent
February 2012
- RFC 6510Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes ObjectsCurrent
February 2012
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?