[or-cvs] r17544: {tor} summarize proposal 111 in tor-spec (in tor/trunk/doc/spec: . proposals)

[arma at seul.org]

Author: arma
Date: 2008-12-09 18:30:50 -0500 (Tue, 09 Dec 2008)
New Revision: 17544

Modified:
   tor/trunk/doc/spec/proposals/000-index.txt
   tor/trunk/doc/spec/proposals/111-local-traffic-priority.txt
   tor/trunk/doc/spec/tor-spec.txt
Log:
summarize proposal 111 in tor-spec


Modified: tor/trunk/doc/spec/proposals/000-index.txt
===================================================================
--- tor/trunk/doc/spec/proposals/000-index.txt	2008-12-09 23:26:12 UTC (rev 17543)
+++ tor/trunk/doc/spec/proposals/000-index.txt	2008-12-09 23:30:50 UTC (rev 17544)
@@ -33,7 +33,7 @@
 108  Base "Stable" Flag on Mean Time Between Failures [CLOSED]
 109  No more than one server per IP address [CLOSED]
 110  Avoiding infinite length circuits [ACCEPTED]
-111  Prioritizing local traffic over relayed traffic [FINISHED]
+111  Prioritizing local traffic over relayed traffic [CLOSED]
 112  Bring Back Pathlen Coin Weight [SUPERSEDED]
 113  Simplifying directory authority administration [SUPERSEDED]
 114  Distributed Storage for Tor Hidden Service Descriptors [CLOSED]
@@ -114,7 +114,6 @@
    098  Proposals that should be written
    099  Miscellaneous proposals
  FINISHED:
-   111  Prioritizing local traffic over relayed traffic [in 0.2.0.x]
    121  Hidden Service Authentication [in 0.2.1.x]
    128  Families of private bridges [in 0.2.0.x]
    155  Four Improvements of Hidden Service Performance [in 0.2.1.x]
@@ -128,6 +127,7 @@
    107  Uptime Sanity Checking [in 0.2.0.x]
    108  Base "Stable" Flag on Mean Time Between Failures [in 0.2.0.x]
    109  No more than one server per IP address [in 0.2.0.x]
+   111  Prioritizing local traffic over relayed traffic [in 0.2.0.x]
    114  Distributed Storage for Tor Hidden Service Descriptors [in 0.2.0.x]
    119  New PROTOCOLINFO command for controllers [in 0.2.0.x]
    122  Network status entries need a new Unnamed flag [in 0.2.0.x]

Modified: tor/trunk/doc/spec/proposals/111-local-traffic-priority.txt
===================================================================
--- tor/trunk/doc/spec/proposals/111-local-traffic-priority.txt	2008-12-09 23:26:12 UTC (rev 17543)
+++ tor/trunk/doc/spec/proposals/111-local-traffic-priority.txt	2008-12-09 23:30:50 UTC (rev 17544)
@@ -4,7 +4,7 @@
 Last-Modified: $Date$
 Author: Roger Dingledine
 Created: 14-Mar-2007
-Status: Finished
+Status: Closed
 Implemented-In: 0.2.0.x
 
 Overview:

Modified: tor/trunk/doc/spec/tor-spec.txt
===================================================================
--- tor/trunk/doc/spec/tor-spec.txt	2008-12-09 23:26:12 UTC (rev 17543)
+++ tor/trunk/doc/spec/tor-spec.txt	2008-12-09 23:30:50 UTC (rev 17544)
@@ -885,12 +885,26 @@
 
 7.1. Link throttling
 
-   Each node should do appropriate bandwidth throttling to keep its
-   user happy.
+   Each client or relay should do appropriate bandwidth throttling to
+   keep its user happy.
 
    Communicants rely on TCP's default flow control to push back when they
    stop reading.
 
+   The mainline Tor implementation uses token buckets (one for reads,
+   one for writes) for the rate limiting.
+
+   Since 0.2.0.x, Tor has let the user specify an additional pair of
+   token buckets for "relayed" traffic, so people can deploy a Tor relay
+   with strict rate limiting, but also use the same Tor as a client. To
+   avoid partitioning concerns we combine both classes of traffic over a
+   given OR connection, and keep track of the last time we read or wrote
+   a high-priority (non-relayed) cell. If it's been less than N seconds
+   (currently N=30), we give the whole connection high priority, else we
+   give the whole connection low priority. We also give low priority
+   to reads and writes for connections that are serving directory
+   information. See proposal 111 for details.
+
 7.2. Link padding
 
    Link padding can be created by sending PADDING cells along the
@@ -942,7 +956,6 @@
    cells when both a) the window is <= 450, and b) there are less than
    ten cell payloads remaining to be flushed at that edge.
 
-
 A.1. Differences between spec and implementation
 
 - The current specification requires all ORs to have IPv4 addresses, but