Hi, Hooman: Sorry for the late reply. Thanks for your comments. On the issues you have mentioned, our thoughts are as follows:
1. Looking at this draft, is the objective to signal join/leaves of a Source specific Multicast (SSM) only and not ASM? We were mainly considering SSM for controllable multicast. ASM was not considered in depth at this time. ASM can be extended in this draft in the future. 2. In addition it seems like this only will work for multicast in base routing and not mvpn i.e. I don’t see a route target or is the RD used for VRF identification, can you please verify this? VPN is taken into consideration. RD is available in MSR object and MRI object, while it is not added in FI object. This is an error, we will add RD to FI object in next update. 3. In addition just to understand why would you want to move the overlay from BGP to PCE? First, we want to reduce the impact of BGP updates on multicast signaling by decoupling multicast signaling from BGP. Secondly, SDN is increasingly widely used in network deployment, and the use of PCE can well fit the SDN architecture. Finally, we will also consider BIER-TE processing, path calculation will inevitably use PCE in BIER-TE. Best Regards Huanan Li China Telecom From: Bidgoli, Hooman (Nokia - CA/Ottawa) Date: 2021-07-01 01:03 To: li...@foxmail.com; \pce\"" Subject: RE: [Pce] Fw: New Version Notification for draft-li-pce-based-bier-00.txt Hi All Looking at this draft, is the objective to signal join/leaves of a Source specific Multicast (SSM) only and not ASM? In addition it seems like this only will work for multicast in base routing and not mvpn i.e. I don’t see a route target or is the RD used for VRF identification, can you please verify this? In addition just to understand why would you want to move the overlay from BGP to PCE? Thanks Hooman From: Pce <pce-boun...@ietf.org> On Behalf Of li...@foxmail.com Sent: Tuesday, June 29, 2021 10:33 PM To: "pce" <pce@ietf.org> Subject: [Pce] Fw: New Version Notification for draft-li-pce-based-bier-00.txt Hi PCE experts, At present, the signaling of multicast is mainly distributed processing via BGP messages, and there is no centralized processing solution. We submit a draft of unified management of BIER multicast signaling by controller via PCEP messages, which can combine the characteristics of BIER and improve the efficiency of interaction, as follows: Registration of a multicast source to controller(PCE). Report of joining/leaving message to controller(PCE). Controller(PCE) sends BitStrings indicating the forwarding of packets in BIER network. Any comments are welcome. Best Regards. Huanan Li China Telecom From: internet-drafts Date: 2021-06-29 14:07 To: Aijun Wang; Huaimo Chen; Huaimo Chen; Huanan Li; Ran Chen Subject: New Version Notification for draft-li-pce-based-bier-00.txt A new version of I-D, draft-li-pce-based-bier-00.txt has been successfully submitted by Huanan Li and posted to the IETF repository. Name: draft-li-pce-based-bier Revision: 00 Title: PCE based BIER Procedures and Protocol Extensions Document date: 2021-06-29 Group: Individual Submission Pages: 18 URL: https://www.ietf.org/archive/id/draft-li-pce-based-bier-00.txt Status: https://datatracker.ietf.org/doc/draft-li-pce-based-bier/ Htmlized: https://datatracker.ietf.org/doc/html/draft-li-pce-based-bier Abstract: This document describes extensions to Path Computation Element (PCE) communication Protocol (PCEP) for supporting the PCE based Bit Index Explicit Replication (BIER) deployment. The IETF Secretariat
_______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce