Another way to look at different flavors/profiles of MVPN is to consider the following two aspects:
1. How are C-multicast state (customer (s,g)/(*,g) or mLDP FEC signaled on PC-CE interfaces) are signaled over provider core 2. How are C-multicast traffic transported through the provider core For #1, you have the choice of PIM (Rosen/PIM-MVPN and its later variants), BGP (BGP-MVPN), and mLDP (mLDP inband signaling). For #2, your provider tunnel choice can be PIM ASM/SSM, RSVP-TE/mLDP P2MP, Ingress Replication, BIER, … and more could be defined (e.g. SR P2MP). The two aspects together will give you many combinations and they’re referred to as different “profiles” of MVPN by a certain vendor (😊) but I personally find it easier to look at those two aspects (e.g. “BGP-MVPN with mLDP tunnel”) 😊 BTW the same applies to EVPN BUM as well. Jeffrey From: BESS <bess-boun...@ietf.org> On Behalf Of Gyan Mishra Sent: Saturday, September 28, 2019 2:06 PM To: Gyan Mishra <hayabusa...@gmail.com>; bess@ietf.org Subject: Re: [bess] RFC or Draft that lists all standards track rfc’s of all mvpn profiles I did some research and theseare the main RFCs for MVPN and how based they map to CISCO profiles and you do the same for Juniper and Huawei. The 1st two are for mLDP w/ BGP-AD pim (in band) or bgp (out of band)c-signaling UI-PMSI (uni directional inclusive provider multicast service instance) Cisco Default MDT for PIM SM or SSM MI-PMSI (multi directional provider multicast service instance) CISCO Default MDT for PIM SM or SSM S-PMSI (Selective Provider multicast service instance) CISCO Data MDT for PIM SM or SSM PIM dense mode MVPN not supported - I don’t think anyone uses dense these days https://tools.ietf.org/html/rfc6513<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc6513__;!8WoA6RjC81c!XrBWTOGj5DVLcAKHFynu0Xz-drszhVTpNKy34DkjXA0ilBykj5ljx0DKdQEKZP27$> MVPN https://tools.ietf.org/html/rfc6514<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc6514__;!8WoA6RjC81c!XrBWTOGj5DVLcAKHFynu0Xz-drszhVTpNKy34DkjXA0ilBykj5ljx0DKdbmRB91B$> MVPN https://tools.ietf.org/html/rfc6037<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc6037__;!8WoA6RjC81c!XrBWTOGj5DVLcAKHFynu0Xz-drszhVTpNKy34DkjXA0ilBykj5ljx0DKdUliuPcJ$>. Rosen PIM GRE https://tools.ietf.org/html/rfc4875<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc4875__;!8WoA6RjC81c!XrBWTOGj5DVLcAKHFynu0Xz-drszhVTpNKy34DkjXA0ilBykj5ljx0DKdQeNDgRo$> P2MP TE Sent from my iPhone On Sep 28, 2019, at 11:58 AM, Gyan Mishra <hayabusa...@gmail.com<mailto:hayabusa...@gmail.com>> wrote: BESS WG / All I am trying to find a list of all MVPN profiles that are supported by Cisco and Juniper and Huawei SP router vendors. Below link shows what CISCO supports most of which I believe are a CISCO proprietary and non standard so won’t work between vendors. https://www.cisco.com/c/en/us/support/docs/ip/multicast/200512-Configure-mVPN-Profiles-within-Cisco-IOS.html<https://urldefense.com/v3/__https:/www.cisco.com/c/en/us/support/docs/ip/multicast/200512-Configure-mVPN-Profiles-within-Cisco-IOS.html__;!8WoA6RjC81c!XrBWTOGj5DVLcAKHFynu0Xz-drszhVTpNKy34DkjXA0ilBykj5ljx0DKdZzUn3UQ$> Thank you Gyan Mishra Verizon Communications Cell 301 502-1347 Sent from my iPhone
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
