aboutsummaryrefslogtreecommitdiff
path: root/proposals/126-geoip-reporting.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-03-29 05:43:02 +0000
committerNick Mathewson <nickm@torproject.org>2008-03-29 05:43:02 +0000
commit5c022c7b94a7bbc72b144493c137c0d63d33eaef (patch)
tree0fefb813ee2aecb73c0d764e49d99eb8cf58fed6 /proposals/126-geoip-reporting.txt
parentafa0547fb046bd65698bb45ba195d9d4554d38e4 (diff)
downloadtorspec-5c022c7b94a7bbc72b144493c137c0d63d33eaef.tar.gz
torspec-5c022c7b94a7bbc72b144493c137c0d63d33eaef.zip
r15024@tombo: nickm | 2008-03-29 01:37:09 -0400
Close proposal 126 ("Getting GeoIP data and publishing usage summaries.") It was never completely built, so note which parts wer and which were not. Not-built parts would be good topics for future proposals. svn:r14232
Diffstat (limited to 'proposals/126-geoip-reporting.txt')
-rw-r--r--proposals/126-geoip-reporting.txt19
1 files changed, 18 insertions, 1 deletions
diff --git a/proposals/126-geoip-reporting.txt b/proposals/126-geoip-reporting.txt
index 544f658..880a8b4 100644
--- a/proposals/126-geoip-reporting.txt
+++ b/proposals/126-geoip-reporting.txt
@@ -4,7 +4,13 @@ Version: $Revision$
Last-Modified: $Date$
Author: Roger Dingledine
Created: 2007-11-24
-Status: Finished
+Status: Closed
+
+0. Status
+
+ In 0.2.0.x, this proposal is implemented to the extent needed to
+ address its motivations. See notes below with the test "RESOLUTION"
+ for details.
1. Background and motivation
@@ -114,6 +120,9 @@ Status: Finished
The IP-to-country details are described further in Sections 5 and
6 below.
+ [RESOLUTION: The geoip file in 0.2.0.x is not distributed through
+ Tor. Instead, it is shipped with the bundle.]
+
4.2. The IP-to-city db
In an ideal world, the IP-to-city db would be small enough that we
@@ -140,6 +149,8 @@ Status: Finished
there another reasonable location for it that can provide similar
consensus security properties?
+ [RESOLUTION: IP-to-city is not supported.]
+
4.2.1. Controllers can query for router annotations
Vidalia needs to stop doing queries on bridge relay IP addresses.
@@ -202,6 +213,8 @@ Status: Finished
[XXX Should consider forward/backward compatibility, e.g. if we want
to move to a new geoip file format. -RD]
+ [RESOLUTION: Not done over Tor.]
+
6. Controllers use the IP-to-country db for mapping and for path building
Down the road, Vidalia could use the IP-to-country mappings for placing
@@ -221,6 +234,8 @@ Status: Finished
GETINFO ip-to-country/128.31.0.34
250+ip-to-country/128.31.0.34="US","USA","UNITED STATES"
+ [RESOLUTION: Not done now, except for the getinfo command.]
+
6.1. Other interfaces
Robert Hogan has also suggested a
@@ -230,6 +245,8 @@ Status: Finished
as well as torrc options for ExitCountryCodes, EntryCountryCodes,
ExcludeCountryCodes, etc.
+ [RESOLUTION: Not implemented in 0.2.0.x. Fodder for a future proposal.]
+
7. Relays and bridges use the IP-to-country db for usage summaries
Once bridges have a GeoIP database locally, they can start to publish