New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit
parameter registry
#49
Comments
I assume there must be previous art in keeping a registry like this that we can mimic, but I can't think of a good example off the top of my head that wouldn't be using a separate registry or document to manage that. What's your thinking about where to keep this registry? |
@unleashed registries are usually maintained by IANA: we can check with @richsalz if that's possible... |
We can pretty easily define a registry. You include a section in the RFC. See https://www.rfc-editor.org/rfc/rfc5226. You define a table that is the registry, and meanings of the columns, and perhaps populate it with the initial entries. The WG decides some rules, like "X-" is left for experimentation. There must be something written (it can be an internet draft or something else on the net), whether a set of "experts" need to review for comliance and clarity, and so on. |
If you'd like, I can make a PR that provides the initial text for this next week. |
Yes, that would be great @richsalz! |
Can you give me an initial set of fields (even if it's just one or two), and an example, and a pointer to which section in the current draft? thanks. |
Hi @richsalz Thanks for your support! WRT the parameter registry: currently the initial set is just
Do you have a proposal for the registration policy? |
Thanks, I'll wait.
I think it should be expert review. That means that there should be a document describing the parameter, and that the experts can be directed to verify that the documentation is clear and unambiguous, and that there is no significant overlap with the parameters already defined. The other choices are "specification required" and "first-come first-served." |
@richsalz we just merged structured fields in RateLimit Headers! |
Thanks for the ping, I saw :) I'll propose a PR soon. |
#60 |
I wish
Since parameters are always allowed in Limit we could define a "registry" and add them subsequently as soon as implementers needs them.
They can be used to specify:
All data in parameters is informative.
The text was updated successfully, but these errors were encountered: