diff options
author | Nick Mathewson <nickm@torproject.org> | 2020-09-17 09:21:27 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2020-09-17 09:21:27 -0400 |
commit | bf81f842f6a7463a66bf6ade04ca62eb0d89947a (patch) | |
tree | 57b5b011fcb1ed7b39ffd992c383a53cd3601626 /tor-spec.txt | |
parent | 7640567727f03906db29d47f036cab5e6d62760d (diff) | |
download | torspec-bf81f842f6a7463a66bf6ade04ca62eb0d89947a.tar.gz torspec-bf81f842f6a7463a66bf6ade04ca62eb0d89947a.zip |
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.
Diffstat (limited to 'tor-spec.txt')
-rw-r--r-- | tor-spec.txt | 4 |
1 files changed, 4 insertions, 0 deletions
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] |