commit 69a67d0733521258cad498b98649fc2e09a8eb18 Author: George Kadianakis desnacked@riseup.net Date: Thu Jan 12 13:23:18 2017 +0200
Don't enforce strict item order when parsing consensuses.
Authorities still need to generate consensus with a specific order to maintain consensus consistency, but clients don't need to. Resolves ticket #21059. --- dir-spec.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/dir-spec.txt b/dir-spec.txt index 32e6347..08a1166 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1526,8 +1526,9 @@ 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 SHOULD occur in the - order given here: + 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:
"network-status-version" SP version NL