Hi Gyan, Now your question and this discussion is really about RFC 6514. As specified in RFC 6514 (section 14 & 13) and mentioned in this draft, there are two ways to support ASM over MVPN. One way is to have a PE (its VRF to be exact) as a C-RP or with an MSDP session to an off-site C-RP is one way (section 14). Its purpose is to avoid establishing (*,g) tree (and subsequent rpt/spt switch) over the provider network, not to provide value-added service. That's why RFC has section title as "14. Supporting PIM-SM without Inter-Site Shared C-Trees". That has one missing feature when the customer also has its own MSDP infrastructure to distribute source information among its MSDP speakers, and that's what this draft is about. What you describe below about how ASM is done is the other way (Section "13. Switching from a Shared C-Tree to a Source C-Tree" in RFC 6514). Thanks. Jeffrey -----Original Message----- From: Gyan Mishra <hayabusagsm@xxxxxxxxx> Sent: Friday, May 7, 2021 12:55 PM To: Jeffrey (Zhaohui) Zhang <zzhang=40juniper.net@xxxxxxxxxxxxxx> Cc: Lenny Giuliano <lenny@xxxxxxxxxxx>; Qin Wu <bill.wu@xxxxxxxxxx>; bess <bess@xxxxxxxx>; draft-ietf-bess-mvpn-msdp-sa-interoperation.all <draft-ietf-bess-mvpn-msdp-sa-interoperation.all@xxxxxxxx>; last-call <last-call@xxxxxxxx>; ops-dir <ops-dir@xxxxxxxx> Subject: Re: [bess] Opsdir last call review of draft-ietf-bess-mvpn-msdp-sa-interoperation-05 [External Email. Be cautious of content] Hi Jeffrey I read the draft and saw your comments that RFC 6514 mentions MSDP on the PE. In what use case would SP have to run Anycast RP / MSDP on the PE when that ASM control plane function can all be done on the CE. I guess there maybe customers looking for value added service to have the SP provide that function and in that case is where this draft would come into play for SPT feature to make it work. My understanding of the shared tree over MVPN using MVPN RFC 6513, 6514 procedures is as follows: ASM 1. Egress receiver PE sends Type 6 shared tree (c-*,c-g) is sent towards the RP PE. 2. The join received by RP behind PE triggers a type 7 source tree join (c-s,c-g) towards the source ingress PE. 3. Ingress PE sends Type-5 source active to trigger SPT switchover back to the RP PE and all PEs on the S-PMSI selective tree. 4. Egress receiver PEs now sends Type-7 (c-s,c-g) to the source PE 5. Multicast stream now flows over the selective tree S-PMSI from Ingress Source PE to all egress receiver PEs. SSM 1. Egress receiver PEs now sends Type-7 (c-s,c-g) to the source PE 2. Multicast stream now flows over the selective tree S-PMSI from Ingress Source PE to all egress receiver PEs. Kind Regards Gyan On Thu, May 6, 2021 at 3:27 PM Jeffrey (Zhaohui) Zhang <zzhang= 40juniper.net@xxxxxxxxxxxxxx> wrote: > Hi Qin, > > > > Thank you so much for the review and comments. I have posted -06 revision Juniper Business Use Only -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
