[tor-commits] [torspec/master] Remove subprotocol versions for everything obsolete.

[nickm@xxxxxxxxxxxxxx]

commit 232a381bdf97bc3ce474ae8cf9bb169a524814b9
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Tue Sep 13 11:13:22 2016 -0400

    Remove subprotocol versions for everything obsolete.
    
       "Because all relays currently on the network are 0.2.4.19 or later, we
       can require 0.2.4.19, and use 0.2.4.19 as the minimal version so we
       we don't need to do code archaeology to determine how many
       no-longer-relevant versions of each protocol once existed."
    
    Describe which versions of the HS* stuff we will require/recommend.
    
    Also fix a spelling mistake.
---
 proposals/264-subprotocol-versions.txt | 24 ++++++++----------------
 1 file changed, 8 insertions(+), 16 deletions(-)

diff --git a/proposals/264-subprotocol-versions.txt b/proposals/264-subprotocol-versions.txt
index 04e07b8..7f8c4d4 100644
--- a/proposals/264-subprotocol-versions.txt
+++ b/proposals/264-subprotocol-versions.txt
@@ -202,14 +202,6 @@ Status: Open
 
    The "HSIntro" protocol handles introduction points.
 
-      "0" -- supports all features in Tor 0.0.6. Deprecated in 0.2.2.1-alpha.
-
-      "1" -- supports picking rendezvous point by identity ID in Tor
-             0.2.0.7-alpha.
-
-      "2" -- supports specifying rendezvous point's address, port and onion
-             key in Tor 0.2.0.7-alpha.
-
       "3" -- supports authentication as of proposal 121 in Tor
              0.2.1.6-alpha.
 
@@ -228,8 +220,6 @@ Status: Open
    that can be uploaded to, understood by, and downloaded from a tor
    relay, and the set of URLs available to fetch them.
 
-      "0" -- supports all features in Tor 0.0.6. Deprecated in 0.2.2.1-alpha.
-
       "2" -- supports all features in Tor 0.2.0.10-alpha.
 
 5.7. "DirCache"
@@ -299,7 +289,7 @@ Status: Open
 
    Because all relays currently on the network are 0.2.4.19 or later, we
    can require 0.2.4.19, and use 0.2.4.19 as the minimal version so we
-   we don't need to do code archeology to determine how many
+   we don't need to do code archaeology to determine how many
    no-longer-relevant versions of each protocol once existed.
 
    Adding new protocol types is pretty cheap, given compression.
@@ -323,16 +313,18 @@ A.1.  Inferring missing proto lines.
 
 A.2. Initial required protocols
 
-   For clients we will Recommend and Require these.  For relays, we will
-   Recommend these:
+   For clients we will Recommend and Require these.
 
-        Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSMid=1 Link=4
+        Cons=1-2 Desc=1-2 DirCache=1 HSDir=2 HSIntro=3 HSRend=1 Link=4
         LinkAuth=1 Microdesc=1-2 Relay=2
 
    For relays we will Require:
 
-        Cons=1 Desc=1 DirCache=1 HSDir=1 HSMid=1 Link=3-4
-        LinkAuth=1 icrodesc=1 Relay=1-2
+        Cons=1 Desc=1 DirCache=1 HSDir=2 HSIntro=3 HSRend=1 Link=3-4
+        LinkAuth=1 Microdesc=1 Relay=1-2
+
+   For relays, we will additionally Recommend all protocols which we
+   recommend for clients.
 
 A.3. Example integration with other open proposals
 



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits