I initially was thinking something similar in regards to name, but not necessarily for that reason. The main reason I think it'd be good not to is when support for OAuth2 JWT authorization (ie JWT authorization grant type) is added it could be confusing since this wouldn't have anything to do with it since this is just a different way of generating a Bearer token. Also, RSA signing is still cryptography, I'm not a cryptography pro by any means, but signing with the private key then verifying with public key is very much in line with this I would think... furthermore how the token is encoded/decoded is an implementation detail, we could in theory come up with our own implementation (lay aside JWT) and it'd still function as is intended which is to avoid datastore lookups on every authorized call to an OAuth protected API.