diff --git a/xep-0280.xml b/xep-0280.xml index 05315943..379fc32d 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -329,7 +329,7 @@ -

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. To exclude a &MESSAGE; from being forwarded to other Carbons-enabled resources, the sending client add a <private/> element qualified by the namespace "urn:xmpp:carbons:2" as a child content element to the &MESSAGE; stanza.

+

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. To exclude a &MESSAGE; from being forwarded to other Carbons-enabled resources, the sending client must add a <private/> element qualified by the namespace "urn:xmpp:carbons:2" and a <no-copy/> hint according to &xep0334; as child content elements to the &MESSAGE; stanza.

Note: use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.

@@ -341,6 +341,7 @@ Neither, fair saint, if either thee dislike. 0e3141cd80894871a68e6fe6b1ec56fa + ]]> Neither, fair saint, if either thee dislike. 0e3141cd80894871a68e6fe6b1ec56fa + ]]>

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.