RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

"Robert Hagens" <rhagens@envysion.com> Mon, 06 February 2006 15:02 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F67sR-0005Pv-GW; Mon, 06 Feb 2006 10:02:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F67sJ-0005Os-VY for mmusic@megatron.ietf.org; Mon, 06 Feb 2006 10:02:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25142 for <mmusic@ietf.org>; Mon, 6 Feb 2006 10:00:02 -0500 (EST)
Received: from mail.icgcomm.com ([204.32.218.26] helo=denexg15.icgcomm.com) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F684J-0001Df-Jk for mmusic@ietf.org; Mon, 06 Feb 2006 10:14:21 -0500
Received: from Hagens1 ([10.138.85.33]) by denexg15.icgcomm.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Feb 2006 08:01:13 -0700
From: Robert Hagens <rhagens@envysion.com>
To: 'Colin Perkins' <csp@csperkins.org>, 'Teodora Guenkova-Luy' <teodora.guenkova-luy@uni-ulm.de>
Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
Date: Mon, 06 Feb 2006 08:02:38 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYrBCNgaqZ7c4hlTr26PndhmTZ2NwAKbLIQ
In-Reply-To: <C5BEB600-A8B3-4865-A1B2-94EDCD178E6C@csperkins.org>
Message-ID: <DENEXG15zzlLT8UeYM700000565@denexg15.icgcomm.com>
X-OriginalArrivalTime: 06 Feb 2006 15:01:13.0356 (UTC) FILETIME=[2C0394C0:01C62B2E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org, Osher.Hmelnizky@audiocodes.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

The other non-standard aspect of SIP/RTSP is that there is a good chuck of
overlap between SIP and RTSP. If you (for example) negotiate the SDP with
SIP, you really don't need to bother with the DESCRIBE and SETUP of RTSP.
After the SIP negotiation, you're ready to PLAY. This leads one to question
if all of the complexity of RTSP is required in these cases; a simpler
version of media control being desirable.

Rob

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
Colin Perkins
Sent: Monday, February 06, 2006 2:57 AM
To: Teodora Guenkova-Luy
Cc: mmusic@ietf.org; Osher.Hmelnizky@audiocodes.com
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

SDP has the concept of "m=control ..." to signal other control  
sessions. If one were to define how to signal RTSP sessions could be  
setup using SIP, that would likely be the appropriate way to do it.

This subject comes up regularly - maybe it would be appropriate for  
someone to write a draft fleshing out the details?

Colin



On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
> SIP and RTSP are two different sessions. Their frameworks do not  
> exclude the scenario that both of them shall be synchronised,  
> however, there is no existing solution on such synchronisation. You  
> can synchronize SIP and RTSP only at presentation level (i.e. SDP),  
> like done for SIP and MRCP, as at session level SIP and RTSP are  
> different instances that are not aware of each other. You could  
> "misuse" the SDP SIP/MRCP attribute "a=channel:xxx" with your own  
> parameters for RTSP, or use the SDP "i=" line also with your own  
> paramentes, or define your own attribute line, e.g.  
> "a=stacksynch:whatever". However, all these are non-standard  
> solutions.
> KR,
> Teodora
>
> mmusic-request@ietf.org wrote:
>
>>
>> Message: 1
>> Date: Sun, 5 Feb 2006 09:41:06 +0200
>> From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Burger, Eric" <eburger@brooktrout.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	 
>> <79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi,
>>
>>
>> What I'm trying to say is: why can't I use SIP for the call
>> establishment and RTSP for the stream control. How can synchronize  
>> two
>> protocols on the MRF side?
>> On the client side it is no problem, but server side should be aware
>> that two sessions are interconnected to the one specific call.
>>
>> Such synchronization I saw in the SIP/MRCP draft
>> (draft-ietf-speechsc-mrcpv2-09).
>>
>>
>> Thanks a lot
>>
>>
>> Osher
>>
>>
>> ________________________________
>>
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It
>> is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>> sessions.
>>
>>
>> ________________________________
>>
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf
>> Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>> synchronize the SIP and MRCP Sessios, defined
>>
>> a=channel:xxx
>>
>>
>> as part of application SDP.
>>
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the
>> Media Server layer without any indication.
>>
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync
>> between SIP and RTSP Streams.
>>
>>
>> Thanks a lot.
>>
>>
>> Osher
>>
>>
>>
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: http://www1.ietf.org/pipermail/mmusic/attachments/ 
>> 20060205/0ce380c0/attachment.htm
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 5 Feb 2006 08:17:22 -0500
>> From: "Burger, Eric" <eburger@brooktrout.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	<330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>> Content-Type: text/plain;	charset="iso-8859-1"
>>
>> That is something totally different and explicitly outside the  
>> scope of MRCPv2.  What you want is something like the mediactrl  
>> work (not chartered).  Search the I-D directory for mediactrl.  To  
>> subscribe, send 'subscribe mediactrl' to  
>> majordomo@lists.ubiquitysoftware.com
>>
>> ________________________________________
>> From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com]  
>> Sent: Sunday, February 05, 2006 2:41 AM
>> To: Burger, Eric
>> Cc: mmusic@ietf.org
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> Hi,
>>
>> What I'm trying to say is: why can't I use SIP for the call  
>> establishment and RTSP for the stream control. How can synchronize  
>> two protocols on the MRF side? On the client side it is no  
>> problem, but server side should be aware that two sessions are  
>> interconnected to the one specific call.
>> Such synchronization I saw in the SIP/MRCP draft (draft-ietf- 
>> speechsc-mrcpv2-09).
>>
>> Thanks a lot
>>
>> Osher
>>
>> ________________________________________
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard)  
>> has two, distinct sessions.
>>
>> ________________________________________
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order  
>> to synchronize the SIP and MRCP Sessios, defined
>>       a=channel:xxx
>>       as part of application SDP.
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the Media Server layer without any indication.
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync between SIP and RTSP Streams.
>>
>> Thanks a lot.
>>
>> Osher
>>
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> End of mmusic Digest, Vol 22, Issue 3
>> *************************************
>>
>
> -- 
> -----------------------------------------
> Teodora Guenkova-Luy
>
> Dept. Distributed Systems, University of Ulm, Oberer Eselsberg,  
> 89069 Ulm, Germany
>
> Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142
>
> e-Mail: teodora.guenkova-luy@uni-ulm.de
>
> Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/
> -----------------------------------------
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


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


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