Merge branch 'feature/protoxep-omemo-media-sharing' into premerge

inbox/omemo-media-sharing.xml

@@ -11,7 +11,7 @@
   &LEGALNOTICE;
   <number>xxxx</number>
   <status>ProtoXEP</status>
-  <type>Informational</type>
+  <type>Historical</type>
   <sig>Standards</sig>
   <approver>Council</approver>
   <dependencies>
@@ -27,6 +27,17 @@
     <email>daniel@gultsch.de</email>
     <jid>daniel@gultsch.de</jid>
   </author>
+  <revision>
+    <version>0.0.2</version>
+    <date>2021-01-10</date>
+    <initials>egp</initials>
+    <remark>
+      <ul>
+        <li>Resubmitted on the Historical track.</li>
+        <li>Added a section on IANA considerations.</li>
+      </ul>
+    </remark>
+  </revision>
   <revision>
     <version>0.0.1</version>
     <date>2018-05-31</date>
@@ -70,4 +81,7 @@ data:image/jpeg,/9j/4AAQSkZJRgABAQEBLAEsAAD…]]></code>
 <section1 topic='Security Considerations' anchor='security'>
   <p>A aesgcm URL MUST never be linkified and clients MUST NOT offer another direct way for users to open them in a browser as this could leak the anchor with the encryption key to the server operator. This is also the reason the aesgcm URL was choosen in the first place to prevent users from accidentally opening a HTTP URL in the browser.</p> 
 </section1>
+<section1 topic='IANA Considerations' anchor='iana'>
+  <p>The aesgcm scheme is not registered at the IANA, and it probably shouldn’t be as it is mostly a hack in order to work around the limitations of &xep0384; version 0.3.0 with regards to the extensibility, as this extension could only encrypt the <code>&lt;body/&gt;</code> of a message.</p>
+</section1>
 </xep>