[tor-commits] [torspec/master] tor-spec: describe the order in which we put link specifiers.

[dgoulet at torproject.org]

commit bf81f842f6a7463a66bf6ade04ca62eb0d89947a
Author: Nick Mathewson <nickm at torproject.org>
Date:   Thu Sep 17 09:21:27 2020 -0400

    tor-spec: describe the order in which we put link specifiers.
    
    Right now, tor encodes them in a certain order; specifying that
    order can help other implementations be indistinguishable.
---
 tor-spec.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tor-spec.txt b/tor-spec.txt
index f20fcfd..3e82ee8 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -1030,6 +1030,10 @@ see tor-design.pdf.
    Nodes MUST ignore unrecognized specifiers, and MUST accept multiple
    instances of specifiers other than 'legacy identity'.
 
+   For purposes of indistinguishability, implementations SHOULD send
+   these link specifiers, if using them, in this order: [00], [02], [03],
+   [01].
+
    The relay payload for an EXTEND relay cell consists of:
 
          Address                       [4 bytes]