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

Augmenting replacement signals with reporting mechanisms #30

Open
philippp opened this issue Mar 28, 2022 · 1 comment
Open

Augmenting replacement signals with reporting mechanisms #30

philippp opened this issue Mar 28, 2022 · 1 comment

Comments

@philippp
Copy link

The current draft proposal lists signals that may compensate for some IP attributes (e.g. loss of longitudinal stability). In addition to providing signals from the proxy to internet-facing services, have we thought about patterns and mechanisms through which services could report abusive connections back to the proxy?

Ideally, this would allow the proxy to curtail the access of specific users, as opposed to having multi-tenant IP addresses blocked by the service under attack. The OHAI proposal (https://datatracker.ietf.org/doc/html/draft-rdb-ohai-feedback-to-proxy) is one such attempt to provide a path for feedback, and may be extensible to two-hop proxies and off-line reporting of abuse.

Should such mechanisms be considered in scope, in addition to signals emitted from the proxy?

@sysrqb
Copy link
Collaborator

sysrqb commented Aug 16, 2023

This could be useful feature if it's designed well, but it certainly requires additional research and development. The OHAI proposal is an interesting example, but I don't believe it's currently being used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants