[Simple] Re: MSRP chat and IMDN

Hi Jussi:

I agree that at some point in time we need to synchronize MSRP chat with 
IMDN, and it is not our intention to specify a mechanism if we can reuse 
IMDN.

BUT: draft-burger-simple-imdn-03 does not provide a mechanism to inform 
whether a message has been delivered or not, instead, the draft relies 
on the protocol (MSRP). Instead, draft-khartabil-simple-im-receipts-00 
provides a mechanism for delivery receipt. So, depending on what the 
final IMDN mechanism is able to provide, we will need or not to extend MSRP.

BR,

      Miguel

Jussi K. Virtanen wrote:
> Hi,
> 
> In draft-niemi-simple-chat-04, a new status code, 427, is
> specified for use in a situation in which the MSRP switch
> is unable to forward a message to some of the intended
> participants.
> 
> I think it would be more appropriate to use, for example,
> IMDN (draft-burger-simple-imdn-03) for this purpose because
> the forwarding mechanism in the MSRP switch is based on CPIM
> instead of MSRP.

> 
> IMDN is anyway needed if a participant wishes to request
> delivery notification. Delivery status in MSRP cannot be
> used because each participant has its own MSRP session with
> the MSRP switch.
> 
> 
> Best Regards,
> 
> --
> Jussi K. Virtanen

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.an.garcia@openlaboratory.net
Nokia Research Center      Helsinki, Finland

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple