Comment 25 for bug 1460222

Ed, I believe that as proposed, labels cannot bar the incorrect usage by drivers, just as much as binding:profile. Therefore I would be wary of exposing them to tenants, and if we do, then we'd just have to accept the consequences as much as we'd have to if we relaxed access to binding:profile.

How would you plan to ensure that labels are not harmful from the platform standpoint if they are meant to be opaque? There's no safeguard that we can put in place other than writing big warning signs in the Neutron devref, asking developers to be careful. But even if that was acceptable what sort of pitfalls should we warn them of, if the use of labels is pretty much open ended? Have you consider how to solve this problem?

In the end, both profile and labels add metadata to ports for drivers to parse in order to do clever things. Once we have allowed tenant access, everything becomes a gamble and they can both potentially cause 3, and 4, when exposed to low-priv tenants, and 1 and 2 when exposed to the admin. Obviously no-one wants to cause this on purpose, as no-one writes buggy software willingly :O