[tor-commits] [torspec/master] Add Version field in shared-rand-commit.

[dgoulet at torproject.org]

commit b140fdd115bd3e42b1fa6954eda609d5da883f55
Author: George Kadianakis <desnacked at riseup.net>
Date:   Thu Jun 9 15:37:55 2016 +0300

    Add Version field in shared-rand-commit.
    
    This is the case in the current codebase.
---
 dir-spec.txt | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt
index 3823da5..fb7ee9a 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -1671,10 +1671,11 @@
         Denotes that the directory authority supports and can participate in the
         shared random protocol.
 
-    "shared-rand-commit" SP AlgName SP Identity SP Commit [SP Reveal] NL
+    "shared-rand-commit" SP Version SP AlgName SP Identity SP Commit [SP Reveal] NL
 
         [Any number for votes; does not occur in consensuses.]
 
+        Version ::= An integer greater or equal to 0.
         AlgName ::= 1*(ALPHA / DIGIT / "_" / "-")
         Identity ::= 40 * HEXDIG
         Commit ::= Base64-encoded-data
@@ -1685,10 +1686,11 @@
         reveal value. See sections [COMMITREVEAL] and [VALIDATEVALUES] of
         proposal 250 on how to generate and validate these values.
 
-        AlgName is the hash algorithm that is used (e.g. "sha3-256") and
-        Identity is the authority's SHA1 v3 identity fingerprint. Commit is the
-        encoded commitment value in base64. Reveal is optional and if it's set,
-        it contains the reveal value in base64.
+        Version is the current shared randomness protocol version. AlgName is
+        the hash algorithm that is used (e.g. "sha3-256") and Identity is the
+        authority's SHA1 v3 identity fingerprint. Commit is the encoded
+        commitment value in base64. Reveal is optional and if it's set, it
+        contains the reveal value in base64.
 
         If a vote contains multiple commits from the same authority, the
         receiver MUST only consider the first commit listed.