Shorter names 🚲🏠

[martinthomson]

GET /.well-known/http-message-signatures-directory HTTP/1.1
Host: example.com
Accept: application/http-message-signatures-directory+json

Both the /.well-known/ resource and the content type are very, very, very long strings. Is there a shorter, more evocative name you can use?

For the resource, "botkeys" or "agentkeys" perhaps.

For the content type, isn't this just "application/jwks+json"?

[thibmeu]

I agree the path and media type could be shorter, even if they are not unreasonably long.

These names are what is deployed today. Migration is likely feasible, but there would be a cost for little gain.
If we were to move, I'd favor botkeys (even if i'm not a fan of bot in this context, names are hard). maybe webbotauth-keys to be more descriptive.
Also worth noting that this path is not on Signature-agent, so that's does not make a difference in term of bytes there.

For the media type, the registered one is application/jwk-set+json. The profile for the directory restrict permitted alg, and kid (with a JWK thumbprint). That might not be sufficient to warrant a content type, and the well-known could impose constraint by itself, similar to how it recommends the response to be signed.

These seems to be decision the group would made after adoption though.

[sandormajor]

Since #132 the path is part of the Signature-Agent so +1 to making it shorter.

I'm also wondering if we should include a version in the media type or somewhere else to tell which version of the protocol people are using. There were a few breaking changes in the protocol so it could be good to know who's using what version.