No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0313.xml 50KB

  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Message Archive Management</title>
  10. <abstract>This document defines a protocol to query and control an archive of messages stored on a server.</abstract>
  12. <number>0313</number>
  13. <status>Experimental</status>
  14. <lastcall>2017-11-15</lastcall>
  15. <type>Standards Track</type>
  16. <sig>Standards</sig>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. <spec>XEP-0030</spec>
  20. <spec>XEP-0059</spec>
  21. <spec>XEP-0297</spec>
  22. </dependencies>
  23. <supersedes/>
  24. <supersededby/>
  25. <shortname>mam</shortname>
  26. <schemaloc>
  27. <url></url>
  28. </schemaloc>
  29. &mwild;
  30. &ksmith;
  31. <revision>
  32. <version>0.6.1</version>
  33. <date>2017-02-22</date>
  34. <initials>mw</initials>
  35. <remark>
  36. <p>Warn of spoofing of &lt;x&gt; elements in MUC stanzas</p>
  37. </remark>
  38. </revision>
  39. <revision>
  40. <version>0.6</version>
  41. <date>2017-02-17</date>
  42. <initials>dg, mw</initials>
  43. <remark>
  44. <p>Namespace bump</p>
  45. <p>Added method for server to communicate the archive id</p>
  46. <p>Incorporated editorial clarifications based on implementation feedback</p>
  47. <p>Clarifications on the topics of message ordering, message deletion and use of the protocol for synchronization</p>
  48. </remark>
  49. </revision>
  50. <revision>
  51. <version>0.5.1</version>
  52. <date>2016-03-07</date>
  53. <initials>XEP Editor (ssw)</initials>
  54. <remark>
  55. <p>Bump old namespace version in examples (Kevin Smith)</p>
  56. </remark>
  57. </revision>
  58. <revision>
  59. <version>0.5</version>
  60. <date>2016-01-20</date>
  61. <initials>XEP Editor (mam)</initials>
  62. <remark>
  63. <p>Added clarifications and enhancements when interacting with Multi-User Chat (MUC) (Mickaël Rémond)</p>
  64. </remark>
  65. </revision>
  66. <revision>
  67. <version>0.4.1</version>
  68. <date>2015-09-29</date>
  69. <initials>XEP Editor (mam)</initials>
  70. <remark>
  71. <p>Fix Example #9 from &lt;/message/&gt; to &lt;/iq&gt; (Florian Schmaus)</p>
  72. <p>Add missing jabber:client namespace in Example #2 (Christian Schudt)</p>
  73. </remark>
  74. </revision>
  75. <revision>
  76. <version>0.4</version>
  77. <date>2015-09-21</date>
  78. <initials>ks/mw</initials>
  79. <remark>
  80. <p>Switch the sentinel message back to the iq result.</p>
  81. <p>Various small fixes to the document.</p>
  82. </remark>
  83. </revision>
  84. <revision>
  85. <version>0.3</version>
  86. <date>2014-08-14</date>
  87. <initials>ka/ks</initials>
  88. <remark><p>Fetching current preferences,
  89. switch to iq-set for searching,
  90. switch to using a data form,
  91. describe how to fetch that form, remove the archived element and
  92. use a sentinel message instead of iq reply.</p></remark>
  93. </revision>
  94. <revision>
  95. <version>0.2</version>
  96. <date>2013-05-31</date>
  97. <initials>mw</initials>
  98. <remark><p>Document the ability to page through results by message UIDs, define the &lt;archived/&gt; element, and various minor improvements.</p></remark>
  99. </revision>
  100. <revision>
  101. <version>0.1</version>
  102. <date>2012-04-18</date>
  103. <initials>mw</initials>
  104. <remark><p>Initial version, to much rejoicing.</p></remark>
  105. </revision>
  106. </header>
  107. <section1 topic='Introduction' anchor='intro'>
  108. <p>It is a common desire for users of XMPP to want to store their messages in a central archive
  109. on their server. This feature allows them to record conversations that take place on clients that do not
  110. support local history storage, to synchronise conversation history seamlessly between
  111. multiple clients, to read the history of a MUC room, or to view old items in a pubsub node.</p>
  112. </section1>
  113. <section1 topic='Requirements' anchor='requirements'>
  114. <p>As this extension aims to make things easy for client developers, some research was made into the
  115. way clients handle history today. The resulting protocol was designed to allow for the following primary
  116. usage scenarios:</p>
  117. <ul>
  118. <li>Automatic history synchronization between multiple clients.</li>
  119. <li>Calendar-based on-demand display of historic messages in a client that doesn't keep local history.</li>
  120. <li>So-called 'infinite' scrollback, whereby a client automatically fetches and displays historical messages
  121. naturally in the message log as the user scrolls back in time.</li>
  122. </ul>
  123. <p>Another extension for archiving already exists in XMPP, &xep0136;). However implementation experience has
  124. shown that the protocol defined therein supports rather more functionality than is typically needed for the
  125. above uses, and is significantly more effort to implement.</p>
  126. <p>This specification aims to define a much simpler and modular protocol for working with a server-side
  127. message store. Through this it is hoped to boost implementation and deployment of archiving in XMPP. It
  128. should be noted that (although not required) a server is free to implement XEP-0136 alongside this
  129. protocol if it so chooses, though a mapping between both protocols is beyond the scope of this specification.</p>
  130. <p>Notable functionality in XEP-0136 that is intentionally not defined by this specification for simplicity:</p>
  131. <ul>
  132. <li>Support for 'collections'. Few clients even support this concept for local history storage, and
  133. it is possible to apply the logic for splitting a stream of messages into conversations on the
  134. client-side, thus greatly simplifying the protocol.</li>
  135. <li>Support for uploading to the archive. On the assumption that a server automatically archives
  136. messages to and from the client, it is typically rare for a client to end up with messages that are
  137. not already in the archive. Uploading could be useful for bootstrapping an empty archive however, and
  138. may be defined in a future specification if there is demand for such functionality.</li>
  139. <li>Support for 'off the record' chats (OTR; not to be confused with the encryption algorithm of
  140. the same name). This allowed complex negotiation for either the user or contact to command specific
  141. conversations to bypass the archive. In reality the archiving behaviour of a contact's server cannot
  142. be enforced (they could ignore the OTR request and archive the messages anyway without your consent)
  143. so this specification does not try and regulate that. Equivalent functionality can be implemented with
  144. server logic for not including encrypted or specially-tagged messages in the archive (out of scope for
  145. this specification).</li>
  146. <li>Support per-session configuration. This feature was deemed unnecessary for the majority of
  147. implementations, and hence the configuration protocol in this specification is much simplified,
  148. which allows for a simple user interface in clients. Advanced configuration however may be performed
  149. through ad-hoc commands depending on the server implementation.</li>
  150. </ul>
  151. </section1>
  152. <section1 topic='Message archives' anchor='archives'>
  153. <p>An archive contains a collection of messages relevant to a particular XMPP address, e.g. a user, MUC, pubsub node, server. Note: while a service might have many "archives" as defined here (one per JID capable of being queried) this is a conceptual distinction,
  154. and a server is not bound to any particular implementation or arrangement of data stores.</p>
  155. <p>Exactly which messages a server archives is up to implementation and deployment policy,
  156. but it is expected that all messages that hold meaningful content, rather than state changes such as Chat State Notifications, would be archived. Rules are specified later in this document.</p>
  157. <p>A stored message consists of at least the following pieces of information:</p>
  158. <ul>
  159. <li>A timestamp of when the message was sent (for an outgoing message) or received (for
  160. an incoming message).</li>
  161. <li>The remote JID that the stanza is to (for an outgoing message) or from (for an
  162. incoming message).</li>
  163. <li>A server-assigned UID that MUST be unpredictable and unique within the archive.</li>
  164. <li>The message stanza itself. The entire original stanza SHOULD be stored, but at a
  165. minimum only the &BODY; tag MUST be preserved (ie. the server might, at its
  166. discretion, strip certain extensions from messages before storage).</li>
  167. </ul>
  168. <p>Note that 'incoming' and 'outgoing' messages are viewed within the context of the archived JID, rather than the system as a whole. For example, if romeo@montegue.lit sent a message to juliet@capulet.lit, it would be an outgoing message in the context of archiving for Romeo, and an incoming message in the context of archiving for Juliet.</p>
  169. <section2 topic='Order of messages' anchor='archive_order'>
  170. <p>Order within the archive MUST be preserved, where the order of messages is the same as the order that the client originally received them (or would have received them if online). Throughout this document the term 'chronological order' refers to this order, however implementors should take care not to rely on timestamps alone for
  171. ordering messages, as multiple messages may share the same timestamp.</p>
  172. </section2>
  173. <section2 topic='Message retention and deletion' anchor='archives_deletion'>
  174. <p>A server MAY impose limits on the size of an individual archive. For example a server might begin
  175. to discard old messages once the archive reaches a certain size, or only keep messages until they
  176. reach a certain age. Any such deleted messages MUST be the oldest in the archive, i.e. it is not permitted
  177. to create gaps or "holes" in the archive. The UIDs of deleted messages MUST NOT be reused for new messages.</p>
  178. <p>However a server that wishes to remove messages from the middle of an archive, e.g. to remove accidentally transmitted
  179. sensitive information may omit the &lt;message&gt; stanza from inside the &lt;forwarded&gt; element or replace the
  180. message with an appropriate placeholder when transmitting the result in response to a query. However servers
  181. MUST retain the UID, timestamp and JID of the original message internally to ensure that all queries remain consistent.
  182. It should also be understood that clients maintaining their own local copy of the archive may still retain the original
  183. message locally in this case, and this protocol provides no mechanism for forcibly removing messages from any local archive
  184. or cache that clients may keep.</p>
  185. </section2>
  186. <section2 topic='Archiving entities' anchor='archiving_entities'>
  187. <p>There is no restriction on which services can expose archives, although only user, MUC and pubsub node archives are discussed here.</p>
  188. <section3 topic='User archives' anchor='archives_user'>
  189. <p>The most typical address is that of a user's own bare JID, within which those messages sent to or from that
  190. user's account would generally automatically be stored by the server. The collection
  191. is ordered chronologically by the time each message was sent/received.</p>
  192. <p>Servers that expose archive messages of sent/received messages on behalf of local users MUST expose these archives to the user on the user's bare JID.</p>
  193. </section3>
  194. <section3 topic='MUC archives' anchor='archives_muc'>
  195. <p>A MUC service allowing MAM queries for a room MUST expose the MAM archive on the room's bare JID</p>
  196. </section3>
  197. <section3 topic='Pubsub node archives' anchor='archives_pubsub'>
  198. <p>A pubsub service allowing MAM queries for a node's data MUST expose this for queries addressed to the pubsub service</p>
  199. </section3>
  200. </section2>
  201. <section2 topic='Querying Entities' anchor='entities'>
  202. <p>While this document talks about 'clients' and 'servers', as these are the common cases, the querying entity (referred to as a 'client') need not be an XMPP client as defined by RFC6120, but could potentially be any type of entity, and the queried entity (referred to as a 'server') need not be an XMPP server as defined by RFC6120, although access controls might prohibit any given entity from being able to access an archive.</p>
  203. </section2>
  204. <section2 topic='Communicating the archive ID' anchor='archives_id'>
  205. <p>When a message is archived, the server MUST add an &lt;stanza-id/&gt; element as defined in &xep0359; to the message, which informs the recipient of where and under what ID the message is stored. When doing this the server MUST follow the business rules defined in XEP-0359. The 'by' attribute MUST be set to the address of the archive. For regular users that’s the bare JID of the account and for MUC that’s the bare JID of the room.</p>
  206. <p>Servers MUST NOT include the &lt;stanza-id/&gt; element in messages addressed to JIDs that do not have permissions to access the archive, such as a users’s outgoing messages to their contacts. However servers SHOULD include the element as a child of the forwarded message when using &xep0280;</p>
  207. <example caption='Client receives a message that has been archived'><![CDATA[
  208. <message to='juliet@capulet.lit/balcony'
  209. from='romeo@montague.lit/orchard'
  210. type='chat'>
  211. <body>Call me but love, and I'll be new baptized; Henceforth I never will be Romeo.</body>
  212. <stanza-id xmlns='urn:xmpp:sid:0' by='juliet@capulet.lit' id='28482-98726-73623' />
  213. </message>]]></example>
  214. <p>Note: Previous versions of this protocol did not specify any interaction with stanza-id, and clients MUST NOT interpret XEP-0359 IDs in messages as archive IDs unless the server advertises support for 'urn:xmpp:mam:2' specifically.</p>
  215. </section2>
  216. </section1>
  217. <section1 topic='Querying an archive' anchor='query'>
  218. <p>An entity is able to query (subject to appropriate access rights) an archive for all messages within a certain timespan, optionally
  219. restricting results to those to/from a particular JID. To allow limiting the results or paging
  220. through them a client may use &xep0059;, which MUST be supported by both the client and the server.</p>
  221. <p>A query consists of an &IQ; stanza of type 'set' addressed to the account or server entity hosting
  222. the archive, with a 'query' payload. On receiving the query, the server pushes to the client a
  223. series of messages in chronological order from the archive that match the client's given criteria. After the
  224. results it then returns the &IQ; result to indicate that the query is completed.</p>
  225. <p>The final &IQ; result response MUST include an RSM &lt;set/&gt; element, wrapped into a &lt;fin/&gt;
  226. element qualified by the 'urn:xmpp:mam:2' namespace, indicating the
  227. UID of the first and last message of the (possibly limited) result set. This
  228. allows clients to accurately page through messages.</p>
  229. <example caption='A user queries their archive for messages'><![CDATA[
  230. <iq type='set' id='juliet1'>
  231. <query xmlns='urn:xmpp:mam:2' queryid='f27' />
  232. </iq>]]></example>
  233. <example caption='Their server sends the matching messages'><![CDATA[
  234. <message id='aeb213' to='juliet@capulet.lit/chamber'>
  235. <result xmlns='urn:xmpp:mam:2' queryid='f27' id='28482-98726-73623'>
  236. <forwarded xmlns='urn:xmpp:forward:0'>
  237. <delay xmlns='urn:xmpp:delay' stamp='2010-07-10T23:08:25Z'/>
  238. <message xmlns='jabber:client' from="witch@shakespeare.lit" to="macbeth@shakespeare.lit">
  239. <body>Hail to thee</body>
  240. </message>
  241. </forwarded>
  242. </result>
  243. </message>]]></example>
  244. <example caption='Server returns the result IQ to signal the end'><![CDATA[
  245. <iq type='result' id='juliet1'>
  246. <fin xmlns='urn:xmpp:mam:2'>
  247. <set xmlns=''>
  248. <first index='0'>28482-98726-73623</first>
  249. <last>09af3-cc343-b409f</last>
  250. </set>
  251. </fin>
  252. </iq>]]></example>
  253. <p>To ensure that the client knows when the results are complete, the server MUST send the &IQ; result after last query result has been sent
  254. to the client. The client can optionally include a 'queryid' attribute in their query, which allows the client to match results to their initiating query.</p>
  255. <p>When querying a pubsub node's archive, the 'node' attribute is added to the &lt;query&gt; element.</p>
  256. <example caption="A user queries a pubsub node's archive for messages"><![CDATA[
  257. <iq to='pubsub.shakespeare.lit' type='set' id='juliet1'>
  258. <query xmlns='urn:xmpp:mam:2' queryid='f28' node='fdp/submitted/capulet.lit/sonnets'/>
  259. </iq>
  260. ]]></example>
  261. <section2 topic='Filtering results' anchor='filter'>
  262. <p>By default all messages match a query, and filters are used to request a subset of the archived
  263. messages. Filters are specified in a &xep0004; data form included with the query. The hidden FORM_TYPE field
  264. MUST be set to this protocol's namespace, 'urn:xmpp:mam:2'. Three further fields are defined by this
  265. XEP and MUST be supported by servers, though all of them are optional for the client. These fields are:</p>
  266. <ul>
  267. <li>start</li>
  268. <li>end</li>
  269. <li>with</li>
  270. </ul>
  271. <p>Other fields may be used, but are not defined in this document - the naming of new fields MUST be
  272. consistent with the format defined in &xep0068;. Servers MUST NOT mark any fields in the form as
  273. being required (i.e. with the data forms &lt;required/&gt; element), regardless of whether they are
  274. defined in this document or elsewhere.</p>
  275. <section3 topic='Filtering by JID' anchor='filter-jid'>
  276. <p>If a 'with' field is present in the form, it contains a JID against which to match messages. The
  277. server MUST only return messages if they match the supplied JID. A message in a user's archive matches if the JID matches either the to or from of the message. An item in a pubsub or MUC archive matches if the publisher of the item matches the JID; note that this should only be available to entities that would already have been allowed to know the publisher of the events (e.g. this could not be used by a visitor to a semi-anonymous MUC).</p>
  278. <p>If the 'with' field's value is the bare JID of the archive, the server must only return results where both the 'to' and 'from' match the bare JID (either as bare or by ignoring the resource), as otherwise every message in the archive would match</p>
  279. <p>If 'with' is omitted, the server MUST match all messages in the selected timespan with the query,
  280. regardless of the to/from addresses on each message.</p>
  281. <example caption='Querying for all messages to/from a particular JID'><![CDATA[
  282. <iq type='set' id='juliet1'>
  283. <query xmlns='urn:xmpp:mam:2'>
  284. <x xmlns='jabber:x:data' type='submit'>
  285. <field var='FORM_TYPE' type='hidden'>
  286. <value>urn:xmpp:mam:2</value>
  287. </field>
  288. <field var='with'>
  289. <value>juliet@capulet.lit</value>
  290. </field>
  291. </x>
  292. </query>
  293. </iq>
  294. ]]></example>
  295. <p>If (and only if) the supplied JID is a bare JID (i.e. no resource is present), then
  296. the server SHOULD return messages if their bare to/from address for a user archive, or from address otherwise, would match it. For example,
  297. if the client supplies a 'with' of "juliet@capulet.lit" a query to their own archive would also match messages to
  298. or from "juliet@capulet.lit/balcony" and "juliet@capulet.lit/chamber".</p>
  299. </section3>
  300. <section3 topic='Filtering by time received' anchor='filter-time'>
  301. <p>The 'start' and 'end' fields, if provided, MUST contain timestamps
  302. formatted according to the DateTime profile defined in &xep0082;</p>
  303. <p>The 'start' field is used to filter out messages before a certain date/time.
  304. If specified, a server MUST only return messages whose timestamp is equal to or later
  305. than the given timestamp.</p>
  306. <p>If omitted, the server SHOULD assume the value of 'start' to be equal to the
  307. date/time of the earliest message stored in the archive.</p>
  308. <p>Conversely, the 'end' field is used to exclude from the results messages
  309. after a certain point in time. If specified, a server MUST only return messages whose
  310. timestamp is equal to or earlier than the timestamp given in the 'end' field.</p>
  311. <p>If omitted, the server SHOULD assume the value of 'end' to be equal to the
  312. date/time of the most recent message stored in the archive.</p>
  313. <example caption='Querying the archive for all messages in a certain timespan'><![CDATA[
  314. <iq type='set' id='juliet1'>
  315. <query xmlns='urn:xmpp:mam:2'>
  316. <x xmlns='jabber:x:data' type='submit'>
  317. <field var='FORM_TYPE' type='hidden'>
  318. <value>urn:xmpp:mam:2</value>
  319. </field>
  320. <field var='start'>
  321. <value>2010-06-07T00:00:00Z</value>
  322. </field>
  323. <field var='end'>
  324. <value>2010-07-07T13:23:54Z</value>
  325. </field>
  326. </x>
  327. </query>
  328. </iq>
  329. ]]></example>
  330. <example caption='Querying the archive for all messages after a certain time'><![CDATA[
  331. <iq type='set' id='juliet1'>
  332. <query xmlns='urn:xmpp:mam:2'>
  333. <x xmlns='jabber:x:data' type='submit'>
  334. <field var='FORM_TYPE' type='hidden'>
  335. <value>urn:xmpp:mam:2</value>
  336. </field>
  337. <field var='start'>
  338. <value>2010-08-07T00:00:00Z</value>
  339. </field>
  340. </x>
  341. </query>
  342. </iq>
  343. ]]></example>
  344. </section3>
  345. <section3 topic='Limiting results' anchor='query-limit'>
  346. <p>Finally, in order for the client or server to limit the number of results transmitted at
  347. a time a server MUST support &xep0059; and MUST support the paging mechanism defined therein.
  348. A client MAY include a &lt;set/&gt; element in its query.</p>
  349. <p>For the purposes of this protocol, the UIDs used by RSM correspond with the UIDs of the
  350. stanzas stored in the archive.</p>
  351. <example caption='A query using Result Set Management'><![CDATA[
  352. <iq type='set' id='q29302'>
  353. <query xmlns='urn:xmpp:mam:2'>
  354. <x xmlns='jabber:x:data' type='submit'>
  355. <field var='FORM_TYPE' type='hidden'>
  356. <value>urn:xmpp:mam:2</value>
  357. </field>
  358. <field var='start'>
  359. <value>2010-08-07T00:00:00Z</value>
  360. </field>
  361. </x>
  362. <set xmlns=''>
  363. <max>10</max>
  364. </set>
  365. </query>
  366. </iq>
  367. ]]></example>
  368. <p>To conserve resources, a server MAY place a reasonable limit on how many stanzas may be
  369. pushed to a client in one request. Whether or not the client query included a &lt;set/&gt; element, the server MAY simply return
  370. its limited results, modifying the &lt;set/&gt; element it returns appropriately.</p>
  371. <example caption='Server responds to client with limited results using RSM'><![CDATA[
  372. <!-- result messages -->
  373. <iq type='result' id='q29302'>
  374. <fin xmlns='urn:xmpp:mam:2'>
  375. <set xmlns=''>
  376. <first index='0'>28482-98726-73623</first>
  377. <last>09af3-cc343-b409f</last>
  378. <count>20</count>
  379. </set>
  380. </fin>
  381. </iq>
  382. ]]></example>
  383. <p>The &lt;first&gt; and &lt;last&gt; elements specify the UID of the first and last returned
  384. results (not necessarily of all the messages that matched the query, if the results have been limited).</p>
  385. <p>The RSM &lt;count&gt; element and the 'index' attribute on the RSM &lt;first&gt; element are optional,
  386. but servers SHOULD include them. Please refer to the RSM specification for more information
  387. surrounding their meaning and use.</p>
  388. </section3>
  389. <section3 topic='Paging through results' anchor='query-paging'>
  390. <p>Having previously made a query that returned results limited by the server (as described above), a client
  391. can re-send the same request and receive the next 'page' of results. It does this by including a &lt;set&gt;
  392. element with its request, containing an &lt;after/&gt; with the UID of the last message it received
  393. from the previous query.</p>
  394. <example caption='A page query using Result Set Management'><![CDATA[
  395. <iq type='set' id='q29303'>
  396. <query xmlns='urn:xmpp:mam:2'>
  397. <x xmlns='jabber:x:data' type='submit'>
  398. <field var='FORM_TYPE' type='hidden'><value>urn:xmpp:mam:2</value></field>
  399. <field var='start'><value>2010-08-07T00:00:00Z</value></field>
  400. </x>
  401. <set xmlns=''>
  402. <max>10</max>
  403. <after>09af3-cc343-b409f</after>
  404. </set>
  405. </query>
  406. </iq>
  407. ]]></example>
  408. <p>Note: There is no concept of an "open query", and servers MUST be prepared to receive arbitrary page requests at any time.</p>
  409. <p>If the UID contained within an &lt;after&gt; or &lt;before&gt; element is not present in the archive, the server MUST return an item-not-found error in response to the query.</p>
  410. <p>When the results returned by the server are complete (that is: when they are the last page of the result set), the server MUST include a 'complete' attribute on the &lt;fin&gt; element, with a value of 'true'. If it is not the last page of the result set, the server MUST either omit the 'complete' attribute, or give it a value of 'false'.</p>
  411. <example caption='Server completes a result with the last page of messages'><![CDATA[
  412. <!-- result messages -->
  413. <iq type='result' id='u29303'>
  414. <fin xmlns='urn:xmpp:mam:2' complete='true'>
  415. <set xmlns=''>
  416. <first index='0'>23452-4534-1</first>
  417. <last>390-2342-22</last>
  418. <count>16</count>
  419. </set>
  420. </fin>
  421. </iq>
  422. ]]></example>
  423. <p>Sometimes (e.g. due to network or storage partitioning, or other transient errors) the server might return results to a client that are unstable (e.g. they might later change in sequence or content). In such a situation the server MUST stamp the &lt;fin&gt; element with a 'stable' attribute with a value of 'false'. If the server knows that the data it's serving are stable it MUST either stamp a 'stable' attribute with a value of 'true', or no such attribute. An example of when unstable might legitimately be returned is if the MAM service uses a clustered data store and a query covers a time period for which the data store has not yet converged; it the server could return best-guess results and tell the client that they may be unstable. A client SHOULD NOT cache unstable results long-term without later confirming (by reissuing appropriate queries) that they have become stable.</p>
  424. </section3>
  425. <section3 topic='Retrieving form fields' anchor='query-form'>
  426. <p>In order for the client find out about additional fields the server might support, it can send an iq stanza of type 'get' addressed to the archive like this:</p>
  427. <example caption="Client requests supported query fields"><![CDATA[
  428. <iq type='get' id='form1'>
  429. <query xmlns='urn:xmpp:mam:2'/>
  430. </iq>
  431. ]]></example>
  432. <p>The server replies with all the form fields it supports in queries, which MUST include the mandatory fields specified in this document.</p>
  433. <example caption="Server returns supported fields"><![CDATA[
  434. <iq type='result' id='form1'>
  435. <query xmlns='urn:xmpp:mam:2'>
  436. <x xmlns='jabber:x:data' type='form'>
  437. <field type='hidden' var='FORM_TYPE'>
  438. <value>urn:xmpp:mam:2</value>
  439. </field>
  440. <field type='jid-single' var='with'/>
  441. <field type='text-single' var='start'/>
  442. <field type='text-single' var='end'/>
  443. <field type='text-single' var='urn:example:xmpp:free-text-search'/>
  444. <field type='text-single' var='urn:example:xmpp:stanza-content'/>
  445. </x>
  446. </query>
  447. </iq>
  448. ]]></example>
  449. <p>If the client understands any of the additional fields it MAY proceed to include any of them in subsequent queries. It is not required to include any or all of the supported fields in queries.</p>
  450. <example caption="Client uses two discovered query fields in a query"><![CDATA[
  451. <iq type='set' id='query4'>
  452. <query xmlns='urn:xmpp:mam:2'>
  453. <x xmlns='jabber:x:data' type='submit'>
  454. <field type='hidden' var='FORM_TYPE'>
  455. <value>urn:xmpp:mam:2</value>
  456. </field>
  457. <field type='text-single' var='urn:example:xmpp:free-text-search'>
  458. <value>Where arth thou, my Juliet?</value>
  459. </field>
  460. <field type='text-single' var='urn:example:xmpp:stanza-content'>
  461. <value>{}mood/lonely</value>
  462. </field>
  463. </x>
  464. </query>
  465. </iq>
  466. ]]></example>
  467. <p>Note that as the 'with', 'start' and 'end' fields MUST be implemented by servers, clients are able to submit forms using combinations of only these fields without needing to first fetch the form from the server and the types of these fields MUST be 'jid-single', 'text-single' and 'text-single' respectively. A server MUST NOT rely on a client having first requested the form before submitting queries</p>
  468. </section3>
  469. </section2>
  470. <section2 topic='Query results' anchor='results'>
  471. <p>The server responds to the archive query by transmitting to the client all the messages
  472. that match the criteria the client requested, subject to implementation limits. The results are sent as individual stanzas,
  473. with the original message encapsulated in a &lt;forwarded/&gt; element as described in &xep0297;.
  474. </p>
  475. <p>The result messages MUST contain a &lt;result/&gt; element with an 'id' attribute that gives
  476. the current message's archive UID (archived messages MAY also contain a XEP-0359 &lt;stanza-id&gt; element, but clients MUST NOT depend
  477. on it). If the client gave a 'queryid' attribute in its initial query, the server MUST also include that in this result element.
  478. </p>
  479. <p>The &lt;result/&gt; element contains a &lt;forwarded/&gt; element which SHOULD contain the
  480. original message as it was received, and SHOULD also contain a &lt;delay/&gt; element
  481. qualified by the 'urn:xmpp:delay' namespace specified in &xep0203;. The value of the 'stamp'
  482. attribute MUST be the time the message was originally received by the forwarding entity.
  483. </p>
  484. <p>The archive results MUST be sorted in chronological order, both within the returned results and within the ordering of RSM such that if a client were to request the first 10 stanzas in an archive, then use RSM to request the next 10 stanzas (by providing the 'after' element with the UID of the 10th stanza in the first results) all 20 result stanzas would be received in chronological order.
  485. </p>
  486. <example caption='Server returns two matching messages'><![CDATA[
  487. <message id='aeb213' to='juliet@capulet.lit/chamber'>
  488. <result xmlns='urn:xmpp:mam:2' queryid='f27' id='28482-98726-73623'>
  489. <forwarded xmlns='urn:xmpp:forward:0'>
  490. <delay xmlns='urn:xmpp:delay' stamp='2010-07-10T23:08:25Z'/>
  491. <message xmlns='jabber:client'
  492. to='juliet@capulet.lit/balcony'
  493. from='romeo@montague.lit/orchard'
  494. type='chat'>
  495. <body>Call me but love, and I'll be new baptized; Henceforth I never will be Romeo.</body>
  496. </message>
  497. </forwarded>
  498. </result>
  499. </message>
  500. <message id='aeb214' to='juliet@capulet.lit/chamber'>
  501. <result xmlns='urn:xmpp:mam:2' queryid='f27' id='5d398-28273-f7382'>
  502. <forwarded xmlns='urn:xmpp:forward:0'>
  503. <delay xmlns='urn:xmpp:delay' stamp='2010-07-10T23:09:32Z'/>
  504. <message xmlns='jabber:client'
  505. to='romeo@montague.lit/orchard'
  506. from='juliet@capulet.lit/balcony'
  507. type='chat' id='8a54s'>
  508. <body>What man art thou that thus bescreen'd in night so stumblest on my counsel?</body>
  509. </message>
  510. </forwarded>
  511. </result>
  512. </message>
  513. ]]></example>
  514. </section2>
  515. </section1>
  516. <section1 topic='Business Rules' anchor='business_rules'>
  517. <section2 topic='Storage and Retrieval Rules' anchor='business-storeret'>
  518. <p>Different entities will have different requirements for which data are stored, as might different deployments. This section provides general rules within which a server will act. While there may be local policy restrictions that prevent archiving of some aspects discussed here, this is a RECOMMENDED baseline. A server MAY implement any subset of possible archives for JIDs it controls (although it MUST advertise support only for those JIDs that support it).</p>
  519. <p>No requirements are placed on how a server implements its storage beyond that it has to store data sufficient to be able to comply with this document. When this document describes storage requirements (e.g. MUST NOT store more than one copy...), it refers to what would appear to have been stored in order to satisfy the query.</p>
  520. <p>If an entity (user's server, MUC room, pubsub node, ...) rejects an incoming message (such as from an occupant not allowed to send messages to the room, a user not authorized to publish to a pubsub node, a contact blocked by the user etc.) that message should not appear in the archive for the entity that rejected it - the archive should represent what logical entities (MUC occupants, users, pubsub subscribers...) would have received, and so only contain messages accepted for delivery to such entities.</p>
  521. <section3 topic="User Archives" anchor='business-storeret-user-archives'>
  522. <p>A user archive is anticipated to provide the user with the ability to access their prior conversations. To this end, a server SHOULD include in a user archive all of the messages a user sends or receives of type 'normal' or 'chat' that contain a &lt;body&gt; element. A server SHOULD also include messages of type 'groupchat' that have a &lt;body&gt;, but where such history is accessible through another method (e.g. through an archive on the MUC JID), a server MAY exclude these from the archive. A server MAY include additional non-conversation messages. A server MAY include messages of type 'headline', but this is not generally suggested.</p>
  523. <p>At a minimum, the server MUST store the &lt;body&gt; elements of a stanza. It is suggested that other elements that are used in a given deployment to supplement conversations (e.g. XHTML-IM payloads) are also stored. Other elements MAY be stored.</p>
  524. <p>If a server supports mechanisms that multiply copies of a stanza (e.g. Carbons, or forking a stanza to a bare JID), it MUST store such a staza within a given archive only once, irrespective of multiple connected clients receiving copies</p>
  525. </section3>
  526. <section3 topic="MUC Archives" anchor='business-storeret-muc-archives'>
  527. <p>A MUC archives allows a user to view the conversation within a room. All messages sent to the room that contain a &lt;body&gt; element SHOULD be stored, as should subject change stanzas, apart from those messages that the room rejects.</p>
  528. <p>A MUC archive MUST store each message only once (not, for example, every copy sent out to an occupant).</p>
  529. <p>A MUC archive MUST NOT include 'private message' results (those sent directly between occupants, not shared in the room) in the results</p>
  530. <p>A MUC archive MUST check that the user requesting the archive has the right to enter it at the time of the query and only allow access if so. In a members-only chat room, only owners, admins or members can query a room archive. In the case of open MUC rooms, the MUC archives can generally be accessed by any users (including those who have never entered the room) who do not have an affiliation of 'outcast', but a MUC archive MAY further limit access based on other criteria as part of the deployment policy. A MUC archive MAY, if it stores historical data about previous configuration states, limit the results returned to only those that the querying user would have been authorised to see at the time (e.g. it MAY limit the results to not include results while a user was an outcast).</p>
  531. <p>When sending out the archives to a requesting client, the 'to' of the forwarded stanza MUST be empty, and the 'from' MUST be the occupant JID of the sender of the archived message.</p>
  532. <p>In the case of non-anonymous rooms or if the recipient of the MUC archive has the right to access the sender real JID at the time of the query, the archive message will use extended message information in an &lt;x/&gt; element qualified by the '' namespace and containing an &lt;item/&gt; child with a 'jid' attribute specifying the occupant's full JID, as defined for non-anonymous room presence in &xep0045;. The archiving entity MUST strip any pre-existing &lt;x&gt; element from MUC messages (as MUC rooms are not required to do this).</p>
  533. <example caption='Server returns MUC messages'><![CDATA[
  534. <message id='iasd207' from='coven@chat.shakespeare.lit' to='hag66@shakespeare.lit/pda'>
  535. <result xmlns='urn:xmpp:mam:2' queryid='g27' id='34482-21985-73620'>
  536. <forwarded xmlns='urn:xmpp:forward:0'>
  537. <delay xmlns='urn:xmpp:delay' stamp='2002-10-13T23:58:37Z'/>
  538. <message xmlns="jabber:client"
  539. from='coven@chat.shakespeare.lit/firstwitch'
  540. id='162BEBB1-F6DB-4D9A-9BD8-CFDCC801A0B2'
  541. type='groupchat'>
  542. <body>Thrice the brinded cat hath mew'd.</body>
  543. <x xmlns=''>
  544. <item affiliation='none'
  545. jid='witch1@shakespeare.lit'
  546. role='participant' />
  547. </x>
  548. </message>
  549. </forwarded>
  550. </result>
  551. </message>
  552. <message id='iasd207' from='coven@chat.shakespeare.lit' to='hag66@shakespeare.lit/pda'>
  553. <result xmlns='urn:xmpp:mam:2' queryid='g27' id='34482-21985-73620'>
  554. <forwarded xmlns='urn:xmpp:forward:0'>
  555. <delay xmlns='urn:xmpp:delay' stamp='2002-10-13T23:58:43Z'/>
  556. <message xmlns="jabber:client"
  557. from='coven@chat.shakespeare.lit/secondwitch'
  558. id='90057840-30FD-4141-AA44-103EEDF218FC'
  559. type='groupchat'>
  560. <body>Thrice and once the hedge-pig whined.</body>
  561. <x xmlns=''>
  562. <item affiliation='none'
  563. jid='witch2@shakespeare.lit'
  564. role='participant' />
  565. </x>
  566. </message>
  567. </forwarded>
  568. </result>
  569. </message>
  570. ]]></example>
  571. </section3>
  572. <section3 topic="Pubsub Archives" anchor='business-storeret-pubsub-archives'>
  573. <p>A PubSub service offering MAM SHOULD store each of the items published to each node. When responding to MAM requests it MUST construct the message stanza within the &lt;forwarded&gt; element in the same manner as the notifications sent to subscribers for the item, except that specifying the 'from' 'to' and 'id' attributes are OPTIONAL. Pubsub items must be returned one per message stanza (i.e. there MUST NOT be multiple &lt;item&gt; elements within the &lt;items&gt; element).</p>
  574. <example caption='Server returns a pubsub messages'><![CDATA[
  575. <message id='iasd208' to='juliet@capulet.lit/chamber'>
  576. <result xmlns='urn:xmpp:mam:2' queryid='g28' id='28482-20987-73623'>
  577. <forwarded xmlns='urn:xmpp:forward:0'>
  578. <delay xmlns='urn:xmpp:delay' stamp='2010-07-10T23:08:25Z'/>
  579. <message xmlns="jabber:client">
  580. <event xmlns=''>
  581. <items node='princely_musings'>
  582. <item id='ae890ac52d0df67ed7cfdf51b644e901'>
  583. <entry xmlns=''>
  584. <title>Soliloquy</title>
  585. <summary>
  586. To be, or not to be: that is the question:
  587. Whether 'tis nobler in the mind to suffer
  588. The slings and arrows of outrageous fortune,
  589. Or to take arms against a sea of troubles,
  590. And by opposing end them?
  591. </summary>
  592. <link rel='alternate' type='text/html'
  593. href='http://denmark.lit/2003/12/13/atom03'/>
  594. <id>tag:denmark.lit,2003:entry-32397</id>
  595. <published>2003-12-13T18:30:02Z</published>
  596. <updated>2003-12-13T18:30:02Z</updated>
  597. </entry>
  598. </item>
  599. </items>
  600. </event>
  601. </message>
  602. </forwarded>
  603. </result>
  604. </message>]]></example>
  605. </section3>
  606. </section2>
  607. <section2 topic='IDs' anchor='business-ids'>
  608. <p>The IDs used within an archive MUST be unique per item stored and MUST NOT be reused, even if the original item with a given ID has since been removed from the archive. If a server provides multiple archives (e.g. many user archives, or many MUC archives), the IDs do not need to be unique across all of these archives unless the server also allows a single query to be run across multiple archives (e.g. searching of all MUC rooms), discussion of which is beyond the scope of this document. These IDs are strings that servers may construct in any manner, and clients must treat as opaque strings (e.g. there is no requirement for them to be numeric, sequenced or GUIDs).</p>
  609. </section2>
  610. <section2 topic='Client synchronization' anchor='sync'>
  611. <p>In addition to one-off queries, clients may use this protocol to synchronize a local archive with the server's archive. However
  612. because this protocol is detached from normal routing of messages, it is possible that a client will receive messages while trying
  613. to synchronize, which has the potential to cause duplicated messages. Resolving this is beyond the scope of this specification,
  614. but may instead be solved during the initial connection phase by using an alternative connection protocol such as &xep0386;.</p>
  615. </section2>
  616. </section1>
  617. <section1 topic='Archiving Preferences' anchor='prefs'>
  618. <p>Depending on implementation and deployment policies, a server MAY allow the user to have control
  619. over the server's archiving behaviour. This specification defines a basic protocol for this, and
  620. also allows a server to offer more advanced configuration to a user.</p>
  621. <section2 topic='Simple configuration' anchor='config'>
  622. <p>If the server supports and allows configuration of the preferences described below then it SHOULD implement the protocol defined
  623. in this section. This allows the user to retrieve and configure the following preferences:</p>
  624. <ul>
  625. <li>A list of JIDs that should always have messages to/from archived in the user's store.</li>
  626. <li>A list of JIDs that should never have messages to/from archived in the user's store.</li>
  627. <li>The default archiving behaviour (for JIDs in neither of the above lists).</li>
  628. </ul>
  629. <example caption='Retrieving archiving preferences'><![CDATA[
  630. <iq type='get' id='juliet2'>
  631. <prefs xmlns='urn:xmpp:mam:2'/>
  632. </iq>
  633. ]]></example>
  634. <p>The server replies with the user's current archiving preferences. The &lt;prefs&gt; element
  635. MUST be present and contain the current default archiving policy. The &lt;always&gt; and &lt;never&gt;
  636. MUST also be present (even if empty), and contain a list of JIDs enclosed in &lt;jid&gt; elements.</p>
  637. <example caption='Server responds with current preferences'><![CDATA[
  638. <iq type='result' id='juliet2'>
  639. <prefs xmlns='urn:xmpp:mam:2' default='roster'>
  640. <always/>
  641. <never/>
  642. </prefs>
  643. </iq>
  644. ]]></example>
  645. <p>It is also possible that the server may respond with a stanza error, for example the standard
  646. 'feature-not-implemented' (server does not support MAM configuration) defined in &rfc6120;.</p>
  647. <example caption='Server does not support archive configuration'><![CDATA[
  648. <iq type='error' id='juliet2'>
  649. <error type='cancel'>
  650. <feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
  651. </error>
  652. </iq>
  653. ]]></example>
  654. <p>To update the preferences, the client can simply send an iq stanza with a type of 'set':</p>
  655. <example caption='Updating archiving preferences'><![CDATA[
  656. <iq type='set' id='juliet3'>
  657. <prefs xmlns='urn:xmpp:mam:2' default='roster'>
  658. <always>
  659. <jid>romeo@montague.lit</jid>
  660. </always>
  661. <never>
  662. <jid>montague@montague.lit</jid>
  663. </never>
  664. </prefs>
  665. </iq>
  666. ]]></example>
  667. <p>The server then replies with the applied preferences (note that due to server policies these
  668. MAY be different to the preferences sent by the client):</p>
  669. <example caption='Server responds with updated preferences'><![CDATA[
  670. <iq type='result' id='juliet3'>
  671. <prefs xmlns='urn:xmpp:mam:2' default='roster'>
  672. <always>
  673. <jid>romeo@montague.lit</jid>
  674. </always>
  675. <never>
  676. <jid>montague@montague.lit</jid>
  677. </never>
  678. </prefs>
  679. </iq>
  680. ]]></example>
  681. <p>It is also possible for the server to respond with an error, for example (but not limited to)
  682. the standard 'feature-not-implemented' (the server does not support configuration of preferences),
  683. 'forbidden' (the user is not authorized to change their preferences) or 'not-allowed' (the server
  684. generally does not allow changing of configuration preferences).</p>
  685. <section3 topic='Default behaviour' anchor='config-default'>
  686. <p>If a JID is in neither the 'always archive' nor the 'never archive' list then whether it
  687. is archived depends on this setting, the default.
  688. </p>
  689. <p>The 'default' attribute of the 'prefs' element MUST be one of the following values:</p>
  690. <ul>
  691. <li>'always' - all messages are archived by default.</li>
  692. <li>'never' - messages are never archived by default.</li>
  693. <li>'roster' - messages are archived only if the contact's bare JID is in the user's roster.</li>
  694. </ul>
  695. </section3>
  696. <section3 topic='Always archive' anchor='config-always'>
  697. <p>The &lt;prefs/&gt; element MAY contain an &lt;always/&gt; child element. If present, it
  698. contains a list of &lt;jid/&gt; elements, each containing a single JID. The server SHOULD
  699. archive any messages to/from this JID (see 'JID matching').
  700. </p>
  701. <p>If missing from the preferences, &lt;always/&gt; SHOULD be assumed by the server to be an
  702. empty list.
  703. </p>
  704. </section3>
  705. <section3 topic='Never archive' anchor='config-never'>
  706. <p>The &lt;prefs/&gt; element MAY contain an &lt;never/&gt; child element. If present, it
  707. contains a list of &lt;jid/&gt; elements, each containing a single JID. The server SHOULD
  708. NOT archive any messages to/from this JID (see 'JID matching').
  709. </p>
  710. <p>If missing from the preferences, &lt;never/&gt; SHOULD be assumed by the server to be an
  711. empty list.
  712. </p>
  713. </section3>
  714. </section2>
  715. <section2 topic='Advanced configuration' anchor='advanced-config'>
  716. <p>In addition to this protocol, a server MAY offer more advanced configuration to the user
  717. through &xep0050;. Such an interface might, for example, allow the user to configure what
  718. types of messages to store, or set a limit on how long messages should remain in the
  719. archive.</p>
  720. <p>If supported, such a configuration command SHOULD be presented on the well-defined
  721. command node of "urn:xmpp:mam#configure".</p>
  722. </section2>
  723. <section2 topic='JID matching' anchor='match'>
  724. <section3 topic='General rules' anchor='match-rules'>
  725. <p>When comparing the message target JID against the user's roster (ie. when the user has
  726. set default='roster') the comparison MUST use the bare target JID (that is, stripped of
  727. any resource).
  728. </p>
  729. <p>For matching against entries in either the 'allow' or 'never' lists, for each listed
  730. JID:
  731. </p>
  732. <ul>
  733. <li>If the listed JID contains a resource, compare against the target JID as-is.</li>
  734. <li>If the listed JID has no resource (it is a bare JID) then first strip any resource
  735. from the target JID prior to comparison.
  736. </li>
  737. </ul>
  738. </section3>
  739. <section3 topic='Outgoing messages' anchor='match-out'>
  740. <p>For outgoing messages, the server MUST use the value of the 'to' attribute as the target JID.
  741. </p>
  742. </section3>
  743. <section3 topic='Incoming messages' anchor='match-in'>
  744. <p>For incoming messages, the server MUST use the value of the 'from' attribute as the target JID.
  745. </p>
  746. </section3>
  747. </section2>
  748. <section2 topic='Processing Hints' anchor='hints'>
  749. <p>Clients can use &xep0334; for signaling that they do not wish some messages to be stored in the archive.</p>
  750. <example><![CDATA[
  751. <message from='romeo@montague.lit/laptop' to='juliet@capulet.lit/laptop'>
  752. <body>V unir avtug'f pybnx gb uvqr zr sebz gurve fvtug</body>
  753. <no-store xmlns='urn:xmpp:hints'/>
  754. </message>
  755. ]]></example>
  756. </section2>
  757. </section1>
  758. <section1 topic='Determining support' anchor='support'>
  759. <p>If a server or other entity hosts archives and supports MAM queries, it MUST advertise
  760. the 'urn:xmpp:mam:2' feature in response to &xep0030; requests made to archiving JIDs
  761. (i.e. JIDs hosting an archive, such as users' bare JIDs):
  762. </p>
  763. <example caption='Client queries for server features'><![CDATA[
  764. <iq type='get' id='disco1' to='juliet@capulet.lit' from='juliet@capulet.lit/balcony'>
  765. <query xmlns=''/>
  766. </iq>
  767. ]]></example>
  768. <example caption='Server responds with features'><![CDATA[
  769. <iq type='result' id='disco1' from='juliet@capulet.lit' to='juliet@capulet.lit/balcony'>
  770. <query xmlns=''>
  771. ...
  772. <feature var='urn:xmpp:mam:2'/>
  773. ...
  774. </query>
  775. </iq>
  776. ]]></example>
  777. </section1>
  778. <section1 topic='Security Considerations' anchor='security'>
  779. <section2 topic='Data privacy' anchor='security-privacy'>
  780. <p>An archive generally consists of private conversations, and so
  781. a server MUST adequately protect an archive from unauthorized third-party
  782. access. For example authorized parties for a user's archive would likely include
  783. just the user, and a MUC archive for a private room might be restricted
  784. to room members. An implementation MAY choose to allow access to any archive
  785. by server administrators. If a client
  786. requests access to an archive is does not have permissions for the server MUST
  787. return an iq with type error, and the error condition SHOULD be 'forbidden'.</p>
  788. <p>A server SHOULD provide a mechanism for a user to disable archiving of
  789. messages with all or specific contacts, such as via the configuration
  790. protocol described in this document. This allows the user to prevent the
  791. archiving of potentially sensitive messages in the first place.</p>
  792. <p>A server MAY automatically prevent certain sensitive messages from being
  793. archived. How such messages are identified is beyond the scope of this
  794. specification, but technologies such as &xep0258; may be used, for example.</p>
  795. </section2>
  796. <section2 topic='Stanza IDs' anchor='security-stanza-ids'>
  797. <p>Entities that implement this specification must also adhere to the security requirements of XEP-0359.</p>
  798. </section2>
  799. <section2 topic='MUC message spoofing' anchor='security-muc-spoofing'>
  800. <p>This specification re-uses the &lt;x&gt; element from the '' namespace to convey information about the sender of a message in a MUC room. However this element is not sanitized by MUC services, so the archiving entity MUST strip any existing &lt;x&gt; element in the '' namespace from messages before archiving them (regardless of whether it adds in its own &lt;x&gt; element).</p>
  801. </section2>
  802. </section1>
  803. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  804. </section1>
  805. <section1 topic='Acknowledgements' anchor='acks'>
  806. <p>Many thanks to Dave Cridland, Kim Alvefur, Yann Leboulanger, Evgeny Khramtsov, Florian Schmaus, Lance Stout,
  807. Waqas Hussain and Daniel Gultsch for their input and feedback on this specification.</p>
  808. </section1>
  809. </xep>