Comment 5 for bug 1811352

Yeah, this fits OSC and OpenStack SDK repositories.

Related to this, there is a thing to be discussed. OSC transition guideline in the neutronclient contributor guide [1] categorizes networking commands into several groups ("Core", "Extension" and "Others"). "Core" is defined as "network resources that provide core neutron project features (e.g. network, subnet, port, etc.)" and "Extension" is defined as "advanced features in the neutron project (e.g. trunk, etc.) or advanced services in separate projects (FWaaS, LBaaS, VPNaaS, dynamic routing, etc.)". This means features in "neutron" repo spread "Core" (OSC repo) and "Extension" (OSC plugin in neutronclient repo). This is confusing. My idea is to implement all features in "neutron" repo into OSC (and OpenStack SDK).

[1] "Where does my CLI belong?" in https://docs.openstack.org/python-neutronclient/latest/contributor/transition_to_osc.html#developer-guide