Abstract
RFC 6513 and RFC 6514 define NG-MVPN procedures in which PEs use BGP MCAST-VPN routes (e.g., RT-1 I-PMSI A-D) to auto-discover participation and to bind multicast delivery to a provider tunnel (P-tunnel) identified by the PMSI Tunnel attribute (Tunnel Type plus identifiers/labels). In practice, a single PMSI binding typically forces a single transport choice across all leaves (e.g., mLDP P2MP for core-efficient replication or ingress replication for simplified edge requirements), limiting mixed-capability deployments. This document describes techniques that allow heterogeneous P-tunnel transports within one NG-MVPN instance by having an ingress PE concurrently support multiple tunnel types and admit egress PEs with different transport capabilities or preferences. In example embodiments, mLDP-capable leaves join an mLDP P2MP tree, while non-mLDP leaves signal an ingress-replication endpoint/label; the ingress PE forwards on the mLDP tree for one subset and performs ingress replication to the other. The approach generalizes to additional tunnel types and supports incremental migration to newer P2MP transports, including Segment Routing based mechanisms, with minimal service disruption.
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.
Recommended Citation
Anonymous, "Hybrid Multicast Transport Support", Technical Disclosure Commons, ()
https://www.tdcommons.org/dpubs_series/9060