RFC 6515: IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPN
In plain English — editorial summary, not part of the RFC
To provide Multicast VPN (MVPN) service, Provider Edge routers originate BGP Update messages that carry Multicast-VPN ("MCAST-VPN") BGP routes; they also originate unicast VPN routes that carry MVPN-specific attributes. These routes encode addresses from the customer's address space, as well as addresses from the provider's address space. These two address spaces are independent, and the address family (IPv4 or IPv6) of the two spaces may or may not be the same. These routes always contain an "address family" field that specifies whether the customer addresses are IPv4 addresses or whether they are IPv6 addresses. However, there is no field that explicitly specifies the address family of the provider addresses. To ensure interoperability, this document specifies that provider IPv4 addresses are always encoded in these update messages as 4-octet addresses, and that the distinction between IPv4 and IPv6 is signaled solely by the length of the address field. Specific cases are explained in detail. This document updates RFC 6514. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6515
- Published
- February 2012
- Authors
- R. Aggarwal; E. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 6514
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6625Wildcards in Multicast VPN Auto-Discovery RoutesUpdated
May 2012
- RFC 7740Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress ReplicationCurrent
January 2016
- RFC 8502L2L3 VPN Multicast MIBCurrent
December 2018
- RFC 8503BGP/MPLS Layer 3 VPN Multicast Management Information BaseCurrent
December 2018
- RFC 8950Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next HopCurrent
November 2020
- RFC 6516IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join MessagesCurrent
February 2012
- RFC 6513Multicast in MPLS/BGP IP VPNsUpdated
February 2012
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
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?