[tor-commits] [torspec/master] Change header ordering from a MUST to SHOULD clause

[atagar@xxxxxxxxxxxxxx]

commit 578477a6af99ec1e4a501e267a563730519ffc0f
Author: Damian Johnson <atagar@xxxxxxxxxxxxxx>
Date:   Mon Jan 2 12:16:44 2017 -0800

    Change header ordering from a MUST to SHOULD clause
    
    We had this as a 'MUST' because the directory authorities need to agree upon an
    ordering in their votes to derive at a signed consensus. However, this
    requirement is turning out to be very error prone...
    
      https://trac.torproject.org/projects/tor/ticket/21059
    
    Got the ordering issues sorted out... I think. However, this has bitten us
    three times in a row and clearly will bite us more in the future so loosening
    these requirements a little.
---
 dir-spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dir-spec.txt b/dir-spec.txt
index 26b0800..c25ccf7 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -1526,7 +1526,7 @@
    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.  They MUST occur in the
+   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