moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

1.1rc1

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3992 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2010-02-25 05:30:18 +00:00
parent 33aea4e65b
commit 2b200b432c
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
xep-0184.xml
View File

@ -11,6 +11,7 @@
&LEGALNOTICE;
<number>0184</number>
<status>Draft</status>
<interim/>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
@ -27,6 +28,12 @@
</schemaloc>
&stpeter;
&hildjj;
<revision>
<version>1.1rc1</version>
<date>in progress, last updated 2010-02-24</date>
<initials>psa</initials>
<remark><p>Relaxed the business rules to allow inclusion of receipt requests even to the bare JID and even if the sender does not yet know if the intended recipient supports this protocol.</p></remark>
</revision>
<revision>
<version>1.0</version>
<date>2007-09-26</date>
@ -114,14 +121,12 @@
<section1 topic='Business Rules' anchor='rules'>
<p>The following business rules apply:</p>
<ol start='1'>
<li><p>A sender SHOULD NOT include a request for message receipts when sending a message to the bare JID &LOCALBARE; of the recipient, only when sending to a full JID &LOCALFULL;.</p></li>
<li><p>A sender SHOULD NOT include a request for message receipts unless it knows (via &xep0030; or &xep0115;) that the intended recipient supports the protocol described herein or unless the use of message receipts is negotiated via &xep0155;.</p></li>
<li><p>A sender SHOULD include an 'id' attribute on the message so that the sender can properly track the receipt.</p></li>
<li><p>If receipts are desired, a sender SHOULD include a request for message receipts on all messages, no matter whether sending to the bare JID &LOCALBARE; of the recipient or the full JID &LOCALFULL;.</p></li>
<li><p>A sender MUST include an 'id' attribute on the message so that the sender can properly track the receipt.</p></li>
</ol>
<p>Naturally, message receipts can be combined with the rules specified in <cite>Advanced Message Processing</cite> (e.g., the deliver rule) for more complete reporting.</p>
</section1>
<section1 topic='Determining Support' anchor='disco'>
<p>If a sender wishes to request message receipts, it SHOULD first determine whether the intended recipient supports message receipts. This can be done directly via <cite>Service Discovery</cite> or indirectly via <cite>Entity Capabilities</cite>.</p>
<p>If an entity supports message receipts, it MUST report that by including a service discovery feature of "urn:xmpp:receipts" in response to disco#info requests:</p>
<example caption="Initial Service Discovery information request"><![CDATA[
<iq from='northumberland@shakespeare.lit/westminster'
@ -137,12 +142,11 @@
to='northumberland@shakespeare.lit/westminster'
type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='urn:xmpp:receipts'/>
...
</query>
</iq>
]]></example>
<p>A sender MAY include a request for message receipts even if it has not been able to determine if the intended recipient supports message receipts. This can be done directly via <cite>Service Discovery</cite> or indirectly via <cite>Entity Capabilities</cite>.</p>
</section1>
<section1 topic='Negotiation' anchor='neg'>
<p>Two entities MAY negotiate the use of message receipts for a given session using <cite>Stanza Session Negotiation</cite>. The parameter to be negotiated is named "urn:xmpp:receipts". Its use is illustrated in the following examples.</p>