From 01b5ee3a4a36e58a1e35bdddb27e250162c2f7ba Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Tue, 20 Feb 2007 23:22:27 +0000 Subject: [PATCH] r12275@Kushana: nickm | 2007-02-20 13:09:14 -0500 Note migration plan change for 104 from conversation with arma. svn:r9605 --- doc/spec/proposals/104-short-descriptors.txt | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/doc/spec/proposals/104-short-descriptors.txt b/doc/spec/proposals/104-short-descriptors.txt index c003a091e2..5489116f60 100644 --- a/doc/spec/proposals/104-short-descriptors.txt +++ b/doc/spec/proposals/104-short-descriptors.txt @@ -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.