Commit 3424a245 authored by David Goulet's avatar David Goulet 🐼
Browse files

prop328: Mark if finished and update it to latest 



Implemented but not yet merged into main spec.

Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
parent d3165c9a

proposals/000-index.txt

+2 −2
Original line number Diff line number Diff line
@@ -248,7 +248,7 @@ Proposals by number: 
325  Packed relay cells: saving space on small commands [OPEN]

326  The "tor-relay" Well-Known Resource Identifier [OPEN]

327  A First Take at PoW Over Introduction Circuits [DRAFT]

328  Make Relays Report When They Are Overloaded [DRAFT]

328  Make Relays Report When They Are Overloaded [FINISHED]

329  Overcoming Tor's Bottlenecks with Traffic Splitting [DRAFT]

330  Modernizing authority contact entries [OPEN]

331  Res tokens: Anonymous Credentials for Onion Service DoS Resilience [DRAFT]
@@ -267,7 +267,6 @@ Proposals by status: 
   294  TLS 1.3 Migration

   316  FlashFlow: A Secure Speed Test for Tor (Parent Proposal)

   327  A First Take at PoW Over Introduction Circuits

   328  Make Relays Report When They Are Overloaded

   329  Overcoming Tor's Bottlenecks with Traffic Splitting

   331  Res tokens: Anonymous Credentials for Onion Service DoS Resilience

   333  Vanguards lite
@@ -331,6 +330,7 @@ Proposals by status: 
   301  Don't include package fingerprints in consensus documents

   310  Towards load-balancing in Prop 271

   314  Allow Markdown for proposal format

   328  Make Relays Report When They Are Overloaded

 CLOSED:

   101  Voting on the Tor Directory System [in 0.2.0.x]

   102  Dropping "opt" from the directory format [in 0.2.0.x]

proposals/328-relay-overload-report.md

+5 −5
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ Filename: 328-relay-overload-report.md 
Title: Make Relays Report When They Are Overloaded

Author: David Goulet, Mike Perry

Created: November 3rd 2020

Status: Draft

Status: Finished

```



# 0. Introduction
@@ -25,8 +25,8 @@ possibly misbehaving or under DDoS attack. 
We propose that relays start collecting several metrics (see section 2)

reflecting their loads from different component of tor.



Then, we propose that 3 new lines be added to the extra-info document (see

dir-spec.txt, section 2.1.2) if only the overload case arises.

Then, we propose that 3 new lines be added to the server descriptor document

(see dir-spec.txt, section 2.1.1) if only the overload case arises.



The following describes a series of metrics to collect but more might come in

the future and thus this is not an exhaustive list.
@@ -43,8 +43,8 @@ state" which can be one or many of the following load metrics: 
   - CPU utilization of Tor's mainloop CPU core above 90% for 60 sec

   - Control port overload (too many messages queued)



The format of the overloaded line added in the extra-info document is as

follows:

The format of the overloaded line added in the server descriptor document is

as follows:



```

"overload-general" SP version SP YYYY-MM-DD HH:MM:SS NL

proposals/BY_INDEX.md

+1 −1
Original line number Diff line number Diff line
@@ -245,7 +245,7 @@ Below are a list of proposals sorted by their proposal number. See 
* [`325-packed-relay-cells.md`](/proposals/325-packed-relay-cells.md): Packed relay cells: saving space on small commands [OPEN]

* [`326-tor-relay-well-known-uri-rfc8615.md`](/proposals/326-tor-relay-well-known-uri-rfc8615.md): The "tor-relay" Well-Known Resource Identifier [OPEN]

* [`327-pow-over-intro.txt`](/proposals/327-pow-over-intro.txt): A First Take at PoW Over Introduction Circuits [DRAFT]

* [`328-relay-overload-report.md`](/proposals/328-relay-overload-report.md): Make Relays Report When They Are Overloaded [DRAFT]

* [`328-relay-overload-report.md`](/proposals/328-relay-overload-report.md): Make Relays Report When They Are Overloaded [FINISHED]

* [`329-traffic-splitting.txt`](/proposals/329-traffic-splitting.txt): Overcoming Tor's Bottlenecks with Traffic Splitting [DRAFT]

* [`330-authority-contact.md`](/proposals/330-authority-contact.md): Modernizing authority contact entries [OPEN]

* [`331-res-tokens-for-anti-dos.md`](/proposals/331-res-tokens-for-anti-dos.md): Res tokens: Anonymous Credentials for Onion Service DoS Resilience [DRAFT]

proposals/README.md

+1 −1
Original line number Diff line number Diff line
@@ -75,6 +75,7 @@ themselves still need to be merged into the specifications proper. 
* [`301-dont-vote-on-package-fingerprints.txt`](/proposals/301-dont-vote-on-package-fingerprints.txt): Don't include package fingerprints in consensus documents

* [`310-bandaid-on-guard-selection.txt`](/proposals/310-bandaid-on-guard-selection.txt): Towards load-balancing in Prop 271

* [`314-allow-markdown-proposals.md`](/proposals/314-allow-markdown-proposals.md): Allow Markdown for proposal format

* [`328-relay-overload-report.md`](/proposals/328-relay-overload-report.md): Make Relays Report When They Are Overloaded





## META proposals: about the proposal process
@@ -112,7 +113,6 @@ discussion. 
* [`294-tls-1.3.txt`](/proposals/294-tls-1.3.txt): TLS 1.3 Migration

* [`316-flashflow.md`](/proposals/316-flashflow.md): FlashFlow: A Secure Speed Test for Tor (Parent Proposal)

* [`327-pow-over-intro.txt`](/proposals/327-pow-over-intro.txt): A First Take at PoW Over Introduction Circuits

* [`328-relay-overload-report.md`](/proposals/328-relay-overload-report.md): Make Relays Report When They Are Overloaded

* [`329-traffic-splitting.txt`](/proposals/329-traffic-splitting.txt): Overcoming Tor's Bottlenecks with Traffic Splitting

* [`331-res-tokens-for-anti-dos.md`](/proposals/331-res-tokens-for-anti-dos.md): Res tokens: Anonymous Credentials for Onion Service DoS Resilience

* [`333-vanguards-lite.md`](/proposals/333-vanguards-lite.md): Vanguards lite