-
Notifications
You must be signed in to change notification settings - Fork 26
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
Default polling wait time #86
Comments
Might have to broaden the perspective and provide more general guidance on how to avoid/limit DDoS |
I think we need general considerations as well, but this is a specific case where a naive implementation could accidentally DoS the system by polling too quickly. |
yes. Then it's simple, anything around the minute should work. |
Discussed in security considerations https://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-07.html#name-denial-of-service-dos-throu However, still no normative requirement in the polling section so this issue is staying open until that's in. |
Need to add this to the interaction response section. I suggest "SHOULD NOT be less than five seconds" and "omission MUST NOT be treated as zero". |
§5 Continuing a Grant Request: Editor's note:
What's a reasonable amount of time to wait by default so as not to DOS the server if the field is missing?
The text was updated successfully, but these errors were encountered: