Enterprise and SP requirements have evolved significantly in last couple of years. With surge in video, collaboration, content-delivery based applications and geographically dispersed sites, expectations to interact with minimal cost and maximum efficiency has gained tremendous momentum. Multicast VPN (MVPN) is proven model to achieve this without incurring extra capex and opex.
Cisco’s first version of MVPN solution was introduced in the early 2000th. It primarily targeted VPN services for enterprises and focused on stability by leveraging proven IP multicast transport with GRE encapsulation. Across core PIM signaling model was used that relied on a LAN-like signaling construct (the Default-MDT or I-PMSI) and optional optimized trees (Data-MDT or S-PMSI). This model is well deployed in different market segments and popularly known as Rosen-model.
Recent enhancements to the MVPN solution introduced new options of “multicast label switch paths” using mLDP and P2MP-RSVP-TE (extensions of LDP and RSVP-TE respectively) to create a consistent forwarding and OAM infrastructure for unicast and multicast streams in the MPLS cloud. BGP was introduced for signaling of I-PMSI and S-PMSI, unifying the control plane operations with IP unicast routing. In-band signaling and Partition model were introduced to support more efficient tree building across MPLS/VPN cores.
Overall these recent enhancements and legacy support are collectively termed as NG-MVPN solution space which provides users the luxury to choose out of supported profiles to suit their requirements