Comment 14 for bug 1470051

In case someone discovers this bug trying to match any protocol with the 'openstack' client (openstackclient), it was not possible to create such a rule but it was recently fixed in Bug #1712242 - you can now specify 'any'

https://bugs.launchpad.net/python-openstackclient/+bug/1712242
https://review.openstack.org/#/c/512113/

Fix was committed Oct 2017, is not in the Pike release so presumably will be in Queens.

Given that the 'neutron' client is deprecated and planned for removal, and there is a function (you can use None, just not 'any') I suspect this bug should probably be closed as WONTFIX since people shouldn't be using the neutron client for new applications, and old applications would want to use the "None" parameter for backwards compatibility.

The 'openstackclient' fix uses any and thus is in line with the original request of this bug (even though it was for neutronclient)