[Simple] Re: MSRP chat and IMDN
Miguel Garcia <Miguel.An.Garcia@nokia.com> Mon, 20 March 2006 10:51 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLHzR-0003YL-EM; Mon, 20 Mar 2006 05:51:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLHzP-0003YG-Nz for simple@ietf.org; Mon, 20 Mar 2006 05:51:55 -0500
Received: from mgw-ext04.nokia.com ([131.228.20.96]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLHzO-0005AN-9f for simple@ietf.org; Mon, 20 Mar 2006 05:51:55 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k2KAncWo012673; Mon, 20 Mar 2006 12:49:40 +0200
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Mar 2006 12:50:52 +0200
Received: from [127.0.0.1] ([172.21.34.185]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 20 Mar 2006 12:50:53 +0200
Message-ID: <441E890C.6010207@nokia.com>
Date: Mon, 20 Mar 2006 12:50:52 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Jussi K. Virtanen" <jussi.k.virtanen@gmail.com>
References: <95d59cef0603192353u546b7e88y15be8a50dded2233@mail.gmail.com> <441E6901.2080902@nokia.com> <95d59cef0603200150j732f0c9dh34c83a1cee4c151@mail.gmail.com>
In-Reply-To: <95d59cef0603200150j732f0c9dh34c83a1cee4c151@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Mar 2006 10:50:53.0018 (UTC) FILETIME=[288B63A0:01C64C0C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Eric Burger <eburger@brooktrout.com>, IETF SIMPLE <simple@ietf.org>
Subject: [Simple] Re: MSRP chat and IMDN
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
Errors-To: simple-bounces@ietf.org
Hi Jussi: Well, the case we are considering is not a full error, because some of the URIs are reachable, others aren't. I guess the mechanism could be extended to indicate "partial delivery", and include a list of URIs for which delivery failed. Certainly, we need a bit more of discussion on this, but first we (SIMPLE) need to take a determination of which path to follow (Eric's or Hisham's draft). BR, Miguel Jussi K. Virtanen wrote: > Hi Miguel, > > On 2006-03-20, Miguel Garcia <Miguel.An.Garcia@nokia.com> wrote: >> 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. > > Couldn't the "first-recipient" mechanism of IMDN, described in > Section 9.3.1 of draft-burger-simple-imdn-03, be extended from > B2BUAs to MSRP switches as well? An excerpt from the section: > > o If the B2BUA forwards the message, it SHOULD return an > "processed" IMDN, mindful of the privacy considerations > enumerated in Section 4. > o If there was an error processing the message, the B2BUA > SHOULD return an "error" IMDN, mindful of the privacy > considerations enumerated in Section 4. > > I believe an "error" IMDN could be a substitute for a 427 > response. > > draft-khartabil-simple-im-receipts-00 explicitly prohibits > requests of delivery receipts for messages that are transferred > on top of MSRP (Section 7.1.1.). I see that as a problem because > the delivery status in MSRP is bound to an MSRP session but > one CPIM message can traverse on its way over multiple MSRP > sessions, as it does in MSRP chat (draft-niemi-simple-chat-04). > > > BR, > > -- > 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
- [Simple] MSRP chat and IMDN Jussi K. Virtanen
- [Simple] Re: MSRP chat and IMDN Miguel Garcia
- [Simple] Re: MSRP chat and IMDN Jussi K. Virtanen
- [Simple] Re: MSRP chat and IMDN Miguel Garcia
- [Simple] RE: MSRP chat and IMDN Burger, Eric