i originally had it that way  but then passing any unexpected query string arguments would throw a typeerror as not all methods use kwargs  one could argue that we should disallow unexpected arguments  but keystoneclient is already passing a  fresh  param  stupid cache busting artifact from original cloud servers client i am inclined to leave it like this unless you are compelled to do otherwise 