[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] Add and document router-status line using new unified liven...
- To: or-cvs@freehaven.net
- Subject: [or-cvs] Add and document router-status line using new unified liven...
- From: nickm@seul.org (Nick Mathewson)
- Date: Tue, 26 Oct 2004 20:48:53 -0400 (EDT)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Tue, 26 Oct 2004 20:49:23 -0400
- Reply-to: or-dev@freehaven.net
- Sender: owner-or-cvs@freehaven.net
Update of /home/or/cvsroot/doc
In directory moria.mit.edu:/tmp/cvs-serv16114/doc
Modified Files:
tor-spec.txt
Log Message:
Add and document router-status line using new unified liveness/verifiedness format; continue to generate running-routers; continue to parse running-routers when no router-status line is found
Index: tor-spec.txt
===================================================================
RCS file: /home/or/cvsroot/doc/tor-spec.txt,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -d -r1.66 -r1.67
--- tor-spec.txt 20 Oct 2004 18:39:05 -0000 1.66
+++ tor-spec.txt 27 Oct 2004 00:48:51 -0000 1.67
@@ -706,7 +706,7 @@
A Directory begins with a "signed-directory" item, followed by one each of
the following, in any order: "recommended-software", "published",
-"running-routers". It may include any number of "opt" items. After these
+"router-status". It may include any number of "opt" items. After these
items, a directory includes any number of router descriptors, and a single
"directory-signature" item.
@@ -723,7 +723,7 @@
A list of which versions of which implementations are currently
believed to be secure and compatible with the network.
- "running-routers" comma-separated-list
+ "running-routers" space-separated-list
A description of which routers are currently believed to be up or
down. Every entry consists of an optional "!", followed by either an
@@ -733,8 +733,30 @@
If a router's nickname is given, exactly one router of that nickname
will appear in the directory, and that router is "approved" by the
directory server. If a hashed identity key is given, that OR is not
- "approved".
+ "approved". [XXXX The 'running-routers' line is only provided for
+ backward compatibility. New code should parse 'router-status'
+ instead.]
+
+ "router-status" space-separated-list
+
+ A description of which routers are currently believed to be up or
+ down, and which are verified or unverified. Contains one entry for
+ every router that the directory server knows. Each entry is of the
+ format:
+ !name=$digest [Verified router, currently not live.]
+ name=$digest [Verified router, currently live.]
+ !$digest [Unverified router, currently not live.]
+ or $digest [Unverified router, currently live.]
+
+ (where 'name' is the router's nickname and 'digest' is a hexadecimal
+ encoding of the hash of the routers' identity key).
+
+ When parsing this line, clients should only mark a router as
+ 'verified' if its nickname AND digest match the one provided.
+ [XXXX 'router-status' was added in 0.0.9pre5; older directory code
+ uses 'running-routers' instead.]
+
"directory-signature" nickname-of-dirserver NL Signature
Note: The router descriptor for the directory server MUST appear first.
@@ -763,7 +785,7 @@
(see 7.2 above)
- "running-routers" list
+ "router-status" list
(see 7.2 above)