On Sun, Jul 10, 2011 at 9:15 PM, XMPP Extensions Editor <edi...@xmpp.org> wrote: > Version 0.2 of XEP-0280 (Message Carbons) has been released. > > Abstract: In order to keep all IM clients for a user engaged in a > conversation, outbound messages are carbon-copied to all interested resources. > > Changelog: Changed enabling and disabling to use separate elements rather > than attributes; ensured all elements in the examples have their namespaces > more explicitly defined; used message forwarding for carbon copies. (mm) > > Diff: http://xmpp.org/extensions/diff/api/xep/0280/diff/0.1/vs/0.2 > > URL: http://xmpp.org/extensions/xep-0280.html
I think: "The wrapping message SHOULD maintain the same 'type', 'from', and 'id' attribute values (if any), while the 'to' attribute SHOULD be the full JID of the resource receiving the copy." isn't right. The encapsulated message already has these data available - the encapsulating message should have attributes that reflect who is really sending/receiving the stanza (i.e. to=the client receiving the carbon, from=the server or the bare JID, unique id). /K
