Unified rate limiting system

[teadur]

We need to come up with a solution to make unified query rate limiting system.
Current rate limiting system forces the application to one machine and is far from ideal for ipv6.

Every registrar has a set limit x of allowed queries.
Every request to EPP or REPP should go to one token bucket.
Rate limiting should be configurable per registrar if needed ( disable or amount )
Rate limiting system should emit metrics about query load globally and per registrar,
failed and completed queries.

The rate, query and session limiting should be done on application level instead of FW level like its done now.

[teadur]

#983 defines that we should support prefixes

[artur-intech]

#813

[teadur]

#813

I think it doesn't make sense to cover whois/rwhois in same issue because it's different app/interface.
But deciding what we do with sessions remains open question.

[artur-intech]

#813 also affects EPP. It's worth creating separate tickets for EPP limits and the rest stuff.

[teadur]

The problem is that EPP/REPP should have combined limit so it kind of makes sense to implement them together.

[artur-intech]

My point was that those two tickets duplicate each other, at least partly. Correct me if I am wrong.

[teadur]

Yep a bit, but as of the new ticket already has more information i would close the older one if any.
The real question here is how we are going to solve the problem.

[yulgolem]

Implemented by https://github.com/yulgolem/shunter , gem needs to be transfered to internetee repo.
Gem lacks documentation & integration with registry.
On hold until 25-06-2021.

[vohmar]

covered by https://github.com/yulgolem/shunter