diff options
author | Nick Mathewson <nickm@torproject.org> | 2008-03-29 05:43:02 +0000 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2008-03-29 05:43:02 +0000 |
commit | 2b1c9d548909a9f54b95c8759c3111f59de11e72 (patch) | |
tree | d27e39a7fff5fe8da170f87c5f82055c564f96fd /doc/spec/dir-spec.txt | |
parent | fd4cff8a6582c8c2bd45710c8542d19f7b57ebde (diff) | |
download | tor-2b1c9d548909a9f54b95c8759c3111f59de11e72.tar.gz tor-2b1c9d548909a9f54b95c8759c3111f59de11e72.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 'doc/spec/dir-spec.txt')
-rw-r--r-- | doc/spec/dir-spec.txt | 24 |
1 files changed, 20 insertions, 4 deletions
diff --git a/doc/spec/dir-spec.txt b/doc/spec/dir-spec.txt index 8e2ddece15..4e482bae00 100644 --- a/doc/spec/dir-spec.txt +++ b/doc/spec/dir-spec.txt @@ -599,6 +599,21 @@ $Id$ As documented in 2.1 above. See migration notes in section 2.2.1. + "geoip-start" YYYY-MM-DD HH:MM:SS NL + "geoip-client-origins" CC=N,CC=N,... NL + + Only generated by bridge routers (see blocking.pdf), and only + when they have been configured with a geoip database. + Non-bridges SHOULD NOT generate these fields. Contains a list + of mappings from two-letter country codes (CC) to the number + of clients that have connected to that bridge from that + country (approximate, and rounded to the nearest multiple of 8 + in order to hamper traffic analysis). A country is included + only if it has at least 8 addresses, and only if the bridge + has seen at least 16 addresses total. The time in + "geoip-start" is the time at which we began collecting geoip + statistics. + "router-signature" NL Signature NL [At end, exactly once.] @@ -613,10 +628,11 @@ $Id$ tools SHOULD accept history values from both sources; if they appear in both documents, the values in the extra-info documents are authoritative. - At some future time, to save space, new versions of Tor will no longer - generate router descriptors containing read-history or write-history. - Tools should continue to accept read-history and write-history values - in router descriptors produced by older versions of Tor. + New versions of Tor no longer generate router descriptors + containing read-history or write-history. Tools should continue to + accept read-history and write-history values in router descriptors + produced by older versions of Tor until all Tor versions earlier + than 0.2.0.x are obsolete. 2.3. Nonterminals in router descriptors |