[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] we had two section 7.1"s
Update of /home2/or/cvsroot/tor/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/tor/doc
Modified Files:
tor-spec.txt
Log Message:
we had two section 7.1's
Index: tor-spec.txt
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/tor-spec.txt,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -d -r1.85 -r1.86
--- tor-spec.txt 2 May 2005 22:35:18 -0000 1.85
+++ tor-spec.txt 20 May 2005 12:43:55 -0000 1.86
@@ -647,7 +647,7 @@
they would not recognize "keyword ....."; and MUST treat "opt keyword ....."
as synonymous with "keyword ......" when keyword is recognized.
-7.1. Router descriptor format.
+7.2. Router descriptor format.
Every router descriptor MUST start with a "router" Item; MUST end with a
"router-signature" Item and an extra NL; and MUST contain exactly one
@@ -784,7 +784,7 @@
Ports are required; if they are not included in the router
line, they must appear in the "ports" lines.
-7.2. Directory format
+7.3. Directory format
A Directory begins with a "signed-directory" item, followed by one each of
the following, in any order: "recommended-software", "published",
@@ -854,7 +854,7 @@
others. If it encounters an unrecognized keyword in the directory header,
it should reject the entire directory.
-7.3. Network-status descriptor
+7.4. Network-status descriptor
A "network-status" (a.k.a "running-routers") document is a truncated
directory that contains only the current status of a list of nodes, not
@@ -867,17 +867,17 @@
"published" YYYY-MM-DD HH:MM:SS
- (see 7.2 above)
+ (see 7.3 above)
"router-status" list
- (see 7.2 above)
+ (see 7.3 above)
"directory-signature" NL signature
- (see 7.2 above)
+ (see 7.3 above)
-7.4. Behavior of a directory server
+7.5. Behavior of a directory server
lists nodes that are connected currently
speaks HTTP on a socket, spits out directory on request