torproject/torspec
1
0
Fork 0
mirror of https://github.com/torproject/torspec.git synced 2024-12-13 21:48:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

r12275@Kushana: nickm | 2007-02-20 13:09:14 -0500

Browse Source 
Note migration plan change for 104 from conversation with arma.


svn:r9605
This commit is contained in:
Nick Mathewson 2007-02-20 23:22:27 +00:00
parent 2ea21adb87
commit 321a4715ca
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
proposals/104-short-descriptors.txt
View File

@ -25,10 +25,11 @@ Proposal:
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
@ -40,6 +41,10 @@ Proposal:
Migration:
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.