aboutsummaryrefslogtreecommitdiff
path: root/proposals/264-subprotocol-versions.txt
diff options
context:
space:
mode:
Diffstat (limited to 'proposals/264-subprotocol-versions.txt')
-rw-r--r--proposals/264-subprotocol-versions.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/proposals/264-subprotocol-versions.txt b/proposals/264-subprotocol-versions.txt
index 75a1c8f..9ccb803 100644
--- a/proposals/264-subprotocol-versions.txt
+++ b/proposals/264-subprotocol-versions.txt
@@ -1,3 +1,4 @@
+```
Filename: 264-subprotocol-versions.txt
Title: Putting version numbers on the Tor subprotocols
Author: Nick Mathewson
@@ -151,9 +152,7 @@ Implemented-In: 0.2.9.4-alpha
versions we expect to continue supporting.]]
These lines should be voted on. A majority of votes is sufficient to
- make a protocol un-supported.
-
- and should require a supermajority of
+ make a protocol un-supported and it should require a supermajority of
authorities (2/3) to make a protocol required. The required protocols
should not be torrc-configurable, but rather should be hardwired in the
Tor code.
@@ -301,7 +300,7 @@ Implemented-In: 0.2.9.4-alpha
Adding new protocol types is pretty cheap, given compression.
-A.1. Inferring missing proto lines.
+A.1. Inferring missing proto lines
The directory authorities no longer allow versions of Tor before
0.2.4.18-rc. But right now, there is no version of Tor in the
@@ -549,3 +548,4 @@ A.3. Example integration with other open proposals
New Relay protocol version.
+```