point out two parts where the spec is wrong

svn:r2569

diff --git a/doc/tor-doc.html b/doc/tor-doc.html
index 7ee816e1bf3caba92191d0106d0377e2cf3271d7..bdf8a429ea14f1ca8785899510b2353737c42ff2 100644 (file)
--- a/doc/tor-doc.html
+++ b/doc/tor-doc.html
@@ -105,7 +105,7 @@ anybody but yourself.</p>
 
 <p>If you have less than 1Mbit in both directions, you should stay
 a client. Otherwise, please consider being a server, to help out the
-network. (Currently each server uses 20-30 gigabytes of traffic
+network. (Currently each server uses 20-150 gigabytes of traffic
 per month; but that may go up.)</p>
 
 <p>Note that you can be a server without allowing users to make

diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index fde7e0e5a609b1bce2a4c87ab9167edd484e814c..1718eab8e94d392aa5ccff4350b2fd96e07c7358 100644 (file)
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -72,6 +72,7 @@ TODO: (very soon)
    support any suite without ephemeral keys, symmetric keys of at
    least 128 bits, and digests of at least 160 bits.
 
+[what kind of cert does an OP send? -RD]
    An OR always sends a two-certificate chain, consisting of a self-signed
    certificate containing the OR's identity key, and a second certificate
    using a short-term connection key.  The commonName of the second
@@ -95,6 +96,7 @@ TODO: (very soon)
    OR-to-OR connections are never deliberately closed.  When an OR
    starts or receives a new directory, it tries to open new
    connections to any OR it is not already connected to.
+[not true, unused OR conns close after 5 mins too -RD]
 
    OR-to-OP connections are not permanent. An OP should close a
    connection to an OR if there are no circuits running over the