commit 72e63452140c50d43f8a7b33c2058ea9d4509d46
parent 9f79ff8eb95ad9c8aaf532c907adab79b3c75936
Author: Bohdan Potuzhnyi <bohdan.potuzhnyi@gmail.com>
Date: Tue, 7 Oct 2025 21:35:12 +0200
fixing tags issues
Diffstat:
1 file changed, 11 insertions(+), 15 deletions(-)
diff --git a/draft-donau.xml b/draft-donau.xml
@@ -198,7 +198,7 @@
used; for now,
only ED25519 (see <xref target="RFC7748" />) is supported.
The signature using the specified algorithm must be
- made over the information above (see <xref target="signature">)
+ made over the information above (see <xref target="signature"/>)
and MUST be encoded using the Base 32 U Crockford encoding
scheme <xref target="base32-U-crockford"/>.
@@ -467,11 +467,10 @@ Example of an element of USD 100.00 :
in the network order on an 32 bit unsigned integer.</li>
<li>The value 1500 written
in the network order on an 32 bit unsigned integer.</li>
- <li>The total number is written in three fields. First the integer part of the value represented on 64 bit unsigned integer in big endian. Then comes the fractional part of the total value represented by a unsigned integer on 32 bit (also big endian) representing the number of 1/100000000th of the base unit. The third part is a 12 byte string (terminating with the 0x00 character) representing the currency of the total value.
-
- <li>The year on a 64 bit long unsigned integer in network order.</li>
- FIXME-EB: this should include hashing over the salt, not just the taxpayer
- ID and thus needs to be elaborated on how exactly this is hashed.
+ <li>The total number is written in three fields. First the integer part of the value represented on 64 bit unsigned integer in big endian. Then comes the fractional part of the total value represented by a unsigned integer on 32 bit (also big endian) representing the number of 1/100000000th of the base unit. The third part is a 12 byte string (terminating with the 0x00 character) representing the currency of the total value.</li>
+ <li>The year on a 64 bit long unsigned integer in network order.</li>
+ <li>FIXME-EB: this should include hashing over the salt, not just the taxpayer
+ ID and thus needs to be elaborated on how exactly this is hashed.</li>
<li>The SHA256 hash code for the donor ID.</li>
</ul>
@@ -535,27 +534,24 @@ Example of an element of USD 100.00 :
<dt>TOTAL value:</dt>
<dd>
The integer part of the total value. Unsigned integer containing the integer part of the value for the total. It is represented on 64 bits value (in big endian),
- </dd>
+ </dd>
<dt>TOTAL fraction:</dt>
<dd>
The fractional part of the total value is represented by an unsigned integer on 32 bits (also in big endian notation). It represents the fractional part of the value in 1/100000000th of the base unit.
</dd>
- <dt>TOTAL Currency</dt>
- A string representing the currency. 12 bytes for the currency as an string. The last byte
- must be a 0-terminator.
+ <dt>TOTAL Currency</dt>
+ <dd>
+ A string representing the currency. 12 bytes for the currency as an string. The last byte
+ must be a 0-terminator.
</dd>
<dt>HASH:</dt>
<dd>The SHA256 hash code for the donor ID.</dd>
- </dl>
<dt>YEAR:</dt>
<dd>The year on a 32 bit unsigned integer in big endian.</dd>
</dl>
+ <t>FIXME-EB: we'll need test vectors for this in an appendix!</t>
</section>
-
- FIXME-EB: we'll need test vectors for this in an appendix!
-
-</section>
<section anchor="signature-verification" title="Signature verification for a donation statement">
<t>
The signature verification step is taking the data presented in the figure <xref target="figure_signature_data" /> as
