Comment 2 for bug 1208639

Oops: I meant "Conversely, when a V3 server requires a domain token". You're quite right that a V2 server doesn't have a concept of domains. I hope that makes more sense now.

In turn, you seem to have a typo of your own :-) I agree that "a domain-scoped token is a completely discrete concept from a project-scoped token", but I'm suggesting that a domain-scoped token has the same use-cases as a token scoped to _no_ project.

It seems to me we're breaking compatibility here when we don't have to, given what looks to me like an easy alternative (an unscoped token = a domain token).

What is the point of a distinction between an unscoped and a domain token in V3, given that it's almost impossible to get an unscoped token in V3? I know that they're described as different things, but _why_ are they different, given the huge cost.