commit da66ae0aca4a31437228c9382da78bd6058b1128
parent 11233d6498fd965b48d58db72c22304541385b85
Author: Elias Summermatter <elias.summermatter@seccom.ch>
Date: Wed, 16 Jun 2021 00:28:57 +0200
Fixed some stuff
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
@@ -2853,7 +2853,7 @@ END FUNCTION
not fewer elements have been received than the other peer has committed to
send at the beginning of the operation.
If the sets differ (the FINAL CHECKSUM field in the <xref target="messages_full_done" format="title" />
- message does not match to the SHA-512 hash of the local set), the operation has failed and the
+ message does not match to the SHA-512 hash XOR sum of the local set), the operation has failed and the
reconciliation MUST be aborted. It is a strong indicator
that something went wrong (eg. some hardware bug). This should never occur!
</t>
@@ -2975,7 +2975,7 @@ END FUNCTION
the decoding of the IBF is finished or all open demands
have been answered, the operation MUST be terminated.
If the sets differ (the FINAL CHECKSUM field in the <xref target="messages_done" format="title" />
- message does not match to the SHA-512 hash of the local set), the operation has failed and the
+ message does not match to the SHA-512 hash XOR sum of the local set), the operation has failed and the
reconciliation MUST be aborted. It is a strong indicator
that something went wrong (eg. some hardware bug). This should never occur!
</t>
@@ -3050,7 +3050,7 @@ END FUNCTION
originally committed to transmitting,
otherwise the operation MUST be terminated.
If the sets differ (the FINAL CHECKSUM field in the <xref target="messages_full_done" format="title" />
- message does not match to the SHA-512 hash of the local set), the operation has failed and the
+ message does not match to the SHA-512 hash XOR sum of the local set), the operation has failed and the
reconciliation MUST be aborted. It is a strong indicator
that something went wrong (eg. some hardware bug). This should never occur!
</t>