From 78ce13c1e4baed8d37a2f73a261e61a42bc652cd Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Sat, 28 Jan 2017 11:47:35 -0600 Subject: [PATCH] XEP-0280: Bump version to 0.11.0 Fix confusing paragraph with a non-RFC2119 "must" Also make quotes consistent in examples --- xep-0280.xml | 25 +++++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/xep-0280.xml b/xep-0280.xml index 379fc32d..e1f555a1 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -40,6 +40,14 @@ linuxwolf@outer-planes.net linuxwolf@outer-planes.net + + 0.11.0 + 2017-01-27 + gl (XEP Editor: ssw) + +

Add <no-copy/> hint.

+ + 0.10.1 2016-02-16 @@ -329,9 +337,18 @@ -

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.

+

+ 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. +

-

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.

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.