[tor-bugs] #25296 [Core Tor/Tor]: update PerConnBWRate/Burst manpage entries to not mention consensus

[Tor Bug Tracker & Wiki]

#25296: update PerConnBWRate/Burst manpage entries to not mention consensus
-------------------------------------------------+-------------------------
 Reporter:  cypherpunks                          |          Owner:  (none)
     Type:  defect                               |         Status:
                                                 |  merge_ready
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.4.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Minor                                |     Resolution:
 Keywords:  tor-doc, 032-backport, 033-backport  |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):

 * status:  needs_review => merge_ready
 * keywords:  tor-doc => tor-doc, 032-backport, 033-backport


Comment:

 This patch seems fine to me, marking for backport to 0.3.3 and 0.3.2,
 because this documentation has confused at least one relay operator.

 > but it would be better to add more information that says if tor has some
 built-in mechanism to avoid that a single client uses all bw

 Tor has a circuit scheduler that tries to allocate bandwidth to low-volume
 circuits.

 > Also: How does tor tell non-relays from relays apart?

 Relays authenticate, clients and bridges do not.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25296#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online