[Standards] Message-IDs

Florian Schmaus flo at geekplace.eu
Tue Feb 13 22:23:13 UTC 2018

On 13.02.2018 21:42, Simon Friedberger wrote:
> On 13.02.2018 17:57, Simon Friedberger wrote:
>>>     C2. According to Daniel it is not clear which ID should be used when
>>>         referencing things. In other words if he gets a delivery receipt
>>> for an
>>>         ID the client might have based that on the origin-ID or the
>>> message-ID.
>> Delivery receipts predate xep359 so it is safe to say that the intention
>> is that delivery receipts use rfc6120-ids. While it is IMHO obvious from
>> reading xep184 that it is based on rfc6120-ids, it can't hurt to specify
>> this more explicitly.
> But looking at https://xmpp.org/extensions/xep-0045.html#message
> the message-ID seems to be rewritten to different values for different
> recipients.
> How can a client who gets a delivery receipt with such an ID figure out
> which
> message it is for?

You can not reliable figure it out with the current specifications. One
possibly option is to extend xep184 receipts to (optionally) include
xep359 IDs. Maybe that would even be a backwards compatible change, e.g.
clients could check for the xep359 ID in the receipt and fall back to
the rfc6120 ID.

- Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 642 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180213/462f43e9/attachment.sig>

More information about the Standards mailing list