commit 4f4d8fc9f51b3c114aef8c67f9ceae45b7775b94
parent 9811020bd9174d3905ed1dacb238154064787651
Author: Emmanuel Benoist <emmanuel.benoist@bfh.ch>
Date: Tue, 10 Jun 2025 12:09:23 +0200
Description of the verification
Diffstat:
1 file changed, 23 insertions(+), 17 deletions(-)
diff --git a/draft-donau.xml b/draft-donau.xml
@@ -10,6 +10,8 @@
<!ENTITY RFC6234 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6234.xml">
<!ENTITY RFC8032 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8032.xml">
<!ENTITY RFC4648 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4648.xml">
+<!ENTITY RFC9498 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.9498.xml">
+<!ENTITY RFC7748 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7748.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- SEE ALSO: https://docs.taler.net/core/taler-uri.html -->
@@ -326,25 +328,22 @@ Example of an element of USD 100.00 :
host using the GET /donation-statement/ endpoint <xref
target="get-donation-statement"/>. Otherwise, it SHOULD use the
value given in the URI.
-
- The verification app MUST generate the JSON corresponding to the
- claim and validate the signature <xref
- target="signature-verification"/> of this element.
- The JSON contains the information of the URI or the ones that have
- been downloaded.
-
+ The verification of the signature is done using EdDSA which was
+ presented in <xref target="RFC7748">.
- Example of JSON string
+ The verification MAY be done with the following instructions
-TODO FIX ME : what is that JSON STRING ??
- <sourcecode>
- <![CDATA[
- {
- kdfjlksdfkl : kkkjlkjkjlkjlkjl
-}
- ]]>
- </sourcecode>
+ The data to be confirmed is composed of the following information
+ :
+
+ <ul>
+ <li>The value 1500 written
+ in the network order on an 64 bit long unsigned integer.</li>
+ <li>The size of the confirmation to verify (also in network order).</li>
+ <li>The year on a 64 bit long unsigned integer in network order.</li>
+ <li>The SHA256 hash code for the donor ID.</li>
+ </ul>
</t>
</section>
@@ -362,7 +361,10 @@ out of it.
binary data">
All binary data MUST be encoded to be transmitted. For encoding, one
MUST use the Base32 U Crockford encoding. This is a variation of the
-base32 encoding <xref target ="RFC4648" />.
+base32 encoding <xref target ="RFC4648" />. This encoding is presented
+in details in the appendix of the RFC for GNU Name System <xref target="RFC9498" />
+
+
The encoding works similarly to the standard, but uses another Base 32
Alphabet. The new alphabet is given in the Table <xref target="figure_base32_encoding"/>, below.
@@ -436,6 +438,10 @@ MUST evaluate it as a V.
&RFC4648;
+ &RFC9498;
+
+ &RFC7748;
+
</references>
