Difference between revisions of "XEP-Remarks/XEP-0184: Message Delivery Receipts"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{remarks}} | |||
= Message 'type' of the receipt = | = Message 'type' of the receipt = | ||
Latest revision as of 20:43, 17 April 2020
|
This is a page for information about XEP-Remarks/XEP-0184: Message Delivery Receipts, including errata, comments, questions, and implementation experience. |
Message 'type' of the receipt
It's underspecified in xep184 what the type of the message with the received extension should be. Consensus seems to be that it must (should?) match the type of the message with the receipt request.
See
- http://mail.jabber.org/pipermail/standards/2015-February/029647.html
- http://mail.jabber.org/pipermail/standards/2014-January/028479.html
- https://community.igniterealtime.org/thread/55160
Suggestion
Variant 1
Use the message type of the request, because 1. as Kurt points out, if the type is groupchat it must match and 2. then the receipt can be easily embedded in the response message containing also a 'body' element. Using a fixed type would break the semantic of a conversation, e.g. message with request of type 'chat', reply with body and receipt of type 'normal'.
Add to XEP-184 5.4.:
The message type of an ack message MUST match the type of the message with the related receipt request, if it's of type 'groupchat'. It SHOULD match the type otherwise. A receiving entity MUST NOT make any assumptions about the message type of an ack message.
Variant 2
Add to XEP-184 5.4.:
The message type of an ack message SHOULD be 'normal'. A receiving entity MUST NOT make any assumptions about the message type of an ack message.
Variant 3
Add to XEP-184 5.4.:
The message type of an ack message MUST be 'normal'.