Re: [siprec] Can an MS object span several CSs in a CSG?

"Parthasarathi R (partr)" <partr@cisco.com> Wed, 25 May 2011 07:47 UTC

Return-Path: <partr@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33465E06BE for <siprec@ietfa.amsl.com>; Wed, 25 May 2011 00:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.383
X-Spam-Level:
X-Spam-Status: No, score=-10.383 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id keQXC+HXWhlU for <siprec@ietfa.amsl.com>; Wed, 25 May 2011 00:47:40 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 89154E06B2 for <siprec@ietf.org>; Wed, 25 May 2011 00:47:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=7076; q=dns/txt; s=iport; t=1306309659; x=1307519259; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=2ntcycOaw1/k+F3g6RnC5uQqZDV7sWrNiD+xBHv0SHI=; b=PcHP37+FqPN4Ooatt5iWCUkaEKMpx9TRcOrTLj+YCRNX99eA9KXM+U1I OV2VRdnW7bL7jlwPU3ctOIFtonSvosNGQ//+/jHBuV2q8u0AFVc1unaNN 2BDp41UNNi0BJnCpS5ncIOr3as1p06+wDmztyUdLJIQLaCJaqyzLsm9rE A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjkBAJKz3E1Io8US/2dsb2JhbACXZY5FeIhwn0edeIYcBIZZjhWKTw
X-IronPort-AV: E=Sophos;i="4.65,266,1304294400"; d="scan'208";a="90584074"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-1.cisco.com with ESMTP; 25 May 2011 07:47:37 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p4P7lafD017107; Wed, 25 May 2011 07:47:36 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 25 May 2011 13:17:36 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 25 May 2011 13:17:34 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A6239055B103C@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA089BE68D2C@MCHP058A.global-ad.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [siprec] Can an MS object span several CSs in a CSG?
Thread-Index: AcwZ5UbR730mQiXZRGSqd4Xx2cnzHgAHpFKQAAkglcAAAc/qEAAHiqxwAARuZ7AAEv0wYAAASlPQ
References: <A444A0F8084434499206E78C106220CA089BE68795@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A6239055B0D70@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C04663764@xmb-sjc-234.amer.cisco.com> <35BCE99A477D6A4986FB2216D8CF2CFD067EECD7@XMB-BGL-417.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0466393B@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A6239055B0EC0@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA089BE68D2C@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, siprec@ietf.org
X-OriginalArrivalTime: 25 May 2011 07:47:36.0079 (UTC) FILETIME=[036AA9F0:01CC1AB0]
Subject: Re: [siprec] Can an MS object span several CSs in a CSG?
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 07:47:41 -0000

John,

===================================================================
> 3) B transfer the call of A & B to C using REFER, B2BUA converts REFER

