[or-cvs] r14231: Merge proposal 123 ("Naming authorities automatically create (in tor/trunk: . doc/spec doc/spec/proposals)

[nickm@xxxxxxxx]

Author: nickm
Date: 2008-03-29 01:43:00 -0400 (Sat, 29 Mar 2008)
New Revision: 14231

Modified:
   tor/trunk/
   tor/trunk/doc/spec/dir-spec.txt
   tor/trunk/doc/spec/proposals/000-index.txt
   tor/trunk/doc/spec/proposals/123-autonaming.txt
Log:
 r15023@tombo:  nickm | 2008-03-29 01:18:03 -0400
 Merge proposal 123 ("Naming authorities automatically create bindings") into dir-spec.txt.



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /tor/trunk [r15023] on 49666b30-7950-49c5-bedf-9dc8f3168102

Modified: tor/trunk/doc/spec/dir-spec.txt
===================================================================
--- tor/trunk/doc/spec/dir-spec.txt	2008-03-29 04:27:34 UTC (rev 14230)
+++ tor/trunk/doc/spec/dir-spec.txt	2008-03-29 05:43:00 UTC (rev 14231)
@@ -987,6 +987,19 @@
    binds X to some other Y'.)  A router is called 'Named' if the router
    believes the given name should be bound to the given key.
 
+        Two strategies exist on the current network for deciding on
+        values for the Named flag.  In the original version, server
+        operators were asked to send nickname-identity pairs to a
+        mailing list of Naming directory authorities operators.  The
+        operators were then supposed to add the pairs to their
+        mapping files; in practice, they didn't get to this often.
+
+        Newer Naming authorities run a script that registers routers
+        in their mapping files once the routers have been online at
+        least two weeks, no other router has that nickname, and no
+        other router has wanted the nickname for a month.  If a router
+        has not been online for six months, the router is removed.
+
    "Unnamed" -- Directory authorities that support naming should vote for a
    router to be 'Unnamed' if its given nickname is mapped to a different
    identity.

Modified: tor/trunk/doc/spec/proposals/000-index.txt
===================================================================
--- tor/trunk/doc/spec/proposals/000-index.txt	2008-03-29 04:27:34 UTC (rev 14230)
+++ tor/trunk/doc/spec/proposals/000-index.txt	2008-03-29 05:43:00 UTC (rev 14231)
@@ -45,7 +45,7 @@
 120  Suicide descriptors when Tor servers stop [OPEN]
 121  Hidden Service Authentication [OPEN]
 122  Network status entries need a new Unnamed flag [CLOSED]
-123  Naming authorities automatically create bindings [FINISHED]
+123  Naming authorities automatically create bindings [CLOSED]
 124  Blocking resistant TLS certificate usage [SUPERSEDED]
 125  Behavior for bridge users, bridge relays, and bridge authorities [FINISHED]
 126  Getting GeoIP data and publishing usage summaries [FINISHED]
@@ -81,7 +81,6 @@
  FINISHED:
    105  Version negotiation for the Tor protocol
    111  Prioritizing local traffic over relayed traffic
-   123  Naming authorities automatically create bindings
    125  Behavior for bridge users, bridge relays, and bridge authorities
    126  Getting GeoIP data and publishing usage summaries
    129  Block Insecure Protocols by Default
@@ -98,6 +97,7 @@
    114  Distributed Storage for Tor Hidden Service Descriptors
    119  New PROTOCOLINFO command for controllers
    122  Network status entries need a new Unnamed flag
+   123  Naming authorities automatically create bindings
  SUPERSEDED:
    112  Bring Back Pathlen Coin Weight
    124  Blocking resistant TLS certificate usage

Modified: tor/trunk/doc/spec/proposals/123-autonaming.txt
===================================================================
--- tor/trunk/doc/spec/proposals/123-autonaming.txt	2008-03-29 04:27:34 UTC (rev 14230)
+++ tor/trunk/doc/spec/proposals/123-autonaming.txt	2008-03-29 05:43:00 UTC (rev 14231)
@@ -4,7 +4,7 @@
 Last-Modified: $Date$
 Author: Peter Palfrader
 Created: 2007-10-11
-Status: Finished
+Status: Closed
 
 Overview: