[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [torspec/master] Revert "Don't enforce strict item order when parsing consensuses."



commit 2db56a087610612892fcadb5d9685f55fe6985d9
Author: George Kadianakis <desnacked@xxxxxxxxxx>
Date:   Tue Jan 17 11:26:08 2017 +0200

    Revert "Don't enforce strict item order when parsing consensuses."
    
    Given the concerns raised in #21059, it seems like the previous wording
    was more appropriate (the final behavior remains the same).
    
    This reverts commit 1d00cabe00000eaab515a0ee54a4ecd3e4fcb651.
---
 dir-spec.txt | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt
index 08a1166..32e6347 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -1526,9 +1526,8 @@
    Some items appear only in votes, and some items appear only in
    consensuses.  Unless specified, items occur in both.
 
-   The preamble contains the following items. Authorities building the
-   consensus MUST place items in the order given here, whereas clients parsing
-   the consensus MUST accept items in any order:
+   The preamble contains the following items.  They SHOULD occur in the
+   order given here:
 
     "network-status-version" SP version NL
 

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