> to RE-INVITE towards A & C and A & C are connected. B2BUA updates RS 
> with CS2, Participant1 as A & participant2 as C, MS1(A's media 
> stream), MS2(C's media stream). There is no update on RS1, CSG1, MS1, 
> MS2. MS2 will become MS2 with the new association and in terms of 
> format, it will associate with <send> tag
[JRE] What harm is done (what do we lose) if, following transfer, A's
media stream is called MS3 and C's media stream is called MS4? 
=====================================================================
<Partha> To indicate MS1 as MS3, MS1 media block has to be stopped in
the partial-update and start MS3 separate which is not required in case
there is a means to have common MS1. </Partha>

========================================================================
=======================
MS3 can reference the same SDP m-line (through a=label) as MS1, and
likewise MS4 could reference the same SDP m-line as MS2, if we are
concerned about recycling media descriptions in RS SDP.
========================================================================
==================
<Partha> As you mentioned, we will lose recycling of media description
in RS SDP without common value in media stream object for this scenario.
AFAIK, Your proposal needs enhancement in RFC 4574 as label attribute
scope is within single SIP message and not required to be unique in all
SIP messages of a given dialog. </Partha> 

Thanks
Partha

John (as individual)

> 
> Thanks
> Partha  
> 
> -----Original Message-----
> From: Charles Eckel (eckelcu) 
> Sent: Wednesday, May 25, 2011 1:39 AM
> To: Ram Mohan R (rmohanr); Parthasarathi R (partr); 'Elwell, John';
> 'siprec@ietf.org'
> Subject: RE: [siprec] Can an MS object span several CSs in a CSG?
> 
> Hi Ram,
> 
> I think that is many cases, they will be treated as separate 
> MSs due to
> the complexities you mention. However, I am trying to understand if
> Partha feels allowing an SRC to treat them as a single MS is still
> required. If not, then what is a use case? A concrete example 
> would help
> me, and potentially others, to better understand the motivation behind
> Partha's requirement for modeling media from multiple CSs as a single
> MS.
> 
> Cheers,
> Charles
> 
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr)
> > Sent: Tuesday, May 24, 2011 9:36 AM
> > To: Charles Eckel (eckelcu); Parthasarathi R (partr); Elwell, John; 
> > siprec@ietf.org
> > Subject: RE: [siprec] Can an MS object span several CSs in a CSG?
> > 
> > Charles,
> > 
> > I did bring about this specific usecase of MMOH/MOH stream being 
> > played to different participants earlier and suggested that 
> they have 
> > to treated as a same MS across multiple CSs (potentially recorded
> using multiple RSs).
> > Refer 
> > http://www.ietf.org/mail-archive/web/siprec/current/msg01886.html
> > 
> > We had several discussions on it and it and several folks were in 
> > favor of treating it as separate MS as there would be 
> complexity in DB
> design.
> > 
> > Regards,
> > Ram
> > 
> > 
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On 
> > > Behalf Of Charles Eckel (eckelcu)
> > > Sent: Tuesday, May 24, 2011 9:11 PM
> > > To: Parthasarathi R (partr); Elwell, John; siprec@ietf.org
> > > Subject: Re: [siprec] Can an MS object span several CSs in a CSG?
> > >
> > > Hi Partha,
> > >
> > > Is an example of this the same music on hold audio stream 
> existing 
> > > as the same MS within multiple CSs? If so, then I understand your 
> > > requirement to be that the SRC be able to indicate multiple 
> > > instances of this audio stream within several CSs as 
> being the same 
> > > MS. Is that correct?
> > >
> > > Thanks,
> > > Charles
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org 
> [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Parthasarathi R (partr)
> > > > Sent: Tuesday, May 24, 2011 4:26 AM
> > > > To: Elwell, John; siprec@ietf.org
> > > > Subject: Re: [siprec] Can an MS object span several CSs 
> in a CSG?
> > > >
> > > > John,
> > > >
> > > > I agree that it is not mandatory to consider recorded 
> stream of a 
> > > > specific participant in several CS within the same CSG as one
> > > recorded
> > > > stream but SIPREC protocol design MUST NOT restrict a 
> SRC in case 
> > > > it wishes to design in such a way.
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org 
> [mailto:siprec-bounces@ietf.org] On
> > > Behalf
> > > > Of Elwell, John
> > > > Sent: Tuesday, May 24, 2011 1:06 PM
> > > > To: siprec@ietf.org
> > > > Subject: [siprec] Can an MS object span several CSs in a CSG?
> > > >
> > > > We seem to have consensus that a Media Stream object 
> represents a 
> > > > recorded media stream, contributed to by one, several or all 
> > > > Participants. However, Partha also wrote:
> > > >
> > > > "2) Each MS lifetime related to CSG because participant 
> may move 
> > > > from one CS to another CS within single CSG and also 
> CSG will span
> 
> > > > across multiple RS."
> > > >
> > > > I am not sure we had resolved this during earlier 
> discussions on 
> > > > the scope of an MS object. Although the same Participant can 
> > > > participate
> > > in
> > > > several CSs within the same CSG, I don't think the 
> recorded media 
> > > > streams need to be considered the same. Any other views?
> > > >
> > > > John (as individual)
> > > > _______________________________________________
> > > > siprec mailing list
> > > > siprec@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/siprec
> > > > _______________________________________________
> > > > siprec mailing list
> > > > siprec@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/siprec
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
>