aboutsummaryrefslogtreecommitdiff
path: root/issues/add-rate-limit-support.md
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus@mullvad.net>2021-12-09 11:14:31 +0100
committerRasmus Dahlberg <rasmus@mullvad.net>2021-12-09 11:14:31 +0100
commit89f0a41e8baefddf2c6962a8f0eee71dfd124d21 (patch)
tree85d7723d8e66225d9fe02304b0bac4c9f00c8eac /issues/add-rate-limit-support.md
parente74021bee14cdc6a5aa22ddc2068c2f72dfe277f (diff)
added issues
Diffstat (limited to 'issues/add-rate-limit-support.md')
-rw-r--r--issues/add-rate-limit-support.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/issues/add-rate-limit-support.md b/issues/add-rate-limit-support.md
new file mode 100644
index 0000000..167199d
--- /dev/null
+++ b/issues/add-rate-limit-support.md
@@ -0,0 +1,16 @@
+**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.