Get Call to get Service Catalog.

Currently keystone has a POST on token /tokens to get the user's token and service catalog.
There are different flavors of the same call, however all of these calls are POST on token.
The operation to get the service catalog is one of the most frequently used operation.Having this operation as a POST prevents us from better using the caching capabilities of http.
My suggestion is to split into two calls
/tokens - POST => This call would just give the token for the user.The token could be for a specific tenant or unscoped.
/access or /catalog - GET => This is the call to retrieve the service catalog and user role related information.
This level of granularity would allow us to scale/serve better for the user who is attempting to get his catalog.
We could also use standard http caching mechanisms to better support the call.