[tor-commits] [torspec/master] Add proposal 201: Make bridges report statistics on daily v3 network status requests

[nickm@xxxxxxxxxxxxxx]

commit 25793f4b7b80063ff19a55c4fa8549bf24f0874a
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Thu May 10 11:43:09 2012 -0400

    Add proposal 201: Make bridges report statistics on daily v3 network status requests
---
 proposals/000-index.txt                |    2 +
 proposals/201-bridge-v3-reqs-stats.txt |   38 ++++++++++++++++++++++++++++++++
 2 files changed, 40 insertions(+), 0 deletions(-)

diff --git a/proposals/000-index.txt b/proposals/000-index.txt
index e35ce60..edab8f2 100644
--- a/proposals/000-index.txt
+++ b/proposals/000-index.txt
@@ -121,6 +121,7 @@ Proposals by number:
 198  Restore semantics of TLS ClientHello [OPEN]
 199  Integration of BridgeFinder and BridgeFinderHelper [OPEN]
 200  Adding new, extensible CREATE, EXTEND, and related cells [OPEN]
+201  Make bridges report statistics on daily v3 network status requests [OPEN]
 
 
 Proposals by status:
@@ -161,6 +162,7 @@ Proposals by status:
    198  Restore semantics of TLS ClientHello
    199  Integration of BridgeFinder and BridgeFinderHelper [for 0.2.3.x+]
    200  Adding new, extensible CREATE, EXTEND, and related cells
+   201  Make bridges report statistics on daily v3 network status requests [for 0.2.4.x]
  ACCEPTED:
    117  IPv6 exits [for 0.2.3.x]
    140  Provide diffs between consensuses
diff --git a/proposals/201-bridge-v3-reqs-stats.txt b/proposals/201-bridge-v3-reqs-stats.txt
new file mode 100644
index 0000000..7ac6e56
--- /dev/null
+++ b/proposals/201-bridge-v3-reqs-stats.txt
@@ -0,0 +1,38 @@
+Filename: 201-bridge-v3-reqs-stats.txt
+Title: Make bridges report statistics on daily v3 network status requests
+Author: Karsten Loesing
+Created: 10-May-2012
+Status: Open
+Target: 0.2.4.x
+
+Overview:
+
+  Our current approach [0] to estimate daily bridge users is based on
+  unique IP addresses reported by bridges, and it is very likely broken.
+  A bridge can connect to two or more bridges, so that unique IP address
+  sets overlap to an unknown extent.  We should instead count requests for
+  v3 network statuses, sum them up for all bridges, and divide by the
+  average number of requests that a bridge client makes per day.  This
+  approach is similar to how we estimate directly connecting users.  This
+  proposal describes how bridges would report v3 network status requests
+  in their extra-info descriptors.
+
+Specification:
+
+  Bridges include a new keyword line in their extra-info descriptors that
+  contains the number of v3 network status requests by country they saw
+  over a period of 24 hours.  The reported numbers refer to the period
+  stated in the "bridge-stats-end" line.  The new keyword line would go
+  after the "bridge-ips" line in dir-spec.txt:
+
+  "bridge-v3-reqs" CC=N,CC=N,... NL
+      [At most once.]
+
+      List of mappings from two-letter country codes to the number of
+      requests for v3 network statuses from that country as seen by the
+      bridge, rounded up to the nearest multiple of 8. Only those requests
+      are counted that the directory can answer with a 200 OK status code.
+
+
+[0] https://metrics.torproject.org/papers/countingusers-2010-11-30.pdf
+

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits