Re: [Sipping] Multi-media messaging and SIP
Richard Barnes <rbarnes@bbn.com> Mon, 22 May 2006 15:23 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiCGB-0008S8-1S; Mon, 22 May 2006 11:23:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiCG9-0008Pe-Ga for sipping@ietf.org; Mon, 22 May 2006 11:23:53 -0400
Received: from mx12.bbn.com ([128.33.0.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiCG7-0005oe-74 for sipping@ietf.org; Mon, 22 May 2006 11:23:53 -0400
Received: from po2.bbn.com ([128.33.0.56]) by mx12.bbn.com with esmtp (Exim 4.60) (envelope-from <rbarnes@bbn.com>) id 1FiCG4-0002ep-6Q; Mon, 22 May 2006 11:23:49 -0400
Received: from [127.0.0.1] (col-lab-dhcp33-245-066.bbn.com [128.33.245.66]) by po2.bbn.com (8.11.6+Sun/8.10.2) with ESMTP id k4MFNmw27160; Mon, 22 May 2006 11:23:48 -0400 (EDT)
Message-ID: <4471D783.8080407@bbn.com>
Date: Mon, 22 May 2006 11:23:47 -0400
From: Richard Barnes <rbarnes@bbn.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: "Jesus Javier Arauz (E2/EEM)" <jesus.javier.arauz@ericsson.com>
Subject: Re: [Sipping] Multi-media messaging and SIP
References: <33D71F0FC0684C4C8A3BB76989EDED9C01B82B3B@eesmdmw020.eemea.ericsson.se>
In-Reply-To: <33D71F0FC0684C4C8A3BB76989EDED9C01B82B3B@eesmdmw020.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org
> However, when a GPRS user sends an MMS to multiple destinations, the > interworking function must take care of initiating the SIP and MSRP > sessions, send the message over all sessions and then releasing those > sessions. The same goes for IMPS. Beacuse MSRP is inherently session-oriented, I don't think you're going to get around having to initiate and release SIP/MSRP sessions. To simplify the internetworking function, perhaps what needs to be done is to define a way for MSRP relays to act as URI-list services. That way, the internetworking function could: 1. Send a forked INVITE to all recipients 2. Gather responses and construct URI-list 3. Send message and URI-list to URI-list Service The URI-list Service could then forward the message to all the recipients and relay MSRP REPORTs back to the internetworking function, who could then send BYE requests to close the SIP sessions. Given the constraints that MSRP is session-oriented (hence requires initiation/release), I think that's about as simple as it can get. (Actually, adding such a URI-list capability to MSRP relays seems like a good idea in general, since it would simplify the implementation of multi-party chat.) Hope this helps, --Richard > > I think it would be advantageous to retro-fit session-based messaging > with the same capability as short messaging. One possible alternative > would be to allow the same MIME body defined in > draft-ietf-sipping-uri-list-message-07 in INVITE requests for MSRP > sessions. However this may not seem appropriate since it impacts a > rather basic message of the SIP specification. Any other alternative > would require defining a new mechanism specific for long, multi-media > messages, like e.g. content indirection. > > I wonder if there've been some discussions on this issue already? What's > the oppinion of the sipping community on it? > > Best regards, > /Javier Arauz > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping > This list is for NEW development of the application of SIP > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sip@ietf.org for new developments of core SIP _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] Multi-media messaging and SIP Jesus Javier Arauz (E2/EEM)
- Re: [Sipping] Multi-media messaging and SIP Dale R. Worley
- Re: [Sipping] Multi-media messaging and SIP Richard Barnes
- [Sipping] Re: Multi-media messaging and SIP Jesus Javier Arauz (E2/EEM)