moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00
Code Issues Releases Wiki Activity

XEP-0280: Bump version to 0.11.0

Browse Source 
Fix confusing paragraph with a non-RFC2119 "must"
Also make quotes consistent in examples
This commit is contained in:
Sam Whited 2017-01-28 11:47:35 -06:00
parent b3dee57aaf
commit 78ce13c1e4
1 changed files with 21 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
xep-0280.xml
View File

@ -40,6 +40,14 @@
<email>linuxwolf@outer-planes.net</email>
<jid>linuxwolf@outer-planes.net</jid>
</author>
<revision>
<version>0.11.0</version>
<date>2017-01-27</date>
<initials>gl (XEP Editor: ssw)</initials>
<remark>
<p>Add &lt;no-copy/&gt; hint.</p>
</remark>
</revision>
<revision>
<version>0.10.1</version>
<date>2016-02-16</date>
@ -329,9 +337,18 @@
</section1>
<section1 topic='Avoiding Carbons for a single message' anchor='avoiding'>
<p>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 &lt;private/&gt; element qualified by the namespace "urn:xmpp:carbons:2" and a &lt;no-copy/&gt; hint according to &xep0334; as child content elements to the &MESSAGE; stanza.</p>
<p>
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 &lt;private/&gt; element qualified by
the namespace "urn:xmpp:carbons:2" and a &lt;no-copy/&gt; hint as described
in &xep0334; as child elements of the &MESSAGE; stanza.
</p>
<p><strong>Note:</strong> use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.</p>
<p><strong>Note:</strong> use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.</p>
<example caption='Romeo sends to Juliet, excluding Carbons'><![CDATA[
<message xmlns='jabber:client'
@ -341,7 +358,7 @@
<body>Neither, fair saint, if either thee dislike.</body>
<thread>0e3141cd80894871a68e6fe6b1ec56fa</thread>
<private xmlns='urn:xmpp:carbons:2'/>
<no-copy xmlns="urn:xmpp:hints"/>
<no-copy xmlns='urn:xmpp:hints'/>
</message>]]></example>
<example caption='Romeo&apos;s server delivers original message, without creating Carbon copies'><![CDATA[
@ -352,7 +369,7 @@
<body>Neither, fair saint, if either thee dislike.</body>
<thread>0e3141cd80894871a68e6fe6b1ec56fa</thread>
<private xmlns='urn:xmpp:carbons:2'/>
<no-copy xmlns="urn:xmpp:hints"/>
<no-copy xmlns='urn:xmpp:hints'/>
</message>]]></example>
<p>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 &lt;private/&gt; element before delivering to the recipient.</p>
<p><strong>Note:</strong> if the private &MESSAGE; stanza is addressed to a bare JID, the receiving server still delivers it according to <cite>RFC 6121</cite>. This might result in a copy being delivered to each resource for the recipient, which effectively negates the behavior of the &lt;private/&gt; element for recipients.</p>