diff options
| author | George Kadianakis <desnacked@riseup.net> | 2016-12-22 18:21:49 +0200 |
|---|---|---|
| committer | George Kadianakis <desnacked@riseup.net> | 2016-12-22 18:24:03 +0200 |
| commit | 54007cd9596fe3a0230a27b54ac4fcad94ab2cac (patch) | |
| tree | 479b6429033a74224dfeadb354eff6f0d4b2a8be | |
| parent | 13196900102ff5fb28aa4a5458a53a04971b0adf (diff) | |
Don't enforce strict item order when parsing consensuses.bug21059
Authorities still need to generate consensus with a specific order to
maintain consensus consistency, but clients don't need to.
| -rw-r--r-- | dir-spec.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/dir-spec.txt b/dir-spec.txt index c701842..ec64ec1 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 MUST 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 |