Comment 2 for bug 1829449

Is part of the concern here that the ML2 mechanism driver interface doesn't allow for any feedback to be consumed from the mechanism it is controlling? Without special vendor extensions it does seem like third-party drivers may be lacking some of the functionality ML2+OVS (as an example) has in its RPC API. Are you suggesting something akin to an RPC API for third-party mech drivers and controllers to leverage? Just thinking out loud, I also wonder where we draw the line of demarcation with neutron and third-party drivers. This sounds like a potential RFE, I think drilling into the details of what this would look like would help me.