Hi Matt,

The RFE “Enable other subprojects to extend l2pop fdb information” was discussed on OpenStack Neutron Driver meetings. The main concern of the community is that this RFE will not be used in the future. For now this RFE got 2 use cases. One is BGPVPN and another is RFE “Add l2pop support for floating ip resources”. The community proposes to do the following things before deciding to approve or not approve RFE “Enable other subprojects to extend l2pop fdb information”:

1) Review the RFE “Add l2pop support for floating ip resources”.

2) Miguel volunteers to facilitate a conversation with the networking-bgpvpn team. The community needs to know whether networking-bgpvpn team will accept to use this RFE to extends l2pop FDB or not.

The link for RFE “Enable other subprojects to extend l2pop fdb information”:

https://bugs.launchpad.net/neutron/+bug/1793653

The link for RFE “Add l2pop support for floating ip resources”:

https://bugs.launchpad.net/neutron/+bug/1803494

The link for the logs of OpenStack Neutron Driver Meeting:

http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-12-07-14.00.log.html

The link for changes in stx-networking-bgpvpn to extend l2pop FDB:

https://github.com/starlingx-staging/stx-networking-bgpvpn/blob/master/networking_bgpvpn/neutron/services/service_drivers/neutron_dynamic_routing/dr.py

Best Regards,

Xu, Chenjie