<remark>Accepted by vote of Council on 2021-01-13.</remark>
</revision>
<revision>
<version>0.0.3</version>
<date>2021-01-21</date>
<initials>dg</initials>
<remark>
<ul>
<li>Fixed key length in examples</li>
</ul>
</remark>
</revision>
<revision>
<version>0.0.2</version>
<date>2021-01-10</date>
@ -66,15 +76,15 @@
@@ -66,15 +76,15 @@
<p>To share the file the entity converts the HTTPS URL, the key and the IV to an aesgcm:// URL. Both IV and key are converted to their hex representation of 24 characters and 64 characters respectively and concatenated for a total of 88 characters (44 bytes). The IV comes first followed by the key. The resulting string is put in the anchor part of the aesgcm URL.</p>
<p>The sending entity MAY also generate a thumbnail as a JPEG data uri and include that in the same message. The aesgcm:// and the data:image/jpep, are seperated by a new line character. The message SHOULD NOT include anything else. The JPEG thumbnail SHOULD be kept small (approximately 5KiB) to not run into into stanza size limitations. As a result the resulting thumbnail is considered to only be a very blury, very rough representation of the image.</p>