Skip to content
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

Identify intended recipient for RateLimit fields #85

Open
ioggstream opened this issue Apr 28, 2022 · 0 comments
Open

Identify intended recipient for RateLimit fields #85

ioggstream opened this issue Apr 28, 2022 · 0 comments
Labels
no-action No changes to the spec

Comments

@ioggstream
Copy link
Collaborator

Discussion

Oblivious Proxy Feedback https://github.com/tireddy2/ohai/blob/main/draft-rdb-ohai-feedback-to-proxy-02.txt relies on this spec to convey service limit information between oblivious resources and oblivious proxy.

The ohai-target parameter identify that the RateLimit fields are intended for the Oblivious proxy: in this case such proxy MUST strip the RateLimit before forwarding the response to the client.

This interesting usage poses some questions, for example:

  1. does the current specification require some tweaks to support similar use cases? Since we just care about syntax and semantics of those fields, it could not be the case but further investigations should be made;
  2. is a general mechanism to identify the intended recipient of the RateLimit fields useful? Is it necessary for the current specification status? Can it be deferred to further specifications?

While no normative changes can be required, it is possible that some editorial adjustments can be useful though. cc: @tireddy2 @unleashed

@ioggstream ioggstream added the no-action No changes to the spec label Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-action No changes to the spec
Projects
None yet
Development

No branches or pull requests

1 participant