From bea49ecf1ef9aa863468e1550ae7902abb51d43b Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 26 Sep 2007 19:08:41 +0000 Subject: [PATCH] 1.0 Draft git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1236 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0184.xml | 63 ++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 51 insertions(+), 12 deletions(-) diff --git a/xep-0184.xml b/xep-0184.xml index e97a6186..4c4f4023 100644 --- a/xep-0184.xml +++ b/xep-0184.xml @@ -10,7 +10,7 @@ This document specifies an XMPP protocol extension for message receipts. &LEGALNOTICE; 0184 - Proposed + Draft Standards Track Standards Council @@ -21,9 +21,18 @@ XEP-0022 (in part) - TO BE ASSIGNED + receipts + + http://www.xmpp.org/schemas/receipts.xsd + &stpeter; &hildjj; + + 1.0 + 2007-09-26 + psa +

Per a vote of the XMPP Council, advanced to Draft.

 + 0.4 2007-05-30 @@ -74,7 +83,7 @@

Note: This document explicitly does not define a protocol for "guaranteed delivery", since that term (like "security") means different things to different people. Instead, we define a more focused protocol that addresses the need for message receipts, thus solving one problem that falls under the heading of "guaranteed delivery".

-

In order to make it possible for senders to request and for recipients to generate message receipts, we define a dedicated protocol extension qualified by the 'http://www.xmpp.org/extensions/xep-0184.html#ns' namespace &NSNOTE;.

+

In order to make it possible for senders to request and for recipients to generate message receipts, we define a dedicated protocol extension qualified by the 'urn:xmpp:receipts' namespace &NSNOTE;.

There are two allowable elements in this namespace:

  • <request/> -- included by a sending entity that wishes to know if the message has been received.
    • @@ -88,7 +97,7 @@ id='richard2-4.1.247' to='kingrichard@royalty.england.lit/throne'> My lord, dispatch; read o'er these articles. - + ]]>

    The recipient shall generate a receipt if and only if it supports the protocol defined herein and it is configured to return receipts, either globally or for this recipient (otherwise it MUST NOT return a receipt and SHOULD NOT return an error).

    @@ -97,7 +106,7 @@ from='kingrichard@royalty.england.lit/throne' id='richard2-4.1.247' to='northumberland@shakespeare.lit/westminster'> - + ]]>

    The <received/> element SHOULD be the only child of the &MESSAGE; stanza and MUST mirror the 'id' of the sent message.

    @@ -113,7 +122,7 @@

    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 Service Discovery or indirectly via Entity Capabilities.

    -

    If an entity supports message receipts, it MUST report that by including a service discovery feature of "http://www.xmpp.org/extensions/xep-0184.html#ns" in response to disco#info requests &NSNOTE;:

    +

    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 &NSNOTE;:

    ... - + ... ]]>     -

    Two entities MAY negotiate the use of message receipts for a given session using Stanza Session Negotiation. The parameter to be negotiated is named "http://www.xmpp.org/extensions/xep-0184.html#ns" &NSNOTE;. Its use is illustrated in the following examples.

    +

    Two entities MAY negotiate the use of message receipts for a given session using Stanza Session Negotiation. The parameter to be negotiated is named "urn:xmpp:receipts" &NSNOTE;. Its use is illustrated in the following examples.

    + var='urn:xmpp:receipts'> 0 @@ -175,7 +184,7 @@ true - + 1 @@ -194,7 +203,7 @@     -

    Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0184.html#ns"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.

    +

    The ®ISTRAR; includes "urn:xmpp:receipts" in its registry of protocol namespaces (see &NAMESPACES;).

    &xep0068; defines a process for standardizing the fields used within Data Forms qualified by a particular namespace, and the XMPP Registrar maintains a registry of such fields (see &FORMTYPES;). The Registrar shall add the following field for use in Stanza Session Negotiation forms:

    @@ -202,13 +211,43 @@ urn:xmpp:ssn ]]>     + + + + + + + + The protocol documented by this schema is defined in + XEP-0184: http://www.xmpp.org/extensions/xep-0184.html + + + + + + + + + + + + + + + ]]> +

    Thanks to Joe Kemp and Kevin Smith for their input.