ATM neutron does allow to configure MTU for networks to reflect underlying infrastructure, but only to operators, and only by changing configuration options.
Ideally, users would be allowed to modify MTU for networks (to simplify matters, on creation only, though we can also look at resource updates) to accommodate for custom workloads relying on specific MTUs. Or maybe sometimes users want to get consistent MTUs across all their networks instead of having different MTUs based on network type backing their networks. Both of those use cases would be served by allowing PUT for 'mtu' network attribute.
I guess it will require a fake extension to signal the change in behavior, even while the implementation may still lay in existing plugin code handling MTUs.
This really sounds reasonable. I received the same request recently in local meetups.
At now, if operators want to allow users to use a big MTU around 8950 bytes in project networks but want to provide users to 1500 bytes by default, the only way is to disable advertise_mtu in DHCP agent config. In addition, there is no way for regular users to specify a default value for their neutron network.
It sounds reasonable to allow regular users to request network MTU as long as it does not exceed the system limit (which equals to neutron config).
One question is how users can know the maximum allowed MTU but I think it is a different topic.