[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r9891: Incorporate ideas from or-dev discussion. (in tor/trunk: . doc/spec/proposals)
- To: or-cvs@xxxxxxxxxxxxx
- Subject: [or-cvs] r9891: Incorporate ideas from or-dev discussion. (in tor/trunk: . doc/spec/proposals)
- From: nickm@xxxxxxxx
- Date: Wed, 21 Mar 2007 00:12:10 -0400 (EDT)
- Delivered-to: email@example.com
- Delivered-to: firstname.lastname@example.org
- Delivered-to: email@example.com
- Delivery-date: Wed, 21 Mar 2007 00:12:25 -0400
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-cvs@xxxxxxxxxxxxx
Date: 2007-03-21 00:12:08 -0400 (Wed, 21 Mar 2007)
New Revision: 9891
r12259@catbus: nickm | 2007-03-21 00:12:02 -0400
Incorporate ideas from or-dev discussion.
Property changes on: tor/trunk
svk:merge ticket from /tor/trunk [r12259] on 8246c3cf-6607-4228-993b-4d95d33730f1
--- tor/trunk/doc/spec/proposals/105-handshake-revision.txt 2007-03-21 03:20:01 UTC (rev 9890)
+++ tor/trunk/doc/spec/proposals/105-handshake-revision.txt 2007-03-21 04:12:08 UTC (rev 9891)
@@ -234,8 +234,39 @@
Discussion: Advertising versions in routerdescs and networkstatuses.
+ In network-statuses:
+ The networkstatus "v" line now has the format:
+ "v" IMPLEMENTATION IMPL-VERSION "Link" LINK-VERSION-LIST
+ Circuit" CIRCUIT-VERSION-LIST NL
+ LINK-VERSION-LIST and CIRCUIT-VERSION-LIST are comma-separated lists of
+ supported version numbers. IMPLEMENTATION is the name of the
+ implementation of the Tor protocol (e.g., "Tor"), and IMPL-VERSION is the
+ version of the implementation.
+ v Tor 0.2.5.1-alpha Link 0,1,2,3 Circuit 0,2,5
+ v OtherOR 2000+ Link 3 Circuit 5
+ Implementations that release independently of the Tor codebase SHOULD NOT
+ use "Tor" as the value of their IMPLEMENTATION.
+ Additional fields on the "v" line MUSTbe ignored.
+ In router descriptors:
+ The router descriptor should contain a line of the form,
+ "protocols" "Link" LINK-VERSION-LIST "Circuit" CIRCUIT_VERSION_LIST
+ Additional fields on the "protocols" line MUST be ignored.
+ [Versions of Tor before 0.1.2.5-alpha rejected router descriptors with
+ unrecognized items; the protocols line should be preceded with an "opt"
+ until these Tors are obsolete.]
Client partitioning is the big danger when we introduce new versions; if a
@@ -244,8 +275,11 @@
version, it will get a disproportionate amount of traffic from clients who
prefer that version. We can mitigate this somewhat as follows:
- - Do not have clients prefer any protocol version by default
- until that version is widespread.
+ - Do not have clients prefer any protocol version by default until that
+ version is widespread. (First introduce the new version to servers,
+ and have clients admit to using it only when configured to do so for
+ testing. Then, once many servers are running the new protocol
+ version, enable its use by default.)
- Do not multiply protocol versions needlessly.