Re: [Stox] Review on -im

[Peter Saint-Andre <[e-mail]>]

On 8/1/13 10:01 AM, Saúl Ibarra Corretgé wrote:
> Hi Markus,
> 
> On Jul 31, 2013, at 6:24 PM, [e-mail] wrote:
> 
>> Hi Saul, Peter,
>>
>> Saúl Ibarra Corretgé wrote:
>>>>
>>>> Well, the sender might really really want to know if the message was
>>>> delivered to the recipient. :-)
>>>>
>>>
>>> Unfortunately there is no way to do that with a SIP MESSAGE. Unless we
>>> invent a special payload for acknowledging reception of a given SIP
>>> MESSAGE, but I think that is really out of the scope of what we are doing in
>>> the IM document.
>>>
>>
>> Please take a look at RFC 5438 (http://datatracker.ietf.org/doc/rfc5438/) and see if it applies to what would be required.
>>
> 
> I had completely forgotten about this one, thanks for the pointer! Indeed this could be used to map receipts for SIP MESSAGE. Now, this is in a different spec to that which defines SIP MESSAGE, whereas MSRP reporting is baked into the protocol itself. Personally, I would define th empaling for MSRP, because REPORT is part of the protocol, and leave it out from IM, at least for the moment.
> 
> Peter added this to his slides, so I guess we'll discuss it in today's meeting.

I didn't add RFC 5438 to my slides, though, because I too had forgotten
about it.

One piece of data that would be helpful is to know how widely RFC 5438
is implemented, in comparison to RFC 4975. IMHO what we're trying to do
in this WG is to describe practical interworking between SIP and XMPP.
If a particular SIP or XMPP method is not widely implemented, I say that
we don't talk about it because it's purely theoretical (e.g., I removed
everything about XEP-0155). Thus some input on that point would be
helpful here.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/