This is an automated email from the git hooks/post-receive script.

dgoulet pushed a commit to branch main in repository torspec.

The following commit(s) were added to refs/heads/main by this push: new ca33a7c DNS timeouts are not causing overload anymore ca33a7c is described below

commit ca33a7ca1ae208d560bc7b03a5b087ef46856b4d Author: Georg Koppen gk@torproject.org AuthorDate: Wed Mar 16 12:48:54 2022 +0000

DNS timeouts are not causing overload anymore

Closes: #81. --- dir-spec.txt | 1 - proposals/328-relay-overload-report.md | 3 ++- 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt index 162ae22..c40023c 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -711,7 +711,6 @@ Table of Contents - Any OOM invocation due to memory pressure - Any ntor onionskins are dropped - TCP port exhaustion - - DNS timeout reached

The timestamp is when at least one metrics was detected. It should always be at the hour and thus, as an example, "2020-01-10 13:00:00" is an diff --git a/proposals/328-relay-overload-report.md b/proposals/328-relay-overload-report.md index e9634ae..e4069b0 100644 --- a/proposals/328-relay-overload-report.md +++ b/proposals/328-relay-overload-report.md @@ -43,6 +43,7 @@ state" which can be one or many of the following load metrics: - Any ntor onionskins are dropped - TCP port exhaustion - DNS timeout reached (X% of timeouts over Y seconds). + [Removed in tor-0.4.7.3-alpha] - CPU utilization of Tor's mainloop CPU core above 90% for 60 sec [Never implemented] - Control port overload (too many messages queued) @@ -73,7 +74,7 @@ this 72 hour period restarts.

The 'version' field is set to '1' for the initial implementation of this proposal which includes all the above overload metrics except from the CPU and -control port overload. +control port overload.

# 1.2. Token bucket size