[or-cvs] [tor/master] Quick patch to pluggable transport spec

[nickm@xxxxxxxxxxxxxx]

commit 38224f95a690c445e52d6f11180727e8c728999d
Author: Jacob Appelbaum <jacob@xxxxxxxxxxxxx>
Date:   Fri Feb 18 16:03:31 2011 -0500

    Quick patch to pluggable transport spec
---
 .../proposals/ideas/xxx-pluggable-transport.txt    |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/doc/spec/proposals/ideas/xxx-pluggable-transport.txt b/doc/spec/proposals/ideas/xxx-pluggable-transport.txt
index 2507f52..53ba9c6 100644
--- a/doc/spec/proposals/ideas/xxx-pluggable-transport.txt
+++ b/doc/spec/proposals/ideas/xxx-pluggable-transport.txt
@@ -126,7 +126,9 @@ Design overview
 
   To configure one of these programs, it should be sufficient simply to
   list it in your torrc.  The program tells Tor which transports it
-  provides.
+  provides.  The Tor consensus should carry a new approved version number that
+  is specific for pluggable transport; this will allow Tor to know when a
+  particular transport is known to be unsafe safe or non-functional.
 
   Bridges (and maybe relays) report in their descriptors which transport
   protocols they support.  This information can be copied into bridge