[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r9605: Note migration plan change for 104 from conversation with ar (in tor/trunk: . doc/spec/proposals)
- To: or-cvs@xxxxxxxxxxxxx
- Subject: [or-cvs] r9605: Note migration plan change for 104 from conversation with ar (in tor/trunk: . doc/spec/proposals)
- From: nickm@xxxxxxxx
- Date: Tue, 20 Feb 2007 18:22:28 -0500 (EST)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Tue, 20 Feb 2007 18:22:37 -0500
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-cvs@xxxxxxxxxxxxx
Author: nickm
Date: 2007-02-20 18:22:27 -0500 (Tue, 20 Feb 2007)
New Revision: 9605
Modified:
tor/trunk/
tor/trunk/doc/spec/proposals/104-short-descriptors.txt
Log:
r12275@Kushana: nickm | 2007-02-20 13:09:14 -0500
Note migration plan change for 104 from conversation with arma.
Property changes on: tor/trunk
___________________________________________________________________
svk:merge ticket from /tor/trunk [r11844] on 8246c3cf-6607-4228-993b-4d95d33730f1
svk:merge ticket from /tor/trunk [r12275] on c95137ef-5f19-0410-b913-86e773d04f59
Modified: tor/trunk/doc/spec/proposals/104-short-descriptors.txt
===================================================================
--- tor/trunk/doc/spec/proposals/104-short-descriptors.txt 2007-02-20 22:25:20 UTC (rev 9604)
+++ tor/trunk/doc/spec/proposals/104-short-descriptors.txt 2007-02-20 23:22:27 UTC (rev 9605)
@@ -25,10 +25,11 @@
One possible solution here is that routers should generate and upload a
short-form and long-form descriptor. Only the short-form descriptor should
ever be used by anybody for routing. The long-form descriptor should be
- used only for analytics and other tools. (If we allowed people to route with
- long descriptors, we'd have to ensure that they stayed in sync with the
- short ones somehow.) We can ensure that the short descriptors are used by
- only recommending those in the network statuses.
+ used only for analytics and other tools. (If we allowed people to route
+ with long descriptors, we'd have to ensure that they stayed in sync with
+ the short ones somehow. So let's not do that.) We can ensure that the
+ short descriptors are used by only recommending those in the network
+ statuses.
Another possible solution would be to drop these fields from descriptors,
and have them uploaded as a part of a separate "bandwidth report" to the
@@ -41,6 +42,10 @@
For long/short descriptors:
* In 0.1.2.x:
+ * Add a "long version" URL that tools can start using now. Need to
+ design it first.
+
+ * In 0.1.2.x:
* Authorities should accept both, now, and silently drop short
descriptors.
* Routers should upload both once authorities accept them.