[or-cvs] r15261: Minor cleanups. (projects/hidserv/trunk/doc)

[kloesing@xxxxxxxx]

Author: kloesing
Date: 2008-06-14 17:28:50 -0400 (Sat, 14 Jun 2008)
New Revision: 15261

Modified:
   projects/hidserv/trunk/doc/report.pdf
   projects/hidserv/trunk/doc/report.tex
Log:
Minor cleanups.

Modified: projects/hidserv/trunk/doc/report.pdf
===================================================================
(Binary files differ)

Modified: projects/hidserv/trunk/doc/report.tex
===================================================================
--- projects/hidserv/trunk/doc/report.tex	2008-06-14 21:03:51 UTC (rev 15260)
+++ projects/hidserv/trunk/doc/report.tex	2008-06-14 21:28:50 UTC (rev 15261)
@@ -238,7 +238,7 @@
 %% public Tor relays for circuit building to make the scenario more realistic in 
 %% terms of latency, compared to measurements in a private local area network.
 
-To measure the multiple substeps necessary to access a hidden service,
+In order to measure the multiple substeps necessary to access a hidden service,
 including message transfer times, a second
 measurement environment is set up. Tor clients generate log statements during
 runtime, which are used to gain insight, when certain internal events occur.
@@ -246,7 +246,7 @@
 process of connection establishment are set up especially for the measurements.
 This includes the two roles mentioned in the first measurement environment, a
 client-side Tor process and a server-side Tor process, providing the hidden 
-service. In addition two more Tor processes are started on the same machine,
+service. In addition to that, two more Tor processes are started on the same machine,
 acting as introduction point and rendezvous point. All other Tor relays involved
 in the process, constituting the circuits between the above-mentioned roles, are 
 selected from the global Tor network during runtime using the regular Tor 
@@ -294,9 +294,11 @@
 
 \paragraph{Open Rendezvous Circuit}
 
-This is not the actual time to open the rendezvous circuit, but the time until
+In the next step the client opens a circuit to a rendezvous point. More
+precisely, it is not the actual time to open the rendezvous circuit that is
+measured here, but the time until
 a usable circuit is open after receiving the rendezvous descriptor. If there
-is a problem with the first rendezvous circuit and a second one must be openend,
+is a problem with the first rendezvous circuit and a second one must be opened,
 both together constitute this value.
 
 The rendezvous circuit is usually open immediately, because an existing 3-hop
@@ -313,7 +315,8 @@
 
 \paragraph{Open Introduction Circuit}
 
-This is also not necessarily the opening time of a single circuit, but may
+The time to open an introduction circuit is also not necessarily equal to
+the opening time of a single circuit, but may
 consist of multiple attempts, if the chosen 3-hop circuit cannot be built, 
 or if it cannot be extended to the introduction point.
 
@@ -324,26 +327,25 @@
   introcirc is open
 \end{verbatim}
 
-
 \paragraph{Rendezvous Establishment}
 
 The ESTABLISH\_RENDEZVOUS cell is sent from the client to the rendezvous point 
-to deliver the rendezvous cookie. While the the first statement occurs in the 
+to deliver the rendezvous cookie. While the first statement occurs in the 
 client log 
 file the second appears in the rendezvous point log file.
 
 \begin{verbatim}
-Apr 23 20:21:37.906 [info] rend_client_send_establish_rendezvous(): 
-  Sending an ESTABLISH_RENDEZVOUS cell
+Apr 23 20:21:37.906 [info]
+  rend_client_send_establish_rendezvous(): Sending an
+  ESTABLISH_RENDEZVOUS cell
 Apr 23 20:21:38.494 [notice] 
   Received an ESTABLISH_RENDEZVOUS request on circuit 3307
 \end{verbatim}
 
-
 \paragraph{Rendezvous Acknowledgment}
 
 The rendezvous point acknowledges with a RENDEZVOUS\_ESTABLISHED cell, that
-is sent immediately after receiving the ESTABLISH\_RENDEZVOUS cell, therefore
+is sent immediately after receiving the ESTABLISH\_RENDEZVOUS cell. Therefore
 the latter is used as starting time for this value.
 
 \begin{verbatim}
@@ -353,13 +355,13 @@
   Got rendezvous ack. This circuit is now ready for rendezvous.
 \end{verbatim}
 
-
 \paragraph{Contacting Introduction Point }
 
-After the rendezvous point is established and has acknowledged, the introduction
+After the rendezvous circuit is established and the router has acknowledged
+to act as rendezvous point, the introduction
 point can be contacted. To do so an INTRODUCE1 cell is sent down the 
 introduction circuit. Again the two following statements occur in the log
-files of two processes. The first in the client's log and the second in the
+files of two processes, the first in the client's log and the second in the
 log file of the introduction point.
 
 \begin{verbatim}
@@ -369,11 +371,10 @@
   Received an INTRODUCE1 request on circuit 49661
 \end{verbatim}
 
-
 \paragraph{Forwarding The Request To The Hidden Service}
 
 The introduction point forwards the client request to the hidden service relay,
-immediately after receiving the latter. It uses the circuit that was built 
+immediately after receiving it. The introduction point uses the circuit that was built 
 during establishing the hidden service.
 
 \begin{verbatim}
@@ -386,7 +387,7 @@
 
 \paragraph{Introduction Acknowledgment}
 
-After successfully forwarding of the request to the hidden service, the 
+After successfully forwarding the introduction request to the hidden service, the 
 introduction point acknowledges this back to the client with an INTRODUCE\_ACK 
 cell.
 
@@ -397,13 +398,12 @@
   Received ack. Telling rend circ...
 \end{verbatim}
 
+\paragraph{Open Rendezvous Circuit on Server-side}
 
-\paragraph{Open Rendezvous Circuit on Server-side }
-
 In the INTRODUCE2 cell the hidden server finds the contact information of 
 the rendezvous point, together with the rendezvous cookie. Then it extends
-a circuit to the rendezvous point. The same applies, what was said about the
-circuits on client-side. This value needs not to be constituted by a single
+a circuit to the rendezvous point. Again, the time to open the rendezvous
+circuit on server-side does not need to be constituted by a single
 circuit extension or build attempt.
 
 \begin{verbatim}
@@ -416,7 +416,6 @@
   for service xpw5lcjsag7u6l6w
 \end{verbatim}
 
-
 \paragraph{Rendezvous Confirmation}
 
 After building the circuit to the rendezvous point, a RENDEZVOUS1 cell is sent
@@ -427,10 +426,10 @@
   Done building circuit 64529 to rendezvous with cookie 4815A117 
   for service xpw5lcjsag7u6l6w
 Apr 23 20:21:45.680 [notice] 
-  Got request for rendezvous from circuit 26085 to cookie 4815A117.
+  Got request for rendezvous from circuit 26085 to cookie
+  4815A117.
 \end{verbatim}
 
-
 \paragraph{Forwarding The Confirmation To The Client}
 
 The rendezvous point forwards the content of the RENDEZVOUS1 cell immediately
@@ -441,13 +440,12 @@
 
 \begin{verbatim}
 Apr 23 20:21:45.680 [notice] 
-  Got request for rendezvous from circuit 26085 to cookie 4815A117.
+  Got request for rendezvous from circuit 26085 to cookie
+  4815A117.
 Apr 23 20:21:46.791 [info] rend_client_receive_rendezvous(): 
   Got RENDEZVOUS2 cell from hidden service.
 \end{verbatim}
 
-
-
 \section{Results}
 
 The \emph{external view} measurements were performed between June 1, 2:50pm