Implement binding-level rate limiting

[gnarea]

To prevent abuse, we should rate-limit the operations from Internet clients. Most of the limits will be tied to the IP address of the client, and it is assumed that multiple private gateways can be behind the same IP address.

The following limits should be implemented, with the concrete parameters defined via configuration by the operator:

• Number of HTTP requests per IP address across all bindings.
  • X requests per IP address per second.
  • Y requests per IP address per minute.
  • Z requests per IP address per hour.
• PoWeb binding:
  • Number of private gateway registrations (global).
    • Y registrations per minute.
    • Z registrations per hour.
  • Number of private gateway registrations per IP address.
    • X registrations per IP address per minute.
    • Y registrations per IP address per hour.
    • Z registrations per IP address per day.
  • Number of parcel deliveries per IP address.
    • X deliveries per IP address per second.
    • Y deliveries per IP address per minute.
    • X deliveries per IP address per second.
  • Number of parcel collection requests per IP address. This boils down to: How many private gateways do we want to allow per IP address?
    • X requests per IP address per minute.
• PoHTTP binding:
  • Number of parcel deliveries per IP address.
    • X deliveries per IP address per second.
    • Y deliveries per IP address per minute.
    • Z deliveries per IP address per hour.
• CogRPC binding:
  • Number of cargo collection calls per IP address.
    • X calls per IP address per second.
    • Y calls per IP address per minute.
    • Z calls per IP address per hour.
  • Number of cargo delivery calls per IP address.
    • X calls per IP address per minute.

System and software stack

Use rate-limiter-flexible with a Redis backend.

Related issues

• Implement messaging-level rate limiting #19
• Add support for Delivery Authorisation rate limiting #20