Hello Chenjie, The referenced blueprint for native-l2pop I don’t think helps in this use-case since the extension framework being proposed for l2pop fdb entries is required for the BGP VPN use-case which is directly managing the FDB entries for l2pop. The native-l2pop wants to move the information to the port object and provide custom extensions at that level, but I think this use-case is best served with extensions to the FDB. -Matt From: "Xu, Chenjie" <chenjie.xu@intel.com> Date: Thursday, October 18, 2018 at 10:58 PM To: "Peters, Matt" <Matt.Peters@windriver.com> Cc: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Community Feedbacks for RFE(patch 4ae5a58) for StartlingX upstreaming Hi Matt, For patch 4ae5a58, the RFE “Enable other subprojects to extend l2pop fdb information” has been draft and is under reviewing for now. Community provide some feedbacks and could you please help review and comment！ 1. The link for the RFE is below: https://bugs.launchpad.net/neutron/+bug/1793653 2. The link for the code is below: https://review.openstack.org/#/c/599319/ 3. The link for the BP mentioned by Slawek is below: https://blueprints.launchpad.net/neutron/+spec/native-l2pop 4. The link for the RFE related to the BP is below: https://bugs.launchpad.net/neutron/+bug/1630981 For patch 9f926a5, the RFE “Add l2pop support for floating ip resources” has been draft and is under internal reviewing for now. This RFE depends on the RFE “Enable other subprojects to extend l2pop fdb information” Best Regards, Xu, Chenjie