Some clients might want to avoid Carbons on a single message, while still keeping all of the other semantics of Carbon support. - This might be useful for clients sending end-to-end encrypted messages, for - example. - The sending client MAY exclude a &MESSAGE; from being forwarded to other - Carbons-enabled resources, by adding a <private/> element qualified by - the namespace "urn:xmpp:carbons:2" and a <no-copy/> hint as described - in &xep0334; as child elements of the &MESSAGE; stanza. + This might be useful for clients sending end-to-end encrypted messages.
-Note: use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.
+Note: + Use of the private mechanism might lead to partial conversations on other devices. This is the intended effect. + If the private &MESSAGE; stanza is addressed to a bare JID, the receiving server still delivers it according to RFC 6121. This might result in a copy being delivered to each resource for the recipient, which effectively negates the behavior of the <private/> element for recipients.
The sending server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resources of the sender. The receiving server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resource of the recipient, and SHOULD remove the <private/> element before delivering to the recipient.
-Note: if the private &MESSAGE; stanza is addressed to a bare JID, the receiving server still delivers it according to RFC 6121. This might result in a copy being delivered to each resource for the recipient, which effectively negates the behavior of the <private/> element for recipients.