aboutsummaryrefslogtreecommitdiff
path: root/issues/add-rate-limit-support.md
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus@mullvad.net>2022-03-30 22:45:46 +0200
committerRasmus Dahlberg <rasmus@mullvad.net>2022-03-30 22:45:46 +0200
commitb09d20111227be5e6d5126ec905b44a7a4e96b0d (patch)
tree955fc6be7fb1e364a1d51bcca89080ea0cfa46bc /issues/add-rate-limit-support.md
parent146cd30b9eb17dd3fa5c49c844c6045d62e54a7c (diff)
move issues to a common pad
Diffstat (limited to 'issues/add-rate-limit-support.md')
-rw-r--r--issues/add-rate-limit-support.md16
1 files changed, 0 insertions, 16 deletions
diff --git a/issues/add-rate-limit-support.md b/issues/add-rate-limit-support.md
deleted file mode 100644
index 167199d..0000000
--- a/issues/add-rate-limit-support.md
+++ /dev/null
@@ -1,16 +0,0 @@
-**Title:** Add rate limit support </br>
-**Date:** 2021-12-09 </br>
-
-# Summary
-Add support for rate-limiting add-leaf requests via second-level domain name.
-
-# Description
-A sigsum log requires a submitter to prove that a domain name is aware of their
-public verification key. Rate limits can then be applied per second-level
-domain name. Trillian has built-in rate-limiting using a so-called quota
-manager; gRPC calls include an arbitrary `charge_to` string that is used as an
-identifier with regards to who should be charged for the request.
-
-First investigate whether Trillian's built-in rate limiting can be used and with
-which assumptions. For example, is `etcd` a required process? Then implement
-and document how an operator can configure sigsum-log-go with rate limits.