(If this should go to the switching forum just holler.)
This question concerns the basic premise for architecting a large-scale MVPN deployment with multiple VRF's per sub-organization within a very large enterprise. The MPLS PE-P architecture is already in place and managed by an independent group not unlike a service provider environment.
Organizations are beginning to request multicast application support, for the most part geographically isolated but in some cases the traffic would reach across the enterprise. MVPN seems like the proper solution.
The details of the configuration don't are not a big concern as long as I understand the philosophy for implementation.
Question(s): Is the idea that you create a VRF dedicated to multicast resources for a given group or organization or client, and then you use the MPLS MVPN infrastructure knobs to pass that dedicated VRF-based multicast resource, (using RD imports and exports just as with MPLS VRF traffic) in to other user VRF's that want to join and receive the multicast?
The other approach I was imagining was that the multicast source was added within an existing user data VRF, imported and exported but then filtered with policy-routing (access-lists) so that if desired, only the multicast traffic, (and not the user traffic that is also present in that VRF) could be mixed with other desired VRF's?
Which of these two theories of distribution are in the "spirit" of a best-practice MVPN architecture? If I am completely off, what is this 3rd theory?