This extension of Message Archive Management (XEP-0313) [1] allows XMPP clients to subscribe to MAM archives and to carbon copy/fork messages to all connected resources of the receiving XMPP entity, removing the need for Message Carbons (XEP-0280) [2]. After a client is subscribed to an archive, it will receive notifications when a new <message/> was added to the archive, which include the added <message/>.
An entity advertises support for this protocol by including the 'urn:xmpp:mam:sub:0' feature in its service discovery information features as specified in Service Discovery (XEP-0030) [3].
<iq xmlns='jabber:client'
from='romeo@montague.example/garden'
id='info1'
to='montague.example'
type='get'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
<iq xmlns='jabber:client'
from='montague.example'
id='info1'
to='romeo@montague.example/garden'
type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='urn:xmpp:mam:sub:0'/>
...
</query>
</iq>When a client wants to receive notifications about messages being added to a MAM archive, it does subscripe to the archive by sending an <iq/> of type 'set' containing a child element <subscribe/> qualified by the 'urn:xmpp:mam:sub:0' namespace.
<iq xmlns='jabber:client'
from='romeo@montague.example/garden'
id='sub1'
type='set'>
<subscribe xmlns='urn:xmpp:mam:sub:0'/>
</iq>The server will respond with an <iq/>-result when the client was successfully subscribed to the archive.
<iq xmlns='jabber:client'
from='romeo@montague.example/garden'
id='sub1'
type='result'/>At any point, clients can unsubscribe from the MAM archive by sending an <iq/> of type 'set' containing a child element <unsubscribe/> qualified by the 'urn:xmpp:mam:sub:0' namespace.
<iq xmlns='jabber:client'
from='romeo@montague.example/garden'
id='unsub1'
type='set'>
<unsubscribe xmlns='urn:xmpp:mam:sub:0'/>
</iq>The server will respond with an <iq/>-result when the client was successfully unsubscribed from the archive.
<iq xmlns='jabber:client'
from='romeo@montague.example/garden'
id='unsub1'
type='result'/>Every time a message is added to the MAM archive, a MAM notification MUST be sent to entities subscribed to the archive, regardless of the message type or content. Note that this implies that clients, which are subscribed to the MAM archive and are also the final recipient of a <message/>, will receive such a <message/> twice: In the first place because of the stanza routing rules defined in RFC 6120 [4] and RFC 6121 [5], and also as content of the resulting MAM archive notification.
Each notification is send as <message/> of type 'normal' from the clients bare JID containing a <mamsub/> extension, which SHOULD contain the a <message-id/> element as defined in XEP-MID (TODO XEP number) and MUST contain exaclty one <forwarded> element as defined in Stanza Forwarding (XEP-0297) [6] containing the original message.
The value of the 'id' attribute found in the <message-id/> element is the unique and stable ID of the message, which unambigously identifies the message withing the MAM archive.
<message xmlns='jabber:client'
from='romeo@montague.example'
to='romeo@montague.example/home'>
<mamsub xmlns='urn:xmpp:mam:sub:0'>
<messsage-id xmlns='urn:xmpp:mid:0' id='de305d54-75b4-431b-adb2-eb6b9e546013'/>
<forwarded xmlns='urn:xmpp:forward:0'>
<message xmlns='jabber:client'
from='juliet@capulet.example/balcony'
to='romeo@montague.example/garden'
type='chat'>
<body>What man art thou that, thus bescreen'd in night, so stumblest on my counsel?</body>
<thread>0e3141cd80894871a68e6fe6b1ec56fa</thread>
</message>
</forwarded>
</mamsub>
</message>
As the notifications defined in this document contain full <message/> stanzas, it is important for implementations to take care that the receiving entities of such notifications are allowed to see that information. This usually means they receiving entities share the same bare JID with the intended receiver. (TODO wording)
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [7].
The XMPP Registrar [8] includes 'urn:xmpp:mam:sub:0' in its registry of protocol namespaces (see <https://xmpp.org/registrar/namespaces.html>).
If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.
REQUIRED for protocol specifications.
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright (c) 1999 - 2014 by the XMPP Standards Foundation (XSF).
Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <http://xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).
The HTML representation (you are looking at) is maintained by the XSF. It is based on the YAML CSS Framework, which is licensed under the terms of the CC-BY-SA 2.0 license.
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <editor@xmpp.org>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
1. XEP-0313: Message Archive Management <https://xmpp.org/extensions/xep-0313.html>.
2. XEP-0280: Message Carbons <https://xmpp.org/extensions/xep-0280.html>.
3. XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>.
4. RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core <http://tools.ietf.org/html/rfc6120>.
5. RFC 6121: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence <http://tools.ietf.org/html/rfc6121>.
6. XEP-0297: Stanza Forwarding <https://xmpp.org/extensions/xep-0297.html>.
7. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
8. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/
First draft.
END