well My idea would be: display the most restrictive by default. add option to list all. about the code vs readable message I would think of a hybrid approach. apply a code and a message. the code coule be used so the client if it knows it that it could e.g. translate it into different languges etc. and the embedded message copes with all clients that dont know the code yet, also add a code for "other" which can be used for stuff that doesnt have a code yet
2016-03-21 23:51 GMT+01:00 J.C. Jones <jjo...@mozilla.com>: > On Mon, Mar 21, 2016 at 3:45 PM, Niklas Keller <m...@kelunik.com> wrote: > > Will it be possible to standardize all names? Other CAs may use other > rate > > limits. So should `RateLimit-Name` be a code or a human readable message? > > My guess is that getting an exhaustive list of rate limits would be > difficult, and that implementing CAs may want to adjust these values > quickly outside IETF. > > It's probably good to leave flexibility it in, if we can. Further thought: > Instead of or in addition to a name, there could be a URI to a description > or help document. > > Cheers, > > - J.C. >
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
