Comment 21 for bug 1805920

I think the issue is that removing the tag could be seen as a bug, not a feature, since by removing it, you would be potentially stripping off a priority tag that could be used further up the stack. (For example, if the machine was deployed with a virtual bridge that was capable of manipulating said tags.) That's why most software will now handle the tag, though unfortunately the iPXE in Ubuntu still doesn't.

In other words, failure to remove the tag isn't the bug. The bug is that whether or not to remove the tag should be a configuration choice at some level, and right now that choice is too opaque (or simply doesn't exist). Because as an end node, you shouldn't /need/ to care about the tags. But if you end up deploying a server for use in a software-defined network, you /would/ care about the tags, because you might even have permission to manipulate them.