[tor-commits] [torspec/master] prop224: More trivial fixups.

[asn@xxxxxxxxxxxxxx]

commit f9313163c3f85d7bbb92f90947dfe9021f637c89
Author: John Brooks <special@xxxxxxxxxxxxxx>
Date:   Tue May 10 14:25:21 2016 -0400

    prop224: More trivial fixups.
    
    - Sectioning fixes
---
 proposals/224-rend-spec-ng.txt | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt
index 292ab3f..5db0ae3 100644
--- a/proposals/224-rend-spec-ng.txt
+++ b/proposals/224-rend-spec-ng.txt
@@ -1165,12 +1165,9 @@ Table of contents:
    earlier fields.
 
    Older versions of Tor always use a 1024-bit RSA key for these introduction
-   authentication keys. Newer hidden services MAY use RSA keys up 1904
-   bits. Any more than that will not fit in a RELAY cell payload.
+   authentication keys.
 
-[There is no 3.1.3?]
-
-3.1.4. Acknowledging establishment of introduction point [INTRO_ESTABLISHED]
+3.1.3. Acknowledging establishment of introduction point [INTRO_ESTABLISHED]
 
    After setting up an introduction circuit, the introduction point reports its
    status back to the hidden service host with an INTRO_ESTABLISHED cell.
@@ -1183,9 +1180,8 @@ Table of contents:
        EXT_FIELD_LEN  [1 byte]
        EXT_FIELD      [EXT_FIELD_LEN bytes]
 
-   [Worth mentioning that old-school Tor relays send back an empty
-    payload here? Or, even better, not mentioning it if we simplify
-    3.1.2 to "don't do that". -RD]
+   Older versions of Tor send back an empty INTRO_ESTABLISHED cell instead.
+   Services must accept an empty INTRO_ESTABLISHED cell from a legacy relay.
 
 3.2. Sending an INTRODUCE1 cell to the introduction point. [SEND_INTRO1]
 



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