Comment 12 for bug 1807697

@Colleen Oh, I assumed the word of 'unbounded' is related to the scope, but it does not at all. After thinking about more Gage's comments, it's not reasonable to add more mutable data because keystone have done it before.

And since the tag's mutable properties (like size) is a lot, now I fully understand adding more mutable data in the auth token is not acceptable. I will close the related reviews.

But last thing, adding client code to fetch project's tag is somewhat unclear for me since I'm not sure where do I have to add the logic. Current implementation from the similar requirements is on demand approach making request when they want to (e.g. validate quota project ID when they have to). I felt fetching tags seems to have a different character since service have to query keystone every time to use as a policy. Could you mind share what you think about it?

Anyway, thank you so much for your reviews of this proposal without any direct need.