Since this discussion has implication on similar features in routers and agents, I'd to offer my opinion (uninformed as it might be):
Routers, networks (private, external, or shared), and agents provide bottle-necks allowing admins to shut down connectivity, the same way as, in the real world, a network-admin might shut down a switch or a router for temporary maintenance and bring it back up.
During shut-down the implied and expected result is that all traffic via bottle neck is broken.
So I believe that this feature is necessary and shouldn't be deprecated. Also, that all affected ports (VMs, floating ips, dhcp, etc...) should reflect this state in their status.
Since this discussion has implication on similar features in routers and agents, I'd to offer my opinion (uninformed as it might be):
Routers, networks (private, external, or shared), and agents provide bottle-necks allowing admins to shut down connectivity, the same way as, in the real world, a network-admin might shut down a switch or a router for temporary maintenance and bring it back up.
During shut-down the implied and expected result is that all traffic via bottle neck is broken.
So I believe that this feature is necessary and shouldn't be deprecated. Also, that all affected ports (VMs, floating ips, dhcp, etc...) should reflect this state in their status.