Comment 6 for bug 1784879

It all boils down to granularity indeed. Port-level is the most granular of course.
On the other hand, coarse-grained approaches such as network or subnet maybe provide better UX for common use cases; if one only wants to expose a port in a network maybe this is already covered by the floating IP approach.

It is also possible to devise a mechanism where the attribute could be set at different levels of granularity. That would bring in additional complexity (both for implementation and usage). Personally at this time I would not consider a scenario where more granular settings can override base settings.

Thinking about subnets vs networks, maybe the subnet is a better choice as it will allow for uniquely identifying the IP that should be registered for a host.

One last point would be about floating IPs registered in designate: should a distinct host name be used for internal IPs?