
From finlay.fraser@bt.com  Tue Nov  1 01:26:31 2011
Return-Path: <finlay.fraser@bt.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 0912A21F8DB4 for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 01:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_81=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DEUU-VuIViJE for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 01:26:30 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.com [62.239.224.234]) by ietfa.amsl.com (Postfix) with ESMTP id A244D21F8DAC for <siprec@ietf.org>; Tue,  1 Nov 2011 01:26:29 -0700 (PDT)
Received: from EVMHT66-UKRD.domain1.systemhost.net (10.36.3.103) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.159.2; Tue, 1 Nov 2011 08:26:28 +0000
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.2.68]) by EVMHT66-UKRD.domain1.systemhost.net ([10.36.3.103]) with mapi; Tue, 1 Nov 2011 08:26:28 +0000
From: <finlay.fraser@bt.com>
To: <rmohanr@cisco.com>, <john.2.stafford@bt.com>, <siprec@ietf.org>
Date: Tue, 1 Nov 2011 08:21:33 +0000
Thread-Topic: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
Thread-Index: AcyX0hMfUaa0S1rzTNidKyxIGmNhvQABfbNwAAMGh8AAAYJv3QAdYrGgAAPi1hQ=
Message-ID: <67DAF295CD01EB44AE6EA8A51F6ABF0A4069146D47@EMV62-UKRD.domain1.systemhost.net>
References: <20111031133617.24449.96357.idtracker@ietfa.amsl.com> <BBA98B7742309546A60F3AE3B4E975A72822C3A32F@EMV64-UKRD.domain1.systemhost.net>, <35BCE99A477D6A4986FB2216D8CF2CFD082B8463@XMB-BGL-417.cisco.com> <BBA98B7742309546A60F3AE3B4E975A72822C3A332@EMV64-UKRD.domain1.systemhost.net>, <35BCE99A477D6A4986FB2216D8CF2CFD082B8592@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD082B8592@XMB-BGL-417.cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
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: Tue, 01 Nov 2011 08:26:31 -0000

Ram

The only issue I can see is that the voice recorder companies will not be a=
ble to do call reconstruction as there will be parts of the call where they=
 have no RS that has an activestream and so will not be informed about thes=
e parts of a CS.

I agree that in terms of recording this info is not needed as there is no r=
ecording associated with it. However any voice recorder that was hoping to =
use the meta data to provide call records will now not be abl eto do so.

Since we are developing th eswitch side of this we are OK with it I just wa=
nted to confirm th eVoice Recorder companies are also happy

Finlay

________________________________________
From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of Ram Mo=
han R (rmohanr) [rmohanr@cisco.com]
Sent: 01 November 2011 06:49
To: Stafford,J,John,JRJ3X C; siprec@ietf.org
Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt

Hi John S

Please see inline

> -----Original Message-----
> From: john.2.stafford@bt.com [mailto:john.2.stafford@bt.com]
> Sent: Monday, October 31, 2011 9:59 PM
> To: Ram Mohan R (rmohanr); siprec@ietf.org
> Subject: RE: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>
> Ram,
>
> If CS has associate/dissaociated instead of begin/end times, then
there
> won't be any way of signalling that a CS has ended, only that it is no
> longer being recorded.
>
> Especially as Charles says it was going to be allowed to have a CS
with
> zero participants.
>
> Maybe CS needs BOTH associate/dissassociate and begin/end times ?

The associate-time here indicates the time a CS was associated with a
RS. IOW it is the time the recording of CS is started in that RS.
Disassociate time indicate the time the recording of CS was stopped from
that RS.  The reason why this attribute was added is to address cases
where only parts of CS is recorded(e.g. you record the first few mins of
a CS, then stop the recording, then re-start recording of the same CS
after some time). In such cases indicating begin/end of CS is not
correct as CS has not ended, but RS has ended.  So the WG decided it's
better to have associate/disassociate time and have its scope to a RS so
that a CS may have multiple associate/disassociate times if need be. For
simple cases where the entire CS is recorded, the associate/disassociate
times may be mapped to the CS begin/end times assuming recording is
started the same moment CS is setup.

 I agree that with this approach, we are not indicating explicitly
indicating when the CS has actually started/ended.
>From the past discussions, there was no much interest in keeping both of
this information. If you think there are enough use-cases where
indicating both these will be helpful please bring them, we can discuss
further and add begin/end times after getting consensus from WG.

Regards,
Ram

>
> Rgds
> John Stafford | Solution Architect 1 | BT Global Services | Tel:+44
> (0)1932 773504   | E: john.2.stafford@bt.com  |
> www.bt.com/globalservices
> ________________________________________
> From: Ram Mohan R (rmohanr) [rmohanr@cisco.com]
> Sent: 31 October 2011 15:46
> To: Stafford,J,John,JRJ3X C; siprec@ietf.org
> Subject: RE: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>
> John,
>
> This needs to be changed to associate/disassociate time to be in
> consistent with model. We will take care in the next revision.
>
> Ram
>
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of john.2.stafford@bt.com
> > Sent: Monday, October 31, 2011 8:09 PM
> > To: siprec@ietf.org
> > Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
> >
> > Partha
> >
> > sections 6.3, 7.1,and  8 show CS as having Associate Time and
> > Dissassociate Time,
> > but  examples in section 13 show CS having start-time and end-time.
> >
> >
> > Rgds
> > John Stafford | Solution Architect 1 | BT Global Services
> >
> > ________________________________________
> > From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of
> > internet-drafts@ietf.org [internet-drafts@ietf.org]
> > Sent: 31 October 2011 13:36
> > To: i-d-announce@ietf.org
> > Cc: siprec@ietf.org
> > Subject: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories. This draft is a work item of the SIP Recording Working
> > Group of the IETF.
> >
> >         Title           : Session Initiation Protocol (SIP)
Recording
> > Metadata
> >         Author(s)       : Ram Mohan Ravindranath
> >                           Parthasarathi Ravindran
> >                           Paul Kyzivat
> >         Filename        : draft-ietf-siprec-metadata-05.txt
> >         Pages           : 45
> >         Date            : 2011-10-31
> >
> >    Session recording is a critical requirement in many
communications
> >    environments such as call centers and financial trading.  In some
> of
> >    these environments, all calls must be recorded for regulatory,
> >    compliance, and consumer protection reasons.  Recording of a
> session
> >    is typically performed by sending a copy of a media stream to a
> >    recording device.  This document describes the metadata model as
> >    viewed by Session Recording Server(SRS) and the Recording
metadata
> >    format.
> >
> >
> > A URL for this Internet-Draft is:
> >
http://www.ietf.org/internet-drafts/draft-ietf-siprec-metadata-05.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-siprec-metadata-05.txt
> > _______________________________________________
> > 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=

From pkyzivat@alum.mit.edu  Tue Nov  1 08:25:10 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 E015721F8CC8 for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 08:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.082
X-Spam-Level: 
X-Spam-Status: No, score=-2.082 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9qyENMxKCb5e for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 08:25:09 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2FD21F8CC6 for <siprec@ietf.org>; Tue,  1 Nov 2011 08:25:09 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta07.westchester.pa.mail.comcast.net with comcast id rrJo1h0051ap0As57rR48N; Tue, 01 Nov 2011 15:25:04 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta22.westchester.pa.mail.comcast.net with comcast id rrR31h01k0tdiYw3irR3iC; Tue, 01 Nov 2011 15:25:04 +0000
Message-ID: <4EB00F4A.6000706@alum.mit.edu>
Date: Tue, 01 Nov 2011 11:24:58 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: siprec@ietf.org
References: <35BCE99A477D6A4986FB2216D8CF2CFD082B7DEA@XMB-BGL-417.cisco.com><4EA9C920.8000200@alum.mit.edu><35BCE99A477D6A4986FB2216D8CF2CFD082B7ECA@XMB-BGL-417.cisco.com><2E239D6FCD033C4BAF15F386A979BF51159D3F@sonusinmail02.sonusnet.com><4EAAB8E9.8070708@alum.mit.edu> <35BCE99A477D6A4986FB2216D8CF2CFD082B80A1@XMB-BGL-417.cisco.com> <35BCE99A477D6A4986FB2216D8CF2CFD082B80A3@XMB-BGL-417.cisco.com> <2E239D6FCD033C4BAF15F386A979BF51159D78@sonusinmail02.sonusnet.com> <35BCE99A477D6A4986FB2216D8CF2CFD082B80C3@XMB-BGL-417.cisco.com> <4EAAEDF5.7080004@alum.mit.edu> <2E239D6FCD033C4BAF15F386A979BF51159D7E@sonusinmail02.sonusnet.com> <622B0E14298DDE47ACA9E16B292F22A40F2F6D2E@Mail1.acmepacket.com>
In-Reply-To: <622B0E14298DDE47ACA9E16B292F22A40F2F6D2E@Mail1.acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] participant & stream outside the scope of session
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: Tue, 01 Nov 2011 15:25:11 -0000

On 10/31/11 4:26 PM, Brad Winslow wrote:
> Hi Folks,
>
> Perhaps I'm missing something about the Participant/Session association, and perhaps some of this applies to the stream/session association as well.
>
> The current metadata draft has two attributes for the participant, the "id" and the "session" both expressed as UUIDs.
> The "id" field seems to be a unique identifier the SRC could use to indicate the uniqueness of this participant in multiple CSs assuming the SRC has the ability to determine if the participant is the same between CSs.  The SRS cold use this field to identify participants across sessions.

That is intended.

> The same holds true of the 'id' field in the stream element, if we assume a particular 'id' is a MOH stream, it's id could be consistent across CSs.

Yes.

> IMO we are under-utilizing the 'id' attribute for participant and stream identity.

I'm happy to have suggestions of how to do things better.

> In the case where the SRC cannot determine if the unique identity of the participant, it would simply create a new UUID for the participant when it enters into a new CS.

Again, that is the intent.
If a newly discovered participant cannot be determined to be "the same" 
as a previously identified participant, then it is treated as a new one.

Note that an identical "From" field is not sufficient info to consider 
this participant the same as some other participant.

> Much of the information in the new ParticipantSessionAssoc element could be contained in the participant element. perhaps I don't understand the use-cases where the association element reduces the complexity of the metadata well enough. Additional xs:any elements could be passed between SRC and SRS to help identify the participants however this would quickly lead to interoperability problems between vendors.

The intent is that the ParticipantSessionAssoc carries information that 
is specific to the involvement of the participant in a particular 
session, while the Participant element carries the information that 
describes the participant independent of the session or stream it is 
involved in.

Which information do you think could be moved?

	Thanks,
	Paul

> Thanks,
> Brad
>
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of Ravindran Parthasarathi
> Sent: Friday, October 28, 2011 3:49 PM
> To: Paul Kyzivat; Ram Mohan R (rmohanr); Leon Portman
> Cc: siprec@ietf.org
> Subject: Re: [siprec] participant&  stream outside the scope of session
>
> Paul/Ram,
>
> Now, participant and stream are associated with session as an aggregation. In case participant is possible to be represented outside session, it is very much possible for stream to be outside the session as shown in persistent usecase. In case of persistent usecase, RS stream is created in advance to avoid the earlier clipping, the session will be associated in metadata whenever the session is established, session will be terminated without removing RS stream
>
> In case new participant session associated XML element is added, it is possible to have stream session associated XML element as well separately.
>
> Including Leon in this mail thread as he asked for persistent usecase.
> I'm reopening this usecase because let us close the related issue at the same time.
>
> Thanks
> Partha
>
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>> Sent: Friday, October 28, 2011 11:31 PM
>> To: Ram Mohan R (rmohanr)
>> Cc: Ravindran Parthasarathi; siprec@ietf.org
>> Subject: Re: [siprec] participant&  stream outside the scope of session
>>
>> +1 to Ram's response.
>>
>> As I noted before, if you want to reopen question of allowing stream
>> without session, I think that should be discussed separately.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 10/28/11 1:27 PM, Ram Mohan R (rmohanr) wrote:
>>> Hi Partha,
>>>
>>> Please see inline
>>>
>>>> -----Original Message-----
>>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>>>> Sent: Friday, October 28, 2011 10:49 PM
>>>> To: Ram Mohan R (rmohanr); Paul Kyzivat
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] participant&   stream outside the scope of
>>> session
>>>>
>>>> Hi Ram,
>>>>
>>>> As Paul mentioned, stream associated with zero session was brought
> up
>>>> as
>>>> part of the persistent connection from the endpoint discussion and
> it
>>>> was pushed back because stream&   participant has to be within
> session
>>>> (CS). I'm worried that participant to zero session change may
> re-open
>>>> the earlier closure and call for one more discussion.
>>>>
>>>> Also, the current syntax of stream is associated with session
> closely
>>>> which has to be changed consistently in case participant is changed
>>> its
>>>> association representation with session.
>>>
>>> I don't see a need for the above. We are changing the participant
>>> association to session to allow it to be consistent with XML if we
>>> choose approach 2.
>>> Even in approach 2, stream has to be associated with a session and so
>>> there is no need to change that association.
>>>
>>> Regards,
>>> Ram
>>>
>>>>
>>>>         <stream id="urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a"
>>>>                 session="urn:uuid:cd27cfa1-2bdd-4830-a653-
>> 70374d10f103">
>>>>                 <label>98</label>
>>>>             </stream>
>>>>
>>>> It will be good in case we get the feedback on these aspect.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>>> -----Original Message-----
>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>> Sent: Friday, October 28, 2011 9:39 PM
>>>>> To: Ram Mohan R (rmohanr); Paul Kyzivat; Ravindran Parthasarathi
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] participant&   stream outside the scope of
>>>> session
>>>>>
>>>>> A typo in the below email. Sorry for that. I meant
>>>>>
>>>>> "
>>>>> I don't see a strong use case to have stream associate to zero
>>>>> sessions. IMO we can retain the stream associations
>>>>>                                          ^^^^^^ ^^^^ as it is in the
>>>>> current model."
>>>>>
>>>>> Thanks,
>>>>> Ram
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>>> Behalf Of Ram Mohan R (rmohanr)
>>>>>> Sent: Friday, October 28, 2011 9:27 PM
>>>>>> To: Paul Kyzivat; Ravindran Parthasarathi
>>>>>> Cc: siprec@ietf.org
>>>>>> Subject: Re: [siprec] participant&   stream outside the scope of
>>>>> session
>>>>>>
>>>>>> I don't see a strong use case to have session associate to zero
>>>>>> sessions. IMO we can retain the session associations as it is in
>>> the
>>>>>> current model.
>>>>>>
>>>>>> Now coming to participant, the main reason why I am inclined to
>>>> change
>>>>>> the association is to have consistency with XML  if we adopt
>>>> approach
>>>>>> 2.
>>>>>>
>>>>>> Regards,
>>>>>> Ram
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>>>>>> Sent: Friday, October 28, 2011 7:45 PM
>>>>>>> To: Ravindran Parthasarathi
>>>>>>> Cc: Ram Mohan R (rmohanr); siprec@ietf.org
>>>>>>> Subject: Re: participant&   stream outside the scope of session
>>>>>>>
>>>>>>> This proposes an additional change, to remove the subordination
>>> of
>>>>>>> stream to session. IMO this should be considered separately from
>>>>>>> participant, as the arguments are different.
>>>>>>>
>>>>>>> AFAICT, the use case Partha gives below is the only one that
>>> calls
>>>>>> for
>>>>>>> stream independent of session. And I'm not sure of the need for
>>>>> this.
>>>>>>> ISTM the only reason to do this is to really record streams from
>>>>>>> participants when there is no session.
>>>>>>>
>>>>>>> This might allow capturing media earlier during call setup, by
>>>>>> defining
>>>>>>> the streams early, and associating them with participants and
>>>>>> sessions
>>>>>>> when that becomes known. *If* an SRS can figure out how to take
>>>>>>> advantage of that.
>>>>>>>
>>>>>>> 	Thanks,
>>>>>>> 	Paul
>>>>>>>
>>>>>>> On 10/28/11 5:09 AM, Ravindran Parthasarathi wrote:
>>>>>>>> <Sorry for the lengthy mail. IMO, This discussion is one of the
>>>>>> major
>>>>>>>>     change in metadata>
>>>>>>>>
>>>>>>>> I'm interested in knowing whether folks are interested in
>>>> handling
>>>>>>>> participant, stream completely outside the scope of session.
>>>>>>>> In fact, we discussed this requirement as part of metadata
>>> model
>>>>>>>> discussion and come to the conclusion not to include. In case
>>>>>>>> participant, stream are outside the scope of session, the
>>>>> following
>>>>>>>> recording metadata from SRC is valid:
>>>>>>>>
>>>>>>>> <recording xmlns='urn:ietf:params:xml:ns:recording'>
>>>>>>>>              <dataMode>full</dataMode>
>>>>>>>>              <participant
>>>>>>>>                 id="urn:uuid:b2b7c112-5982-469d-9007-
>>>> 6ddbecca64d3">
>>>>>>>>                  <aor>sip:agent1@callcenter.com</aor>
>>>>>>>>                 <send>urn:uuid:f3373a7b-4958-4e55-8820-
>>>>>>> d03a191fb76a</send>
>>>>>>>>               </participant>
>>>>>>>>              <stream id="urn:uuid:f3373a7b-4958-4e55-8820-
>>>>>>> d03a191fb76a">
>>>>>>>>                  <label>96</label>
>>>>>>>>              </stream>
>>>>>>>>              <stream id="urn:uuid:01c47915-4777-11d8-bc70-
>>>>>>> 0090272ff725">
>>>>>>>>                  <label>97</label>
>>>>>>>>              </stream>
>>>>>>>> </recording>
>>>>>>>>
>>>>>>>> Also, in the later partial update, session shall be added and
>>>>>>> associate
>>>>>>>> with the above participant&    stream element.
>>>>>>>>
>>>>>>>> Here, SRS has to maintain participant, stream unique id as a
>>>>>> separate
>>>>>>>> flat
>>>>>>>> Data (no hierarchy). Only issue is that SRS has to maintain
>>> flat
>>>>>>>> database for
>>>>>>>> Each of these elements.
>>>>>>>>
>>>>>>>> The current -04 draft is based on the assumption that
>>>> participant
>>>>>> and
>>>>>>>> stream are within a session and it is possible for participant&
>>>>>>> stream
>>>>>>>> to move across multiple sessions using unique id. The rationale
>>>> of
>>>>>>> the
>>>>>>>> current draft approach is that commonly used callflow metadata
>>>> is
>>>>>>> simple
>>>>>>>>
>>>>>>>> whereas specific corner case callflow like same participant in
>>>>>>> multiple
>>>>>>>> session will have complex mechanism.
>>>>>>>>
>>>>>>>> In case we see the strong usecases for going for independent
>>>>>> stream,
>>>>>>>> Participants which is outside the session, we will go for it.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Partha
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>>>> On
>>>>>>>> Behalf
>>>>>>>>> Of Ram Mohan R (rmohanr)
>>>>>>>>> Sent: Friday, October 28, 2011 10:24 AM
>>>>>>>>> To: Paul Kyzivat; siprec@ietf.org
>>>>>>>>> Subject: Re: [siprec] Issue with participant scoping in the
>>>>>> current
>>>>>>>>> modeland its implication on association attr representation
>>>>>>>>>
>>>>>>>>> To add to Paul, with the proposed change, the model will look
>>>> as
>>>>>>> below
>>>>>>>>>
>>>>>>>>>     +-------------------------------+
>>>>>>>>>     |   Communication Session (CS)  |
>>>>>>>>>     |                               |
>>>>>>>>>     +-------------------------------+
>>>>>>>>>           | 0..*                 |1..*
>>>>>>>>>           | ^^^^^^^^             |
>>>>>>>>>           | 2..*                 |0..*
>>>>>>>>>     +-------------+ receives +----------------+
>>>>>>>>>     | Participant |----------|  Media Streams |
>>>>>>>>>     |             |0..*  0..*|                |
>>>>>>>>>     |             |          |                |
>>>>>>>>>     |             |          |                |
>>>>>>>>>     |             |  sends   |                |
>>>>>>>>>     |             |----------|                |
>>>>>>>>>     |             |1.*   0..*|                |
>>>>>>>>>     +-------------+          +----------------+
>>>>>>>>>
>>>>>>>>> A participant can be associated with zero or more sessions.
>>>>>>>>>
>>>>>>>>> And with the above model we can have an approach to define a
>>>>>>>> participant
>>>>>>>>> with no associations to sessions and have XML elements
>>> separate
>>>>>>> (like
>>>>>>>>> <participantSessAssoc>) for association classes as in approach
>>>> 2
>>>>>>>>> mentioned below
>>>>>>>>>
>>>>>>>>> Ram
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: siprec-bounces@ietf.org
>>> [mailto:siprec-bounces@ietf.org]
>>>>> On
>>>>>>>>>> Behalf Of Paul Kyzivat
>>>>>>>>>> Sent: Friday, October 28, 2011 2:42 AM
>>>>>>>>>> To: siprec@ietf.org
>>>>>>>>>> Subject: Re: [siprec] Issue with participant scoping in the
>>>>>> current
>>>>>>>>>> model and its implication on association attr representation
>>>>>>>>>>
>>>>>>>>>> On 10/27/11 1:46 PM, Ram Mohan R (rmohanr) wrote:
>>>>>>>>>>> (Sorry for lengthy e-mail)
>>>>>>>>>>>
>>>>>>>>>>> This is a follow up to the mail thread
>>>>>>>>>>> http://www.ietf.org/mail-
>>>>>> archive/web/siprec/current/msg02810.html
>>>>>>>>>>>
>>>>>>>>>>> In the last IETF meeting there was a consensus that a
>>>>>> participant
>>>>>>>>> can
>>>>>>>>>>> have a life outside of CS.
>>>>>>>>>>>
>>>>>>>>>>> However the current model scopes participant to always a
>>>>>> session.
>>>>>>>>>>
>>>>>>>>>> I don't think that is quite right. The *model* requires that
>>>>> each
>>>>>>>>>> participant be associated with one or more sessions. It
>>>> doesn't
>>>>>>> scope
>>>>>>>>>> to
>>>>>>>>>> a single session.
>>>>>>>>>>
>>>>>>>>>>> Should we have to change the model to have participant
>>>> outside
>>>>>>>> scope
>>>>>>>>>> of
>>>>>>>>>>> session ? I think it may not make sense to model
>>> participants
>>>>>>> under
>>>>>>>>>> RS
>>>>>>>>>>> as these are participants of Session. The only use case
>>> where
>>>>> we
>>>>>>>> can
>>>>>>>>>>> have a participant in a RS with no CS is for Persistent
>>>>>> recording
>>>>>>>>>>> sessions (e.g. setup from agent phone(SRC) to SRS) This RS
>>>> will
>>>>>> be
>>>>>>>>>> setup
>>>>>>>>>>> even without any CS.  If an SRC for this case sends a
>>>> snapshot
>>>>>>>>> before
>>>>>>>>>> a
>>>>>>>>>>> CS starts it may have participant information without any
>>>>>> session.
>>>>>>>>>>> Does the WG sees a value in such a use case or should we
>>>> retain
>>>>>>> the
>>>>>>>>>>> model as is ?
>>>>>>>>>>
>>>>>>>>>> IMO the change we would be talking about is that a
>>> participant
>>>>>> can
>>>>>>> be
>>>>>>>>>> associated with *zero* or more sessions, rather than one or
>>>>> more.
>>>>>>>>>>
>>>>>>>>>> In addition to the use case Ram mentions above, this would
>>>> help
>>>>>>> with
>>>>>>>>>> the
>>>>>>>>>> mapping to xml. If we go with participantSessAssoc (as
>>>> mentioned
>>>>>>>>> below)
>>>>>>>>>> it becomes *possible* to define a participant with no
>>>>>> associations
>>>>>>> to
>>>>>>>>>> sessions. Allowing the same in the model at least makes them
>>>>>>>>>> consistent.
>>>>>>>>>>
>>>>>>>>>> 	Thanks,
>>>>>>>>>> 	Paul
>>>>>>>>>>
>>>>>>>>>>> The current model (ver 04) also impacts the way association
>>>>>>>>>> attributes
>>>>>>>>>>> are represented. Since the current draft (ver-04)the
>>> metadata
>>>>>>> model
>>>>>>>>>>> scopes participant and stream elements to session the schema
>>>>>> also
>>>>>>>>> was
>>>>>>>>>>> designed the same way. The<participant>     and<stream>
>>>>>> attributes
>>>>>>>> are
>>>>>>>>>>> scoped/associated to a session (see section 7.1 example).
>>> IOW
>>>>>> the
>>>>>>>>>>> association attributes of<participant>     to<session>     are
>>>>>> already
>>>>>>>>>>> represented.
>>>>>>>>>>>
>>>>>>>>>>> Now if we have to go with approach 2 for representing
>>>>>> association
>>>>>>>>>>> attributes, we will have to do one of the two ways:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> If we stick the current model/schema:
>>>>>>>>>>> -----------------------------------
>>>>>>>>>>> We will have represent in the following way. Note this is a
>>>> mix
>>>>>> of
>>>>>>>>>>> approach 1 (existing representation which acheives
>>>> participant
>>>>>>>>>> session
>>>>>>>>>>> association) and approach 2 ( for part-stream association).
>>>>> The
>>>>>>>>>> issue
>>>>>>>>>>> with this approach is if the same participant is
>>>> simultaneously
>>>>>> in
>>>>>>>>>>> multiple sessions( cases like participant goes on hold on
>>> one
>>>>>> line
>>>>>>>>>> and
>>>>>>>>>>> talks to another participant) and SRC sends a snapshot then
>>>> we
>>>>>>> will
>>>>>>>>>> have
>>>>>>>>>>> multiple<participant>     elements each having different
>>>> session
>>>>>>> IDs.
>>>>>>>>>>>             <participant
>>>>>>>>>>>
>>>> id="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>
>>>>>>>> session="urn:uuid:855a5ded-8420-456d-a70f-6da1eeaeb425">
>>>>>>>>>>>                      <aor>sip:ram@blr.cisco.com</aor>
>>>>>>>>>>>                      <associate-time>2010-12-
>>>>>>> 16T23:41:07Z</associate-
>>>>>>>>>> time>
>>>>>>>>>>>                      <capabilities>     XXX</capabilties>
>>>>>>>>>>>              </participant>
>>>>>>>>>>>
>>>>>>>>>>> And for participant-stream you will have a new element
>>>>>>>>>>>
>>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>>      participant="urn:uuid:b2b7c112-5982-469d-9007-
>>>> 6ddbecca64d3"
>>>>>>>>>>>      stream ="urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>>>>         <associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>         <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>>
>>>>>>>>>>> If we change the model to remove the scoping of
>>>>>> participant/stream
>>>>>>>>> to
>>>>>>>>>>> session:
>>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>> --------------------------------------------------------------------
>>>>>>> -
>>>>>>>>>> ---
>>>>>>>>>>> -----
>>>>>>>>>>>
>>>>>>>>>>> <participant
>>>>>>>>>>>
>>>>> id="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3">
>>>>>>>>>>>                <aor>sip:ram@blr.cisco.com</aor>  </participant>
>>>>>>>>>>>
>>>>>>>>>>> <participantSessAssoc
>>>>>>>>>>>
>>>>>>>>> participant="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>                session="urn:uuid:855a5ded-8420-456d-a70f-
>>>>>>> 6da1eeaeb425"
>>>>>>>>>>>
>>>>>>>>> <associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>                    <capabilities>     XXX</capabilties>
>>>>>>>>>>> </participantSessAssoc>
>>>>>>>>>>>
>>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>>      participant="urn:uuid:b2b7c112-5982-469d-9007-
>>>> 6ddbecca64d3"
>>>>>>>>>>>      stream ="urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>>>>         <associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>         <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>>
>>>>>>>>>>> Let me know your comments.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Ram
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>


From andrew.hutton@siemens-enterprise.com  Tue Nov  1 10:04:09 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 E8D211F0CBA for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 10:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQym1QuzEdA3 for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 10:04:07 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 161DD1F0C48 for <siprec@ietf.org>; Tue,  1 Nov 2011 10:04:07 -0700 (PDT)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 2FDA41EB8472; Tue,  1 Nov 2011 18:02:50 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 1 Nov 2011 18:02:50 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 1 Nov 2011 18:02:47 +0100
Thread-Topic: [siprec] SRS-initiated initial INVITE
Thread-Index: AcyBU5Z82AsXoy0oQ3WH9csMTOBpJQXX9f5Q
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311F80426C1@MCHP058A.global-ad.net>
References: <A4E1C77AFA24EF4A9DBDF6CB6491D0E73AF67003@SE-EX019.groupinfra.com><A4E1C77AFA24EF4A9DBDF6CB6491D0E73AF67285@SE-EX019.groupinfra.com><07465C1D981ABC41A344374066AE1A2C38B066C6FC@TLVMBX01.nice.com><A4E1C77AFA24EF4A9DBDF6CB6491D0E73AF673C8@SE-EX019.groupinfra.com><A444A0F8084434499206E78C106220CA0BC11A84F6@MCHP058A.global-ad.net><101C6067BEC68246B0C3F6843BCCC1E311F7B7CD35@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38B066D0F5@TLVMBX01.nice.com> <2E239D6FCD033C4BAF15F386A979BF510F0F56@sonusinmail02.sonusnet.com> <101C6067BEC68246B0C3F6843BCCC1E311F7B7CFC3@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF510F0F84@sonusinmail02.sonusnet.com> <A444A0F8084434499206E78C106220CA0BC11A8A8A@MCHP058A.global-ad.net> <A4E1C77AFA24EF4A9DBDF6CB6491D0E73AF67E28@SE-EX019.groupinfra.com> <A444A0F8084434499206E78C106220CA0BC11A8AD8@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311F7B7D168@MCHP058A.global-ad.net> <4E88E727.6010009@alum.mit.edu>
In-Reply-To: <4E88E727.6010009@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] SRS-initiated initial INVITE
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: Tue, 01 Nov 2011 17:04:10 -0000

Hi,

On 02 October 2011 at 23:35 Kyzivat Paul wrote:

> I think there are a couple of choices here:
> - we can require that an SRC and an SRS have a unique URI, that behaves
>    only as an SRC/SRS, never any other way. And only when addressed by
>    such a URI does it support the siprec option and advertise support
> for
>    the corresponding capability/feature-tag.
>

I don't think we want to require a SRC or SRS to have a unique URI for this=
 purpose this would really increase complexity of deploying and provisionin=
g the solution especially if we have lots of SRC's located in endpoints for=
 example.


> - we can permit the same URI to be used for an RS or a CS. In this case
>    it can support siprec all the time, and announce an SRC or SRS
> feature
>    tag all the time. But then we need something to indicate "behave as
>    an SRC" or "behave as an SRS".

I had previously envisaged that the UA would only include the "src" or "srs=
" feature tag in the Contact during the establishment of a RS this is how i=
t is currently described in for example section 5.1 of the protocol draft. =
 That is except for possible use in a REGISTER.

So if this is the case then if this is combined with the use of the "siprec=
" option tag in Require then I would not thought it to be too big a stretch=
 to say that the siprec aware UAS receiving an INVITE it knows to be from a=
n SRC MUST assume the role of SRS or reject the INVITE. Do we really need s=
omething else?

Regards
Andy (as an individual).


> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: 02 October 2011 23:35
> To: siprec@ietf.org
> Subject: Re: [siprec] SRS-initiated initial INVITE
>
> On 9/23/11 5:13 AM, Hutton, Andrew wrote:
> > Hi,
> >
> > I think Friso is correct this is covered in the protocol draft and it
> works like this.
> >
> > 1. The SRS includes a Require header field with the option tag
> "recording-session". This means that the UAS that receives the INVITE
> has to understand SIPREC or it will reject the INVITE.
> >
> > 2. The SRS also includes the feature tag "SRS" in the contact so that
> the UAS that receives it knows that it is an SRS that initiated the
> INVITE for the purpose of creating a recording session so it has to
> become the SRC. Therefore if the UAS is an SRC that does not handle SRS
> initiated INVITE's it should reject the INVITE at this point. Maybe we
> could say something about this in the protocol draft.
>
> IMO this isn't sufficient. SIP feature tags in Contact encode "callee
> capabilities". They don't say anything about what the recipient should
> do.
>
> I think there are a couple of choices here:
> - we can require that an SRC and an SRS have a unique URI, that behaves
>    only as an SRC/SRS, never any other way. And only when addressed by
>    such a URI does it support the siprec option and advertise support
> for
>    the corresponding capability/feature-tag.
>
> - we can permit the same URI to be used for an RS or a CS. In this case
>    it can support siprec all the time, and announce an SRC or SRS
> feature
>    tag all the time. But then we need something to indicate "behave as
>    an SRC" or "behave as an SRS".
>
>       Thanks,
>       Paul
>
> > The only issue I see is possible in the naming of the "recording-
> session" option tag as this should not be used as an indication that
> this is a recording session it is only used to indicate to the UAS that
> it should reject the INVITE if it does not understand SIPREC
> extensions. However this is just a naming issue.
> >
> > Regards
> > Andy
> >
> >
> >> -----Original Message-----
> >> From: Elwell, John
> >> Sent: 23 September 2011 09:42
> >> To: Feenstra, Friso; Ravindran Parthasarathi; Hutton, Andrew; Leon
> >> Portman; siprec@ietf.org
> >> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>
> >> Friso,
> >>
> >> Quite right, it is not yet covered, and the whole purpose of this
> >> thread is to discuss whether something needs to go into the protocol
> >> draft to cover the SRS-initiated case, to align with the
> architecture
> >> draft.
> >>
> >> John
> >>
> >>
> >>> -----Original Message-----
> >>> From: Feenstra, Friso [mailto:friso.feenstra@logica.com]
> >>> Sent: 23 September 2011 09:23
> >>> To: Elwell, John; Ravindran Parthasarathi; Hutton, Andrew;
> >>> Leon Portman; siprec@ietf.org
> >>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>
> >>> Hi John,
> >>>
> >>> Please excuse me as being relative new to this, but is this
> >>> not covered by the current description in Session Recording
> >>> Protocol draft-ietf-siprec-protocol-00 paragraph 5.1 and 5.2?
> >>>
> >>> Friso ( as individual)
> >>>
> >>> -----Original Message-----
> >>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> >>> Sent: vrijdag 23 september 2011 10:04
> >>> To: Ravindran Parthasarathi; Hutton, Andrew; Leon Portman;
> >>> Feenstra, Friso; siprec@ietf.org
> >>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>
> >>> I think we need to avoid violating the semantics of Require.
> >>> The Require header field just means reject the request if you
> >>> don't understand this extension. If you want a
> >>> SIPREC-compliant UAS to act as an SRC, I think you also need
> >>> to put something in the INVITE request to this effect. This
> >>> could simply be the srs feature tag. So we could specify that
> >>> if an entity receives an INVITE request with an srs feature
> >>> tag this is to be interpreted as a request to become an SRC.
> >>> If the UAS is not prepared to do this it can reject it
> >>> somehow (e.g., 403 Forbidden).
> >>>
> >>> John (as individual)
> >>>
> >>>> -----Original Message-----
> >>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
> >>>> Sent: 23 September 2011 07:46
> >>>> To: Hutton, Andrew; Leon Portman; Elwell, John; Feenstra,
> >>>> Friso; siprec@ietf.org
> >>>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>>
> >>>> Hi Andrew,
> >>>>
> >>>> Thanks for correction. I assumed that softswitch as B2BUA.
> >>>> So, the scenario is that SIP proxy which does not want to
> >>>> push the intelligence to its UA but push it to some-other server.
> >>>>
> >>>> I'm fine as long as there is no extra normative statement for
> >>>> SRC. Let us also spell out the error-code for recording
> >>>> request rejection by SRC in case of INVITE without offer.
> >>>>
> >>>> Thanks
> >>>> Partha
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Hutton, Andrew [mailto:andrew.hutton@siemens-
> enterprise.com]
> >>>>> Sent: Friday, September 23, 2011 1:37 AM
> >>>>> To: Ravindran Parthasarathi; Leon Portman; Elwell, John;
> Feenstra,
> >>>>> Friso; siprec@ietf.org
> >>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>>>
> >>>>> Hi Partha,
> >>>>>
> >>>>> But in Friso's scenario the "softswitch" is really acting
> >>> just a SIP
> >>>>> Proxy so it cannot be the case that the SIP Proxy and the
> >>> SIP UA are
> >>>>> acting as a kind of decomposed SRC.
> >>>>>
> >>>>> Of course whether a given SRC implements the capability to
> receive
> >>>>> INVITE's from the SRS is an implementation option if it does
> >>>> not the SRC
> >>>>> will reject the INVITE due to the recording-session option
> >>> tag in the
> >>>>> Require header.
> >>>>>
> >>>>> Regards
> >>>>>
> >>>>> Andy (As an individual).
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
> >>>>>> Sent: 22 September 2011 18:43
> >>>>>> To: Leon Portman; Hutton, Andrew; Elwell, John; Feenstra, Friso;
> >>>>>> siprec@ietf.org
> >>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>>>>
> >>>>>>
> >>>>>> I have earlier mentioned as a not good design because better
> >>>>>> alternative exists for the same recording topology within SIPREC
> >>>>>> solution. I look at Friso recording topology as decomposed
> >>>> SRC to SRS
> >>>>>> network topology and details are as follows:
> >>>>>>
> >>>>>> 1) Softswitch&  Agent phone act as SRC wherein Softswitch is a
> >>>>>> signaling Entity (SIP) and Agent phone as media entity (RTP).
> >>>>>> 2) Softswitch communicates with SRS in the standard SIPREC
> >>>> RS session
> >>>>>> establishment (with extension data) to SRS.
> >>>>>> 3) Based on SRS negotiation, softswitch indicates to agent
> >>>> phone using
> >>>>>> proprietary SDP extension with m-line addition (to start
> >>> recording
> >>>>>> towards SRS). Here, Agent phone forks the media towards
> >>> SRS. I have
> >>>>>> mentioned proprietary SDP extension because the
> >>> interaction between
> >>>>>> decomposed SRC is outside the scope of SIPREC. (I know of
> >>>> the working
> >>>>>> solution in the fashion for the call center).
> >>>>>>
> >>>>>> The advantages in this decomposed SRC solution are
> >>>>>> 1) There is no need of extra CTI or equivalent channel between
> >>>>>> softswitch&  SRS.
> >>>>>> 2) Agent phone has no need to handle multiple dialogs (CS&  RS).
> >>>>>> 3) It is easy for tracking the session from Softswitch
> >>> during agent
> >>>>>> transfer as it is acting as SRC.
> >>>>>> 4) No need to use "join" or some unique session-id
> >>> between all the
> >>>>>> entities
> >>>>>>
> >>>>>> Any recording entity has to support multiple m-lines in
> >>> SDP and so,
> >>>>>> there is no difference for agent-phone between SRS-initiated
> >> and
> >>>>>> decomposed SRC media box. Please correct in case any other
> >>>> advantage
> >>>>> in
> >>>>>> SRS-initiated solution compare to decomposed-SRC.
> >>>>>>
> >>>>>>
> >>>>>> Having said that, I'm fine with SRS-initiated INVITE in
> >>>> case everybody
> >>>>>> is interested for some specific callflow but I'm not
> >>> interested to
> >>>>> hear
> >>>>>> more mandate in SRC to handle this callflow.
> >>>>>>
> >>>>>> Thanks
> >>>>>> Partha
> >>>>>>
> >>>>>> PS: The proposed decomposed SRC solution may work in
> >>>> RTCWeb recording
> >>>>>> solution between RTCWebserver&  browser ;-)
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: siprec-bounces@ietf.org
> >>> [mailto:siprec-bounces@ietf.org] On
> >>>>>> Behalf
> >>>>>>> Of Leon Portman
> >>>>>>> Sent: Thursday, September 22, 2011 7:34 PM
> >>>>>>> To: Hutton, Andrew; Elwell, John; Feenstra, Friso;
> >>> siprec@ietf.org
> >>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
> >>>>>>>
> >>>>>>> Andy Hi
> >>>>>>>
> >>>>>>> I will update the drafts with below. I agree on the flow
> >>>>>>>
> >>>>>>> Leon
> >>>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Hutton, Andrew
> >>> [mailto:andrew.hutton@siemens-enterprise.com]
> >>>>>>> Sent: Thursday, September 22, 2011 4:28 PM
> >>>>>>> To: Elwell, John; Feenstra, Friso; Leon Portman;
> >> siprec@ietf.org
> >>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>>>>>
> >>>>>>> Hi All,
> >>>>>>>
> >>>>>>> I think what Friso describes is a perfectly valid use
> >>> case and is
> >>>>>>> something that we intended to cover in SIPREC hence the
> >> existing
> >>>>>> section
> >>>>>>> in the architecture draft.
> >>>>>>>
> >>>>>>> I don't think we need to be concerned with how the SRS
> >>>> knows when to
> >>>>>>> start recording this could be via CTI, SIP Dialog Events or
> >> many
> >>>>>> others
> >>>>>>> means. This is I think out of scope of SIPREC.
> >>>>>>>
> >>>>>>> What I think we do need to do is tidy up the architecture draft
> >>>>>> (Section
> >>>>>>> 3.2.2) which covers this use SRS initiated recording.  We
> >>>> need to say
> >>>>>>> more about how the CS that is to be recorded is
> >>>> identified. Currently
> >>>>>>> the arch draft says that one possibly way of doing this
> >>>> is using the
> >>>>>>> "Join" header which obviously only applies if the CS
> >>>> dialog already
> >>>>>>> exists and the SRS knows the dialog identifiers.
> >>>>>>>
> >>>>>>> Do people think that specifying the use of "Join" for
> >>>> this purpose is
> >>>>>>> useful or can we just say something generic about the
> >>> Request-URI
> >>>>>>> identifying what needs to be recorded?
> >>>>>>>
> >>>>>>> I also noticed a mistake in section 3.2.2 of the
> >>>> architecture draft
> >>>>> in
> >>>>>>> the 4th bullet "Session Recording Client" should be "Session
> >>>>> Recording
> >>>>>>> Server" as this refers to the case when the SRS
> >>> generates the SDP
> >>>>>> offer.
> >>>>>>> Leon as you have the pen can you fix this.
> >>>>>>>
> >>>>>>> Andy (As individual).
> >>>>>>>
> >>>>>>> Andrew Hutton
> >>>>>>> http://www.siemens-enterprise.com/uk/
> >>>>>>>
> >>>>>>> Siemens Enterprise Communications Limited.
> >>>>>>> Registered office: Brickhill Street, Willen Lake, Milton
> >>>> Keynes, MK15
> >>>>>>> 0DJ.
> >>>>>>> Registered No: 5903714, England.
> >>>>>>>
> >>>>>>> Siemens Enterprise Communications Limited is a Trademark
> >>>> Licensee of
> >>>>>>> Siemens AG.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: siprec-bounces@ietf.org
> >>>> [mailto:siprec-bounces@ietf.org] On
> >>>>>>>> Behalf Of Elwell, John
> >>>>>>>> Sent: 22 September 2011 08:47
> >>>>>>>> To: Feenstra, Friso; Leon Portman; siprec@ietf.org
> >>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
> >>>>>>>>
> >>>>>>>> What Friso describes is fairly similar to what I had in mind.
> >>>>>>>> Basically the SRS knows, through some out-of-band means
> >>>> (e.g., CTI,
> >>>>>>>> human involvement), that it should record a CS or CSs (e.g.,
> >>>>>>>> persistent recording of CSs involving a given user,
> >>>> recording the
> >>>>>>>> current CS of a particular user). Based on this it can
> >>>> construct a
> >>>>>> URI
> >>>>>>>> that identifies the SRC and instructs it what to record.
> >>>>>>>>
> >>>>>>>> Personally I am more interested in the case where the
> >>>> SRS is at a
> >>>>>>>> B2BUA. Although the UA case is also potentially of
> >>>> interest, that
> >>>>>>>> tends to have limited applicability for the following
> >> reasons:
> >>>>>>>> - requires SRC support at all UAs that might be
> >>> involved, rather
> >>>>>> than
> >>>>>>>> just in one or a few network entities;
> >>>>>>>> - bandwidth limitations, particularly for mobile
> >>> users and users
> >>>>>> with
> >>>>>>>> limited uplink speeds.
> >>>>>>>>
> >>>>>>>> Since SRS-initiated INVITEs do not require any new SIP
> >>>> mechanism,
> >>>>> it
> >>>>>>>> seems quite reasonable to me to allow them.
> >>>>>>>>
> >>>>>>>> John (as individual)
> >>>>>>>>
> >>>>>>>> John Elwell
> >>>>>>>> Tel: +44 1908 817801 (office and mobile)
> >>>>>>>> Email: john.elwell@siemens-enterprise.com
> >>>>>>>> http://www.siemens-enterprise.com/uk/
> >>>>>>>>
> >>>>>>>> Siemens Enterprise Communications Limited.
> >>>>>>>> Registered office: Brickhill Street, Willen Lake,
> >>> Milton Keynes,
> >>>>>> MK15
> >>>>>>>> 0DJ.
> >>>>>>>> Registered No: 5903714, England.
> >>>>>>>>
> >>>>>>>> Siemens Enterprise Communications Limited is a
> >>>> Trademark Licensee
> >>>>> of
> >>>>>>>> Siemens AG.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: siprec-bounces@ietf.org
> >>>>>>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of
> >>> Feenstra, Friso
> >>>>>>>>> Sent: 21 September 2011 08:31
> >>>>>>>>> To: Leon Portman; siprec@ietf.org
> >>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
> >>>>>>>>>
> >>>>>>>>> Leon,
> >>>>>>>>>
> >>>>>>>>> Yes, this is correct and this is how I would like
> >>> it to work.
> >>>>>>>>>
> >>>>>>>>> A few additional notes.
> >>>>>>>>> a. The implementation details of the CTI signalling between
> >>>>>>>>> softswitch and SRS is out of scope for the SIPREC
> >>>> standard, but
> >>>>>> most
> >>>>>>>>> softswitches offer a form of CTI signalling that can
> >>>> be used for
> >>>>>>>>> this signalling.
> >>>>>>>>> b. It is not defined how much info is send with the
> >>>> SDP from the
> >>>>>> SRS
> >>>>>>>>> to the SRC (via the softswitch). Worse case an
> >>>> offerless invite
> >>>>> is
> >>>>>>>>> send to start the RS session, next the SRC will
> >>> provide the CS
> >>>>>> info
> >>>>>>>>> in the OK with SDP and Metadata and the SRS will select the
> >>>>>> correct
> >>>>>>>>> streams with the ACK or through a re-Invite.
> >>>>>>>>> c. I anticipate that the forwarding by the softswitch
> >>>> of Invite
> >>>>>>>>> messages (CS and RS) is a 'standard' feature for the
> >>>> softswitch
> >>>>>>>>> acting as a SIP proxy server and as such can be left
> >>>> outside the
> >>>>>>>>> scope of the SIPREC standard.
> >>>>>>>>>
> >>>>>>>>> As an individual,
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>>
> >>>>>>>>> Friso
> >>>>>>>>>
> >>>>>>>>> friso.feenstra@logica.com
> >>>>>>>>> +31 6 415 46 305
> >>>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> >>>>>>>>> Sent: dinsdag 20 september 2011 18:03
> >>>>>>>>> To: Feenstra, Friso; siprec@ietf.org
> >>>>>>>>> Cc: Ravindran Parthasarathi; Paul Kyzivat
> >>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>>>>>>>
> >>>>>>>>> Friso
> >>>>>>>>>
> >>>>>>>>> It is a very good discussion. Let me try to understand the
> >>>>>> proposed
> >>>>>>>>> sequence  for example as incoming call from UA A to
> >>>> UA B, where
> >>>>> UA
> >>>>>> B
> >>>>>>>>> is SRC.
> >>>>>>>>> Actually UA B and softswitch are decomposed SRC.
> >>>>>>>>>
> >>>>>>>>> 1. UA A sends CS INVITE to softswitch 2. softswitch sends
> >> CS
> >>>>>> INVITE
> >>>>>>>>> to UA B (SRC) 3. softswitch reports via CTI to SRS
> >>>> about CS (UA A
> >>>>>>>>> calling UA B) 4. SRS decides to record and sends RS
> >>>> INVITE with
> >>>>>> SDP
> >>>>>>>>> to softswitch with some CS mapping info 5.
> >>> Softswitch sends RS
> >>>>>>>>> INVITE to UA B that acts as SRC 6. UA B send OK with
> >>>> its SDP via
> >>>>>>>>> softswitch to SRS
> >>>>>>>>>
> >>>>>>>>> This flow will require definition additional
> >>>> interface for step 3
> >>>>>>>>> and for softswitch to implement step 5 Is it correct flow?
> >>>>>>>>>
> >>>>>>>>> Regards
> >>>>>>>>>
> >>>>>>>>> Leon
> >>>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Feenstra, Friso [mailto:friso.feenstra@logica.com]
> >>>>>>>>> Sent: Tuesday, September 20, 2011 6:34 PM
> >>>>>>>>> To: siprec@ietf.org
> >>>>>>>>> Cc: Leon Portman; Ravindran Parthasarathi; Paul Kyzivat
> >>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>>>>>>>
> >>>>>>>>> Partha and Leon,
> >>>>>>>>>
> >>>>>>>>> The business intelligence (Policy Manager) in our
> >>> case is with
> >>>>> the
> >>>>>>>>> SRS and like the softswitch (acting as a SIP proxy)
> >>>> is deployed
> >>>>> on
> >>>>>> a
> >>>>>>>>> central location.
> >>>>>>>>> Agent handsets (UA's) are globally dispersed. So I am
> >>>> definitely
> >>>>>>>>> looking for a SIPREC solution where the SRC is
> >>>> implemented on the
> >>>>>> UA
> >>>>>>>>> (agent handset).
> >>>>>>>>>
> >>>>>>>>> When only the SRC can provide the RS Invite than additional
> >>>>>>>>> signalling is needed to initiate the recording between SRS
> >>>>> (Policy
> >>>>>>>>> Manager) and softswitch (CTI based API) and between
> >>> softswitch
> >>>>> and
> >>>>>>>>> agent handset (UA) (SIP?). So standards are needed for CTI
> >>>>>>>>> signalling from Policy Manager / SRS to softswitch and from
> >>>>>>>>> softswitch to the agent handset.
> >>>>>>>>>
> >>>>>>>>> Another reason why this is not a good idea, is that an
> >> extra
> >>>>>>>>> component (softswitch) is involved in the RS setup for the
> >>>>>>>>> conversion of the CTI message from the SRS into a SIP
> >>>>>>>>> message(?) towards the handset (SRC).
> >>>>>>>>>
> >>>>>>>>> With an SRS initiated flow the additional signalling
> >>>> definition
> >>>>> is
> >>>>>>>>> not needed and only minimal changes are needed on the
> >>>> softswitch
> >>>>>>>>> acting as a SIP proxy.
> >>>>>>>>>
> >>>>>>>>> Having all the agent handsets always start a RS
> >>>> session for each
> >>>>>> CS
> >>>>>>>>> would be quite a waste of SIP sessions,
> >>> specifically since the
> >>>>>>>>> softswitch is involved as SIP-proxy in all session setup
> >> and
> >>>>> since
> >>>>>>>>> only a limited number of sessions will need
> >>>>>>>> recording.
> >>>>>>>>>
> >>>>>>>>> As such I would appreciate the option of a SRS
> >>> based Invite in
> >>>>> the
> >>>>>>>>> standards.
> >>>>>>>>>
> >>>>>>>>> As an individual,
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>>
> >>>>>>>>> Friso
> >>>>>>>>> friso.feenstra@logica.com
> >>>>>>>>> +31 6 415 46 305
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Ravindran Parthasarathi
> >>> [mailto:pravindran@sonusnet.com]
> >>>>>>>>> Sent: dinsdag 20 september 2011 16:22
> >>>>>>>>> To: Feenstra, Friso; Paul Kyzivat; siprec@ietf.org
> >>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
> >>>>>>>>>
> >>>>>>>>> Friso,
> >>>>>>>>>
> >>>>>>>>> In case I remember correctly, the same SRS callflow
> >>>> was discussed
> >>>>>>>>> long back. The mentioned callflow is not good design in my
> >>>>> opinion
> >>>>>>>>> because extra channel is required between softswitch
> >>>> &  SRS apart
> >>>>>>>>> from SIPREC framework.
> >>>>>>>>>
> >>>>>>>>> The alternative is to start the recording from agent
> >> handset
> >>>>>> towards
> >>>>>>>>> SRS with CS id.  Please let me know the issue in this
> >>>> approach.
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>> Partha
> >>>>>>>>>
> >>>>>>>>>> -----Original Message-----
> >>>>>>>>>> From: siprec-bounces@ietf.org
> >>>> [mailto:siprec-bounces@ietf.org]
> >>>>> On
> >>>>>>>>>> Behalf Of Feenstra, Friso
> >>>>>>>>>> Sent: Tuesday, September 20, 2011 7:38 PM
> >>>>>>>>>> To: Paul Kyzivat; siprec@ietf.org
> >>>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
> >>>>>>>>>>
> >>>>>>>>>> Paul,
> >>>>>>>>>>
> >>>>>>>>>> Business intelligence is in the SRS. SRS is informed
> >>>>>>>>> out-of-band that
> >>>>>>>>>> CS session is started. Based on the out-of-band provided
> >>>>>>>>>> information the SRS determines that RS is needed.
> >>> Part of the
> >>>>>> out-
> >>>>>>>>>> of-band information is the identification of the
> >>>> SRC. Based on
> >>>>>> this
> >>>>>>>>> information
> >>>>>>>>>> the (offerless) Invite is send to the SRC.
> >>>>>>>>>>
> >>>>>>>>>> The SRC intelligence is included in the UA (agent
> >>>> handset). This
> >>>>>>>>>> way only a limited implementation is needed on the
> >>>> controlling
> >>>>>>>>> softswitch.
> >>>>>>>>>> RS is managed between SRS recorder and agent handset.
> >>>>>>>>>>
> >>>>>>>>>> As an individual,
> >>>>>>>>>>
> >>>>>>>>>> Regards,
> >>>>>>>>>>
> >>>>>>>>>> Friso
> >>>>>>>>>> friso.feenstra@logica.com
> >>>>>>>>>> +31 6 415 46 305
> >>>>>>>>>>
> >>>>>>>>>> -----Original Message-----
> >>>>>>>>>> From: siprec-bounces@ietf.org
> >>>> [mailto:siprec-bounces@ietf.org]
> >>>>> On
> >>>>>>>>>> Behalf Of Paul Kyzivat
> >>>>>>>>>> Sent: dinsdag 20 september 2011 15:54
> >>>>>>>>>> To: siprec@ietf.org
> >>>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
> >>>>>>>>>>
> >>>>>>>>>> Friso,
> >>>>>>>>>>
> >>>>>>>>>> On 9/20/11 6:23 AM, Feenstra, Friso wrote:
> >>>>>>>>>>> As a new participant I would like to make the following
> >>>>> remark.
> >>>>>>>>>>>
> >>>>>>>>>>> We currently have a strong requirement for a
> >>>> =B4intelligent=B4 SRS
> >>>>>>>>>>> capable
> >>>>>>>>>> of
> >>>>>>>>>>>
> >>>>>>>>>>> starting and stopping RS sessions. We want to deploy a
> >>>>>>>>> contact centre
> >>>>>>>>>>>
> >>>>>>>>>>> solution with agents dispersed around the globe.
> >>>> The business
> >>>>>>>>>> intelligence
> >>>>>>>>>>>
> >>>>>>>>>>> of what and when to record will be at the SRS, so the
> >> SRS
> >>>>>> should
> >>>>>>>> be
> >>>>>>>>>> capable
> >>>>>>>>>>>
> >>>>>>>>>>> determining what's to be recorded and of starting the
> >> RS.
> >>>>>>>>>>
> >>>>>>>>>> Could you explain more about how the intelligence is
> >>>>> distributed?
> >>>>>>>>>> How much does the SRS know a priori about the calls?
> >>>>>>>>>> And what is the granularity of the SRC? Are you imagining
> >>>>>>>>> that the SRC
> >>>>>>>>>> is on a per-agent basis? Or does an SRC cover many
> >>> agents and
> >>>>>> many
> >>>>>>>>>> concurrent calls?
> >>>>>>>>>>
> >>>>>>>>>>> An option could be that the SRS sends an offerless
> >>>> invite, as
> >>>>>>>>>> currently
> >>>>>>>>>>>
> >>>>>>>>>>> defined in the architecture. Next the SRC could provide
> >>>>>>>>> based on its
> >>>>>>>>>>>
> >>>>>>>>>>> knowledge of the current CS send the 200 OK with the SDP
> >>>>>>>>> and metadata
> >>>>>>>>>>>
> >>>>>>>>>>> describing the available sessions. With this
> >>> knowledge and
> >>>>>> based
> >>>>>>>> on
> >>>>>>>>>> the
> >>>>>>>>>>>
> >>>>>>>>>>> business intelligence in the SRS, the SRS could then
> >>>>>>>>> accept which of
> >>>>>>>>>> the
> >>>>>>>>>>>
> >>>>>>>>>>> available streams it would like for recording,
> >>> either in an
> >>>>> ACK
> >>>>>>>>>> response or
> >>>>>>>>>>>
> >>>>>>>>>>> through a re-Invite.
> >>>>>>>>>>
> >>>>>>>>>> I can see how this could at least scale right if
> >>> the SRC was
> >>>>>>>>> per-agent.
> >>>>>>>>>> But if the SRC was something like a PBX that
> >>> covered all the
> >>>>>>>>> agents in
> >>>>>>>>>> a facility, then it wouldn't scale reasonably, because the
> >>>>>>>>> offer would
> >>>>>>>>>> then contain perhaps hundreds of media streams.
> >>>>>>>>>>
> >>>>>>>>>>> I hope there will be room for this use case in the RFC.
> >>>>>>>>>>>
> >>>>>>>>>>> As an individual,
> >>>>>>>>>>>
> >>>>>>>>>>> Regards,
> >>>>>>>>>>>
> >>>>>>>>>>> Friso Feenstra
> >>>>>>>>>>>
> >>>>>>>>>>> Friso.feenstra@logica.com
> >>>> <mailto:Friso.feenstra@logica.com>
> >>>>>>>>>>>
> >>>>>>>>>>> +31 6 415 46 305
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Think green - keep it on the screen. This e-mail and any
> >>>>>>>>> attachment
> >>>>>>>>>>> is for authorised use by the intended
> >>> recipient(s) only. It
> >>>>> may
> >>>>>>>>>>> contain proprietary material, confidential
> >>>> information and/or
> >>>>>> be
> >>>>>>>>>>> subject to legal privilege. It should not be
> >>>> copied, disclosed
> >>>>>>>>>>> to, retained or
> >>>>>>>>>> used
> >>>>>>>>>>> by, any other party. If you are not an intended
> >> recipient
> >>>>>>>>> then please
> >>>>>>>>>>> promptly delete this e-mail and any attachment and
> >>>> all copies
> >>>>>> and
> >>>>>>>>>> inform
> >>>>>>>>>>> the sender. Thank you.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> 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
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Think green - keep it on the screen.
> >>>>>>>>>>
> >>>>>>>>>> This e-mail and any attachment is for authorised use by
> >> the
> >>>>>>>>>> intended
> >>>>>>>>>> recipient(s) only. It may contain proprietary material,
> >>>>>>>>>> confidential information and/or be subject to legal
> >>>> privilege.
> >>>>> It
> >>>>>>>>>> should not be copied, disclosed to, retained or
> >>> used by, any
> >>>>>> other
> >>>>>>> party.
> >>>>>>>>> If you are
> >>>>>>>>>> not an intended recipient then please promptly delete this
> >>>>>>>>> e-mail and
> >>>>>>>>>> any attachment and all copies and inform the sender.
> >>>> Thank you.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> siprec mailing list
> >>>>>>>>>> siprec@ietf.org
> >>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Think green - keep it on the screen.
> >>>>>>>>>
> >>>>>>>>> This e-mail and any attachment is for authorised use by the
> >>>>>> intended
> >>>>>>>>> recipient(s) only. It may contain proprietary material,
> >>>>>> confidential
> >>>>>>>>> information and/or be subject to legal privilege. It
> >>>> should not
> >>>>> be
> >>>>>>>>> copied, disclosed to, retained or used by, any
> >>> other party. If
> >>>>> you
> >>>>>>>>> are not an intended recipient then please promptly
> >>> delete this
> >>>>>>>>> e-mail and any attachment and all copies and inform
> >>>> the sender.
> >>>>>>>>> Thank you.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Think green - keep it on the screen.
> >>>>>>>>>
> >>>>>>>>> This e-mail and any attachment is for authorised use by the
> >>>>>> intended
> >>>>>>>>> recipient(s) only. It may contain proprietary material,
> >>>>>> confidential
> >>>>>>>>> information and/or be subject to legal privilege. It
> >>>> should not
> >>>>> be
> >>>>>>>>> copied, disclosed to, retained or used by, any
> >>> other party. If
> >>>>> you
> >>>>>>>>> are not an intended recipient then please promptly
> >>> delete this
> >>>>>>>>> e-mail and any attachment and all copies and inform
> >>>> the sender.
> >>>>>>>>> Thank you.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> 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
> >>>>
> >>>
> >>>
> >>> Think green - keep it on the screen.
> >>>
> >>> This e-mail and any attachment is for authorised use by the
> >>> intended recipient(s) only. It may contain proprietary
> >>> material, confidential information and/or be subject to legal
> >>> privilege. It should not be copied, disclosed to, retained or
> >>> used by, any other party. If you are not an intended
> >>> recipient then please promptly delete this e-mail and any
> >>> attachment and all copies and inform the sender. Thank you.
> >>>
> >>>
> >>>
> > _______________________________________________
> > 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

From pravindran@sonusnet.com  Tue Nov  1 11:09:47 2011
Return-Path: <pravindran@sonusnet.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 24FD611E80B0 for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 11:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.365
X-Spam-Level: 
X-Spam-Status: No, score=-2.365 tagged_above=-999 required=5 tests=[AWL=-0.366, BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HR9AAfBoXQuS for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 11:09:45 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id AE37121F9891 for <siprec@ietf.org>; Tue,  1 Nov 2011 11:09:38 -0700 (PDT)
Received: from sonusmail07.sonusnet.com (sonusmail07.sonusnet.com [10.128.32.157]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pA1I89oa008259;  Tue, 1 Nov 2011 14:08:10 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail07.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Nov 2011 14:05:56 -0400
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Nov 2011 23:35:59 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Tue, 1 Nov 2011 23:35:59 +0530
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] participant & stream outside the scope of session
Thread-Index: AcyVm6FSEXoItteWRSWY5B83xRNGowAAE87wAJBWCYAAJ8HxAAAQRwbg
Date: Tue, 1 Nov 2011 18:05:58 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6CBD20@inba-mail01.sonusnet.com>
References: <35BCE99A477D6A4986FB2216D8CF2CFD082B7DEA@XMB-BGL-417.cisco.com><4EA9C920.8000200@alum.mit.edu><35BCE99A477D6A4986FB2216D8CF2CFD082B7ECA@XMB-BGL-417.cisco.com><2E239D6FCD033C4BAF15F386A979BF51159D3F@sonusinmail02.sonusnet.com><4EAAB8E9.8070708@alum.mit.edu> <35BCE99A477D6A4986FB2216D8CF2CFD082B80A1@XMB-BGL-417.cisco.com> <35BCE99A477D6A4986FB2216D8CF2CFD082B80A3@XMB-BGL-417.cisco.com> <2E239D6FCD033C4BAF15F386A979BF51159D78@sonusinmail02.sonusnet.com> <35BCE99A477D6A4986FB2216D8CF2CFD082B80C3@XMB-BGL-417.cisco.com> <4EAAEDF5.7080004@alum.mit.edu> <2E239D6FCD033C4BAF15F386A979BF51159D7E@sonusinmail02.sonusnet.com> <622B0E14298DDE47ACA9E16B292F22A40F2F6D2E@Mail1.acmepacket.com> <4EB00F4A.6000706@alum.mit.edu>
In-Reply-To: <4EB00F4A.6000706@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Nov 2011 18:05:59.0831 (UTC) FILETIME=[E911EA70:01CC98C0]
Subject: Re: [siprec] participant & stream outside the scope of session
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: Tue, 01 Nov 2011 18:09:47 -0000

Paul/Brad,

Please read inline.

Thanks
Partha

>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>Of Paul Kyzivat
>Sent: Tuesday, November 01, 2011 8:55 PM
>To: siprec@ietf.org
>Subject: Re: [siprec] participant & stream outside the scope of session
>
>On 10/31/11 4:26 PM, Brad Winslow wrote:
>> Hi Folks,
>>
>> Perhaps I'm missing something about the Participant/Session
>association, and perhaps some of this applies to the stream/session
>association as well.
>>
>> The current metadata draft has two attributes for the participant, the
>"id" and the "session" both expressed as UUIDs.
>> The "id" field seems to be a unique identifier the SRC could use to
>indicate the uniqueness of this participant in multiple CSs assuming the
>SRC has the ability to determine if the participant is the same between
>CSs.  The SRS cold use this field to identify participants across
>sessions.
>
>That is intended.
>
>> The same holds true of the 'id' field in the stream element, if we
>assume a particular 'id' is a MOH stream, it's id could be consistent
>across CSs.
>
>Yes.
>
>> IMO we are under-utilizing the 'id' attribute for participant and
>stream identity.
>
>I'm happy to have suggestions of how to do things better.
>
>> In the case where the SRC cannot determine if the unique identity of
>the participant, it would simply create a new UUID for the participant
>when it enters into a new CS.
>
>Again, that is the intent.
>If a newly discovered participant cannot be determined to be "the same"
>as a previously identified participant, then it is treated as a new one.
>
>Note that an identical "From" field is not sufficient info to consider
>this participant the same as some other participant.
<partha> Agree with Paul till this point </partha>

>
>> Much of the information in the new ParticipantSessionAssoc element
>could be contained in the participant element. perhaps I don't
>understand the use-cases where the association element reduces the
>complexity of the metadata well enough. Additional xs:any elements could
>be passed between SRC and SRS to help identify the participants however
>this would quickly lead to interoperability problems between vendors.
>
>The intent is that the ParticipantSessionAssoc carries information that
>is specific to the involvement of the participant in a particular
>session, while the Participant element carries the information that
>describes the participant independent of the session or stream it is
>involved in.
>
<partha> Infact, participant XML element with session id (current XML form)=
=20
includes participant and participantsessionassoc. The reason for this desig=
n=20
is to make partial update of metadata element or else we would have easily
end-up in simple hierarchical metadata. Now the question is whether=20
separating participant XML element and participantSessionAssoc element is=20
going to make much difference in the partial update? IMO, participantSessio=
nAssoc
change is limited compare to participant change itself. We have 4 element
within participant (1 for participant + 3 for participantsessioAssoc). The =
partial
update for 1 element in participant does not make much different.

The same argument applies for streamSessionAssoc as well. </partha>

>Which information do you think could be moved?
>
>	Thanks,
>	Paul
>
>> Thanks,
>> Brad
>>
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>Behalf Of Ravindran Parthasarathi
>> Sent: Friday, October 28, 2011 3:49 PM
>> To: Paul Kyzivat; Ram Mohan R (rmohanr); Leon Portman
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] participant&  stream outside the scope of
>session
>>
>> Paul/Ram,
>>
>> Now, participant and stream are associated with session as an
>aggregation. In case participant is possible to be represented outside
>session, it is very much possible for stream to be outside the session
>as shown in persistent usecase. In case of persistent usecase, RS stream
>is created in advance to avoid the earlier clipping, the session will be
>associated in metadata whenever the session is established, session will
>be terminated without removing RS stream
>>
>> In case new participant session associated XML element is added, it is
>possible to have stream session associated XML element as well
>separately.
>>
>> Including Leon in this mail thread as he asked for persistent usecase.
>> I'm reopening this usecase because let us close the related issue at
>the same time.
>>
>> Thanks
>> Partha
>>
>>> -----Original Message-----
>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>> Sent: Friday, October 28, 2011 11:31 PM
>>> To: Ram Mohan R (rmohanr)
>>> Cc: Ravindran Parthasarathi; siprec@ietf.org
>>> Subject: Re: [siprec] participant&  stream outside the scope of
>session
>>>
>>> +1 to Ram's response.
>>>
>>> As I noted before, if you want to reopen question of allowing stream
>>> without session, I think that should be discussed separately.
>>>
>>> 	Thanks,
>>> 	Paul
>>>
>>> On 10/28/11 1:27 PM, Ram Mohan R (rmohanr) wrote:
>>>> Hi Partha,
>>>>
>>>> Please see inline
>>>>
>>>>> -----Original Message-----
>>>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>>>>> Sent: Friday, October 28, 2011 10:49 PM
>>>>> To: Ram Mohan R (rmohanr); Paul Kyzivat
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] participant&   stream outside the scope of
>>>> session
>>>>>
>>>>> Hi Ram,
>>>>>
>>>>> As Paul mentioned, stream associated with zero session was brought
>> up
>>>>> as
>>>>> part of the persistent connection from the endpoint discussion and
>> it
>>>>> was pushed back because stream&   participant has to be within
>> session
>>>>> (CS). I'm worried that participant to zero session change may
>> re-open
>>>>> the earlier closure and call for one more discussion.
>>>>>
>>>>> Also, the current syntax of stream is associated with session
>> closely
>>>>> which has to be changed consistently in case participant is changed
>>>> its
>>>>> association representation with session.
>>>>
>>>> I don't see a need for the above. We are changing the participant
>>>> association to session to allow it to be consistent with XML if we
>>>> choose approach 2.
>>>> Even in approach 2, stream has to be associated with a session and
>so
>>>> there is no need to change that association.
>>>>
>>>> Regards,
>>>> Ram
>>>>
>>>>>
>>>>>         <stream id=3D"urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a"
>>>>>                 session=3D"urn:uuid:cd27cfa1-2bdd-4830-a653-
>>> 70374d10f103">
>>>>>                 <label>98</label>
>>>>>             </stream>
>>>>>
>>>>> It will be good in case we get the feedback on these aspect.
>>>>>
>>>>> Thanks
>>>>> Partha
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>> Sent: Friday, October 28, 2011 9:39 PM
>>>>>> To: Ram Mohan R (rmohanr); Paul Kyzivat; Ravindran Parthasarathi
>>>>>> Cc: siprec@ietf.org
>>>>>> Subject: RE: [siprec] participant&   stream outside the scope of
>>>>> session
>>>>>>
>>>>>> A typo in the below email. Sorry for that. I meant
>>>>>>
>>>>>> "
>>>>>> I don't see a strong use case to have stream associate to zero
>>>>>> sessions. IMO we can retain the stream associations
>>>>>>                                          ^^^^^^ ^^^^ as it is in
>the
>>>>>> current model."
>>>>>>
>>>>>> Thanks,
>>>>>> Ram
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>>>> Behalf Of Ram Mohan R (rmohanr)
>>>>>>> Sent: Friday, October 28, 2011 9:27 PM
>>>>>>> To: Paul Kyzivat; Ravindran Parthasarathi
>>>>>>> Cc: siprec@ietf.org
>>>>>>> Subject: Re: [siprec] participant&   stream outside the scope of
>>>>>> session
>>>>>>>
>>>>>>> I don't see a strong use case to have session associate to zero
>>>>>>> sessions. IMO we can retain the session associations as it is in
>>>> the
>>>>>>> current model.
>>>>>>>
>>>>>>> Now coming to participant, the main reason why I am inclined to
>>>>> change
>>>>>>> the association is to have consistency with XML  if we adopt
>>>>> approach
>>>>>>> 2.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Ram
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>>>>>>> Sent: Friday, October 28, 2011 7:45 PM
>>>>>>>> To: Ravindran Parthasarathi
>>>>>>>> Cc: Ram Mohan R (rmohanr); siprec@ietf.org
>>>>>>>> Subject: Re: participant&   stream outside the scope of session
>>>>>>>>
>>>>>>>> This proposes an additional change, to remove the subordination
>>>> of
>>>>>>>> stream to session. IMO this should be considered separately from
>>>>>>>> participant, as the arguments are different.
>>>>>>>>
>>>>>>>> AFAICT, the use case Partha gives below is the only one that
>>>> calls
>>>>>>> for
>>>>>>>> stream independent of session. And I'm not sure of the need for
>>>>>> this.
>>>>>>>> ISTM the only reason to do this is to really record streams from
>>>>>>>> participants when there is no session.
>>>>>>>>
>>>>>>>> This might allow capturing media earlier during call setup, by
>>>>>>> defining
>>>>>>>> the streams early, and associating them with participants and
>>>>>>> sessions
>>>>>>>> when that becomes known. *If* an SRS can figure out how to take
>>>>>>>> advantage of that.
>>>>>>>>
>>>>>>>> 	Thanks,
>>>>>>>> 	Paul
>>>>>>>>
>>>>>>>> On 10/28/11 5:09 AM, Ravindran Parthasarathi wrote:
>>>>>>>>> <Sorry for the lengthy mail. IMO, This discussion is one of the
>>>>>>> major
>>>>>>>>>     change in metadata>
>>>>>>>>>
>>>>>>>>> I'm interested in knowing whether folks are interested in
>>>>> handling
>>>>>>>>> participant, stream completely outside the scope of session.
>>>>>>>>> In fact, we discussed this requirement as part of metadata
>>>> model
>>>>>>>>> discussion and come to the conclusion not to include. In case
>>>>>>>>> participant, stream are outside the scope of session, the
>>>>>> following
>>>>>>>>> recording metadata from SRC is valid:
>>>>>>>>>
>>>>>>>>> <recording xmlns=3D'urn:ietf:params:xml:ns:recording'>
>>>>>>>>>              <dataMode>full</dataMode>
>>>>>>>>>              <participant
>>>>>>>>>                 id=3D"urn:uuid:b2b7c112-5982-469d-9007-
>>>>> 6ddbecca64d3">
>>>>>>>>>                  <aor>sip:agent1@callcenter.com</aor>
>>>>>>>>>                 <send>urn:uuid:f3373a7b-4958-4e55-8820-
>>>>>>>> d03a191fb76a</send>
>>>>>>>>>               </participant>
>>>>>>>>>              <stream id=3D"urn:uuid:f3373a7b-4958-4e55-8820-
>>>>>>>> d03a191fb76a">
>>>>>>>>>                  <label>96</label>
>>>>>>>>>              </stream>
>>>>>>>>>              <stream id=3D"urn:uuid:01c47915-4777-11d8-bc70-
>>>>>>>> 0090272ff725">
>>>>>>>>>                  <label>97</label>
>>>>>>>>>              </stream>
>>>>>>>>> </recording>
>>>>>>>>>
>>>>>>>>> Also, in the later partial update, session shall be added and
>>>>>>>> associate
>>>>>>>>> with the above participant&    stream element.
>>>>>>>>>
>>>>>>>>> Here, SRS has to maintain participant, stream unique id as a
>>>>>>> separate
>>>>>>>>> flat
>>>>>>>>> Data (no hierarchy). Only issue is that SRS has to maintain
>>>> flat
>>>>>>>>> database for
>>>>>>>>> Each of these elements.
>>>>>>>>>
>>>>>>>>> The current -04 draft is based on the assumption that
>>>>> participant
>>>>>>> and
>>>>>>>>> stream are within a session and it is possible for participant&
>>>>>>>> stream
>>>>>>>>> to move across multiple sessions using unique id. The rationale
>>>>> of
>>>>>>>> the
>>>>>>>>> current draft approach is that commonly used callflow metadata
>>>>> is
>>>>>>>> simple
>>>>>>>>>
>>>>>>>>> whereas specific corner case callflow like same participant in
>>>>>>>> multiple
>>>>>>>>> session will have complex mechanism.
>>>>>>>>>
>>>>>>>>> In case we see the strong usecases for going for independent
>>>>>>> stream,
>>>>>>>>> Participants which is outside the session, we will go for it.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Partha
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>>>>> On
>>>>>>>>> Behalf
>>>>>>>>>> Of Ram Mohan R (rmohanr)
>>>>>>>>>> Sent: Friday, October 28, 2011 10:24 AM
>>>>>>>>>> To: Paul Kyzivat; siprec@ietf.org
>>>>>>>>>> Subject: Re: [siprec] Issue with participant scoping in the
>>>>>>> current
>>>>>>>>>> modeland its implication on association attr representation
>>>>>>>>>>
>>>>>>>>>> To add to Paul, with the proposed change, the model will look
>>>>> as
>>>>>>>> below
>>>>>>>>>>
>>>>>>>>>>     +-------------------------------+
>>>>>>>>>>     |   Communication Session (CS)  |
>>>>>>>>>>     |                               |
>>>>>>>>>>     +-------------------------------+
>>>>>>>>>>           | 0..*                 |1..*
>>>>>>>>>>           | ^^^^^^^^             |
>>>>>>>>>>           | 2..*                 |0..*
>>>>>>>>>>     +-------------+ receives +----------------+
>>>>>>>>>>     | Participant |----------|  Media Streams |
>>>>>>>>>>     |             |0..*  0..*|                |
>>>>>>>>>>     |             |          |                |
>>>>>>>>>>     |             |          |                |
>>>>>>>>>>     |             |  sends   |                |
>>>>>>>>>>     |             |----------|                |
>>>>>>>>>>     |             |1.*   0..*|                |
>>>>>>>>>>     +-------------+          +----------------+
>>>>>>>>>>
>>>>>>>>>> A participant can be associated with zero or more sessions.
>>>>>>>>>>
>>>>>>>>>> And with the above model we can have an approach to define a
>>>>>>>>> participant
>>>>>>>>>> with no associations to sessions and have XML elements
>>>> separate
>>>>>>>> (like
>>>>>>>>>> <participantSessAssoc>) for association classes as in approach
>>>>> 2
>>>>>>>>>> mentioned below
>>>>>>>>>>
>>>>>>>>>> Ram
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>> [mailto:siprec-bounces@ietf.org]
>>>>>> On
>>>>>>>>>>> Behalf Of Paul Kyzivat
>>>>>>>>>>> Sent: Friday, October 28, 2011 2:42 AM
>>>>>>>>>>> To: siprec@ietf.org
>>>>>>>>>>> Subject: Re: [siprec] Issue with participant scoping in the
>>>>>>> current
>>>>>>>>>>> model and its implication on association attr representation
>>>>>>>>>>>
>>>>>>>>>>> On 10/27/11 1:46 PM, Ram Mohan R (rmohanr) wrote:
>>>>>>>>>>>> (Sorry for lengthy e-mail)
>>>>>>>>>>>>
>>>>>>>>>>>> This is a follow up to the mail thread
>>>>>>>>>>>> http://www.ietf.org/mail-
>>>>>>> archive/web/siprec/current/msg02810.html
>>>>>>>>>>>>
>>>>>>>>>>>> In the last IETF meeting there was a consensus that a
>>>>>>> participant
>>>>>>>>>> can
>>>>>>>>>>>> have a life outside of CS.
>>>>>>>>>>>>
>>>>>>>>>>>> However the current model scopes participant to always a
>>>>>>> session.
>>>>>>>>>>>
>>>>>>>>>>> I don't think that is quite right. The *model* requires that
>>>>>> each
>>>>>>>>>>> participant be associated with one or more sessions. It
>>>>> doesn't
>>>>>>>> scope
>>>>>>>>>>> to
>>>>>>>>>>> a single session.
>>>>>>>>>>>
>>>>>>>>>>>> Should we have to change the model to have participant
>>>>> outside
>>>>>>>>> scope
>>>>>>>>>>> of
>>>>>>>>>>>> session ? I think it may not make sense to model
>>>> participants
>>>>>>>> under
>>>>>>>>>>> RS
>>>>>>>>>>>> as these are participants of Session. The only use case
>>>> where
>>>>>> we
>>>>>>>>> can
>>>>>>>>>>>> have a participant in a RS with no CS is for Persistent
>>>>>>> recording
>>>>>>>>>>>> sessions (e.g. setup from agent phone(SRC) to SRS) This RS
>>>>> will
>>>>>>> be
>>>>>>>>>>> setup
>>>>>>>>>>>> even without any CS.  If an SRC for this case sends a
>>>>> snapshot
>>>>>>>>>> before
>>>>>>>>>>> a
>>>>>>>>>>>> CS starts it may have participant information without any
>>>>>>> session.
>>>>>>>>>>>> Does the WG sees a value in such a use case or should we
>>>>> retain
>>>>>>>> the
>>>>>>>>>>>> model as is ?
>>>>>>>>>>>
>>>>>>>>>>> IMO the change we would be talking about is that a
>>>> participant
>>>>>>> can
>>>>>>>> be
>>>>>>>>>>> associated with *zero* or more sessions, rather than one or
>>>>>> more.
>>>>>>>>>>>
>>>>>>>>>>> In addition to the use case Ram mentions above, this would
>>>>> help
>>>>>>>> with
>>>>>>>>>>> the
>>>>>>>>>>> mapping to xml. If we go with participantSessAssoc (as
>>>>> mentioned
>>>>>>>>>> below)
>>>>>>>>>>> it becomes *possible* to define a participant with no
>>>>>>> associations
>>>>>>>> to
>>>>>>>>>>> sessions. Allowing the same in the model at least makes them
>>>>>>>>>>> consistent.
>>>>>>>>>>>
>>>>>>>>>>> 	Thanks,
>>>>>>>>>>> 	Paul
>>>>>>>>>>>
>>>>>>>>>>>> The current model (ver 04) also impacts the way association
>>>>>>>>>>> attributes
>>>>>>>>>>>> are represented. Since the current draft (ver-04)the
>>>> metadata
>>>>>>>> model
>>>>>>>>>>>> scopes participant and stream elements to session the schema
>>>>>>> also
>>>>>>>>>> was
>>>>>>>>>>>> designed the same way. The<participant>     and<stream>
>>>>>>> attributes
>>>>>>>>> are
>>>>>>>>>>>> scoped/associated to a session (see section 7.1 example).
>>>> IOW
>>>>>>> the
>>>>>>>>>>>> association attributes of<participant>     to<session>
>are
>>>>>>> already
>>>>>>>>>>>> represented.
>>>>>>>>>>>>
>>>>>>>>>>>> Now if we have to go with approach 2 for representing
>>>>>>> association
>>>>>>>>>>>> attributes, we will have to do one of the two ways:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> If we stick the current model/schema:
>>>>>>>>>>>> -----------------------------------
>>>>>>>>>>>> We will have represent in the following way. Note this is a
>>>>> mix
>>>>>>> of
>>>>>>>>>>>> approach 1 (existing representation which acheives
>>>>> participant
>>>>>>>>>>> session
>>>>>>>>>>>> association) and approach 2 ( for part-stream association).
>>>>>> The
>>>>>>>>>>> issue
>>>>>>>>>>>> with this approach is if the same participant is
>>>>> simultaneously
>>>>>>> in
>>>>>>>>>>>> multiple sessions( cases like participant goes on hold on
>>>> one
>>>>>>> line
>>>>>>>>>>> and
>>>>>>>>>>>> talks to another participant) and SRC sends a snapshot then
>>>>> we
>>>>>>>> will
>>>>>>>>>>> have
>>>>>>>>>>>> multiple<participant>     elements each having different
>>>>> session
>>>>>>>> IDs.
>>>>>>>>>>>>             <participant
>>>>>>>>>>>>
>>>>> id=3D"urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>>
>>>>>>>>> session=3D"urn:uuid:855a5ded-8420-456d-a70f-6da1eeaeb425">
>>>>>>>>>>>>                      <aor>sip:ram@blr.cisco.com</aor>
>>>>>>>>>>>>                      <associate-time>2010-12-
>>>>>>>> 16T23:41:07Z</associate-
>>>>>>>>>>> time>
>>>>>>>>>>>>                      <capabilities>     XXX</capabilties>
>>>>>>>>>>>>              </participant>
>>>>>>>>>>>>
>>>>>>>>>>>> And for participant-stream you will have a new element
>>>>>>>>>>>>
>>>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>>>      participant=3D"urn:uuid:b2b7c112-5982-469d-9007-
>>>>> 6ddbecca64d3"
>>>>>>>>>>>>      stream =3D"urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a
>">
>>>>>>>>>>>>         <associate-time>2010-12-16T23:41:07Z</associate-
>time>
>>>>>>>>>>>>         <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>>>
>>>>>>>>>>>> If we change the model to remove the scoping of
>>>>>>> participant/stream
>>>>>>>>>> to
>>>>>>>>>>>> session:
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>> --------------------------------------------------------------------
>>>>>>>> -
>>>>>>>>>>> ---
>>>>>>>>>>>> -----
>>>>>>>>>>>>
>>>>>>>>>>>> <participant
>>>>>>>>>>>>
>>>>>> id=3D"urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3">
>>>>>>>>>>>>                <aor>sip:ram@blr.cisco.com</aor>
></participant>
>>>>>>>>>>>>
>>>>>>>>>>>> <participantSessAssoc
>>>>>>>>>>>>
>>>>>>>>>> participant=3D"urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>>                session=3D"urn:uuid:855a5ded-8420-456d-a70f-
>>>>>>>> 6da1eeaeb425"
>>>>>>>>>>>>
>>>>>>>>>> <associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>>                    <capabilities>     XXX</capabilties>
>>>>>>>>>>>> </participantSessAssoc>
>>>>>>>>>>>>
>>>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>>>      participant=3D"urn:uuid:b2b7c112-5982-469d-9007-
>>>>> 6ddbecca64d3"
>>>>>>>>>>>>      stream =3D"urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a
>">
>>>>>>>>>>>>         <associate-time>2010-12-16T23:41:07Z</associate-
>time>
>>>>>>>>>>>>         <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>>>
>>>>>>>>>>>> Let me know your comments.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Ram
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>
>
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec

From pravindran@sonusnet.com  Tue Nov  1 12:54:13 2011
Return-Path: <pravindran@sonusnet.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 039AE1F0CE2 for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 12:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level: 
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[AWL=-0.344, BAYES_00=-2.599, J_CHICKENPOX_81=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmtDPSYXyzSf for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 12:54:12 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 0378E1F0CD5 for <siprec@ietf.org>; Tue,  1 Nov 2011 12:54:11 -0700 (PDT)
Received: from sonusmail04.sonusnet.com (sonusmail04.sonusnet.com [10.128.32.98]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pA1JS0E9028292;  Tue, 1 Nov 2011 15:28:00 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail04.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Nov 2011 15:26:25 -0400
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Nov 2011 00:56:28 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Wed, 2 Nov 2011 00:56:28 +0530
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: "finlay.fraser@bt.com" <finlay.fraser@bt.com>, "rmohanr@cisco.com" <rmohanr@cisco.com>, "john.2.stafford@bt.com" <john.2.stafford@bt.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
Thread-Index: AQHMl9IYaRYn3PgZpEiEBZ/ddZrMQZWWKdaAgAASwYCAAAvsgIAA8I2AgAAZn4CAARV/UA==
Date: Tue, 1 Nov 2011 19:26:27 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6CBDF4@inba-mail01.sonusnet.com>
References: <20111031133617.24449.96357.idtracker@ietfa.amsl.com> <BBA98B7742309546A60F3AE3B4E975A72822C3A32F@EMV64-UKRD.domain1.systemhost.net>, <35BCE99A477D6A4986FB2216D8CF2CFD082B8463@XMB-BGL-417.cisco.com> <BBA98B7742309546A60F3AE3B4E975A72822C3A332@EMV64-UKRD.domain1.systemhost.net>, <35BCE99A477D6A4986FB2216D8CF2CFD082B8592@XMB-BGL-417.cisco.com> <67DAF295CD01EB44AE6EA8A51F6ABF0A4069146D47@EMV62-UKRD.domain1.systemhost.net>
In-Reply-To: <67DAF295CD01EB44AE6EA8A51F6ABF0A4069146D47@EMV62-UKRD.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Nov 2011 19:26:28.0956 (UTC) FILETIME=[2773E9C0:01CC98CC]
Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
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: Tue, 01 Nov 2011 19:54:13 -0000

Hi Finlay,

AFAIK, we haven't heard any objection for the current proposal from Voice=20
Recorder implementers.=20

Thanks
Partha

>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>Of finlay.fraser@bt.com
>Sent: Tuesday, November 01, 2011 1:52 PM
>To: rmohanr@cisco.com; john.2.stafford@bt.com; siprec@ietf.org
>Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>
>Ram
>
>The only issue I can see is that the voice recorder companies will not
>be able to do call reconstruction as there will be parts of the call
>where they have no RS that has an activestream and so will not be
>informed about these parts of a CS.
>
>I agree that in terms of recording this info is not needed as there is
>no recording associated with it. However any voice recorder that was
>hoping to use the meta data to provide call records will now not be abl
>eto do so.
>
>Since we are developing th eswitch side of this we are OK with it I just
>wanted to confirm th eVoice Recorder companies are also happy
>
>Finlay
>
>________________________________________
>From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of Ram
>Mohan R (rmohanr) [rmohanr@cisco.com]
>Sent: 01 November 2011 06:49
>To: Stafford,J,John,JRJ3X C; siprec@ietf.org
>Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>
>Hi John S
>
>Please see inline
>
>> -----Original Message-----
>> From: john.2.stafford@bt.com [mailto:john.2.stafford@bt.com]
>> Sent: Monday, October 31, 2011 9:59 PM
>> To: Ram Mohan R (rmohanr); siprec@ietf.org
>> Subject: RE: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>
>> Ram,
>>
>> If CS has associate/dissaociated instead of begin/end times, then
>there
>> won't be any way of signalling that a CS has ended, only that it is no
>> longer being recorded.
>>
>> Especially as Charles says it was going to be allowed to have a CS
>with
>> zero participants.
>>
>> Maybe CS needs BOTH associate/dissassociate and begin/end times ?
>
>The associate-time here indicates the time a CS was associated with a
>RS. IOW it is the time the recording of CS is started in that RS.
>Disassociate time indicate the time the recording of CS was stopped from
>that RS.  The reason why this attribute was added is to address cases
>where only parts of CS is recorded(e.g. you record the first few mins of
>a CS, then stop the recording, then re-start recording of the same CS
>after some time). In such cases indicating begin/end of CS is not
>correct as CS has not ended, but RS has ended.  So the WG decided it's
>better to have associate/disassociate time and have its scope to a RS so
>that a CS may have multiple associate/disassociate times if need be. For
>simple cases where the entire CS is recorded, the associate/disassociate
>times may be mapped to the CS begin/end times assuming recording is
>started the same moment CS is setup.
>
> I agree that with this approach, we are not indicating explicitly
>indicating when the CS has actually started/ended.
>From the past discussions, there was no much interest in keeping both of
>this information. If you think there are enough use-cases where
>indicating both these will be helpful please bring them, we can discuss
>further and add begin/end times after getting consensus from WG.
>
>Regards,
>Ram
>
>>
>> Rgds
>> John Stafford | Solution Architect 1 | BT Global Services | Tel:+44
>> (0)1932 773504   | E: john.2.stafford@bt.com  |
>> www.bt.com/globalservices
>> ________________________________________
>> From: Ram Mohan R (rmohanr) [rmohanr@cisco.com]
>> Sent: 31 October 2011 15:46
>> To: Stafford,J,John,JRJ3X C; siprec@ietf.org
>> Subject: RE: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>
>> John,
>>
>> This needs to be changed to associate/disassociate time to be in
>> consistent with model. We will take care in the next revision.
>>
>> Ram
>>
>> > -----Original Message-----
>> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> > Behalf Of john.2.stafford@bt.com
>> > Sent: Monday, October 31, 2011 8:09 PM
>> > To: siprec@ietf.org
>> > Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>> >
>> > Partha
>> >
>> > sections 6.3, 7.1,and  8 show CS as having Associate Time and
>> > Dissassociate Time,
>> > but  examples in section 13 show CS having start-time and end-time.
>> >
>> >
>> > Rgds
>> > John Stafford | Solution Architect 1 | BT Global Services
>> >
>> > ________________________________________
>> > From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of
>> > internet-drafts@ietf.org [internet-drafts@ietf.org]
>> > Sent: 31 October 2011 13:36
>> > To: i-d-announce@ietf.org
>> > Cc: siprec@ietf.org
>> > Subject: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>> >
>> > A New Internet-Draft is available from the on-line Internet-Drafts
>> > directories. This draft is a work item of the SIP Recording Working
>> > Group of the IETF.
>> >
>> >         Title           : Session Initiation Protocol (SIP)
>Recording
>> > Metadata
>> >         Author(s)       : Ram Mohan Ravindranath
>> >                           Parthasarathi Ravindran
>> >                           Paul Kyzivat
>> >         Filename        : draft-ietf-siprec-metadata-05.txt
>> >         Pages           : 45
>> >         Date            : 2011-10-31
>> >
>> >    Session recording is a critical requirement in many
>communications
>> >    environments such as call centers and financial trading.  In some
>> of
>> >    these environments, all calls must be recorded for regulatory,
>> >    compliance, and consumer protection reasons.  Recording of a
>> session
>> >    is typically performed by sending a copy of a media stream to a
>> >    recording device.  This document describes the metadata model as
>> >    viewed by Session Recording Server(SRS) and the Recording
>metadata
>> >    format.
>> >
>> >
>> > A URL for this Internet-Draft is:
>> >
>http://www.ietf.org/internet-drafts/draft-ietf-siprec-metadata-05.txt
>> >
>> > Internet-Drafts are also available by anonymous FTP at:
>> > ftp://ftp.ietf.org/internet-drafts/
>> >
>> > This Internet-Draft can be retrieved at:
>> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-siprec-metadata-05.txt
>> > _______________________________________________
>> > 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
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec

From pkyzivat@alum.mit.edu  Tue Nov  1 13:50:52 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 3640A11E81F9 for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 13:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.091
X-Spam-Level: 
X-Spam-Status: No, score=-2.091 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_00=-2.599, J_CHICKENPOX_81=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OgOtWmt-l87b for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 13:50:50 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id 5747E11E812D for <siprec@ietf.org>; Tue,  1 Nov 2011 13:50:50 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta13.westchester.pa.mail.comcast.net with comcast id rwkD1h0030Fqzac5DwoRCy; Tue, 01 Nov 2011 20:48:25 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta08.westchester.pa.mail.comcast.net with comcast id rwoQ1h00S0tdiYw3UwoQCU; Tue, 01 Nov 2011 20:48:25 +0000
Message-ID: <4EB05B16.7040002@alum.mit.edu>
Date: Tue, 01 Nov 2011 16:48:22 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: siprec@ietf.org
References: <058.f76a86cfba526ca37c258c5ffc98b278@trac.tools.ietf.org><35BCE99A477D6A4986FB2216D8CF2CFD07F6F9D2@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38BA8728E6@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD07F6F9D8@XMB-BGL-417.cisco.com><4E971D30.5090101@alum.mit.edu><35BCE99A477D6A4986FB2216D8CF2CFD080912F6@XMB-BGL-417.cisco.com><F62A45FE3109498D85EB786F3B4503AC@JohnsComputer>, <35BCE99A477D6A4986FB2216D8CF2CFD082B7DD5@XMB-BGL-417.cisco.com><BBA98B7742309546A60F3AE3B4E975A72820ED8FBB@EMV64-UKRD.domain1.systemh ost.net	>	<35BCE99A477D6A4986FB2216D8CF2CFD082B806E@XMB-BGL-417.cisco.com> <2E239D6FCD033C4BAF15F386A979BF51159D6B@sonusinmail02.sonusnet.com> <BBA98B7742309546A60F3AE3B4E975A72820CC5B49@EMV64-UKRD.domain1.systemhost.net>, <4EAAD2C9.5030008@alum.mit.edu> <BBA98B7742309546A60F3AE3B4E975A72820ED8FC1@EMV64-UKRD.domain1.systemhost.net>, <4EAAE681.40107@alum.mit.edu> <BBA98B7742309546A60F3AE3B4E975A72822C3A32D@EMV64-UKRD.domain1.systemhost.net>
In-Reply-To: <BBA98B7742309546A60F3AE3B4E975A72822C3A32D@EMV64-UKRD.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Need Inputs: How to representattributesofassociation in Metadata Model and in XML ?
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: Tue, 01 Nov 2011 20:50:52 -0000

This is just from me - it hasn't been reviewed by Ram and Partha.
Lets see if they agree.

	Thanks,
	Paul

On 10/31/11 7:58 AM, john.2.stafford@bt.com wrote:
> Paul,
> RE use of recv with conferences,
>
> thanks for your response, I think I am ok with this now, I got myself all confused last week, your response made me stop and think.
>
> Here is my understanding,  please point if I am still wrong:
>
> The<stream>  elements in metadata describe the RTP streams that flow as part of the call,
> so for a 3 party conference (A,B,C) with a separate media server conference focus, there are 6 streams.

This is one way.
Another way is to describe it as a single stream with (A,B,C) each both 
sending and receiving it.

> The recorder stream is sent from the conference focus,  assume this this has  a=label:1234 in its SDP.
>
> So in the metadata, the streams would be labelled to indicate that the the transmit streams from the 3 participants are mixed into the recorder stream, as follows:
> A->focus  stream<label>1234</label>
> focus->A  stream
> B->focus  stream<label>1234</label>
> focus->B  stream
> C->focus  stream<label>1234</label>
> focus->C stream

Why do you have the same label for all three?
Each stream that is sent to the SRS should have a different label, 
mapping to a separate m-line.

If it had been represented as a single stream, then the SRC would have 
to do the mixing, and there would be only one label.

> I think the metadata draft would benefit from having a conference example.

Yes, it would.

	Thanks,
	Paul

> Rgds
> John Stafford | Solution Architect 1 | BT Global Services
>
> ________________________________________
> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat [pkyzivat@alum.mit.edu]
> Sent: 28 October 2011 18:29
> To: siprec@ietf.org
> Subject: Re: [siprec] Need Inputs: How to representattributesofassociation in Metadata Model and in XML ?
>
> On 10/28/11 12:10 PM, john.2.stafford@bt.com wrote:
>> Paul,
>>
>> OK, I understand, but how does the recorder know that the stream sent by the focus is a mixed conference stream , ie contains all of the streams received by the focus. ?
>
> I don't think I understand the question.
> The SRS should just believe what it is told:
> the stream it receives contains a mix of all the participants reported
> as sending to it.
>
>          Thanks,
>          Paul
>
>> Rgds
>> John Stafford | Solution Architect 1 | BT Global Services
>>
>> ________________________________________
>> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat [pkyzivat@alum.mit.edu]
>> Sent: 28 October 2011 17:05
>> To: siprec@ietf.org
>> Subject: Re: [siprec] Need Inputs: How to representattributesofassociation in Metadata Model and in XML ?
>>
>> On 10/28/11 11:06 AM, john.2.stafford@bt.com wrote:
>>>
>>> Ram,
>>>>> I presume the participant - CS<session>    element will be replaced by
>>>>> the<    participantSessionAssoc>.
>>>>
>>>> No.<session>    will continue to remain. We are talking about association
>>>> attributes of participant-session.
>>>> The other attributes of<participant>    and<session>    which are not
>>>> association attributes will continue to be the respective elements.
>>>
>>> What I meant to say was:
>>> I presume the participant's session attribute will be replaced by the<participantSessionAssoc>.
>>> Is that correct ?
>>
>> Yup, that's the idea.
>>
>>> RE use of<recv>, this means for a large conference each participant update will be very large as it needs to include recv's for every other participants send  ?
>>
>> The association is between each participant and a stream, not between
>> two participants. There are two ways to represent this, and neither has
>> the problem you describe:
>>
>> - one stream for the conference.
>>      Each participant both sends and receives it.
>>
>> - one stream for each participant in the conference.
>>      The focus is represented as a participant.
>>      Each real participant sends and receives its own stream.
>>      The focus sends and receives all the streams.
>>
>> I guess the situation you describe would occur if there was a full-mesh
>> of streams between participants. But afaik nobody does that. And if they
>> did it would be hard to get an SRC in the middle.
>>
>>           Thanks,
>>           Paul
>>
>>> Rgds John
>>>
>>>
>>> -----Original Message-----
>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>>> Sent: 28 October 2011 14:43
>>> To: Ram Mohan R (rmohanr); Stafford,J,John,JRJ3X C; siprec@ietf.org
>>> Subject: RE: [siprec] Need Inputs: How to representattributesofassociation in Metadata Model and in XML ?
>>>
>>> Hi,
>>>
>>> IMO, send&    recv are the element which has to be pushed inside participant stream association element which is inline with the model.
>>>
>>> Thanks
>>> Partha
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf
>>>> Of Ram Mohan R (rmohanr)
>>>> Sent: Friday, October 28, 2011 7:04 PM
>>>> To: john.2.stafford@bt.com; siprec@ietf.org
>>>> Subject: Re: [siprec] Need Inputs: How to
>>>> representattributesofassociation in Metadata Model and in XML ?
>>>>
>>>> Hello John S,
>>>>
>>>> Please see inline for answers.
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>> Behalf Of john.2.stafford@bt.com
>>>>> Sent: Thursday, October 27, 2011 11:15 PM
>>>>> To: siprec@ietf.org
>>>>> Subject: Re: [siprec] Need Inputs: How to represent
>>>>> attributesofassociation in Metadata Model and in XML ?
>>>>>
>>>>> I am not clear on the effect on the other XMl elements.
>>>>>
>>>>> I presume the participant - CS<session>    element will be replaced by
>>>>> the<    participantSessionAssoc>.
>>>>
>>>> No.<session>    will continue to remain. We are talking about association
>>>> attributes of participant-session.
>>>> The other attributes of<participant>    and<session>    which are not
>>>> association attributes will continue to be the respective elements.
>>>>
>>>>>
>>>>> I also presume<send>    and<recv>     will no longer be needed, and that
>>>>> the<participantStream Assoc>    will include an attribute to say send
>>>> or
>>>>> recv ?
>>>>
>>>> This is a good suggestion. I have not given a thought on this so far.
>>> In
>>>> principle this should be fine as once the association of a participant
>>>> to a stream ends it stops sending/receiving the same. We need to think
>>>> through different use-cases to see if its fine to have<send>,<recv>
>>>> inside association element itself. By having send, recv inside the
>>>> association we can avoid one XML element as they can be attribute.
>>>>
>>>>>
>>>>> Is that correct ?
>>>>>
>>>>> I hope the rule will remain that,  in the abscence of any recv
>>>> elements
>>>>> by default a stream is assumed to be recieved by all participants.
>>>>
>>>> No, in the last IETF we agreed it's better to always explicity indicate
>>>> recv. We will continue to stick to that as I see no reason to change.
>>>>
>>>> Regards,
>>>> Ram
>>>>
>>>>>
>>>>> Rgds
>>>>> John Stafford | Solution Architect 1 | BT Global Services
>>>>>
>>>>> ________________________________________
>>>>> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of
>>>>> Ram Mohan R (rmohanr) [rmohanr@cisco.com]
>>>>> Sent: 27 October 2011 18:08
>>>>> To: John Elwell; Paul Kyzivat; siprec@ietf.org
>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>>>> ofassociation    in Metadata Model and in XML ?
>>>>>
>>>>> Hi John,
>>>>>
>>>>> Thanks for your comment on this. Yes several of us seem to be
>>> inclined
>>>>> towards approach 2.  I like your point that once one of the elements
>>>> in
>>>>> the association gets deleted, the association element life ends. SRC
>>>>> may choose to send the association element optionally or the SRS can
>>> still
>>>>> learn that as the way you mentioned.
>>>>>
>>>>> We ( authors of metadata draft ) discussed internally on this open
>>>> item
>>>>> and see some issues with adopting approach 2 as is with the current
>>>>> model /schema. I will start a separate mail thread for the issue as
>>>>> this thread is already too long.
>>>>>
>>>>> Thanks,
>>>>> Ram
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: John Elwell [mailto:john.r.elwell@gmail.com]
>>>>>> Sent: Thursday, October 27, 2011 2:03 PM
>>>>>> To: Ram Mohan R (rmohanr); Paul Kyzivat; siprec@ietf.org
>>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>>>>> ofassociation in Metadata Model and in XML ?
>>>>>>
>>>>>> Approach 2 seems reasonable. Could we say that an association is
>>>>>> implicitly deleted (gains a dissociate time) as soon as one of the
>>>>>> associated elements is deleted (gains a dissociate time)? This
>>>>>> would reduce the on-the
>>>>> wire
>>>>>> document size for both partial and full metadata in some
>>>>> circumstances
>>>>>> (e.g., conference termination by the focus).
>>>>>>
>>>>>> John
>>>>>>
>>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Ram Mohan R (rmohanr)"<rmohanr@cisco.com>
>>>>>> To: "Paul Kyzivat"<pkyzivat@alum.mit.edu>;<siprec@ietf.org>
>>>>>> Sent: Friday, October 14, 2011 4:59 AM
>>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>>>>> ofassociation in Metadata Model and in XML ?
>>>>>>
>>>>>>
>>>>>>> Thanks Paul for your comments. I also prefer approach 2 as
>>>>> mentioned
>>>>>>> below in this thread.
>>>>>>> I will wait to hear for comments/opinion from others.
>>>>>>>
>>>>>>> Ram
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>>> On
>>>>>>>> Behalf Of Paul Kyzivat
>>>>>>>> Sent: Thursday, October 13, 2011 10:48 PM
>>>>>>>> To: siprec@ietf.org
>>>>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>> of
>>>>>>>> association in Metadata Model and in XML ?
>>>>>>>>
>>>>>>>> I like approach 2, as Ram has shown it. It deals with the
>>>> problems
>>>>>>> John
>>>>>>>> raised with the others.
>>>>>>>>
>>>>>>>> I didn't follow John's arithmetic on this one, using his 20
>>> party
>>>>>>>> conference example. As I count that, there are 21 participants
>>>>> when
>>>>>>> you
>>>>>>>> include the focus. Each of the 20 has two stream/participant
>>>>>>>> associations with the focus, for a total of 40. (The association
>>>>> is
>>>>>>>> bidirectional. I can only get to 80 by assuming we had to
>>>>> represent
>>>>>> an
>>>>>>>> association in each direction.) And each has two ids, each of
>>>>> which
>>>>>> is
>>>>>>>> also the id of a stream or participant. So there are really only
>>>>> 23
>>>>>>>> distinct ids that need to be assigned for this. (One for each of
>>>>> the
>>>>>>> 21
>>>>>>>> participants, and one for each of the two streams.)
>>>>>>>>
>>>>>>>> The 40 associations, each carrying two ids, is still kind of a
>>>> lot
>>>>>> if
>>>>>>>> its sent all at once. But when starting up a conference they
>>> will
>>>>>>>> probably be added gradually as each participant joins. Same at
>>>> the
>>>>>> end
>>>>>>>> if they drop off individually. But it could be a bunch together
>>>> if
>>>>>> the
>>>>>>>> conference is forcibly dropped by the focus. But it does
>>> minimize
>>>>>> what
>>>>>>>> is sent when things happen incrementally.
>>>>>>>>
>>>>>>>> There may be some optimizations that can be done - e.g. a sort
>>> of
>>>>>>>> "wildcard" for one of the the two ids in the association class.
>>>>> E.g.
>>>>>>>>
>>>>>>>> <participantStreamAssoc
>>>>>>>>       participant="*"
>>>>>>>>       stream ="urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>
>>> <disassociate-time>2010-12-16T23:41:07Z</disassociate-time>
>>>>>>>> </participantStreamAssoc>
>>>>>>>>
>>>>>>>> (I'm not advocating that particular syntax. Its just something
>>> to
>>>>>> make
>>>>>>>> the point.)
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Paul
>>>>>>>>
>>>>>>>>
>>>>>>>> On 10/12/11 4:56 AM, Ram Mohan R (rmohanr) wrote:
>>>>>>>>> My bad(typo) while sending the example. The correct partial
>>>>> update
>>>>>> I
>>>>>>>>> intended to send  is:
>>>>>>>>>
>>>>>>>>> <participantStreamAssoc
>>>>>>>>>       participant="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>       stream ="urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>>          <disassociate-time>2010-12-16T23:41:07Z</disassociate-
>>>>> time>
>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>
>>>>>>>>> This is inline with approach 2 where in each association XML
>>>>>> element
>>>>>>>>> will have the IDs of the related associated elements.
>>>>>>>>>
>>>>>>>>> Ram
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>>>>>>> Sent: Wednesday, October 12, 2011 2:24 PM
>>>>>>>>>> To: Ram Mohan R (rmohanr); siprec@ietf.org
>>>>>>>>>> Cc: Ofir Roth
>>>>>>>>>> Subject: RE: Need Inputs: How to represent attributes of
>>>>>>> association
>>>>>>>>> in
>>>>>>>>>> Metadata Model and in XML ?
>>>>>>>>>>
>>>>>>>>>> We do prefer to receive related elements as well, it makes
>>>>>>>>>> implementation much easier.
>>>>>>>>>>      At least we should get relevant IDs.  For example below,
>>> SRC
>>>>>>>> should
>>>>>>>>>> also send ParticipantId
>>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>> Sent: Wednesday, October 12, 2011 10:52 AM
>>>>>>>>>> To: Leon Portman; siprec@ietf.org
>>>>>>>>>> Cc: Ofir Roth
>>>>>>>>>> Subject: RE: Need Inputs: How to represent attributes of
>>>>>>> association
>>>>>>>>> in
>>>>>>>>>> Metadata Model and in XML ?
>>>>>>>>>>
>>>>>>>>>> Leon,
>>>>>>>>>> Thanks for your response. One of the adv with approach 2 is
>>> we
>>>>>> can
>>>>>>>>>> indicate only changes in the association without the need to
>>>>>>>>> indicating
>>>>>>>>>> the elements ( of association). IOW for the below example, if
>>>>>> there
>>>>>>>> is
>>>>>>>>>> a change in participant-stream association I can simply send
>>>>> the
>>>>>>>>>> following in partial update:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>      stream ="urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a">
>>>>>>>>>>
>>>>> <disassociate-time>2010-12-16T23:41:07Z</disassociate-time>
>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>
>>>>>>>>>> Do you see a need to always indicate the related elements too
>>>> ?
>>>>>> In
>>>>>>>>>> which case I see approach 1 as more suitable.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Ram
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>>>>>>>> Sent: Wednesday, October 12, 2011 12:55 PM
>>>>>>>>>>> To: Ram Mohan R (rmohanr); siprec@ietf.org
>>>>>>>>>>> Cc: Ofir Roth
>>>>>>>>>>> Subject: RE: Need Inputs: How to represent attributes of
>>>>>>>> association
>>>>>>>>>>> inmetadata Model and in XML ?
>>>>>>>>>>>
>>>>>>>>>>> Ram Hi
>>>>>>>>>>>
>>>>>>>>>>> I am ok with approaches 1 and  however I do prefer approach
>>>>> one
>>>>>>>>>> because
>>>>>>>>>>> it will be easier for SRS to get decode - association is
>>>>> inside
>>>>>>>>>>> relevant element. And it is more readable.
>>>>>>>>>>> Approach 2 will work as well, however it is important that
>>> if
>>>>>>> there
>>>>>>>>>>> will be a change in association then to send to SRS not only
>>>>>>>> updated
>>>>>>>>>>> association element but also related elements: for example
>>> if
>>>>>>>> stream
>>>>>>>>>>> was associated to participant and session, send also
>>>>> participant
>>>>>>>> and
>>>>>>>>>>> session latest state.
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>> Leon
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>> [mailto:siprec-bounces@ietf.org]
>>>>>> On
>>>>>>>>>>> Behalf Of Ram Mohan R (rmohanr)
>>>>>>>>>>> Sent: Wednesday, October 12, 2011 7:48 AM
>>>>>>>>>>> To: siprec@ietf.org
>>>>>>>>>>> Subject: [siprec] Need Inputs: How to represent attributes
>>> of
>>>>>>>>>>> association in metadata Model and in XML ?
>>>>>>>>>>>
>>>>>>>>>>> (Sorry for lengthy e-mail)
>>>>>>>>>>>
>>>>>>>>>>> Hi All,
>>>>>>>>>>>
>>>>>>>>>>> In the last interim we discussed 4 approaches for
>>>> representing
>>>>>>>>>>> attributes of association in XML.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Here are some pros/cons for each of them:
>>>>>>>>>>> Approach 1:
>>>>>>>>>>> ----------
>>>>>>>>>>> Represent the association attribute as a property within one
>>>>> of
>>>>>>> the
>>>>>>>>>>> associated elements. Example given at
>>>>> http://www.ietf.org/mail-
>>>>>>>>>>> archive/web/siprec/current/msg02709.html Does not need
>>>> another
>>>>>> XML
>>>>>>>>>>> element and represents the association attributes as
>>>>> capability
>>>>>> of
>>>>>>>>>> one
>>>>>>>>>>> of the association element.
>>>>>>>>>>> e.g.
>>>>>>>>>>> <participant
>>>>>>>>>>>
>>>> id="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>                session="urn:uuid:855a5ded-8420-456d-a70f-
>>>>>>>> 6da1eeaeb425">
>>>>>>>>>>>                      <aor>sip:ram@blr.cisco.com</aor>
>>>>>>>>>>>                      <associate-time>2010-12-
>>>>>> 16T23:41:07Z</associate-
>>>>>>>>>> time>
>>>>>>>>>>>                      <capabilities>     TBD</capabilties>
>>>>>>>>>>>                      <participantStreamAssoc
>>>>>>>>>>>                       stream
>>> ="urn:uuid:f3373a7b-4958-4e55-8820-
>>>>>>>>>>> d03a191fb76a
>>>>>>>>>>> ">
>>>>>>>>>>>                        <associate-time>2010-12-
>>>>>>>> 16T23:41:07Z</associate-
>>>>>>>>>>> time>
>>>>>>>>>>>                        <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>>                      </participantStreamAssoc>      </participant>
>>>>> In
>>>>>>>> the
>>>>>>>>>> above
>>>>>>>>>>> example the participant contributes a single streams. For
>>>> each
>>>>>>>>> stream
>>>>>>>>>>> the association attribute (participant-stream) is shown with
>>>>> the
>>>>>>>>>> stream
>>>>>>>>>>> ID nested in.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Approach 2:
>>>>>>>>>>> -----------
>>>>>>>>>>> In this approach we have a new XML element for every
>>>>> association
>>>>>>>>>> class.
>>>>>>>>>>> This xml element will NOT have a unique ID instead it
>>>>> references
>>>>>>>> the
>>>>>>>>>> ID
>>>>>>>>>>> of associated elements (shown below). With this approach it
>>>> is
>>>>>>> easy
>>>>>>>>>> to
>>>>>>>>>>> update as the association class is a separate XML element
>>> and
>>>>>> not
>>>>>>>>>>> property.
>>>>>>>>>>> e.g.
>>>>>>>>>>> <participantSessionAssoc
>>>>>>>>>>>
>>> participant="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>      session="urn:uuid:855a5ded-8420-456d-a70f-6da1eeaeb425">
>>>>>>>>>>>       <associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>       <capabilities>     TBD</capabilties>
>>>>>>>>>>> </participantSessionAssoc>
>>>>>>>>>>>
>>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>>
>>> participant="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>      stream ="urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>>>>         <associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>         <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>>
>>>>>>>>>>> Approach 3 and 4 are in the below e-mail from John.
>>>>>>>>>>> Approach 3 defines a new Unique ID for every association XML
>>>>>>>> elment.
>>>>>>>>>>> Also it creates alias for the other IDs. In the discussions
>>>> in
>>>>>>>>>> interim
>>>>>>>>>>> there was no strong support for this approach.
>>>>>>>>>>>
>>>>>>>>>>> Approach 4 is same as approach 1 where in the association
>>>>>> element
>>>>>>>> is
>>>>>>>>>>> encapsulated in one of  the XML elements (to which it is
>>>>>>>>> associated).
>>>>>>>>>>> In addition to that it also has reference to the elements
>>>>> (alias
>>>>>>> of
>>>>>>>>>>> IDs) to which the association belongs.
>>>>>>>>>>>
>>>>>>>>>>> I prefer approach 2 as it is has a separate XML element to
>>>>>>>> represent
>>>>>>>>>>> the association class. The only difference of this XML
>>>> element
>>>>>>> from
>>>>>>>>>>> others is this does not need a unique ID. Instead it
>>>>> references
>>>>>>> the
>>>>>>>>>> IDs
>>>>>>>>>>> of the elements to which the association belongs.
>>>>>>>>>>> Since association class is a special class meant to
>>> associate
>>>>>>>>>> multiple
>>>>>>>>>>> classes, I see it ok to have a representation as in approach
>>>> 2
>>>>>>>> where
>>>>>>>>>> in
>>>>>>>>>>> the identifier is the concatenation of the classes to which
>>>>> the
>>>>>>>>>>> association belongs to.
>>>>>>>>>>>
>>>>>>>>>>> Please provide your comments on this and also suggest any
>>>>> other
>>>>>>>>>>> approaches to represent association classes in XML.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Ram
>>>>>>>>>>>
>>>>> _______________________________________________
>>>>> 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
>>> _______________________________________________
>>> 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
>>
>
> _______________________________________________
> 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
>


From pkyzivat@alum.mit.edu  Tue Nov  1 14:08:55 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 0E93111E8105 for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 14:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-NmN7cIcEUs for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 14:08:53 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id 902DE11E812D for <siprec@ietf.org>; Tue,  1 Nov 2011 14:08:53 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta13.westchester.pa.mail.comcast.net with comcast id rulW1h0061ap0As5Dx6QkN; Tue, 01 Nov 2011 21:06:24 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta22.westchester.pa.mail.comcast.net with comcast id rx6P1h00T0tdiYw3ix6QpL; Tue, 01 Nov 2011 21:06:24 +0000
Message-ID: <4EB05F4D.5080600@alum.mit.edu>
Date: Tue, 01 Nov 2011 17:06:21 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: siprec@ietf.org
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] FW: New Version Notification for draft-eckel-siprec-rtp-rec-03.txt
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: Tue, 01 Nov 2011 21:08:55 -0000

Charles,

While reading this I got wondering if we need more guidance on the use 
of CNAME. (As referenced in section 5.) Do we need guidance on mapping 
of CNAME to participants?

	Thanks,
	Paul

On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
> FYI, I have submitted the updated draft and it is available through the SIPREC documents page:
> http://proxy2974.my-addr.net/myaddrproxy.php/https/datatracker.ietf.org/wg/siprec/
>
> It contains editorial changes as well as additional text describing the handling of RTCP packets by the SRC and UAs per the recent SIPREC list discussion.
>
> Cheers,
> Charles
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, October 31, 2011 10:53 AM
> To: Charles Eckel (eckelcu)
> Cc: Charles Eckel (eckelcu)
> Subject: New Version Notification for draft-eckel-siprec-rtp-rec-03.txt
>
> A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been successfully submitted by Charles Eckel and posted to the IETF repository.
>
> Filename:	 draft-eckel-siprec-rtp-rec
> Revision:	 03
> Title:		 Real-time Transport Protocol (RTP) Recommendations for SIPREC
> Creation date:	 2011-10-31
> WG ID:		 Individual Submission
> Number of pages: 13
>
> Abstract:
>     This document provides recommendations and guidelines for RTP and
>     RTCP in the context of SIPREC.  This document exists as a standalone
>     document to facilitate discussion of the RTP recommendations, and it
>     is anticipated that portions of this document will be incorporated
>     into [I-D.ietf-siprec-protocol] rather than this document itself
>     being adopted as a working group document.
>
>
>
>
> The IETF Secretariat
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>


From pkyzivat@alum.mit.edu  Tue Nov  1 14:21:58 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 4799C11E808B for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 14:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yqkRgvewRKY for <siprec@ietfa.amsl.com>; Tue,  1 Nov 2011 14:21:56 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by ietfa.amsl.com (Postfix) with ESMTP id A3BE821F9BE2 for <siprec@ietf.org>; Tue,  1 Nov 2011 14:21:55 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta01.westchester.pa.mail.comcast.net with comcast id rwzE1h00V27AodY51xMrKu; Tue, 01 Nov 2011 21:21:51 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta19.westchester.pa.mail.comcast.net with comcast id rxMq1h01d0tdiYw3fxMqUY; Tue, 01 Nov 2011 21:21:51 +0000
Message-ID: <4EB062EC.30704@alum.mit.edu>
Date: Tue, 01 Nov 2011 17:21:48 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
References: <A4E1C77AFA24EF4A9DBDF6CB6491D0E73AF67003@SE-EX019.groupinfra.com><07465C1D981ABC41A344374066AE1A2C38B066C6FC@TLVMBX01.nice.com><A4E1C77AFA24EF4A9DBDF6CB6491D0E73AF673C8@SE-EX019.groupinfra.com><A444A0F8084434499206E78C106220CA0BC11A84F6@MCHP058A.global-ad.net><101C6067BEC68246B0C3F6843BCCC1E311F7B7CD35@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38B066D0F5@TLVMBX01.nice.com> <2E239D6FCD033C4BAF15F386A979BF510F0F56@sonusinmail02.sonusnet.com> <101C6067BEC68246B0C3F6843BCCC1E311F7B7CFC3@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF510F0F84@sonusinmail02.sonusnet.com> <A444A0F8084434499206E78C106220CA0BC11A8A8A@MCHP058A.global-ad.net> <A4E1C77AFA24EF4A9DBDF6CB6491D0E73AF67E28@SE-EX019.groupinfra.com> <A444A0F8084434499206E78C106220CA0BC11A8AD8@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311F7B7D168@MCHP058A.global-ad.net> <4E88E727.6010009@alum.mit.edu> <101C6067BEC68246B0C3F6843BCCC1E311F80426C1@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311F80426C1@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SRS-initiated initial INVITE
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: Tue, 01 Nov 2011 21:21:58 -0000

On 11/1/11 1:02 PM, Hutton, Andrew wrote:
> Hi,
>
> On 02 October 2011 at 23:35 Kyzivat Paul wrote:
>
>> I think there are a couple of choices here:
>> - we can require that an SRC and an SRS have a unique URI, that behaves
>>     only as an SRC/SRS, never any other way. And only when addressed by
>>     such a URI does it support the siprec option and advertise support
>> for
>>     the corresponding capability/feature-tag.
>>
>
> I don't think we want to require a SRC or SRS to have a unique URI for this purpose this would really increase complexity of deploying and provisioning the solution especially if we have lots of SRC's located in endpoints for example.

I guess that makes sense, especially when addressing phones that can act 
as SRCs.

>> - we can permit the same URI to be used for an RS or a CS. In this case
>>     it can support siprec all the time, and announce an SRC or SRS
>> feature
>>     tag all the time. But then we need something to indicate "behave as
>>     an SRC" or "behave as an SRS".
>
> I had previously envisaged that the UA would only include the "src" or "srs" feature tag in the Contact during the establishment of a RS this is how it is currently described in for example section 5.1 of the protocol draft.  That is except for possible use in a REGISTER.

The feature tag means "I have this capability" (similar to what 
Supported means).

ISTM its an abuse to treat it as meaning "I'm doing this".

> So if this is the case then if this is combined with the use of the "siprec" option tag in Require then I would not thought it to be too big a stretch to say that the siprec aware UAS receiving an INVITE it knows to be from an SRC MUST assume the role of SRS or reject the INVITE. Do we really need something else?

I think so. It could be very simple.
The invite could include a snapshot request.

	Thanks,
	Paul

> Regards
> Andy (as an individual).
>
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Paul Kyzivat
>> Sent: 02 October 2011 23:35
>> To: siprec@ietf.org
>> Subject: Re: [siprec] SRS-initiated initial INVITE
>>
>> On 9/23/11 5:13 AM, Hutton, Andrew wrote:
>>> Hi,
>>>
>>> I think Friso is correct this is covered in the protocol draft and it
>> works like this.
>>>
>>> 1. The SRS includes a Require header field with the option tag
>> "recording-session". This means that the UAS that receives the INVITE
>> has to understand SIPREC or it will reject the INVITE.
>>>
>>> 2. The SRS also includes the feature tag "SRS" in the contact so that
>> the UAS that receives it knows that it is an SRS that initiated the
>> INVITE for the purpose of creating a recording session so it has to
>> become the SRC. Therefore if the UAS is an SRC that does not handle SRS
>> initiated INVITE's it should reject the INVITE at this point. Maybe we
>> could say something about this in the protocol draft.
>>
>> IMO this isn't sufficient. SIP feature tags in Contact encode "callee
>> capabilities". They don't say anything about what the recipient should
>> do.
>>
>> I think there are a couple of choices here:
>> - we can require that an SRC and an SRS have a unique URI, that behaves
>>     only as an SRC/SRS, never any other way. And only when addressed by
>>     such a URI does it support the siprec option and advertise support
>> for
>>     the corresponding capability/feature-tag.
>>
>> - we can permit the same URI to be used for an RS or a CS. In this case
>>     it can support siprec all the time, and announce an SRC or SRS
>> feature
>>     tag all the time. But then we need something to indicate "behave as
>>     an SRC" or "behave as an SRS".
>>
>>        Thanks,
>>        Paul
>>
>>> The only issue I see is possible in the naming of the "recording-
>> session" option tag as this should not be used as an indication that
>> this is a recording session it is only used to indicate to the UAS that
>> it should reject the INVITE if it does not understand SIPREC
>> extensions. However this is just a naming issue.
>>>
>>> Regards
>>> Andy
>>>
>>>
>>>> -----Original Message-----
>>>> From: Elwell, John
>>>> Sent: 23 September 2011 09:42
>>>> To: Feenstra, Friso; Ravindran Parthasarathi; Hutton, Andrew; Leon
>>>> Portman; siprec@ietf.org
>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>
>>>> Friso,
>>>>
>>>> Quite right, it is not yet covered, and the whole purpose of this
>>>> thread is to discuss whether something needs to go into the protocol
>>>> draft to cover the SRS-initiated case, to align with the
>> architecture
>>>> draft.
>>>>
>>>> John
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Feenstra, Friso [mailto:friso.feenstra@logica.com]
>>>>> Sent: 23 September 2011 09:23
>>>>> To: Elwell, John; Ravindran Parthasarathi; Hutton, Andrew;
>>>>> Leon Portman; siprec@ietf.org
>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>
>>>>> Hi John,
>>>>>
>>>>> Please excuse me as being relative new to this, but is this
>>>>> not covered by the current description in Session Recording
>>>>> Protocol draft-ietf-siprec-protocol-00 paragraph 5.1 and 5.2?
>>>>>
>>>>> Friso ( as individual)
>>>>>
>>>>> -----Original Message-----
>>>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>>>> Sent: vrijdag 23 september 2011 10:04
>>>>> To: Ravindran Parthasarathi; Hutton, Andrew; Leon Portman;
>>>>> Feenstra, Friso; siprec@ietf.org
>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>
>>>>> I think we need to avoid violating the semantics of Require.
>>>>> The Require header field just means reject the request if you
>>>>> don't understand this extension. If you want a
>>>>> SIPREC-compliant UAS to act as an SRC, I think you also need
>>>>> to put something in the INVITE request to this effect. This
>>>>> could simply be the srs feature tag. So we could specify that
>>>>> if an entity receives an INVITE request with an srs feature
>>>>> tag this is to be interpreted as a request to become an SRC.
>>>>> If the UAS is not prepared to do this it can reject it
>>>>> somehow (e.g., 403 Forbidden).
>>>>>
>>>>> John (as individual)
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>>>>>> Sent: 23 September 2011 07:46
>>>>>> To: Hutton, Andrew; Leon Portman; Elwell, John; Feenstra,
>>>>>> Friso; siprec@ietf.org
>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>>
>>>>>> Hi Andrew,
>>>>>>
>>>>>> Thanks for correction. I assumed that softswitch as B2BUA.
>>>>>> So, the scenario is that SIP proxy which does not want to
>>>>>> push the intelligence to its UA but push it to some-other server.
>>>>>>
>>>>>> I'm fine as long as there is no extra normative statement for
>>>>>> SRC. Let us also spell out the error-code for recording
>>>>>> request rejection by SRC in case of INVITE without offer.
>>>>>>
>>>>>> Thanks
>>>>>> Partha
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Hutton, Andrew [mailto:andrew.hutton@siemens-
>> enterprise.com]
>>>>>>> Sent: Friday, September 23, 2011 1:37 AM
>>>>>>> To: Ravindran Parthasarathi; Leon Portman; Elwell, John;
>> Feenstra,
>>>>>>> Friso; siprec@ietf.org
>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>>>
>>>>>>> Hi Partha,
>>>>>>>
>>>>>>> But in Friso's scenario the "softswitch" is really acting
>>>>> just a SIP
>>>>>>> Proxy so it cannot be the case that the SIP Proxy and the
>>>>> SIP UA are
>>>>>>> acting as a kind of decomposed SRC.
>>>>>>>
>>>>>>> Of course whether a given SRC implements the capability to
>> receive
>>>>>>> INVITE's from the SRS is an implementation option if it does
>>>>>> not the SRC
>>>>>>> will reject the INVITE due to the recording-session option
>>>>> tag in the
>>>>>>> Require header.
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Andy (As an individual).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>>>>>>>> Sent: 22 September 2011 18:43
>>>>>>>> To: Leon Portman; Hutton, Andrew; Elwell, John; Feenstra, Friso;
>>>>>>>> siprec@ietf.org
>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>>>>
>>>>>>>>
>>>>>>>> I have earlier mentioned as a not good design because better
>>>>>>>> alternative exists for the same recording topology within SIPREC
>>>>>>>> solution. I look at Friso recording topology as decomposed
>>>>>> SRC to SRS
>>>>>>>> network topology and details are as follows:
>>>>>>>>
>>>>>>>> 1) Softswitch&   Agent phone act as SRC wherein Softswitch is a
>>>>>>>> signaling Entity (SIP) and Agent phone as media entity (RTP).
>>>>>>>> 2) Softswitch communicates with SRS in the standard SIPREC
>>>>>> RS session
>>>>>>>> establishment (with extension data) to SRS.
>>>>>>>> 3) Based on SRS negotiation, softswitch indicates to agent
>>>>>> phone using
>>>>>>>> proprietary SDP extension with m-line addition (to start
>>>>> recording
>>>>>>>> towards SRS). Here, Agent phone forks the media towards
>>>>> SRS. I have
>>>>>>>> mentioned proprietary SDP extension because the
>>>>> interaction between
>>>>>>>> decomposed SRC is outside the scope of SIPREC. (I know of
>>>>>> the working
>>>>>>>> solution in the fashion for the call center).
>>>>>>>>
>>>>>>>> The advantages in this decomposed SRC solution are
>>>>>>>> 1) There is no need of extra CTI or equivalent channel between
>>>>>>>> softswitch&   SRS.
>>>>>>>> 2) Agent phone has no need to handle multiple dialogs (CS&   RS).
>>>>>>>> 3) It is easy for tracking the session from Softswitch
>>>>> during agent
>>>>>>>> transfer as it is acting as SRC.
>>>>>>>> 4) No need to use "join" or some unique session-id
>>>>> between all the
>>>>>>>> entities
>>>>>>>>
>>>>>>>> Any recording entity has to support multiple m-lines in
>>>>> SDP and so,
>>>>>>>> there is no difference for agent-phone between SRS-initiated
>>>> and
>>>>>>>> decomposed SRC media box. Please correct in case any other
>>>>>> advantage
>>>>>>> in
>>>>>>>> SRS-initiated solution compare to decomposed-SRC.
>>>>>>>>
>>>>>>>>
>>>>>>>> Having said that, I'm fine with SRS-initiated INVITE in
>>>>>> case everybody
>>>>>>>> is interested for some specific callflow but I'm not
>>>>> interested to
>>>>>>> hear
>>>>>>>> more mandate in SRC to handle this callflow.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Partha
>>>>>>>>
>>>>>>>> PS: The proposed decomposed SRC solution may work in
>>>>>> RTCWeb recording
>>>>>>>> solution between RTCWebserver&   browser ;-)
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: siprec-bounces@ietf.org
>>>>> [mailto:siprec-bounces@ietf.org] On
>>>>>>>> Behalf
>>>>>>>>> Of Leon Portman
>>>>>>>>> Sent: Thursday, September 22, 2011 7:34 PM
>>>>>>>>> To: Hutton, Andrew; Elwell, John; Feenstra, Friso;
>>>>> siprec@ietf.org
>>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
>>>>>>>>>
>>>>>>>>> Andy Hi
>>>>>>>>>
>>>>>>>>> I will update the drafts with below. I agree on the flow
>>>>>>>>>
>>>>>>>>> Leon
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Hutton, Andrew
>>>>> [mailto:andrew.hutton@siemens-enterprise.com]
>>>>>>>>> Sent: Thursday, September 22, 2011 4:28 PM
>>>>>>>>> To: Elwell, John; Feenstra, Friso; Leon Portman;
>>>> siprec@ietf.org
>>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> I think what Friso describes is a perfectly valid use
>>>>> case and is
>>>>>>>>> something that we intended to cover in SIPREC hence the
>>>> existing
>>>>>>>> section
>>>>>>>>> in the architecture draft.
>>>>>>>>>
>>>>>>>>> I don't think we need to be concerned with how the SRS
>>>>>> knows when to
>>>>>>>>> start recording this could be via CTI, SIP Dialog Events or
>>>> many
>>>>>>>> others
>>>>>>>>> means. This is I think out of scope of SIPREC.
>>>>>>>>>
>>>>>>>>> What I think we do need to do is tidy up the architecture draft
>>>>>>>> (Section
>>>>>>>>> 3.2.2) which covers this use SRS initiated recording.  We
>>>>>> need to say
>>>>>>>>> more about how the CS that is to be recorded is
>>>>>> identified. Currently
>>>>>>>>> the arch draft says that one possibly way of doing this
>>>>>> is using the
>>>>>>>>> "Join" header which obviously only applies if the CS
>>>>>> dialog already
>>>>>>>>> exists and the SRS knows the dialog identifiers.
>>>>>>>>>
>>>>>>>>> Do people think that specifying the use of "Join" for
>>>>>> this purpose is
>>>>>>>>> useful or can we just say something generic about the
>>>>> Request-URI
>>>>>>>>> identifying what needs to be recorded?
>>>>>>>>>
>>>>>>>>> I also noticed a mistake in section 3.2.2 of the
>>>>>> architecture draft
>>>>>>> in
>>>>>>>>> the 4th bullet "Session Recording Client" should be "Session
>>>>>>> Recording
>>>>>>>>> Server" as this refers to the case when the SRS
>>>>> generates the SDP
>>>>>>>> offer.
>>>>>>>>> Leon as you have the pen can you fix this.
>>>>>>>>>
>>>>>>>>> Andy (As individual).
>>>>>>>>>
>>>>>>>>> Andrew Hutton
>>>>>>>>> http://www.siemens-enterprise.com/uk/
>>>>>>>>>
>>>>>>>>> Siemens Enterprise Communications Limited.
>>>>>>>>> Registered office: Brickhill Street, Willen Lake, Milton
>>>>>> Keynes, MK15
>>>>>>>>> 0DJ.
>>>>>>>>> Registered No: 5903714, England.
>>>>>>>>>
>>>>>>>>> Siemens Enterprise Communications Limited is a Trademark
>>>>>> Licensee of
>>>>>>>>> Siemens AG.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>> [mailto:siprec-bounces@ietf.org] On
>>>>>>>>>> Behalf Of Elwell, John
>>>>>>>>>> Sent: 22 September 2011 08:47
>>>>>>>>>> To: Feenstra, Friso; Leon Portman; siprec@ietf.org
>>>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
>>>>>>>>>>
>>>>>>>>>> What Friso describes is fairly similar to what I had in mind.
>>>>>>>>>> Basically the SRS knows, through some out-of-band means
>>>>>> (e.g., CTI,
>>>>>>>>>> human involvement), that it should record a CS or CSs (e.g.,
>>>>>>>>>> persistent recording of CSs involving a given user,
>>>>>> recording the
>>>>>>>>>> current CS of a particular user). Based on this it can
>>>>>> construct a
>>>>>>>> URI
>>>>>>>>>> that identifies the SRC and instructs it what to record.
>>>>>>>>>>
>>>>>>>>>> Personally I am more interested in the case where the
>>>>>> SRS is at a
>>>>>>>>>> B2BUA. Although the UA case is also potentially of
>>>>>> interest, that
>>>>>>>>>> tends to have limited applicability for the following
>>>> reasons:
>>>>>>>>>> - requires SRC support at all UAs that might be
>>>>> involved, rather
>>>>>>>> than
>>>>>>>>>> just in one or a few network entities;
>>>>>>>>>> - bandwidth limitations, particularly for mobile
>>>>> users and users
>>>>>>>> with
>>>>>>>>>> limited uplink speeds.
>>>>>>>>>>
>>>>>>>>>> Since SRS-initiated INVITEs do not require any new SIP
>>>>>> mechanism,
>>>>>>> it
>>>>>>>>>> seems quite reasonable to me to allow them.
>>>>>>>>>>
>>>>>>>>>> John (as individual)
>>>>>>>>>>
>>>>>>>>>> John Elwell
>>>>>>>>>> Tel: +44 1908 817801 (office and mobile)
>>>>>>>>>> Email: john.elwell@siemens-enterprise.com
>>>>>>>>>> http://www.siemens-enterprise.com/uk/
>>>>>>>>>>
>>>>>>>>>> Siemens Enterprise Communications Limited.
>>>>>>>>>> Registered office: Brickhill Street, Willen Lake,
>>>>> Milton Keynes,
>>>>>>>> MK15
>>>>>>>>>> 0DJ.
>>>>>>>>>> Registered No: 5903714, England.
>>>>>>>>>>
>>>>>>>>>> Siemens Enterprise Communications Limited is a
>>>>>> Trademark Licensee
>>>>>>> of
>>>>>>>>>> Siemens AG.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>>>>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of
>>>>> Feenstra, Friso
>>>>>>>>>>> Sent: 21 September 2011 08:31
>>>>>>>>>>> To: Leon Portman; siprec@ietf.org
>>>>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
>>>>>>>>>>>
>>>>>>>>>>> Leon,
>>>>>>>>>>>
>>>>>>>>>>> Yes, this is correct and this is how I would like
>>>>> it to work.
>>>>>>>>>>>
>>>>>>>>>>> A few additional notes.
>>>>>>>>>>> a. The implementation details of the CTI signalling between
>>>>>>>>>>> softswitch and SRS is out of scope for the SIPREC
>>>>>> standard, but
>>>>>>>> most
>>>>>>>>>>> softswitches offer a form of CTI signalling that can
>>>>>> be used for
>>>>>>>>>>> this signalling.
>>>>>>>>>>> b. It is not defined how much info is send with the
>>>>>> SDP from the
>>>>>>>> SRS
>>>>>>>>>>> to the SRC (via the softswitch). Worse case an
>>>>>> offerless invite
>>>>>>> is
>>>>>>>>>>> send to start the RS session, next the SRC will
>>>>> provide the CS
>>>>>>>> info
>>>>>>>>>>> in the OK with SDP and Metadata and the SRS will select the
>>>>>>>> correct
>>>>>>>>>>> streams with the ACK or through a re-Invite.
>>>>>>>>>>> c. I anticipate that the forwarding by the softswitch
>>>>>> of Invite
>>>>>>>>>>> messages (CS and RS) is a 'standard' feature for the
>>>>>> softswitch
>>>>>>>>>>> acting as a SIP proxy server and as such can be left
>>>>>> outside the
>>>>>>>>>>> scope of the SIPREC standard.
>>>>>>>>>>>
>>>>>>>>>>> As an individual,
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Friso
>>>>>>>>>>>
>>>>>>>>>>> friso.feenstra@logica.com
>>>>>>>>>>> +31 6 415 46 305
>>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>>>>>>>> Sent: dinsdag 20 september 2011 18:03
>>>>>>>>>>> To: Feenstra, Friso; siprec@ietf.org
>>>>>>>>>>> Cc: Ravindran Parthasarathi; Paul Kyzivat
>>>>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>>>>>>>
>>>>>>>>>>> Friso
>>>>>>>>>>>
>>>>>>>>>>> It is a very good discussion. Let me try to understand the
>>>>>>>> proposed
>>>>>>>>>>> sequence  for example as incoming call from UA A to
>>>>>> UA B, where
>>>>>>> UA
>>>>>>>> B
>>>>>>>>>>> is SRC.
>>>>>>>>>>> Actually UA B and softswitch are decomposed SRC.
>>>>>>>>>>>
>>>>>>>>>>> 1. UA A sends CS INVITE to softswitch 2. softswitch sends
>>>> CS
>>>>>>>> INVITE
>>>>>>>>>>> to UA B (SRC) 3. softswitch reports via CTI to SRS
>>>>>> about CS (UA A
>>>>>>>>>>> calling UA B) 4. SRS decides to record and sends RS
>>>>>> INVITE with
>>>>>>>> SDP
>>>>>>>>>>> to softswitch with some CS mapping info 5.
>>>>> Softswitch sends RS
>>>>>>>>>>> INVITE to UA B that acts as SRC 6. UA B send OK with
>>>>>> its SDP via
>>>>>>>>>>> softswitch to SRS
>>>>>>>>>>>
>>>>>>>>>>> This flow will require definition additional
>>>>>> interface for step 3
>>>>>>>>>>> and for softswitch to implement step 5 Is it correct flow?
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>> Leon
>>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Feenstra, Friso [mailto:friso.feenstra@logica.com]
>>>>>>>>>>> Sent: Tuesday, September 20, 2011 6:34 PM
>>>>>>>>>>> To: siprec@ietf.org
>>>>>>>>>>> Cc: Leon Portman; Ravindran Parthasarathi; Paul Kyzivat
>>>>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>>>>>>>
>>>>>>>>>>> Partha and Leon,
>>>>>>>>>>>
>>>>>>>>>>> The business intelligence (Policy Manager) in our
>>>>> case is with
>>>>>>> the
>>>>>>>>>>> SRS and like the softswitch (acting as a SIP proxy)
>>>>>> is deployed
>>>>>>> on
>>>>>>>> a
>>>>>>>>>>> central location.
>>>>>>>>>>> Agent handsets (UA's) are globally dispersed. So I am
>>>>>> definitely
>>>>>>>>>>> looking for a SIPREC solution where the SRC is
>>>>>> implemented on the
>>>>>>>> UA
>>>>>>>>>>> (agent handset).
>>>>>>>>>>>
>>>>>>>>>>> When only the SRC can provide the RS Invite than additional
>>>>>>>>>>> signalling is needed to initiate the recording between SRS
>>>>>>> (Policy
>>>>>>>>>>> Manager) and softswitch (CTI based API) and between
>>>>> softswitch
>>>>>>> and
>>>>>>>>>>> agent handset (UA) (SIP?). So standards are needed for CTI
>>>>>>>>>>> signalling from Policy Manager / SRS to softswitch and from
>>>>>>>>>>> softswitch to the agent handset.
>>>>>>>>>>>
>>>>>>>>>>> Another reason why this is not a good idea, is that an
>>>> extra
>>>>>>>>>>> component (softswitch) is involved in the RS setup for the
>>>>>>>>>>> conversion of the CTI message from the SRS into a SIP
>>>>>>>>>>> message(?) towards the handset (SRC).
>>>>>>>>>>>
>>>>>>>>>>> With an SRS initiated flow the additional signalling
>>>>>> definition
>>>>>>> is
>>>>>>>>>>> not needed and only minimal changes are needed on the
>>>>>> softswitch
>>>>>>>>>>> acting as a SIP proxy.
>>>>>>>>>>>
>>>>>>>>>>> Having all the agent handsets always start a RS
>>>>>> session for each
>>>>>>>> CS
>>>>>>>>>>> would be quite a waste of SIP sessions,
>>>>> specifically since the
>>>>>>>>>>> softswitch is involved as SIP-proxy in all session setup
>>>> and
>>>>>>> since
>>>>>>>>>>> only a limited number of sessions will need
>>>>>>>>>> recording.
>>>>>>>>>>>
>>>>>>>>>>> As such I would appreciate the option of a SRS
>>>>> based Invite in
>>>>>>> the
>>>>>>>>>>> standards.
>>>>>>>>>>>
>>>>>>>>>>> As an individual,
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Friso
>>>>>>>>>>> friso.feenstra@logica.com
>>>>>>>>>>> +31 6 415 46 305
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Ravindran Parthasarathi
>>>>> [mailto:pravindran@sonusnet.com]
>>>>>>>>>>> Sent: dinsdag 20 september 2011 16:22
>>>>>>>>>>> To: Feenstra, Friso; Paul Kyzivat; siprec@ietf.org
>>>>>>>>>>> Subject: RE: [siprec] SRS-initiated initial INVITE
>>>>>>>>>>>
>>>>>>>>>>> Friso,
>>>>>>>>>>>
>>>>>>>>>>> In case I remember correctly, the same SRS callflow
>>>>>> was discussed
>>>>>>>>>>> long back. The mentioned callflow is not good design in my
>>>>>>> opinion
>>>>>>>>>>> because extra channel is required between softswitch
>>>>>> &   SRS apart
>>>>>>>>>>> from SIPREC framework.
>>>>>>>>>>>
>>>>>>>>>>> The alternative is to start the recording from agent
>>>> handset
>>>>>>>> towards
>>>>>>>>>>> SRS with CS id.  Please let me know the issue in this
>>>>>> approach.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Partha
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>> [mailto:siprec-bounces@ietf.org]
>>>>>>> On
>>>>>>>>>>>> Behalf Of Feenstra, Friso
>>>>>>>>>>>> Sent: Tuesday, September 20, 2011 7:38 PM
>>>>>>>>>>>> To: Paul Kyzivat; siprec@ietf.org
>>>>>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
>>>>>>>>>>>>
>>>>>>>>>>>> Paul,
>>>>>>>>>>>>
>>>>>>>>>>>> Business intelligence is in the SRS. SRS is informed
>>>>>>>>>>> out-of-band that
>>>>>>>>>>>> CS session is started. Based on the out-of-band provided
>>>>>>>>>>>> information the SRS determines that RS is needed.
>>>>> Part of the
>>>>>>>> out-
>>>>>>>>>>>> of-band information is the identification of the
>>>>>> SRC. Based on
>>>>>>>> this
>>>>>>>>>>> information
>>>>>>>>>>>> the (offerless) Invite is send to the SRC.
>>>>>>>>>>>>
>>>>>>>>>>>> The SRC intelligence is included in the UA (agent
>>>>>> handset). This
>>>>>>>>>>>> way only a limited implementation is needed on the
>>>>>> controlling
>>>>>>>>>>> softswitch.
>>>>>>>>>>>> RS is managed between SRS recorder and agent handset.
>>>>>>>>>>>>
>>>>>>>>>>>> As an individual,
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Friso
>>>>>>>>>>>> friso.feenstra@logica.com
>>>>>>>>>>>> +31 6 415 46 305
>>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>> [mailto:siprec-bounces@ietf.org]
>>>>>>> On
>>>>>>>>>>>> Behalf Of Paul Kyzivat
>>>>>>>>>>>> Sent: dinsdag 20 september 2011 15:54
>>>>>>>>>>>> To: siprec@ietf.org
>>>>>>>>>>>> Subject: Re: [siprec] SRS-initiated initial INVITE
>>>>>>>>>>>>
>>>>>>>>>>>> Friso,
>>>>>>>>>>>>
>>>>>>>>>>>> On 9/20/11 6:23 AM, Feenstra, Friso wrote:
>>>>>>>>>>>>> As a new participant I would like to make the following
>>>>>>> remark.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We currently have a strong requirement for a
>>>>>> ´intelligent´ SRS
>>>>>>>>>>>>> capable
>>>>>>>>>>>> of
>>>>>>>>>>>>>
>>>>>>>>>>>>> starting and stopping RS sessions. We want to deploy a
>>>>>>>>>>> contact centre
>>>>>>>>>>>>>
>>>>>>>>>>>>> solution with agents dispersed around the globe.
>>>>>> The business
>>>>>>>>>>>> intelligence
>>>>>>>>>>>>>
>>>>>>>>>>>>> of what and when to record will be at the SRS, so the
>>>> SRS
>>>>>>>> should
>>>>>>>>>> be
>>>>>>>>>>>> capable
>>>>>>>>>>>>>
>>>>>>>>>>>>> determining what's to be recorded and of starting the
>>>> RS.
>>>>>>>>>>>>
>>>>>>>>>>>> Could you explain more about how the intelligence is
>>>>>>> distributed?
>>>>>>>>>>>> How much does the SRS know a priori about the calls?
>>>>>>>>>>>> And what is the granularity of the SRC? Are you imagining
>>>>>>>>>>> that the SRC
>>>>>>>>>>>> is on a per-agent basis? Or does an SRC cover many
>>>>> agents and
>>>>>>>> many
>>>>>>>>>>>> concurrent calls?
>>>>>>>>>>>>
>>>>>>>>>>>>> An option could be that the SRS sends an offerless
>>>>>> invite, as
>>>>>>>>>>>> currently
>>>>>>>>>>>>>
>>>>>>>>>>>>> defined in the architecture. Next the SRC could provide
>>>>>>>>>>> based on its
>>>>>>>>>>>>>
>>>>>>>>>>>>> knowledge of the current CS send the 200 OK with the SDP
>>>>>>>>>>> and metadata
>>>>>>>>>>>>>
>>>>>>>>>>>>> describing the available sessions. With this
>>>>> knowledge and
>>>>>>>> based
>>>>>>>>>> on
>>>>>>>>>>>> the
>>>>>>>>>>>>>
>>>>>>>>>>>>> business intelligence in the SRS, the SRS could then
>>>>>>>>>>> accept which of
>>>>>>>>>>>> the
>>>>>>>>>>>>>
>>>>>>>>>>>>> available streams it would like for recording,
>>>>> either in an
>>>>>>> ACK
>>>>>>>>>>>> response or
>>>>>>>>>>>>>
>>>>>>>>>>>>> through a re-Invite.
>>>>>>>>>>>>
>>>>>>>>>>>> I can see how this could at least scale right if
>>>>> the SRC was
>>>>>>>>>>> per-agent.
>>>>>>>>>>>> But if the SRC was something like a PBX that
>>>>> covered all the
>>>>>>>>>>> agents in
>>>>>>>>>>>> a facility, then it wouldn't scale reasonably, because the
>>>>>>>>>>> offer would
>>>>>>>>>>>> then contain perhaps hundreds of media streams.
>>>>>>>>>>>>
>>>>>>>>>>>>> I hope there will be room for this use case in the RFC.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As an individual,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Friso Feenstra
>>>>>>>>>>>>>
>>>>>>>>>>>>> Friso.feenstra@logica.com
>>>>>> <mailto:Friso.feenstra@logica.com>
>>>>>>>>>>>>>
>>>>>>>>>>>>> +31 6 415 46 305
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Think green - keep it on the screen. This e-mail and any
>>>>>>>>>>> attachment
>>>>>>>>>>>>> is for authorised use by the intended
>>>>> recipient(s) only. It
>>>>>>> may
>>>>>>>>>>>>> contain proprietary material, confidential
>>>>>> information and/or
>>>>>>>> be
>>>>>>>>>>>>> subject to legal privilege. It should not be
>>>>>> copied, disclosed
>>>>>>>>>>>>> to, retained or
>>>>>>>>>>>> used
>>>>>>>>>>>>> by, any other party. If you are not an intended
>>>> recipient
>>>>>>>>>>> then please
>>>>>>>>>>>>> promptly delete this e-mail and any attachment and
>>>>>> all copies
>>>>>>>> and
>>>>>>>>>>>> inform
>>>>>>>>>>>>> the sender. Thank you.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Think green - keep it on the screen.
>>>>>>>>>>>>
>>>>>>>>>>>> This e-mail and any attachment is for authorised use by
>>>> the
>>>>>>>>>>>> intended
>>>>>>>>>>>> recipient(s) only. It may contain proprietary material,
>>>>>>>>>>>> confidential information and/or be subject to legal
>>>>>> privilege.
>>>>>>> It
>>>>>>>>>>>> should not be copied, disclosed to, retained or
>>>>> used by, any
>>>>>>>> other
>>>>>>>>> party.
>>>>>>>>>>> If you are
>>>>>>>>>>>> not an intended recipient then please promptly delete this
>>>>>>>>>>> e-mail and
>>>>>>>>>>>> any attachment and all copies and inform the sender.
>>>>>> Thank you.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> siprec mailing list
>>>>>>>>>>>> siprec@ietf.org
>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Think green - keep it on the screen.
>>>>>>>>>>>
>>>>>>>>>>> This e-mail and any attachment is for authorised use by the
>>>>>>>> intended
>>>>>>>>>>> recipient(s) only. It may contain proprietary material,
>>>>>>>> confidential
>>>>>>>>>>> information and/or be subject to legal privilege. It
>>>>>> should not
>>>>>>> be
>>>>>>>>>>> copied, disclosed to, retained or used by, any
>>>>> other party. If
>>>>>>> you
>>>>>>>>>>> are not an intended recipient then please promptly
>>>>> delete this
>>>>>>>>>>> e-mail and any attachment and all copies and inform
>>>>>> the sender.
>>>>>>>>>>> Thank you.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Think green - keep it on the screen.
>>>>>>>>>>>
>>>>>>>>>>> This e-mail and any attachment is for authorised use by the
>>>>>>>> intended
>>>>>>>>>>> recipient(s) only. It may contain proprietary material,
>>>>>>>> confidential
>>>>>>>>>>> information and/or be subject to legal privilege. It
>>>>>> should not
>>>>>>> be
>>>>>>>>>>> copied, disclosed to, retained or used by, any
>>>>> other party. If
>>>>>>> you
>>>>>>>>>>> are not an intended recipient then please promptly
>>>>> delete this
>>>>>>>>>>> e-mail and any attachment and all copies and inform
>>>>>> the sender.
>>>>>>>>>>> Thank you.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>> Think green - keep it on the screen.
>>>>>
>>>>> This e-mail and any attachment is for authorised use by the
>>>>> intended recipient(s) only. It may contain proprietary
>>>>> material, confidential information and/or be subject to legal
>>>>> privilege. It should not be copied, disclosed to, retained or
>>>>> used by, any other party. If you are not an intended
>>>>> recipient then please promptly delete this e-mail and any
>>>>> attachment and all copies and inform the sender. Thank you.
>>>>>
>>>>>
>>>>>
>>> _______________________________________________
>>> 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
>


From john.2.stafford@bt.com  Wed Nov  2 03:51:40 2011
Return-Path: <john.2.stafford@bt.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 96DC911E8164 for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 03:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.059
X-Spam-Level: 
X-Spam-Status: No, score=-3.059 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, J_CHICKENPOX_81=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhxbW1XR-C9o for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 03:51:38 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.com [62.239.224.234]) by ietfa.amsl.com (Postfix) with ESMTP id 308ED11E8163 for <siprec@ietf.org>; Wed,  2 Nov 2011 03:51:38 -0700 (PDT)
Received: from EVMHT61-UKRD.domain1.systemhost.net (10.36.3.127) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.159.2; Wed, 2 Nov 2011 10:51:36 +0000
Received: from EMV64-UKRD.domain1.systemhost.net ([169.254.2.102]) by EVMHT61-UKRD.domain1.systemhost.net ([10.36.3.127]) with mapi; Wed, 2 Nov 2011 10:51:36 +0000
From: <john.2.stafford@bt.com>
To: <pkyzivat@alum.mit.edu>, <siprec@ietf.org>
Date: Wed, 2 Nov 2011 10:51:30 +0000
Thread-Topic: [siprec] Need Inputs: How to representattributesofassociation in Metadata Model and in XML ?
Thread-Index: AcyY1/ZXf7fLdfZPQRe2bCr2HQjk4wAcilRw
Message-ID: <BBA98B7742309546A60F3AE3B4E975A72822DC2DCC@EMV64-UKRD.domain1.systemhost.net>
References: <058.f76a86cfba526ca37c258c5ffc98b278@trac.tools.ietf.org><35BCE99A477D6A4986FB2216D8CF2CFD07F6F9D2@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38BA8728E6@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD07F6F9D8@XMB-BGL-417.cisco.com><4E971D30.5090101@alum.mit.edu><35BCE99A477D6A4986FB2216D8CF2CFD080912F6@XMB-BGL-417.cisco.com><F62A45FE3109498D85EB786F3B4503AC@JohnsComputer>, <35BCE99A477D6A4986FB2216D8CF2CFD082B7DD5@XMB-BGL-417.cisco.com><BBA98B7742309546A60F3AE3B4E975A72820ED8FBB@EMV64-UKRD.domain1.systemh ost.net	>	<35BCE99A477D6A4986FB2216D8CF2CFD082B806E@XMB-BGL-417.cisco.com> <2E239D6FCD033C4BAF15F386A979BF51159D6B@sonusinmail02.sonusnet.com> <BBA98B7742309546A60F3AE3B4E975A72820CC5B49@EMV64-UKRD.domain1.systemhost.net>, <4EAAD2C9.5030008@alum.mit.edu> <BBA98B7742309546A60F3AE3B4E975A72820ED8FC1@EMV64-UKRD.domain1.systemhost.net>, <4EAAE681.40107@alum.mit.edu> <BBA98B7742309546A60F3AE3B4E975A72822C3A32D@EMV64-UKRD.domain1.systemhost.net> <4EB05B16.7040002@alum.mit.edu>
In-Reply-To: <4EB05B16.7040002@alum.mit.edu>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Need Inputs: How to representattributesofassociation in Metadata Model and in XML ?
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, 02 Nov 2011 10:51:40 -0000

Paul,
I am still confused, comments inline
Rgds
John

>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>On Behalf Of Paul Kyzivat
>Sent: 01 November 2011 20:48
>To: siprec@ietf.org
>Subject: Re: [siprec] Need Inputs: How to
>representattributesofassociation in Metadata Model and in XML ?
>
>This is just from me - it hasn't been reviewed by Ram and Partha.
>Lets see if they agree.
>
>       Thanks,
>       Paul
>
>On 10/31/11 7:58 AM, john.2.stafford@bt.com wrote:
>> Paul,
>> RE use of recv with conferences,
>>
>> thanks for your response, I think I am ok with this now, I
>got myself all confused last week, your response made me stop
>and think.
>>
>> Here is my understanding,  please point if I am still wrong:
>>
>> The<stream>  elements in metadata describe the RTP streams that flow
>> as part of the call, so for a 3 party conference (A,B,C)
>with a separate media server conference focus, there are 6 streams.
>
>This is one way.
>Another way is to describe it as a single stream with (A,B,C)
>each both sending and receiving it.
But isn't the meta data meant to be describing the actual RTP streams?
I don't understand why this means the stream contains a mix.
Draft-ietf-siprec-metadata-05 describes a stream by "A media stream class (=
and its objects) has the properties of media as seen by SRC and sent to SRS=
",  and then goes on "The metadata model should include media streams that =
are not being delivered to the SRS". Which doesn't help me at all.

>
>> The recorder stream is sent from the conference focus,
>assume this this has  a=3Dlabel:1234 in its SDP.
>>
>> So in the metadata, the streams would be labelled to
>indicate that the the transmit streams from the 3 participants
>are mixed into the recorder stream, as follows:
>> A->focus  stream<label>1234</label>
>> focus->A  stream
>> B->focus  stream<label>1234</label>
>> focus->B  stream
>> C->focus  stream<label>1234</label>
>> focus->C stream
>
>Why do you have the same label for all three?
>Each stream that is sent to the SRS should have a different
>label, mapping to a separate m-line.
Because what is being recorded is a SRC mix of the 3 participants transmit =
streams into a single recorder
stream described by the one m-line

>
>If it had been represented as a single stream, then the SRC
>would have to do the mixing, and there would be only one label.
One label where ?


Can you show me how metadata and SDP should be for this example
if I don't want to describe it as a single stream with (A,B,C)
each both sending and receiving it.


>
>> I think the metadata draft would benefit from having a
>conference example.
>
>Yes, it would.
>
>       Thanks,
>       Paul
>
>> Rgds
>> John Stafford | Solution Architect 1 | BT Global Services
>>
>> ________________________________________
>> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of
>> Paul Kyzivat [pkyzivat@alum.mit.edu]
>> Sent: 28 October 2011 18:29
>> To: siprec@ietf.org
>> Subject: Re: [siprec] Need Inputs: How to
>representattributesofassociation in Metadata Model and in XML ?
>>
>> On 10/28/11 12:10 PM, john.2.stafford@bt.com wrote:
>>> Paul,
>>>
>>> OK, I understand, but how does the recorder know that the
>stream sent by the focus is a mixed conference stream , ie
>contains all of the streams received by the focus. ?
>>
>> I don't think I understand the question.
>> The SRS should just believe what it is told:
>> the stream it receives contains a mix of all the
>participants reported
>> as sending to it.
>>
>>          Thanks,
>>          Paul
>>
>>> Rgds
>>> John Stafford | Solution Architect 1 | BT Global Services
>>>
>>> ________________________________________
>>> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On
>Behalf Of
>>> Paul Kyzivat [pkyzivat@alum.mit.edu]
>>> Sent: 28 October 2011 17:05
>>> To: siprec@ietf.org
>>> Subject: Re: [siprec] Need Inputs: How to
>representattributesofassociation in Metadata Model and in XML ?
>>>
>>> On 10/28/11 11:06 AM, john.2.stafford@bt.com wrote:
>>>>
>>>> Ram,
>>>>>> I presume the participant - CS<session>    element will
>be replaced by
>>>>>> the<    participantSessionAssoc>.
>>>>>
>>>>> No.<session>    will continue to remain. We are talking
>about association
>>>>> attributes of participant-session.
>>>>> The other attributes of<participant>    and<session>
>which are not
>>>>> association attributes will continue to be the respective
>elements.
>>>>
>>>> What I meant to say was:
>>>> I presume the participant's session attribute will be
>replaced by the<participantSessionAssoc>.
>>>> Is that correct ?
>>>
>>> Yup, that's the idea.
>>>
>>>> RE use of<recv>, this means for a large conference each
>participant update will be very large as it needs to include
>recv's for every other participants send  ?
>>>
>>> The association is between each participant and a stream,
>not between
>>> two participants. There are two ways to represent this, and neither
>>> has the problem you describe:
>>>
>>> - one stream for the conference.
>>>      Each participant both sends and receives it.
>>>
>>> - one stream for each participant in the conference.
>>>      The focus is represented as a participant.
>>>      Each real participant sends and receives its own stream.
>>>      The focus sends and receives all the streams.
>>>
>>> I guess the situation you describe would occur if there was a
>>> full-mesh of streams between participants. But afaik nobody does
>>> that. And if they did it would be hard to get an SRC in the middle.
>>>
>>>           Thanks,
>>>           Paul
>>>
>>>> Rgds John
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Ravindran Parthasarathi [mailto:pravindran@sonusnet.com]
>>>> Sent: 28 October 2011 14:43
>>>> To: Ram Mohan R (rmohanr); Stafford,J,John,JRJ3X C; siprec@ietf.org
>>>> Subject: RE: [siprec] Need Inputs: How to
>representattributesofassociation in Metadata Model and in XML ?
>>>>
>>>> Hi,
>>>>
>>>> IMO, send&    recv are the element which has to be pushed
>inside participant stream association element which is inline
>with the model.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>> Behalf
>>>>> Of Ram Mohan R (rmohanr)
>>>>> Sent: Friday, October 28, 2011 7:04 PM
>>>>> To: john.2.stafford@bt.com; siprec@ietf.org
>>>>> Subject: Re: [siprec] Need Inputs: How to
>>>>> representattributesofassociation in Metadata Model and in XML ?
>>>>>
>>>>> Hello John S,
>>>>>
>>>>> Please see inline for answers.
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org
>[mailto:siprec-bounces@ietf.org] On
>>>>>> Behalf Of john.2.stafford@bt.com
>>>>>> Sent: Thursday, October 27, 2011 11:15 PM
>>>>>> To: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Need Inputs: How to represent
>>>>>> attributesofassociation in Metadata Model and in XML ?
>>>>>>
>>>>>> I am not clear on the effect on the other XMl elements.
>>>>>>
>>>>>> I presume the participant - CS<session>    element will
>be replaced by
>>>>>> the<    participantSessionAssoc>.
>>>>>
>>>>> No.<session>    will continue to remain. We are talking
>about association
>>>>> attributes of participant-session.
>>>>> The other attributes of<participant>    and<session>
>which are not
>>>>> association attributes will continue to be the respective
>elements.
>>>>>
>>>>>>
>>>>>> I also presume<send>    and<recv>     will no longer be
>needed, and that
>>>>>> the<participantStream Assoc>    will include an
>attribute to say send
>>>>> or
>>>>>> recv ?
>>>>>
>>>>> This is a good suggestion. I have not given a thought on
>this so far.
>>>> In
>>>>> principle this should be fine as once the association of a
>>>>> participant to a stream ends it stops sending/receiving the same.
>>>>> We need to think through different use-cases to see if
>its fine to
>>>>> have<send>,<recv> inside association element itself. By having
>>>>> send, recv inside the association we can avoid one XML
>element as they can be attribute.
>>>>>
>>>>>>
>>>>>> Is that correct ?
>>>>>>
>>>>>> I hope the rule will remain that,  in the abscence of any recv
>>>>> elements
>>>>>> by default a stream is assumed to be recieved by all
>participants.
>>>>>
>>>>> No, in the last IETF we agreed it's better to always explicity
>>>>> indicate recv. We will continue to stick to that as I see
>no reason to change.
>>>>>
>>>>> Regards,
>>>>> Ram
>>>>>
>>>>>>
>>>>>> Rgds
>>>>>> John Stafford | Solution Architect 1 | BT Global Services
>>>>>>
>>>>>> ________________________________________
>>>>>> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org]
>On Behalf
>>>>>> Of Ram Mohan R (rmohanr) [rmohanr@cisco.com]
>>>>>> Sent: 27 October 2011 18:08
>>>>>> To: John Elwell; Paul Kyzivat; siprec@ietf.org
>>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>>>>> ofassociation    in Metadata Model and in XML ?
>>>>>>
>>>>>> Hi John,
>>>>>>
>>>>>> Thanks for your comment on this. Yes several of us seem to be
>>>> inclined
>>>>>> towards approach 2.  I like your point that once one of the
>>>>>> elements
>>>>> in
>>>>>> the association gets deleted, the association element life ends.
>>>>>> SRC may choose to send the association element optionally or the
>>>>>> SRS can
>>>> still
>>>>>> learn that as the way you mentioned.
>>>>>>
>>>>>> We ( authors of metadata draft ) discussed internally on
>this open
>>>>> item
>>>>>> and see some issues with adopting approach 2 as is with the
>>>>>> current model /schema. I will start a separate mail
>thread for the
>>>>>> issue as this thread is already too long.
>>>>>>
>>>>>> Thanks,
>>>>>> Ram
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: John Elwell [mailto:john.r.elwell@gmail.com]
>>>>>>> Sent: Thursday, October 27, 2011 2:03 PM
>>>>>>> To: Ram Mohan R (rmohanr); Paul Kyzivat; siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>>>>>> ofassociation in Metadata Model and in XML ?
>>>>>>>
>>>>>>> Approach 2 seems reasonable. Could we say that an
>association is
>>>>>>> implicitly deleted (gains a dissociate time) as soon as one of
>>>>>>> the associated elements is deleted (gains a dissociate time)?
>>>>>>> This would reduce the on-the
>>>>>> wire
>>>>>>> document size for both partial and full metadata in some
>>>>>> circumstances
>>>>>>> (e.g., conference termination by the focus).
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>> From: "Ram Mohan R (rmohanr)"<rmohanr@cisco.com>
>>>>>>> To: "Paul Kyzivat"<pkyzivat@alum.mit.edu>;<siprec@ietf.org>
>>>>>>> Sent: Friday, October 14, 2011 4:59 AM
>>>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>>>>>> ofassociation in Metadata Model and in XML ?
>>>>>>>
>>>>>>>
>>>>>>>> Thanks Paul for your comments. I also prefer approach 2 as
>>>>>> mentioned
>>>>>>>> below in this thread.
>>>>>>>> I will wait to hear for comments/opinion from others.
>>>>>>>>
>>>>>>>> Ram
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>>>> On
>>>>>>>>> Behalf Of Paul Kyzivat
>>>>>>>>> Sent: Thursday, October 13, 2011 10:48 PM
>>>>>>>>> To: siprec@ietf.org
>>>>>>>>> Subject: Re: [siprec] Need Inputs: How to represent attributes
>>>> of
>>>>>>>>> association in Metadata Model and in XML ?
>>>>>>>>>
>>>>>>>>> I like approach 2, as Ram has shown it. It deals with the
>>>>> problems
>>>>>>>> John
>>>>>>>>> raised with the others.
>>>>>>>>>
>>>>>>>>> I didn't follow John's arithmetic on this one, using his 20
>>>> party
>>>>>>>>> conference example. As I count that, there are 21 participants
>>>>>> when
>>>>>>>> you
>>>>>>>>> include the focus. Each of the 20 has two stream/participant
>>>>>>>>> associations with the focus, for a total of 40. (The
>>>>>>>>> association
>>>>>> is
>>>>>>>>> bidirectional. I can only get to 80 by assuming we had to
>>>>>> represent
>>>>>>> an
>>>>>>>>> association in each direction.) And each has two ids, each of
>>>>>> which
>>>>>>> is
>>>>>>>>> also the id of a stream or participant. So there are really
>>>>>>>>> only
>>>>>> 23
>>>>>>>>> distinct ids that need to be assigned for this. (One for each
>>>>>>>>> of
>>>>>> the
>>>>>>>> 21
>>>>>>>>> participants, and one for each of the two streams.)
>>>>>>>>>
>>>>>>>>> The 40 associations, each carrying two ids, is still kind of a
>>>>> lot
>>>>>>> if
>>>>>>>>> its sent all at once. But when starting up a conference they
>>>> will
>>>>>>>>> probably be added gradually as each participant joins. Same at
>>>>> the
>>>>>>> end
>>>>>>>>> if they drop off individually. But it could be a
>bunch together
>>>>> if
>>>>>>> the
>>>>>>>>> conference is forcibly dropped by the focus. But it does
>>>> minimize
>>>>>>> what
>>>>>>>>> is sent when things happen incrementally.
>>>>>>>>>
>>>>>>>>> There may be some optimizations that can be done - e.g. a sort
>>>> of
>>>>>>>>> "wildcard" for one of the the two ids in the
>association class.
>>>>>> E.g.
>>>>>>>>>
>>>>>>>>> <participantStreamAssoc
>>>>>>>>>       participant=3D"*"
>>>>>>>>>       stream
>=3D"urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>>
>>>> <disassociate-time>2010-12-16T23:41:07Z</disassociate-time>
>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>
>>>>>>>>> (I'm not advocating that particular syntax. Its just something
>>>> to
>>>>>>> make
>>>>>>>>> the point.)
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Paul
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 10/12/11 4:56 AM, Ram Mohan R (rmohanr) wrote:
>>>>>>>>>> My bad(typo) while sending the example. The correct partial
>>>>>> update
>>>>>>> I
>>>>>>>>>> intended to send  is:
>>>>>>>>>>
>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>
>participant=3D"urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>       stream
>=3D"urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>>>
>>>>>>>>>> <disassociate-time>2010-12-16T23:41:07Z</disassociate-
>>>>>> time>
>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>
>>>>>>>>>> This is inline with approach 2 where in each association XML
>>>>>>> element
>>>>>>>>>> will have the IDs of the related associated elements.
>>>>>>>>>>
>>>>>>>>>> Ram
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>>>>>>>> Sent: Wednesday, October 12, 2011 2:24 PM
>>>>>>>>>>> To: Ram Mohan R (rmohanr); siprec@ietf.org
>>>>>>>>>>> Cc: Ofir Roth
>>>>>>>>>>> Subject: RE: Need Inputs: How to represent attributes of
>>>>>>>> association
>>>>>>>>>> in
>>>>>>>>>>> Metadata Model and in XML ?
>>>>>>>>>>>
>>>>>>>>>>> We do prefer to receive related elements as well, it makes
>>>>>>>>>>> implementation much easier.
>>>>>>>>>>>      At least we should get relevant IDs.  For
>example below,
>>>> SRC
>>>>>>>>> should
>>>>>>>>>>> also send ParticipantId
>>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>>> Sent: Wednesday, October 12, 2011 10:52 AM
>>>>>>>>>>> To: Leon Portman; siprec@ietf.org
>>>>>>>>>>> Cc: Ofir Roth
>>>>>>>>>>> Subject: RE: Need Inputs: How to represent attributes of
>>>>>>>> association
>>>>>>>>>> in
>>>>>>>>>>> Metadata Model and in XML ?
>>>>>>>>>>>
>>>>>>>>>>> Leon,
>>>>>>>>>>> Thanks for your response. One of the adv with approach 2 is
>>>> we
>>>>>>> can
>>>>>>>>>>> indicate only changes in the association without the need to
>>>>>>>>>> indicating
>>>>>>>>>>> the elements ( of association). IOW for the below
>example, if
>>>>>>> there
>>>>>>>>> is
>>>>>>>>>>> a change in participant-stream association I can simply send
>>>>>> the
>>>>>>>>>>> following in partial update:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>>      stream
>=3D"urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a">
>>>>>>>>>>>
>>>>>> <disassociate-time>2010-12-16T23:41:07Z</disassociate-time>
>>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>>
>>>>>>>>>>> Do you see a need to always indicate the related
>elements too
>>>>> ?
>>>>>>> In
>>>>>>>>>>> which case I see approach 1 as more suitable.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Ram
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>>>>>>>>> Sent: Wednesday, October 12, 2011 12:55 PM
>>>>>>>>>>>> To: Ram Mohan R (rmohanr); siprec@ietf.org
>>>>>>>>>>>> Cc: Ofir Roth
>>>>>>>>>>>> Subject: RE: Need Inputs: How to represent attributes of
>>>>>>>>> association
>>>>>>>>>>>> inmetadata Model and in XML ?
>>>>>>>>>>>>
>>>>>>>>>>>> Ram Hi
>>>>>>>>>>>>
>>>>>>>>>>>> I am ok with approaches 1 and  however I do prefer approach
>>>>>> one
>>>>>>>>>>> because
>>>>>>>>>>>> it will be easier for SRS to get decode - association is
>>>>>> inside
>>>>>>>>>>>> relevant element. And it is more readable.
>>>>>>>>>>>> Approach 2 will work as well, however it is important that
>>>> if
>>>>>>>> there
>>>>>>>>>>>> will be a change in association then to send to
>SRS not only
>>>>>>>>> updated
>>>>>>>>>>>> association element but also related elements: for example
>>>> if
>>>>>>>>> stream
>>>>>>>>>>>> was associated to participant and session, send also
>>>>>> participant
>>>>>>>>> and
>>>>>>>>>>>> session latest state.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>>
>>>>>>>>>>>> Leon
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>> [mailto:siprec-bounces@ietf.org]
>>>>>>> On
>>>>>>>>>>>> Behalf Of Ram Mohan R (rmohanr)
>>>>>>>>>>>> Sent: Wednesday, October 12, 2011 7:48 AM
>>>>>>>>>>>> To: siprec@ietf.org
>>>>>>>>>>>> Subject: [siprec] Need Inputs: How to represent attributes
>>>> of
>>>>>>>>>>>> association in metadata Model and in XML ?
>>>>>>>>>>>>
>>>>>>>>>>>> (Sorry for lengthy e-mail)
>>>>>>>>>>>>
>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>
>>>>>>>>>>>> In the last interim we discussed 4 approaches for
>>>>> representing
>>>>>>>>>>>> attributes of association in XML.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Here are some pros/cons for each of them:
>>>>>>>>>>>> Approach 1:
>>>>>>>>>>>> ----------
>>>>>>>>>>>> Represent the association attribute as a property
>within one
>>>>>> of
>>>>>>>> the
>>>>>>>>>>>> associated elements. Example given at
>>>>>> http://www.ietf.org/mail-
>>>>>>>>>>>> archive/web/siprec/current/msg02709.html Does not need
>>>>> another
>>>>>>> XML
>>>>>>>>>>>> element and represents the association attributes as
>>>>>> capability
>>>>>>> of
>>>>>>>>>>> one
>>>>>>>>>>>> of the association element.
>>>>>>>>>>>> e.g.
>>>>>>>>>>>> <participant
>>>>>>>>>>>>
>>>>> id=3D"urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>>                session=3D"urn:uuid:855a5ded-8420-456d-a70f-
>>>>>>>>> 6da1eeaeb425">
>>>>>>>>>>>>                      <aor>sip:ram@blr.cisco.com</aor>
>>>>>>>>>>>>                      <associate-time>2010-12-
>>>>>>> 16T23:41:07Z</associate-
>>>>>>>>>>> time>
>>>>>>>>>>>>                      <capabilities>     TBD</capabilties>
>>>>>>>>>>>>                      <participantStreamAssoc
>>>>>>>>>>>>                       stream
>>>> =3D"urn:uuid:f3373a7b-4958-4e55-8820-
>>>>>>>>>>>> d03a191fb76a
>>>>>>>>>>>> ">
>>>>>>>>>>>>                        <associate-time>2010-12-
>>>>>>>>> 16T23:41:07Z</associate-
>>>>>>>>>>>> time>
>>>>>>>>>>>>                        <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>>>                      </participantStreamAssoc>
> </participant>
>>>>>> In
>>>>>>>>> the
>>>>>>>>>>> above
>>>>>>>>>>>> example the participant contributes a single streams. For
>>>>> each
>>>>>>>>>> stream
>>>>>>>>>>>> the association attribute (participant-stream) is
>shown with
>>>>>> the
>>>>>>>>>>> stream
>>>>>>>>>>>> ID nested in.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Approach 2:
>>>>>>>>>>>> -----------
>>>>>>>>>>>> In this approach we have a new XML element for every
>>>>>> association
>>>>>>>>>>> class.
>>>>>>>>>>>> This xml element will NOT have a unique ID instead it
>>>>>> references
>>>>>>>>> the
>>>>>>>>>>> ID
>>>>>>>>>>>> of associated elements (shown below). With this approach it
>>>>> is
>>>>>>>> easy
>>>>>>>>>>> to
>>>>>>>>>>>> update as the association class is a separate XML element
>>>> and
>>>>>>> not
>>>>>>>>>>>> property.
>>>>>>>>>>>> e.g.
>>>>>>>>>>>> <participantSessionAssoc
>>>>>>>>>>>>
>>>> participant=3D"urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>>
>session=3D"urn:uuid:855a5ded-8420-456d-a70f-6da1eeaeb425">
>>>>>>>>>>>>       <associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>>       <capabilities>     TBD</capabilties>
>>>>>>>>>>>> </participantSessionAssoc>
>>>>>>>>>>>>
>>>>>>>>>>>> <participantStreamAssoc
>>>>>>>>>>>>
>>>> participant=3D"urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3"
>>>>>>>>>>>>      stream
>=3D"urn:uuid:f3373a7b-4958-4e55-8820-d03a191fb76a ">
>>>>>>>>>>>>
><associate-time>2010-12-16T23:41:07Z</associate-time>
>>>>>>>>>>>>         <csrc>contributing SSRC-1</csrc>
>>>>>>>>>>>> </participantStreamAssoc>
>>>>>>>>>>>>
>>>>>>>>>>>> Approach 3 and 4 are in the below e-mail from John.
>>>>>>>>>>>> Approach 3 defines a new Unique ID for every
>association XML
>>>>>>>>> elment.
>>>>>>>>>>>> Also it creates alias for the other IDs. In the discussions
>>>>> in
>>>>>>>>>>> interim
>>>>>>>>>>>> there was no strong support for this approach.
>>>>>>>>>>>>
>>>>>>>>>>>> Approach 4 is same as approach 1 where in the association
>>>>>>> element
>>>>>>>>> is
>>>>>>>>>>>> encapsulated in one of  the XML elements (to which it is
>>>>>>>>>> associated).
>>>>>>>>>>>> In addition to that it also has reference to the elements
>>>>>> (alias
>>>>>>>> of
>>>>>>>>>>>> IDs) to which the association belongs.
>>>>>>>>>>>>
>>>>>>>>>>>> I prefer approach 2 as it is has a separate XML element to
>>>>>>>>> represent
>>>>>>>>>>>> the association class. The only difference of this XML
>>>>> element
>>>>>>>> from
>>>>>>>>>>>> others is this does not need a unique ID. Instead it
>>>>>> references
>>>>>>>> the
>>>>>>>>>>> IDs
>>>>>>>>>>>> of the elements to which the association belongs.
>>>>>>>>>>>> Since association class is a special class meant to
>>>> associate
>>>>>>>>>>> multiple
>>>>>>>>>>>> classes, I see it ok to have a representation as
>in approach
>>>>> 2
>>>>>>>>> where
>>>>>>>>>>> in
>>>>>>>>>>>> the identifier is the concatenation of the classes to which
>>>>>> the
>>>>>>>>>>>> association belongs to.
>>>>>>>>>>>>
>>>>>>>>>>>> Please provide your comments on this and also suggest any
>>>>>> other
>>>>>>>>>>>> approaches to represent association classes in XML.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Ram
>>>>>>>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>> _______________________________________________
>>>> 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
>>>
>>
>> _______________________________________________
>> 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
>

From eckelcu@cisco.com  Wed Nov  2 09:59:28 2011
Return-Path: <eckelcu@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 0586921F8DDC for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 09:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.285
X-Spam-Level: 
X-Spam-Status: No, score=-6.285 tagged_above=-999 required=5 tests=[AWL=0.314,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DojtqK7vP-O for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 09:59:27 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 405AF21F8C31 for <siprec@ietf.org>; Wed,  2 Nov 2011 09:59:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=2861; q=dns/txt; s=iport; t=1320253167; x=1321462767; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=eSXOMf3YocKlpavZ+yBLjofWhEOR2rPR/j4hoHLWbMI=; b=dXs+FFJBpWBgEhcu4Qz3vq7eKKas1Aj9F6fJgk7EwUMMLjD3uwl28rIp qpwKZf0SRwGj/lCbqX69qZEYdphs1R8SpXv81CAJU1rRuaX5vk9K9PW+1 EFD55vSV5kv0EZlcAtRJvMQ3Fd3WrEOu4bk3r1vffDioFfKlJoMYf1YNz I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtcAAOF1sU6rRDoI/2dsb2JhbAAoGg6ZYo5dgSCBBYFyAQEBBAEBAQ8BHQo0CQ4EAgEIDgMEAQEBCgYXAQYBJh8IAQgBAQQBEggah2gjlhoBnnGIL2EEiAeRR4t0Vw
X-IronPort-AV: E=Sophos;i="4.69,444,1315180800"; d="scan'208";a="10560096"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 02 Nov 2011 16:59:26 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA2GxQTM009900; Wed, 2 Nov 2011 16:59:26 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Nov 2011 09:59:26 -0700
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, 2 Nov 2011 09:59:25 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4EB05F4D.5080600@alum.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
Thread-Index: AcyY2noqPa2ShhBwSFauYKCixh7DegApPMoA
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com> <4EB05F4D.5080600@alum.mit.edu>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>, <siprec@ietf.org>
X-OriginalArrivalTime: 02 Nov 2011 16:59:26.0848 (UTC) FILETIME=[C77AD000:01CC9980]
Subject: Re: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
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, 02 Nov 2011 16:59:28 -0000

Hi Paul,

We certainly could. In general, you would have one CNAME value per
participant. I suppose there may be cases in which a participant would
use multiple CNAMEs despite the fact it is not recommended to do so.
Including the CNAME in the participant info is a good thing. I do not
know if we need to plan to support multiple CNAMEs per participant. Is
that your concern?

Cheers,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Paul Kyzivat
> Sent: Tuesday, November 01, 2011 2:06 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] FW: New Version Notification
fordraft-eckel-siprec-rtp-rec-03.txt
>=20
> Charles,
>=20
> While reading this I got wondering if we need more guidance on the use
> of CNAME. (As referenced in section 5.) Do we need guidance on mapping
> of CNAME to participants?
>=20
> 	Thanks,
> 	Paul
>=20
> On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
> > FYI, I have submitted the updated draft and it is available through
the SIPREC documents page:
> >
http://proxy2974.my-addr.net/myaddrproxy.php/https/datatracker.ietf.org/
wg/siprec/
> >
> > It contains editorial changes as well as additional text describing
the handling of RTCP packets by
> the SRC and UAs per the recent SIPREC list discussion.
> >
> > Cheers,
> > Charles
> >
> > -----Original Message-----
> > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > Sent: Monday, October 31, 2011 10:53 AM
> > To: Charles Eckel (eckelcu)
> > Cc: Charles Eckel (eckelcu)
> > Subject: New Version Notification for
draft-eckel-siprec-rtp-rec-03.txt
> >
> > A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been
successfully submitted by Charles
> Eckel and posted to the IETF repository.
> >
> > Filename:	 draft-eckel-siprec-rtp-rec
> > Revision:	 03
> > Title:		 Real-time Transport Protocol (RTP)
Recommendations for SIPREC
> > Creation date:	 2011-10-31
> > WG ID:		 Individual Submission
> > Number of pages: 13
> >
> > Abstract:
> >     This document provides recommendations and guidelines for RTP
and
> >     RTCP in the context of SIPREC.  This document exists as a
standalone
> >     document to facilitate discussion of the RTP recommendations,
and it
> >     is anticipated that portions of this document will be
incorporated
> >     into [I-D.ietf-siprec-protocol] rather than this document itself
> >     being adopted as a working group document.
> >
> >
> >
> >
> > The IETF Secretariat
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From pkyzivat@alum.mit.edu  Wed Nov  2 10:27:44 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 5285921F9FDE for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 10:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gldq7CyUgPCH for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 10:27:43 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id 6AE9821F9FDB for <siprec@ietf.org>; Wed,  2 Nov 2011 10:27:43 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta01.westchester.pa.mail.comcast.net with comcast id sEAL1h00D1vXlb851HTjRR; Wed, 02 Nov 2011 17:27:43 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta17.westchester.pa.mail.comcast.net with comcast id sHTi1h00j0tdiYw3dHTixF; Wed, 02 Nov 2011 17:27:43 +0000
Message-ID: <4EB17D8C.1050307@alum.mit.edu>
Date: Wed, 02 Nov 2011 13:27:40 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com> <4EB05F4D.5080600@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
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, 02 Nov 2011 17:27:44 -0000

On 11/2/11 12:59 PM, Charles Eckel (eckelcu) wrote:
> Hi Paul,
>
> We certainly could. In general, you would have one CNAME value per
> participant. I suppose there may be cases in which a participant would
> use multiple CNAMEs despite the fact it is not recommended to do so.
> Including the CNAME in the participant info is a good thing. I do not
> know if we need to plan to support multiple CNAMEs per participant. Is
> that your concern?

This may just be my ignorance of how SSRC and CNAME are supposed to be 
used. I understand that SSRC may change due to collision, and that then 
CNAME is supposed to correlate the stream before/after the change. I 
also gather that CNAME, rather than SSRC, is supposed to be used to 
correlate related streams, like audio and video from same source.

Does that mean that we should reference CNAME in metadata, rather, or in 
addition, to SSRC? Or if we update metadata when SSRC changes does that 
eliminate CNAME for tracking the change?

	Thanks,
	Paul

> Cheers,
> Charles
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
>> Sent: Tuesday, November 01, 2011 2:06 PM
>> To: siprec@ietf.org
>> Subject: Re: [siprec] FW: New Version Notification
> fordraft-eckel-siprec-rtp-rec-03.txt
>>
>> Charles,
>>
>> While reading this I got wondering if we need more guidance on the use
>> of CNAME. (As referenced in section 5.) Do we need guidance on mapping
>> of CNAME to participants?
>>
>> 	Thanks,
>> 	Paul
>>
>> On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
>>> FYI, I have submitted the updated draft and it is available through
> the SIPREC documents page:
>>>
> http://proxy2974.my-addr.net/myaddrproxy.php/https/datatracker.ietf.org/
> wg/siprec/
>>>
>>> It contains editorial changes as well as additional text describing
> the handling of RTCP packets by
>> the SRC and UAs per the recent SIPREC list discussion.
>>>
>>> Cheers,
>>> Charles
>>>
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>> Sent: Monday, October 31, 2011 10:53 AM
>>> To: Charles Eckel (eckelcu)
>>> Cc: Charles Eckel (eckelcu)
>>> Subject: New Version Notification for
> draft-eckel-siprec-rtp-rec-03.txt
>>>
>>> A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been
> successfully submitted by Charles
>> Eckel and posted to the IETF repository.
>>>
>>> Filename:	 draft-eckel-siprec-rtp-rec
>>> Revision:	 03
>>> Title:		 Real-time Transport Protocol (RTP)
> Recommendations for SIPREC
>>> Creation date:	 2011-10-31
>>> WG ID:		 Individual Submission
>>> Number of pages: 13
>>>
>>> Abstract:
>>>      This document provides recommendations and guidelines for RTP
> and
>>>      RTCP in the context of SIPREC.  This document exists as a
> standalone
>>>      document to facilitate discussion of the RTP recommendations,
> and it
>>>      is anticipated that portions of this document will be
> incorporated
>>>      into [I-D.ietf-siprec-protocol] rather than this document itself
>>>      being adopted as a working group document.
>>>
>>>
>>>
>>>
>>> The IETF Secretariat
>>> _______________________________________________
>>> 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
>


From eckelcu@cisco.com  Wed Nov  2 18:08:57 2011
Return-Path: <eckelcu@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 D194D11E80DB for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 18:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t5qqhEfYC28O for <siprec@ietfa.amsl.com>; Wed,  2 Nov 2011 18:08:56 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id DCC3911E80CB for <siprec@ietf.org>; Wed,  2 Nov 2011 18:08:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=4741; q=dns/txt; s=iport; t=1320282537; x=1321492137; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=rmQaAAPQdUtJKqNs7QHUx8Z1V4TafMyRTN+mpq9spbA=; b=WA2fgjrmmDRQF0kpstX4tQNKJxVlz9anL37RsG8k49sBZqLeVvM3mytc neZTpOQ/nAF5JUCIeIs71rnVOWrmgeo87Z7LA4h/JLQQv/vssVVXqhms2 4HED0EsPEVsG2ty1nMDWUpj3x4odqFDST/dvCxl6QWRL+pjR20iKrxpjk A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAAJnosU6rRDoH/2dsb2JhbAAqGg6ZbY99gQWBcgEBAQQBAQEPAR0KNAkCDAQCAQgOAwQBAQEKBhcBBgEmHwgBCAEBBBMIGodoI5YdAZ8EiC9hBIgHkUeLdFc
X-IronPort-AV: E=Sophos;i="4.69,446,1315180800"; d="scan'208";a="12043579"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 03 Nov 2011 01:08:56 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pA318uSP010242; Thu, 3 Nov 2011 01:08:56 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Nov 2011 18:08:56 -0700
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, 2 Nov 2011 18:08:55 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C8EF@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4EB17D8C.1050307@alum.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
Thread-Index: AcyZhLx1A42GTEvSTFKP9H82bYNeLQAP8jdw
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com> <4EB05F4D.5080600@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com> <4EB17D8C.1050307@alum.mit.edu>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>
X-OriginalArrivalTime: 03 Nov 2011 01:08:56.0409 (UTC) FILETIME=[291A2C90:01CC99C5]
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
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: Thu, 03 Nov 2011 01:08:57 -0000

I think the CNAME would be useful for identifying the participant, in
cases where the media packets from the participant make it to the SRS.
I think the SSRC would be useful for identifying a stream from a
participant, in cases where the media packets from the participant make
it to the SRS directly, or are incorporated into a mixed stream that
ultimately make it to the SRS. In the second case, the SSRC from the
stream sent by the participant to the SRC will be included as a CSRC in
the mixed stream sent by the SRC to the SRS.
So I think both are useful, and the cases and ways in which they are
useful varies depending on the functionality of the SRC.

Cheers,
Charles

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> Sent: Wednesday, November 02, 2011 10:28 AM
> To: Charles Eckel (eckelcu)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] FW: New Version Notification
fordraft-eckel-siprec-rtp-rec-03.txt
>=20
> On 11/2/11 12:59 PM, Charles Eckel (eckelcu) wrote:
> > Hi Paul,
> >
> > We certainly could. In general, you would have one CNAME value per
> > participant. I suppose there may be cases in which a participant
would
> > use multiple CNAMEs despite the fact it is not recommended to do so.
> > Including the CNAME in the participant info is a good thing. I do
not
> > know if we need to plan to support multiple CNAMEs per participant.
Is
> > that your concern?
>=20
> This may just be my ignorance of how SSRC and CNAME are supposed to be
> used. I understand that SSRC may change due to collision, and that
then
> CNAME is supposed to correlate the stream before/after the change. I
> also gather that CNAME, rather than SSRC, is supposed to be used to
> correlate related streams, like audio and video from same source.
>=20
> Does that mean that we should reference CNAME in metadata, rather, or
in
> addition, to SSRC? Or if we update metadata when SSRC changes does
that
> eliminate CNAME for tracking the change?
>=20
> 	Thanks,
> 	Paul
>=20
> > Cheers,
> > Charles
> >
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Paul Kyzivat
> >> Sent: Tuesday, November 01, 2011 2:06 PM
> >> To: siprec@ietf.org
> >> Subject: Re: [siprec] FW: New Version Notification
> > fordraft-eckel-siprec-rtp-rec-03.txt
> >>
> >> Charles,
> >>
> >> While reading this I got wondering if we need more guidance on the
use
> >> of CNAME. (As referenced in section 5.) Do we need guidance on
mapping
> >> of CNAME to participants?
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >> On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
> >>> FYI, I have submitted the updated draft and it is available
through
> > the SIPREC documents page:
> >>>
> >
http://proxy2974.my-addr.net/myaddrproxy.php/https/datatracker.ietf.org/
> > wg/siprec/
> >>>
> >>> It contains editorial changes as well as additional text
describing
> > the handling of RTCP packets by
> >> the SRC and UAs per the recent SIPREC list discussion.
> >>>
> >>> Cheers,
> >>> Charles
> >>>
> >>> -----Original Message-----
> >>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >>> Sent: Monday, October 31, 2011 10:53 AM
> >>> To: Charles Eckel (eckelcu)
> >>> Cc: Charles Eckel (eckelcu)
> >>> Subject: New Version Notification for
> > draft-eckel-siprec-rtp-rec-03.txt
> >>>
> >>> A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been
> > successfully submitted by Charles
> >> Eckel and posted to the IETF repository.
> >>>
> >>> Filename:	 draft-eckel-siprec-rtp-rec
> >>> Revision:	 03
> >>> Title:		 Real-time Transport Protocol (RTP)
> > Recommendations for SIPREC
> >>> Creation date:	 2011-10-31
> >>> WG ID:		 Individual Submission
> >>> Number of pages: 13
> >>>
> >>> Abstract:
> >>>      This document provides recommendations and guidelines for RTP
> > and
> >>>      RTCP in the context of SIPREC.  This document exists as a
> > standalone
> >>>      document to facilitate discussion of the RTP recommendations,
> > and it
> >>>      is anticipated that portions of this document will be
> > incorporated
> >>>      into [I-D.ietf-siprec-protocol] rather than this document
itself
> >>>      being adopted as a working group document.
> >>>
> >>>
> >>>
> >>>
> >>> The IETF Secretariat
> >>> _______________________________________________
> >>> 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
> >


From pkyzivat@alum.mit.edu  Thu Nov  3 09:01:55 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 479B91F0C81 for <siprec@ietfa.amsl.com>; Thu,  3 Nov 2011 09:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[AWL=-0.103, BAYES_00=-2.599, J_CHICKENPOX_81=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPibUbdawAea for <siprec@ietfa.amsl.com>; Thu,  3 Nov 2011 09:01:54 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by ietfa.amsl.com (Postfix) with ESMTP id 232221F0C7C for <siprec@ietf.org>; Thu,  3 Nov 2011 09:01:53 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta10.westchester.pa.mail.comcast.net with comcast id sfHQ1h00727AodY5Ag1uEn; Thu, 03 Nov 2011 16:01:54 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta19.westchester.pa.mail.comcast.net with comcast id sg1t1h00X0tdiYw3fg1ujC; Thu, 03 Nov 2011 16:01:54 +0000
Message-ID: <4EB2BAF0.2000109@alum.mit.edu>
Date: Thu, 03 Nov 2011 12:01:52 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: siprec@ietf.org
References: <20111031133617.24449.96357.idtracker@ietfa.amsl.com> <BBA98B7742309546A60F3AE3B4E975A72822C3A32F@EMV64-UKRD.domain1.systemhost.net>, <35BCE99A477D6A4986FB2216D8CF2CFD082B8463@XMB-BGL-417.cisco.com> <BBA98B7742309546A60F3AE3B4E975A72822C3A332@EMV64-UKRD.domain1.systemhost.net>, <35BCE99A477D6A4986FB2216D8CF2CFD082B8592@XMB-BGL-417.cisco.com> <67DAF295CD01EB44AE6EA8A51F6ABF0A4069146D47@EMV62-UKRD.domain1.systemhost.net> <387F9047F55E8C42850AD6B3A7A03C6CBDF4@inba-mail01.sonusnet.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6CBDF4@inba-mail01.sonusnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
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: Thu, 03 Nov 2011 16:01:55 -0000

Finlay,

IIUC you are concerned about recording the actual start and stop times 
of call signaling, regardless of whether the media is recorded or not. 
Is that right? But it isn't entirely straightforward to determine when a 
call starts and ends. We have abstracted CS, so that it isn't identical 
to SIP Dialog - it might be a conference, or more complex things.

We do have the associate/dissociate of participants to CS - which is 
distinct from association/dissociate from media streams. So for 
practical purposes, you can assume a CS to start when a participant is 
first associated with it, and to end when the last participant is 
dissociated from it. This is so even if none of the media is ever recorded.

So what is missing?

	Thanks,
	Paul

>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>> Of finlay.fraser@bt.com
>> Sent: Tuesday, November 01, 2011 1:52 PM
>> To: rmohanr@cisco.com; john.2.stafford@bt.com; siprec@ietf.org
>> Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>
>> Ram
>>
>> The only issue I can see is that the voice recorder companies will not
>> be able to do call reconstruction as there will be parts of the call
>> where they have no RS that has an activestream and so will not be
>> informed about these parts of a CS.
>>
>> I agree that in terms of recording this info is not needed as there is
>> no recording associated with it. However any voice recorder that was
>> hoping to use the meta data to provide call records will now not be abl
>> eto do so.
>>
>> Since we are developing th eswitch side of this we are OK with it I just
>> wanted to confirm th eVoice Recorder companies are also happy
>>
>> Finlay
>>
>> ________________________________________
>> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of Ram
>> Mohan R (rmohanr) [rmohanr@cisco.com]
>> Sent: 01 November 2011 06:49
>> To: Stafford,J,John,JRJ3X C; siprec@ietf.org
>> Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>
>> Hi John S
>>
>> Please see inline
>>
>>> -----Original Message-----
>>> From: john.2.stafford@bt.com [mailto:john.2.stafford@bt.com]
>>> Sent: Monday, October 31, 2011 9:59 PM
>>> To: Ram Mohan R (rmohanr); siprec@ietf.org
>>> Subject: RE: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>>
>>> Ram,
>>>
>>> If CS has associate/dissaociated instead of begin/end times, then
>> there
>>> won't be any way of signalling that a CS has ended, only that it is no
>>> longer being recorded.
>>>
>>> Especially as Charles says it was going to be allowed to have a CS
>> with
>>> zero participants.
>>>
>>> Maybe CS needs BOTH associate/dissassociate and begin/end times ?
>>
>> The associate-time here indicates the time a CS was associated with a
>> RS. IOW it is the time the recording of CS is started in that RS.
>> Disassociate time indicate the time the recording of CS was stopped from
>> that RS.  The reason why this attribute was added is to address cases
>> where only parts of CS is recorded(e.g. you record the first few mins of
>> a CS, then stop the recording, then re-start recording of the same CS
>> after some time). In such cases indicating begin/end of CS is not
>> correct as CS has not ended, but RS has ended.  So the WG decided it's
>> better to have associate/disassociate time and have its scope to a RS so
>> that a CS may have multiple associate/disassociate times if need be. For
>> simple cases where the entire CS is recorded, the associate/disassociate
>> times may be mapped to the CS begin/end times assuming recording is
>> started the same moment CS is setup.
>>
>> I agree that with this approach, we are not indicating explicitly
>> indicating when the CS has actually started/ended.
>> From the past discussions, there was no much interest in keeping both of
>> this information. If you think there are enough use-cases where
>> indicating both these will be helpful please bring them, we can discuss
>> further and add begin/end times after getting consensus from WG.
>>
>> Regards,
>> Ram
>>
>>>
>>> Rgds
>>> John Stafford | Solution Architect 1 | BT Global Services | Tel:+44
>>> (0)1932 773504   | E: john.2.stafford@bt.com  |
>>> www.bt.com/globalservices
>>> ________________________________________
>>> From: Ram Mohan R (rmohanr) [rmohanr@cisco.com]
>>> Sent: 31 October 2011 15:46
>>> To: Stafford,J,John,JRJ3X C; siprec@ietf.org
>>> Subject: RE: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>>
>>> John,
>>>
>>> This needs to be changed to associate/disassociate time to be in
>>> consistent with model. We will take care in the next revision.
>>>
>>> Ram
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>> Behalf Of john.2.stafford@bt.com
>>>> Sent: Monday, October 31, 2011 8:09 PM
>>>> To: siprec@ietf.org
>>>> Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>>>
>>>> Partha
>>>>
>>>> sections 6.3, 7.1,and  8 show CS as having Associate Time and
>>>> Dissassociate Time,
>>>> but  examples in section 13 show CS having start-time and end-time.
>>>>
>>>>
>>>> Rgds
>>>> John Stafford | Solution Architect 1 | BT Global Services
>>>>
>>>> ________________________________________
>>>> From: siprec-bounces@ietf.org [siprec-bounces@ietf.org] On Behalf Of
>>>> internet-drafts@ietf.org [internet-drafts@ietf.org]
>>>> Sent: 31 October 2011 13:36
>>>> To: i-d-announce@ietf.org
>>>> Cc: siprec@ietf.org
>>>> Subject: [siprec] I-D Action: draft-ietf-siprec-metadata-05.txt
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories. This draft is a work item of the SIP Recording Working
>>>> Group of the IETF.
>>>>
>>>>          Title           : Session Initiation Protocol (SIP)
>> Recording
>>>> Metadata
>>>>          Author(s)       : Ram Mohan Ravindranath
>>>>                            Parthasarathi Ravindran
>>>>                            Paul Kyzivat
>>>>          Filename        : draft-ietf-siprec-metadata-05.txt
>>>>          Pages           : 45
>>>>          Date            : 2011-10-31
>>>>
>>>>     Session recording is a critical requirement in many
>> communications
>>>>     environments such as call centers and financial trading.  In some
>>> of
>>>>     these environments, all calls must be recorded for regulatory,
>>>>     compliance, and consumer protection reasons.  Recording of a
>>> session
>>>>     is typically performed by sending a copy of a media stream to a
>>>>     recording device.  This document describes the metadata model as
>>>>     viewed by Session Recording Server(SRS) and the Recording
>> metadata
>>>>     format.
>>>>
>>>>
>>>> A URL for this Internet-Draft is:
>>>>
>> http://www.ietf.org/internet-drafts/draft-ietf-siprec-metadata-05.txt
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> This Internet-Draft can be retrieved at:
>>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-siprec-metadata-05.txt
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
>


From andrew.hutton@siemens-enterprise.com  Fri Nov  4 04:23:46 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 842FE21F8C3F; Fri,  4 Nov 2011 04:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6kHBjzMZ1VsF; Fri,  4 Nov 2011 04:23:45 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 7255221F8C34; Fri,  4 Nov 2011 04:23:42 -0700 (PDT)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id B38AB23F041E; Fri,  4 Nov 2011 12:23:40 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 4 Nov 2011 12:23:40 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: IETF AVTCore WG <avt@ietf.org>
Date: Fri, 4 Nov 2011 12:23:39 +0100
Thread-Topic: SIPREC draft relating to RTP
Thread-Index: Acx48cGG5DyouTPCThiVpxSEwYHLVgh7b2bA
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311F809B130@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA0BC11A84A0@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0BC11A84A0@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: [siprec] SIPREC draft relating to RTP
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: Fri, 04 Nov 2011 11:23:46 -0000

Hi AVTCORE,

The SIPREC (SIP Session Recording) WG are still looking for AVT experts who=
 can review draft http://datatracker.ietf.org/doc/draft-eckel-siprec-rtp-re=
c/. The draft provides recommendations and guidelines for RTP/RTCP in the c=
ontext of SIPREC.

If you are an expert and can help please consider reviewing the document an=
d attending the SIPREC session at IETF82 (See http://www.ietf.org/proceedin=
gs/82/agenda/siprec.html).


Regards
Andy (SIPREC co-chair).




> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Elwell, John
> Sent: 22 September 2011 07:35
> To: IETF AVTCore WG
> Cc: siprec@ietf.org
> Subject: [AVTCORE] SIPREC draft relating to RTP
>=20
> AVTCORE members,
>=20
> Please be aware that an updated I-D has been published:
> https://datatracker.ietf.org/doc/draft-eckel-siprec-rtp-rec/
>=20
> This discusses use of RTP in the context of SIPREC, and contains
> candidate normative material for inclusion in the SIPREC protocol
> document.
>=20
> SIPREC is holding a virtual interim meeting on Friday (13.00 GMT/UTC):
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=3DSIPREC_interim
> _part2&iso=3D20110923T13&ah=3D2
>=20
> This draft will be the first agenda item. Slides are available in the
> official place:
> http://www.ietf.org/proceedings/interim/2011/09/19/siprec/proceedings.h
> tml
>=20
> Webex details are available here:
> http://www.ietf.org/mail-archive/web/siprec/current/msg02535.html
>=20
> It would be great to receive feedback on the draft from RTP experts
> and/or participation in Friday's discussions. Apologies for the short
> notice and for the inconvenient time for some of you (we have a number
> of Asian key participants).
>=20
> John (SIPREC co-chair)
>=20
> John Elwell
> Tel: +44 1908 817801 (office and mobile)
> Email: john.elwell@siemens-enterprise.com
> http://www.siemens-enterprise.com/uk/
>=20
> Siemens Enterprise Communications Limited.
> Registered office: Brickhill Street, Willen Lake, Milton Keynes, MK15
> 0DJ.
> Registered No: 5903714, England.
>=20
> Siemens Enterprise Communications Limited is a Trademark Licensee of
> Siemens AG.
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From magnus.westerlund@ericsson.com  Fri Nov  4 05:27:17 2011
Return-Path: <magnus.westerlund@ericsson.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 E40D921F8BCB; Fri,  4 Nov 2011 05:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyUuhayvwVWm; Fri,  4 Nov 2011 05:27:17 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id DD83721F8BC5; Fri,  4 Nov 2011 05:27:16 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-f1-4eb3da239fda
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 0F.1B.13753.32AD3BE4; Fri,  4 Nov 2011 13:27:15 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Fri, 4 Nov 2011 13:27:14 +0100
Message-ID: <4EB3DA1B.7040908@ericsson.com>
Date: Fri, 4 Nov 2011 13:27:07 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
References: <A444A0F8084434499206E78C106220CA0BC11A84A0@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311F809B130@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311F809B130@MCHP058A.global-ad.net>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "siprec@ietf.org" <siprec@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [siprec] [AVTCORE] SIPREC draft relating to RTP
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: Fri, 04 Nov 2011 12:27:18 -0000

On 2011-11-04 12:23, Hutton, Andrew wrote:
> Hi AVTCORE,
> 
> The SIPREC (SIP Session Recording) WG are still looking for AVT
> experts who can review draft
> http://datatracker.ietf.org/doc/draft-eckel-siprec-rtp-rec/. The
> draft provides recommendations and guidelines for RTP/RTCP in the
> context of SIPREC.
> 
> If you are an expert and can help please consider reviewing the
> document and attending the SIPREC session at IETF82 (See
> http://www.ietf.org/proceedings/82/agenda/siprec.html).
> 

WG Participants

Please help SIPREC with this. If you are doing a review, please drop us
AVTCORE chairs an email so we know that they get help.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From andrew.hutton@siemens-enterprise.com  Fri Nov  4 08:07:46 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 28DAA21F8C09 for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 08:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XhCK2rk0WiZs for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 08:07:45 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 639C921F8BF7 for <siprec@ietf.org>; Fri,  4 Nov 2011 08:07:45 -0700 (PDT)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 397DB1EB84E1; Fri,  4 Nov 2011 16:07:42 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 4 Nov 2011 16:07:42 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
Date: Fri, 4 Nov 2011 16:07:40 +0100
Thread-Topic: SIPREC Agenda for IETF82.
Thread-Index: AcybA37n+Nj4RQ+IQ0SP1hLMHUfwjw==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311F809B378@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311F809B378MCHP058Agloba_"
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: [siprec] SIPREC Agenda for IETF82.
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: Fri, 04 Nov 2011 15:07:46 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311F809B378MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

Last chance to comment on the Agenda (see http://www.ietf.org/proceedings/8=
2/agenda/siprec.html)

Leon, Charles, Ram ,  You are listed as presenting let me know if you want =
more time for your presentation and it would be good if we could have some =
slides before you travel.

Could the document editors please make sure open issues are put in to the t=
racker.

Regards
Andy (SIPREC Co-Chair).


--_000_101C6067BEC68246B0C3F6843BCCC1E311F809B378MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri, sans-serif" size=3D"2">
<div>Hi All,</div>
<div>&nbsp;</div>
<div>Last chance to comment on the Agenda (see <a href=3D"http://www.ietf.o=
rg/proceedings/82/agenda/siprec.html"><font color=3D"#0000FF"><u>http://www=
.ietf.org/proceedings/82/agenda/siprec.htm</u></font><font color=3D"#0000FF=
"><u>l</u></font></a>) </div>
<div>&nbsp;</div>
<div>Leon, Charles, Ram ,&nbsp; You are listed as presenting let me know if=
 you want more time for your presentation and it would be good if we could =
have some slides before you travel.</div>
<div>&nbsp;</div>
<div>Could the document editors please make sure open issues are put in to =
the tracker.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Andy (SIPREC Co-Chair).</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_101C6067BEC68246B0C3F6843BCCC1E311F809B378MCHP058Agloba_--

From eckelcu@cisco.com  Fri Nov  4 10:37:04 2011
Return-Path: <eckelcu@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 2E5D921F8AEE for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 10:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.323
X-Spam-Level: 
X-Spam-Status: No, score=-6.323 tagged_above=-999 required=5 tests=[AWL=0.276,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+eiVL8z4bCq for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 10:37:02 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id A5D4721F8ADE for <siprec@ietf.org>; Fri,  4 Nov 2011 10:37:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=5623; q=dns/txt; s=iport; t=1320428222; x=1321637822; h=mime-version:content-transfer-encoding:subject:date: message-id:references:from:to:cc; bh=i37o/aA6KcMAFH+9Yc9ID6wIwSDlmrO560sbPsU8pBk=; b=KGkCAZwJwosYkUSSRYjxuXDvipW78+bA84rMkr5KTLBLBqUejKbr7e+0 HQ1AbTutfGi4LBli02DbszFIT6v26RV8XPSddpgX/VXfjWS5tFoHKhB64 clnYz4BZi+Chqyfl+NmzipnRKIBFBmYVQRHhJfBr2BMNHPP/o5xUrxP6J I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMAAGwitE6rRDoI/2dsb2JhbAAqGg6aAo5TgSCBBYFyAQEBAwEBAQEPAR0KNAQFAgwEAgEIDgMEAQEBCgYXAQYBJh8IAQgBAQQTCBqHYAgjlwEBnlSISGMEiAqRTIt1Vw
X-IronPort-AV: E=Sophos;i="4.69,456,1315180800"; d="scan'208";a="12390481"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 04 Nov 2011 17:37:02 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA4Hb2WI006721; Fri, 4 Nov 2011 17:37:02 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Nov 2011 10:37:02 -0700
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: Fri, 4 Nov 2011 10:37:01 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B3EA@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
Thread-Index: AcyZhLx1A42GTEvSTFKP9H82bYNeLQAP8jdwAFS3dFA=
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com> <4EB05F4D.5080600@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com> <4EB17D8C.1050307@alum.mit.edu> 
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>
X-OriginalArrivalTime: 04 Nov 2011 17:37:02.0375 (UTC) FILETIME=[5CB46B70:01CC9B18]
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
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: Fri, 04 Nov 2011 17:37:04 -0000

I've been churning on this a bit more. As it stands,
draft-eckel-siprec-rtp-rec does not discuss any relationship or mapping
between RTP/RTCP elements and the SIPREC metadata. It uses the term
participant, but that it is as close it gets. I think such a mapping is
needed, but that this draft is not the appropriate place for it. Are
there other opinions?

Cheers,
Charles=20

> -----Original Message-----
> From: Charles Eckel (eckelcu)
> Sent: Wednesday, November 02, 2011 6:09 PM
> To: 'Paul Kyzivat'
> Cc: siprec@ietf.org
> Subject: RE: [siprec] FW: New Version Notification
fordraft-eckel-siprec-rtp-rec-03.txt
>=20
> I think the CNAME would be useful for identifying the participant, in
cases where the media packets
> from the participant make it to the SRS.
> I think the SSRC would be useful for identifying a stream from a
participant, in cases where the media
> packets from the participant make it to the SRS directly, or are
incorporated into a mixed stream that
> ultimately make it to the SRS. In the second case, the SSRC from the
stream sent by the participant to
> the SRC will be included as a CSRC in the mixed stream sent by the SRC
to the SRS.
> So I think both are useful, and the cases and ways in which they are
useful varies depending on the
> functionality of the SRC.
>=20
> Cheers,
> Charles
>=20
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> > Sent: Wednesday, November 02, 2011 10:28 AM
> > To: Charles Eckel (eckelcu)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] FW: New Version Notification
fordraft-eckel-siprec-rtp-rec-03.txt
> >
> > On 11/2/11 12:59 PM, Charles Eckel (eckelcu) wrote:
> > > Hi Paul,
> > >
> > > We certainly could. In general, you would have one CNAME value per
> > > participant. I suppose there may be cases in which a participant
would
> > > use multiple CNAMEs despite the fact it is not recommended to do
so.
> > > Including the CNAME in the participant info is a good thing. I do
not
> > > know if we need to plan to support multiple CNAMEs per
participant. Is
> > > that your concern?
> >
> > This may just be my ignorance of how SSRC and CNAME are supposed to
be
> > used. I understand that SSRC may change due to collision, and that
then
> > CNAME is supposed to correlate the stream before/after the change. I
> > also gather that CNAME, rather than SSRC, is supposed to be used to
> > correlate related streams, like audio and video from same source.
> >
> > Does that mean that we should reference CNAME in metadata, rather,
or in
> > addition, to SSRC? Or if we update metadata when SSRC changes does
that
> > eliminate CNAME for tracking the change?
> >
> > 	Thanks,
> > 	Paul
> >
> > > Cheers,
> > > Charles
> > >
> > >> -----Original Message-----
> > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Paul Kyzivat
> > >> Sent: Tuesday, November 01, 2011 2:06 PM
> > >> To: siprec@ietf.org
> > >> Subject: Re: [siprec] FW: New Version Notification
> > > fordraft-eckel-siprec-rtp-rec-03.txt
> > >>
> > >> Charles,
> > >>
> > >> While reading this I got wondering if we need more guidance on
the use
> > >> of CNAME. (As referenced in section 5.) Do we need guidance on
mapping
> > >> of CNAME to participants?
> > >>
> > >> 	Thanks,
> > >> 	Paul
> > >>
> > >> On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
> > >>> FYI, I have submitted the updated draft and it is available
through
> > > the SIPREC documents page:
> > >>>
> > >
http://proxy2974.my-addr.net/myaddrproxy.php/https/datatracker.ietf.org/
> > > wg/siprec/
> > >>>
> > >>> It contains editorial changes as well as additional text
describing
> > > the handling of RTCP packets by
> > >> the SRC and UAs per the recent SIPREC list discussion.
> > >>>
> > >>> Cheers,
> > >>> Charles
> > >>>
> > >>> -----Original Message-----
> > >>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > >>> Sent: Monday, October 31, 2011 10:53 AM
> > >>> To: Charles Eckel (eckelcu)
> > >>> Cc: Charles Eckel (eckelcu)
> > >>> Subject: New Version Notification for
> > > draft-eckel-siprec-rtp-rec-03.txt
> > >>>
> > >>> A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been
> > > successfully submitted by Charles
> > >> Eckel and posted to the IETF repository.
> > >>>
> > >>> Filename:	 draft-eckel-siprec-rtp-rec
> > >>> Revision:	 03
> > >>> Title:		 Real-time Transport Protocol (RTP)
> > > Recommendations for SIPREC
> > >>> Creation date:	 2011-10-31
> > >>> WG ID:		 Individual Submission
> > >>> Number of pages: 13
> > >>>
> > >>> Abstract:
> > >>>      This document provides recommendations and guidelines for
RTP
> > > and
> > >>>      RTCP in the context of SIPREC.  This document exists as a
> > > standalone
> > >>>      document to facilitate discussion of the RTP
recommendations,
> > > and it
> > >>>      is anticipated that portions of this document will be
> > > incorporated
> > >>>      into [I-D.ietf-siprec-protocol] rather than this document
itself
> > >>>      being adopted as a working group document.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> The IETF Secretariat
> > >>> _______________________________________________
> > >>> 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
> > >


From pravindran@sonusnet.com  Fri Nov  4 11:12:03 2011
Return-Path: <pravindran@sonusnet.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 A502221F86A0 for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 11:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level: 
X-Spam-Status: No, score=-2.345 tagged_above=-999 required=5 tests=[AWL=-0.346, BAYES_00=-2.599, J_CHICKENPOX_14=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q5JLY9DShq+A for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 11:12:02 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1F521F8888 for <siprec@ietf.org>; Fri,  4 Nov 2011 11:12:02 -0700 (PDT)
Received: from sonusmail07.sonusnet.com (sonusmail07.sonusnet.com [10.128.32.157]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pA4ICZO2007724;  Fri, 4 Nov 2011 14:12:35 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail07.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Nov 2011 14:11:58 -0400
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Nov 2011 23:42:04 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Fri, 4 Nov 2011 23:42:03 +0530
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
Thread-Index: AcyZhLx1fWWlm1r05kS/cKtir1TIkgAP8jdwAFS3dFAAATQmAA==
Date: Fri, 4 Nov 2011 18:12:02 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6CD88D@inba-mail01.sonusnet.com>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com> <4EB05F4D.5080600@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com> <4EB17D8C.1050307@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B3EA@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B3EA@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 04 Nov 2011 18:12:04.0409 (UTC) FILETIME=[419D5A90:01CC9B1D]
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] FW: New Version Notification	fordraft-eckel-siprec-rtp-rec-03.txt
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: Fri, 04 Nov 2011 18:12:03 -0000

Hi Charles,

SIPREC metadata is related to RTP/RTCP through SDP. Lot of media related me=
tadata is possible to be conveyed through SDP and the infrastructure is reu=
sed for extensibility. In fact, I have mentioned like a=3Dssrc parameter fo=
r representing SSRC value in SDP. So in case there is a need for extension =
in SDP, let us discuss here to understand whether it is SIPREC specific or =
generic enough to discuss in MMUSIC.

Also, I'm not very sure whether CNAME and participant name-id are same in t=
he all scenario, particularly in case of RTP translator and mixer. If so, I=
 would have attempted to avoid the duplicate participant information in Met=
adata XML.

Thanks
Partha

>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>Of Charles Eckel (eckelcu)
>Sent: Friday, November 04, 2011 11:07 PM
>To: Paul Kyzivat
>Cc: siprec@ietf.org
>Subject: Re: [siprec] FW: New Version Notification fordraft-eckel-
>siprec-rtp-rec-03.txt
>
>I've been churning on this a bit more. As it stands,
>draft-eckel-siprec-rtp-rec does not discuss any relationship or mapping
>between RTP/RTCP elements and the SIPREC metadata. It uses the term
>participant, but that it is as close it gets. I think such a mapping is
>needed, but that this draft is not the appropriate place for it. Are
>there other opinions?
>
>Cheers,
>Charles
>
>> -----Original Message-----
>> From: Charles Eckel (eckelcu)
>> Sent: Wednesday, November 02, 2011 6:09 PM
>> To: 'Paul Kyzivat'
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] FW: New Version Notification
>fordraft-eckel-siprec-rtp-rec-03.txt
>>
>> I think the CNAME would be useful for identifying the participant, in
>cases where the media packets
>> from the participant make it to the SRS.
>> I think the SSRC would be useful for identifying a stream from a
>participant, in cases where the media
>> packets from the participant make it to the SRS directly, or are
>incorporated into a mixed stream that
>> ultimately make it to the SRS. In the second case, the SSRC from the
>stream sent by the participant to
>> the SRC will be included as a CSRC in the mixed stream sent by the SRC
>to the SRS.
>> So I think both are useful, and the cases and ways in which they are
>useful varies depending on the
>> functionality of the SRC.
>>
>> Cheers,
>> Charles
>>
>> > -----Original Message-----
>> > From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>> > Sent: Wednesday, November 02, 2011 10:28 AM
>> > To: Charles Eckel (eckelcu)
>> > Cc: siprec@ietf.org
>> > Subject: Re: [siprec] FW: New Version Notification
>fordraft-eckel-siprec-rtp-rec-03.txt
>> >
>> > On 11/2/11 12:59 PM, Charles Eckel (eckelcu) wrote:
>> > > Hi Paul,
>> > >
>> > > We certainly could. In general, you would have one CNAME value per
>> > > participant. I suppose there may be cases in which a participant
>would
>> > > use multiple CNAMEs despite the fact it is not recommended to do
>so.
>> > > Including the CNAME in the participant info is a good thing. I do
>not
>> > > know if we need to plan to support multiple CNAMEs per
>participant. Is
>> > > that your concern?
>> >
>> > This may just be my ignorance of how SSRC and CNAME are supposed to
>be
>> > used. I understand that SSRC may change due to collision, and that
>then
>> > CNAME is supposed to correlate the stream before/after the change. I
>> > also gather that CNAME, rather than SSRC, is supposed to be used to
>> > correlate related streams, like audio and video from same source.
>> >
>> > Does that mean that we should reference CNAME in metadata, rather,
>or in
>> > addition, to SSRC? Or if we update metadata when SSRC changes does
>that
>> > eliminate CNAME for tracking the change?
>> >
>> > 	Thanks,
>> > 	Paul
>> >
>> > > Cheers,
>> > > Charles
>> > >
>> > >> -----Original Message-----
>> > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> > > Behalf Of Paul Kyzivat
>> > >> Sent: Tuesday, November 01, 2011 2:06 PM
>> > >> To: siprec@ietf.org
>> > >> Subject: Re: [siprec] FW: New Version Notification
>> > > fordraft-eckel-siprec-rtp-rec-03.txt
>> > >>
>> > >> Charles,
>> > >>
>> > >> While reading this I got wondering if we need more guidance on
>the use
>> > >> of CNAME. (As referenced in section 5.) Do we need guidance on
>mapping
>> > >> of CNAME to participants?
>> > >>
>> > >> 	Thanks,
>> > >> 	Paul
>> > >>
>> > >> On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
>> > >>> FYI, I have submitted the updated draft and it is available
>through
>> > > the SIPREC documents page:
>> > >>>
>> > >
>http://proxy2974.my-addr.net/myaddrproxy.php/https/datatracker.ietf.org/
>> > > wg/siprec/
>> > >>>
>> > >>> It contains editorial changes as well as additional text
>describing
>> > > the handling of RTCP packets by
>> > >> the SRC and UAs per the recent SIPREC list discussion.
>> > >>>
>> > >>> Cheers,
>> > >>> Charles
>> > >>>
>> > >>> -----Original Message-----
>> > >>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> > >>> Sent: Monday, October 31, 2011 10:53 AM
>> > >>> To: Charles Eckel (eckelcu)
>> > >>> Cc: Charles Eckel (eckelcu)
>> > >>> Subject: New Version Notification for
>> > > draft-eckel-siprec-rtp-rec-03.txt
>> > >>>
>> > >>> A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been
>> > > successfully submitted by Charles
>> > >> Eckel and posted to the IETF repository.
>> > >>>
>> > >>> Filename:	 draft-eckel-siprec-rtp-rec
>> > >>> Revision:	 03
>> > >>> Title:		 Real-time Transport Protocol (RTP)
>> > > Recommendations for SIPREC
>> > >>> Creation date:	 2011-10-31
>> > >>> WG ID:		 Individual Submission
>> > >>> Number of pages: 13
>> > >>>
>> > >>> Abstract:
>> > >>>      This document provides recommendations and guidelines for
>RTP
>> > > and
>> > >>>      RTCP in the context of SIPREC.  This document exists as a
>> > > standalone
>> > >>>      document to facilitate discussion of the RTP
>recommendations,
>> > > and it
>> > >>>      is anticipated that portions of this document will be
>> > > incorporated
>> > >>>      into [I-D.ietf-siprec-protocol] rather than this document
>itself
>> > >>>      being adopted as a working group document.
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>> The IETF Secretariat
>> > >>> _______________________________________________
>> > >>> 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

From pkyzivat@alum.mit.edu  Fri Nov  4 15:13:22 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 478E721F8AD3 for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 15:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level: 
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, J_CHICKENPOX_14=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Km3zs5xtk6Hb for <siprec@ietfa.amsl.com>; Fri,  4 Nov 2011 15:13:21 -0700 (PDT)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by ietfa.amsl.com (Postfix) with ESMTP id 383EC21F8A80 for <siprec@ietf.org>; Fri,  4 Nov 2011 15:13:21 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta06.westchester.pa.mail.comcast.net with comcast id t7qR1h0031uE5Es56ADLbU; Fri, 04 Nov 2011 22:13:20 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta16.westchester.pa.mail.comcast.net with comcast id tADJ1h00e07duvL3cADKVQ; Fri, 04 Nov 2011 22:13:20 +0000
Message-ID: <4EB4637D.3050808@alum.mit.edu>
Date: Fri, 04 Nov 2011 18:13:17 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Ravindran Parthasarathi <pravindran@sonusnet.com>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com> <4EB05F4D.5080600@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com> <4EB17D8C.1050307@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B3EA@xmb-sjc-234.amer.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6CD88D@inba-mail01.sonusnet.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6CD88D@inba-mail01.sonusnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] FW: New Version Notification fordraft-eckel-siprec-rtp-rec-03.txt
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: Fri, 04 Nov 2011 22:13:22 -0000

On 11/4/11 2:12 PM, Ravindran Parthasarathi wrote:
> Hi Charles,
>
> SIPREC metadata is related to RTP/RTCP through SDP. Lot of media related metadata is possible to be conveyed through SDP and the infrastructure is reused for extensibility. In fact, I have mentioned like a=ssrc parameter for representing SSRC value in SDP. So in case there is a need for extension in SDP, let us discuss here to understand whether it is SIPREC specific or generic enough to discuss in MMUSIC.
>
> Also, I'm not very sure whether CNAME and participant name-id are same in the all scenario, particularly in case of RTP translator and mixer. If so, I would have attempted to avoid the duplicate participant information in Metadata XML.

Check out RFC 6222, for latest guidance on assigning CNAMEs. This pretty 
much guarantees that CNAMEs are distinct from the participant name-id. I 
think that also means that a single participant may have multiple CNAMEs.

	Thanks,
	Paul

> Thanks
> Partha
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>> Of Charles Eckel (eckelcu)
>> Sent: Friday, November 04, 2011 11:07 PM
>> To: Paul Kyzivat
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] FW: New Version Notification fordraft-eckel-
>> siprec-rtp-rec-03.txt
>>
>> I've been churning on this a bit more. As it stands,
>> draft-eckel-siprec-rtp-rec does not discuss any relationship or mapping
>> between RTP/RTCP elements and the SIPREC metadata. It uses the term
>> participant, but that it is as close it gets. I think such a mapping is
>> needed, but that this draft is not the appropriate place for it. Are
>> there other opinions?
>>
>> Cheers,
>> Charles
>>
>>> -----Original Message-----
>>> From: Charles Eckel (eckelcu)
>>> Sent: Wednesday, November 02, 2011 6:09 PM
>>> To: 'Paul Kyzivat'
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] FW: New Version Notification
>> fordraft-eckel-siprec-rtp-rec-03.txt
>>>
>>> I think the CNAME would be useful for identifying the participant, in
>> cases where the media packets
>>> from the participant make it to the SRS.
>>> I think the SSRC would be useful for identifying a stream from a
>> participant, in cases where the media
>>> packets from the participant make it to the SRS directly, or are
>> incorporated into a mixed stream that
>>> ultimately make it to the SRS. In the second case, the SSRC from the
>> stream sent by the participant to
>>> the SRC will be included as a CSRC in the mixed stream sent by the SRC
>> to the SRS.
>>> So I think both are useful, and the cases and ways in which they are
>> useful varies depending on the
>>> functionality of the SRC.
>>>
>>> Cheers,
>>> Charles
>>>
>>>> -----Original Message-----
>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>>> Sent: Wednesday, November 02, 2011 10:28 AM
>>>> To: Charles Eckel (eckelcu)
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] FW: New Version Notification
>> fordraft-eckel-siprec-rtp-rec-03.txt
>>>>
>>>> On 11/2/11 12:59 PM, Charles Eckel (eckelcu) wrote:
>>>>> Hi Paul,
>>>>>
>>>>> We certainly could. In general, you would have one CNAME value per
>>>>> participant. I suppose there may be cases in which a participant
>> would
>>>>> use multiple CNAMEs despite the fact it is not recommended to do
>> so.
>>>>> Including the CNAME in the participant info is a good thing. I do
>> not
>>>>> know if we need to plan to support multiple CNAMEs per
>> participant. Is
>>>>> that your concern?
>>>>
>>>> This may just be my ignorance of how SSRC and CNAME are supposed to
>> be
>>>> used. I understand that SSRC may change due to collision, and that
>> then
>>>> CNAME is supposed to correlate the stream before/after the change. I
>>>> also gather that CNAME, rather than SSRC, is supposed to be used to
>>>> correlate related streams, like audio and video from same source.
>>>>
>>>> Does that mean that we should reference CNAME in metadata, rather,
>> or in
>>>> addition, to SSRC? Or if we update metadata when SSRC changes does
>> that
>>>> eliminate CNAME for tracking the change?
>>>>
>>>> 	Thanks,
>>>> 	Paul
>>>>
>>>>> Cheers,
>>>>> Charles
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>> Behalf Of Paul Kyzivat
>>>>>> Sent: Tuesday, November 01, 2011 2:06 PM
>>>>>> To: siprec@ietf.org
>>>>>> Subject: Re: [siprec] FW: New Version Notification
>>>>> fordraft-eckel-siprec-rtp-rec-03.txt
>>>>>>
>>>>>> Charles,
>>>>>>
>>>>>> While reading this I got wondering if we need more guidance on
>> the use
>>>>>> of CNAME. (As referenced in section 5.) Do we need guidance on
>> mapping
>>>>>> of CNAME to participants?
>>>>>>
>>>>>> 	Thanks,
>>>>>> 	Paul
>>>>>>
>>>>>> On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
>>>>>>> FYI, I have submitted the updated draft and it is available
>> through
>>>>> the SIPREC documents page:
>>>>>>>
>>>>>
>> http://proxy2974.my-addr.net/myaddrproxy.php/https/datatracker.ietf.org/
>>>>> wg/siprec/
>>>>>>>
>>>>>>> It contains editorial changes as well as additional text
>> describing
>>>>> the handling of RTCP packets by
>>>>>> the SRC and UAs per the recent SIPREC list discussion.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Charles
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>>>>> Sent: Monday, October 31, 2011 10:53 AM
>>>>>>> To: Charles Eckel (eckelcu)
>>>>>>> Cc: Charles Eckel (eckelcu)
>>>>>>> Subject: New Version Notification for
>>>>> draft-eckel-siprec-rtp-rec-03.txt
>>>>>>>
>>>>>>> A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been
>>>>> successfully submitted by Charles
>>>>>> Eckel and posted to the IETF repository.
>>>>>>>
>>>>>>> Filename:	 draft-eckel-siprec-rtp-rec
>>>>>>> Revision:	 03
>>>>>>> Title:		 Real-time Transport Protocol (RTP)
>>>>> Recommendations for SIPREC
>>>>>>> Creation date:	 2011-10-31
>>>>>>> WG ID:		 Individual Submission
>>>>>>> Number of pages: 13
>>>>>>>
>>>>>>> Abstract:
>>>>>>>       This document provides recommendations and guidelines for
>> RTP
>>>>> and
>>>>>>>       RTCP in the context of SIPREC.  This document exists as a
>>>>> standalone
>>>>>>>       document to facilitate discussion of the RTP
>> recommendations,
>>>>> and it
>>>>>>>       is anticipated that portions of this document will be
>>>>> incorporated
>>>>>>>       into [I-D.ietf-siprec-protocol] rather than this document
>> itself
>>>>>>>       being adopted as a working group document.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The IETF Secretariat
>>>>>>> _______________________________________________
>>>>>>> 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
>


From pkyzivat@alum.mit.edu  Fri Nov 11 15:14:02 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 14BEC21F85AA for <siprec@ietfa.amsl.com>; Fri, 11 Nov 2011 15:14:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktliNC2-iDp2 for <siprec@ietfa.amsl.com>; Fri, 11 Nov 2011 15:14:01 -0800 (PST)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id 3887821F852E for <siprec@ietf.org>; Fri, 11 Nov 2011 15:14:01 -0800 (PST)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by QMTA11.westchester.pa.mail.comcast.net with comcast id vzB61h0070SCNGk5BzE14Z; Fri, 11 Nov 2011 23:14:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta09.westchester.pa.mail.comcast.net with comcast id vzE01h01P07duvL3VzE1Gy; Fri, 11 Nov 2011 23:14:01 +0000
Message-ID: <4EBDAC36.1090007@alum.mit.edu>
Date: Fri, 11 Nov 2011 18:13:58 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "siprec@ietf.org" <siprec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] draft-ietf-siprec-protocol-02
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: Fri, 11 Nov 2011 23:14:02 -0000

I was just reviewing draft-ietf-siprec-protocol-02, and the following 
are things I noted along the way:

Section 4.2:

    Metadata is transported in the body of INVITE or UPDATE messages.
    Certain metadata, such as the attributes of the recorded media stream
    are located in the SDP of the recording session.

I think we should point out that this is typically going to require 
multipart support. Perhaps:

    Metadata is transported within the body of INVITE or UPDATE messages
    for the recording session. Most metadata is located in a siprec
    specific body part, but certain metadata, such as the attributes
    of the recorded media stream, are located in the SDP offer or answer.
    In many cases this means a message will contain both a siprec
    specific part as well as an SDP part, contained within a body of
    type multipart/mixed.

Figure 3:

Shouldn't the first message be:
     (1) INVITE (metadata snapshot(1) + SDP offer)

Section 5.1:

    An SRS uses the presence of the 'src' feature
    tag in dialog creating and modifying requests and responses to
    confirm that the dialog being created is for the purpose of a
    Recording Session. ... Other SIP Recording extensions and behaviors
    can be triggered by the presence of this feature tag.

This is an abuse of the feature tag mechanism. The tag indicates a 
*capability*. It shouldn't be used to infer intent. OTOH, I think it 
would be ok to interpret the presence of metadata in the message as an 
indication that request is intended for the purpose of establishing an RS.

Also, the option tag should be "sip.src". (Indicated as "+sip.src" in 
the Contact header.)

    Since SIP Caller Preferences extensions are optional to implement for
    routing proxies, there is no guarantee that a recording session will
    be routed to an SRC or SRS.  A new options tag is introduced:
    "siprec".  As per [RFC3261], only an SRC or an SRS can accept this
    option tag in a recording session.  An SRC SHOULD include the
    "siprec" option tag in the Require header when initiating a Recording
    Session so that other types of user agents can simply reject the
    INVITE request with a 420 Bad Extension.

This doesn't distinguish between SRC and SRS behavior. It might be 
better to have two option tags: src and srs.

If that was done, its not evident that the feature tags add anything. It 
would be simpler to have the INVITE contain:

	Supported: src
	Require: srs

(An RS initiated by the SRS would invert those.)

6.1

Given the work that is being done in other WGs on multiplexing media 
streams on RTP streams, I wonder if we ought to revisit our decision to 
always map a CS media stream uniquely to an RS m-line, and instead 
consider allowing multiplexing. (But doing this would require more 
description in metadata and/or SDP.)

6.1.1

    ... To
    add a recorded stream to the recording session, the SRC sends a new
    SDP offer by adding a new media stream description or by reusing an
    old media stream which had been previously disabled, according to the
    procedures in [RFC3264].

Its not necessary to disable one before reusing it. You can repurpose a 
stream in one step. How about:

    ... To
    add a recorded stream to the recording session, the SRC sends a new
    SDP offer by adding a new media stream description or by reusing an
    media stream which had been previously disabled or that is no
    longer needed, according to the procedures in [RFC3264].

Section 9:

    ... In order
    not to lose the NAT bindings for the RTP/RTCP ports opened for the
    recorded streams, the SRC and SRS SHOULD follow the recommendations
    provided in [RFC6263] to maintain the NAT bindings.

The recommendation involves also enabling multiplexing of rtcp and rtp. 
If that is what we are going to do it would be worth calling that out, 
and showing it in the examples.

But that document also only applies when ICE isn't used.

Maybe this should all be addressed as part of draft-eckel-siprec-rtp-rec.

Section 10.1.1

    A new SDP attribute "recordpref" is introduced.  The SDP attribute
    appears at the media level and can appear in an SDP offer or answer.
    The recording indication applies to the specified media stream only.
    The following is the ABNF of the recordpref attribute:

IMO this attribute should be permitted at either session or media level, 
with session level establishing a default for all media. (Thus only one 
session level attribute need be supplied to request that all media 
should/shouldn't be recorded.)

Section 10.2.1

The comments above for "recordpref" also apply to "record".

    The recording attribute is a declaration by an endpoint in the CS to
    indicate whether recording is taking place.

This seems wrong. The indication is from the SRC toward and endpoint. 
How about:

    The recording attribute is a declaration by the SRC to an endpoint
    in the CS to indicate whether recording is taking place.  For
    example, if a UA (A)

	Thanks,
	Paul

From andrew.hutton@siemens-enterprise.com  Sat Nov 12 06:33:53 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 7A58D21F85B8 for <siprec@ietfa.amsl.com>; Sat, 12 Nov 2011 06:33:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j48XzgF7BPhV for <siprec@ietfa.amsl.com>; Sat, 12 Nov 2011 06:33:53 -0800 (PST)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id B903621F8538 for <siprec@ietf.org>; Sat, 12 Nov 2011 06:33:52 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 1AA8F23F04B0 for <siprec@ietf.org>; Sat, 12 Nov 2011 15:33:49 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Sat, 12 Nov 2011 15:33:49 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Sat, 12 Nov 2011 15:33:48 +0100
Thread-Topic: Comments on draft-ietf-siprec-protocol-02
Thread-Index: AcyhIQ1B++XNHyp1SEuLuRIgJiHwtg==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAAB8B91@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Comments on draft-ietf-siprec-protocol-02
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: Sat, 12 Nov 2011 14:33:53 -0000

Some comments on this draft.

1. The introduction & abstract states "The Session
   Recording Protocol specifies the use of SIP, SDP, and RTP to
   establish a Recording Session (RS) from the Session Recording Client
   (SRC), which is on the path of the CS, to a Session Recording Server
   (SRS) at the recording device."

This is incorrect as the RS can be established in both directions so change=
 the "from" to "between" and the "to a.." to "and".

2. Section 5.1 states "Participants information is not recorded in the From=
 or To
header; they are included in the m
etadata".

I don't think this adds anything and I think should be removed.

3. Section 5.1 "SRC Procedures" 2nd Para. "An SRS uses the presence of the =
'src'..." . This paragraph details what the SRS makes use of the feature ta=
g and therefore does not belong in this section but in the SRS section. We =
also need a discussion as whether this is valid use of the feature tag by t=
he SRS and the SRC.

4. Section 5.1 3rd paragraph. Maybe we should change "when initiating a Rec=
ording Session" to "when generating an INVITE to initiate a recording sessi=
on". To make it clear that the "siprec" option tag is included in the initi=
al invite.

5. Section 5.2 2nd Para. I think the sentence "Other SIP Recording extensio=
ns and behaviors can be triggered by the presence of this feature tag" shou=
ld be removed as it does not add anything.

6. Section 5.2 last para. "An SRS SHOULD include the "siprec" option tag in=
 the Require header as per [RFC3261] when initiating a Recording Session so=
 that other types of user agents can simply reject the INVITE request with =
a 420 Bad Extension".  The "other types of users agents" is too vague and n=
ot strictly correct as a SRC is another type of UA and would not reject the=
 INVITE. Probably should say that "UA's that don't support the Session Reco=
rding Protocol extensions will reject the INVITE...".

7. Section 6.1 2nd Para. "Note that a recorded stream is different than a C=
S stream;". Not sure what this note is trying to say and should either be r=
emoved or expanded with more explanation.

Will provide comments on section 8 very soon assuming I have some.

Regards
Andy (as an individual).





From leon.portman@gmail.com  Sun Nov 13 17:42:52 2011
Return-Path: <leon.portman@gmail.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 C81C111E80D7 for <siprec@ietfa.amsl.com>; Sun, 13 Nov 2011 17:42:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IF79zh2nM35R for <siprec@ietfa.amsl.com>; Sun, 13 Nov 2011 17:42:51 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id AF3FD11E8073 for <siprec@ietf.org>; Sun, 13 Nov 2011 17:42:51 -0800 (PST)
Received: by yenq4 with SMTP id q4so2788333yen.31 for <siprec@ietf.org>; Sun, 13 Nov 2011 17:42:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=af5vrSqcZepl6yJ2TDBNI4L5QyyN6zazcxBqHNwDvVg=; b=xKFdV5ST28mP3Znpf7gzzoMCf9aByUrGx27fTyvWdfSjZlTUfLfJzlmorm4k2C3asD Jy+XEq1o+UJLI2qLkdEDXL5sxevQ8sgiMiqVP3A7caVKnH6vC7kadmj+nHTzKn3eozQI CZYZ8dVzWy5uO0oGwqG/c5DlWH0NeQeIr5gQg=
Received: by 10.236.184.35 with SMTP id r23mr11410320yhm.11.1321234967051; Sun, 13 Nov 2011 17:42:47 -0800 (PST)
Received: from ?IPv6:2001:df8::16:a570:1138:d4b4:c28c? ([2001:df8:0:16:a570:1138:d4b4:c28c]) by mx.google.com with ESMTPS id r5sm25287121anl.13.2011.11.13.17.42.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 17:42:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <4EBDAC36.1090007@alum.mit.edu>
Date: Sun, 13 Nov 2011 20:42:43 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C51D12EB-40A2-4B84-819D-F7485FD307D5@gmail.com>
References: <4EBDAC36.1090007@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1251.1)
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] draft-ietf-siprec-protocol-02
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: Mon, 14 Nov 2011 01:42:52 -0000

Paul Hi

Thank you for the review. Please see below

Leon

On Nov 11, 2011, at 6:13 PM, Paul Kyzivat wrote:

> I was just reviewing draft-ietf-siprec-protocol-02, and the following =
are things I noted along the way:
>=20
> Section 4.2:
>=20
>   Metadata is transported in the body of INVITE or UPDATE messages.
>   Certain metadata, such as the attributes of the recorded media =
stream
>   are located in the SDP of the recording session.
>=20
> I think we should point out that this is typically going to require =
multipart support. Perhaps:
>=20
>   Metadata is transported within the body of INVITE or UPDATE messages
>   for the recording session. Most metadata is located in a siprec
>   specific body part, but certain metadata, such as the attributes
>   of the recorded media stream, are located in the SDP offer or =
answer.
>   In many cases this means a message will contain both a siprec
>   specific part as well as an SDP part, contained within a body of
>   type multipart/mixed.

[Leon] I agree

>=20
> Figure 3:
>=20
> Shouldn't the first message be:
>    (1) INVITE (metadata snapshot(1) + SDP offer)
>=20
[Leon] Correct ,it is also true for persistent recording use case

> Section 5.1:
>=20
>   An SRS uses the presence of the 'src' feature
>   tag in dialog creating and modifying requests and responses to
>   confirm that the dialog being created is for the purpose of a
>   Recording Session. ... Other SIP Recording extensions and behaviors
>   can be triggered by the presence of this feature tag.
>=20
> This is an abuse of the feature tag mechanism. The tag indicates a =
*capability*. It shouldn't be used to infer intent. OTOH, I think it =
would be ok to interpret the presence of metadata in the message as an =
indication that request is intended for the purpose of establishing an =
RS.
>=20
> Also, the option tag should be "sip.src". (Indicated as "+sip.src" in =
the Contact header.)
>=20
[Leon] I will add it to open items to the IETF 82 presentation. The main =
question is if we always have metadata in RS INVITE. I think we always =
should have also for persistent use case as well, even it only describes =
preallocated media sessions and not specific CS.

>   Since SIP Caller Preferences extensions are optional to implement =
for
>   routing proxies, there is no guarantee that a recording session will
>   be routed to an SRC or SRS.  A new options tag is introduced:
>   "siprec".  As per [RFC3261], only an SRC or an SRS can accept this
>   option tag in a recording session.  An SRC SHOULD include the
>   "siprec" option tag in the Require header when initiating a =
Recording
>   Session so that other types of user agents can simply reject the
>   INVITE request with a 420 Bad Extension.
>=20
> This doesn't distinguish between SRC and SRS behavior. It might be =
better to have two option tags: src and srs.
>=20
> If that was done, its not evident that the feature tags add anything. =
It would be simpler to have the INVITE contain:
>=20
> 	Supported: src
> 	Require: srs
>=20
> (An RS initiated by the SRS would invert those.)

[Leon] Will add as an open item to the presentation
>=20
> 6.1
>=20
> Given the work that is being done in other WGs on multiplexing media =
streams on RTP streams, I wonder if we ought to revisit our decision to =
always map a CS media stream uniquely to an RS m-line, and instead =
consider allowing multiplexing. (But doing this would require more =
description in metadata and/or SDP.)
>=20
[Leon] I believe the decision was not to prevent support for =
multiplexing but just not to require it.
> 6.1.1
>=20
>   ... To
>   add a recorded stream to the recording session, the SRC sends a new
>   SDP offer by adding a new media stream description or by reusing an
>   old media stream which had been previously disabled, according to =
the
>   procedures in [RFC3264].
>=20
> Its not necessary to disable one before reusing it. You can repurpose =
a stream in one step. How about:
>=20
>   ... To
>   add a recorded stream to the recording session, the SRC sends a new
>   SDP offer by adding a new media stream description or by reusing an
>   media stream which had been previously disabled or that is no
>   longer needed, according to the procedures in [RFC3264].
>=20
[Leon] I am ok with that

> Section 9:
>=20
>   ... In order
>   not to lose the NAT bindings for the RTP/RTCP ports opened for the
>   recorded streams, the SRC and SRS SHOULD follow the recommendations
>   provided in [RFC6263] to maintain the NAT bindings.
>=20
> The recommendation involves also enabling multiplexing of rtcp and =
rtp. If that is what we are going to do it would be worth calling that =
out, and showing it in the examples.
>=20
> But that document also only applies when ICE isn't used.
>=20
> Maybe this should all be addressed as part of =
draft-eckel-siprec-rtp-rec.

[Leon] I am ok with that
>=20
> Section 10.1.1
>=20
>   A new SDP attribute "recordpref" is introduced.  The SDP attribute
>   appears at the media level and can appear in an SDP offer or answer.
>   The recording indication applies to the specified media stream only.
>   The following is the ABNF of the recordpref attribute:
>=20
> IMO this attribute should be permitted at either session or media =
level, with session level establishing a default for all media. (Thus =
only one session level attribute need be supplied to request that all =
media should/shouldn't be recorded.)

[Leon] I am ok with that
>=20
> Section 10.2.1
>=20
> The comments above for "recordpref" also apply to "record".
>=20
>   The recording attribute is a declaration by an endpoint in the CS to
>   indicate whether recording is taking place.
>=20
> This seems wrong. The indication is from the SRC toward and endpoint. =
How about:
>=20
>   The recording attribute is a declaration by the SRC to an endpoint
>   in the CS to indicate whether recording is taking place.  For
>   example, if a UA (A)
>=20
[Leon] Agree, we should fix it in the document
> 	Thanks,
> 	Paul
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From leon.portman@gmail.com  Sun Nov 13 17:47:05 2011
Return-Path: <leon.portman@gmail.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 D0B5611E80F7 for <siprec@ietfa.amsl.com>; Sun, 13 Nov 2011 17:47:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhMubzKs9MlG for <siprec@ietfa.amsl.com>; Sun, 13 Nov 2011 17:47:05 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 32E5111E80EE for <siprec@ietf.org>; Sun, 13 Nov 2011 17:47:05 -0800 (PST)
Received: by mail-yx0-f172.google.com with SMTP id q4so2790660yen.31 for <siprec@ietf.org>; Sun, 13 Nov 2011 17:47:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=0chhHAScMvPyekoP56+xASiL9ppbsADEsD/gY2mbVI0=; b=imVR+a763At6VeTNnAfIJfasXQeUaigyxJUwn9/AWbsEB4Nbo5ZBmUmfypMpuSp5Zs kNBkL+VhGG5k3E8sYYXLFjUbX79P5/p5VP0PPMn33e/NykpNYtxjbWYHH3wQpuModzed iSwbgYMmedjieHSXMcIhxjpyl9oHJDlXqWDXM=
Received: by 10.236.170.72 with SMTP id o48mr11281977yhl.43.1321235225036; Sun, 13 Nov 2011 17:47:05 -0800 (PST)
Received: from ?IPv6:2001:df8::16:a570:1138:d4b4:c28c? ([2001:df8:0:16:a570:1138:d4b4:c28c]) by mx.google.com with ESMTPS id i31sm34525903anm.19.2011.11.13.17.47.03 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 17:47:04 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAAB8B91@MCHP058A.global-ad.net>
Date: Sun, 13 Nov 2011 20:47:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <155482E1-8348-4339-8902-84BE06729435@gmail.com>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAAB8B91@MCHP058A.global-ad.net>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comments on draft-ietf-siprec-protocol-02
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: Mon, 14 Nov 2011 01:47:05 -0000

Andy Hi.

Thank you for the comments.

Please see below

Leon

On Nov 12, 2011, at 9:33 AM, Hutton, Andrew wrote:

> Some comments on this draft.
>=20
> 1. The introduction & abstract states "The Session
>   Recording Protocol specifies the use of SIP, SDP, and RTP to
>   establish a Recording Session (RS) from the Session Recording Client
>   (SRC), which is on the path of the CS, to a Session Recording Server
>   (SRS) at the recording device."
>=20
> This is incorrect as the RS can be established in both directions so =
change the "from" to "between" and the "to a.." to "and".
>=20
[Leon] Correct

> 2. Section 5.1 states "Participants information is not recorded in the =
=46rom or To
> header; they are included in the m
> etadata".
>=20
> I don't think this adds anything and I think should be removed.

[Leon] It emphasizes  the point that we should put there SRS anf SRS =
identities however i am ok to remove
>=20
> 3. Section 5.1 "SRC Procedures" 2nd Para. "An SRS uses the presence of =
the 'src'..." . This paragraph details what the SRS makes use of the =
feature tag and therefore does not belong in this section but in the SRS =
section. We also need a discussion as whether this is valid use of the =
feature tag by the SRS and the SRC.

[Leon] i have added it to open items
>=20
> 4. Section 5.1 3rd paragraph. Maybe we should change "when initiating =
a Recording Session" to "when generating an INVITE to initiate a =
recording session". To make it clear that the "siprec" option tag is =
included in the initial invite.
>=20
[Leon] But we also should have for reinvites and updates, correct?

> 5. Section 5.2 2nd Para. I think the sentence "Other SIP Recording =
extensions and behaviors can be triggered by the presence of this =
feature tag" should be removed as it does not add anything.
>=20
[Leon] Ok

> 6. Section 5.2 last para. "An SRS SHOULD include the "siprec" option =
tag in the Require header as per [RFC3261] when initiating a Recording =
Session so that other types of user agents can simply reject the INVITE =
request with a 420 Bad Extension".  The "other types of users agents" is =
too vague and not strictly correct as a SRC is another type of UA and =
would not reject the INVITE. Probably should say that "UA's that don't =
support the Session Recording Protocol extensions will reject the =
INVITE...".
>=20
[Leon] ok

> 7. Section 6.1 2nd Para. "Note that a recorded stream is different =
than a CS stream;". Not sure what this note is trying to say and should =
either be removed or expanded with more explanation.
>=20

[Leon] Ok
> Will provide comments on section 8 very soon assuming I have some.
>=20
> Regards
> Andy (as an individual).
>=20
>=20
>=20
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From rmohanr@cisco.com  Mon Nov 14 00:07:17 2011
Return-Path: <rmohanr@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 842BD11E8269 for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 00:07:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.995
X-Spam-Level: 
X-Spam-Status: No, score=-8.995 tagged_above=-999 required=5 tests=[AWL=1.604,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sT-2dRv6ZlbO for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 00:07:16 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 26A5111E8129 for <siprec@ietf.org>; Mon, 14 Nov 2011 00:07:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=579; q=dns/txt; s=iport; t=1321258036; x=1322467636; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=wh/d7FdrUEIKTM7P91Mk7nin9wJ7Cb6u9l2dpetRN/w=; b=HLUacX6VxQRjW+u7VjF21eD/SSID2sTwGrrXuT/XSZvVgZ5IjIMoFNO5 t9r7zh1Dmsc+gHxuLusZ7QRVeNU8Sthkhsx/yne7Oz/CXqYC3XUQ0wUGt JS8ZNvXm98rGfho5I6XysDyr7rTlPwp8Ju8R+x4kL9nCjo8KLpG7mn2+w M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOvLwE5Io8UT/2dsb2JhbABCqX6BBYF0AQQSAR0KUQEqBhMFB1cBBAsQGp9lgSYBnViGaoIyYwSIDpFkjD0
X-IronPort-AV: E=Sophos;i="4.69,507,1315180800"; d="scan'208";a="121513102"
Received: from bgl-core-4.cisco.com ([72.163.197.19]) by ams-iport-1.cisco.com with ESMTP; 14 Nov 2011 08:07:14 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAE87EXi012994 for <siprec@ietf.org>; Mon, 14 Nov 2011 08:07:14 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 13:37:13 +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: Mon, 14 Nov 2011 13:37:12 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD08651FC1@XMB-BGL-417.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Metadata model: Should ssociate-time/disassociate-time of CS be attributes of association of CS to RS?
Thread-Index: AcyipGoa3YMaL9MeQBKQgqAhea16eg==
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 14 Nov 2011 08:07:13.0940 (UTC) FILETIME=[6AF0BD40:01CCA2A4]
Subject: [siprec] Metadata model: Should ssociate-time/disassociate-time of CS be attributes of association of CS to RS?
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: Mon, 14 Nov 2011 08:07:17 -0000

The current metadata model (ver 05) has following meaning for times of
CS class:-

Associate Time - This optional attribute represents the time a CS
      is associated with a RS
Disassociate Time - This optional attribute represents the time a
      CS is disassociated with a RS.

A CS can be associated with multiple RS in the current model.
 So putting a timestamp for the association in CS doesn't work. Should
this be attributes of association of CS to RS ?
If that is the case we may need a new XML element for this association.

Comments ?

Regards,
Ram

From rmohanr@cisco.com  Mon Nov 14 02:10:52 2011
Return-Path: <rmohanr@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 6339D21F8D44 for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 02:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.051
X-Spam-Level: 
X-Spam-Status: No, score=-9.051 tagged_above=-999 required=5 tests=[AWL=1.548,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fmqNKsyiGZji for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 02:10:51 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 59B1721F8F03 for <siprec@ietf.org>; Mon, 14 Nov 2011 02:04:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=5722; q=dns/txt; s=iport; t=1321265089; x=1322474689; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=YbuAfsTj79wnuw4FqS2TgriJmLO0zG6OPdWNpC9cclY=; b=kmtHv33KnLsbzZ6BSNC0m6xrx6d8U9c1xbjliMvMcfxWK9x10VmU3JfG u8ahxWSg9gabJCl65AdJ5739+H/ZQt417mpoR9jbTrIVQ8qEcNQByrcp6 IQt0F5Gk9+YizcM770rK4tfWhnmEiI6LOivqP7noSYiWfrZw1QBmxuRIt 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApkAAHrnwE5Io8UQ/2dsb2JhbABCDplpkAWBBYFyAQEBBAEBAQ8BHQo0CQIMBAIBCBEEAQEBCgYXAQYBJh8IAQgBAQQBCggIGodomRwBnWOJHGMEiA6RZIt+Pw
X-IronPort-AV: E=Sophos;i="4.69,508,1315180800"; d="scan'208";a="59788387"
Received: from bgl-core-1.cisco.com ([72.163.197.16]) by ams-iport-2.cisco.com with ESMTP; 14 Nov 2011 10:04:14 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAEA4D7t002689; Mon, 14 Nov 2011 10:04:13 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 15:34:13 +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: Mon, 14 Nov 2011 15:34:20 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD08652059@XMB-BGL-417.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C8EF@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New Version Notificationfordraft-eckel-siprec-rtp-rec-03.txt
Thread-Index: AcyZhLx1A42GTEvSTFKP9H82bYNeLQAP8jdwAjvxJtA=
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8BFBE@xmb-sjc-234.amer.cisco.com><4EB05F4D.5080600@alum.mit.edu><E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C677@xmb-sjc-234.amer.cisco.com><4EB17D8C.1050307@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05A8C8EF@xmb-sjc-234.amer.cisco.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Paul Kyzivat" <pkyzivat@alum.mit.edu>
X-OriginalArrivalTime: 14 Nov 2011 10:04:13.0404 (UTC) FILETIME=[C2DDF1C0:01CCA2B4]
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New Version Notificationfordraft-eckel-siprec-rtp-rec-03.txt
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: Mon, 14 Nov 2011 10:10:52 -0000

Charles,

Sorry for getting late on this. I am ok with adding a new attribute in
participant element to represent the CNAME.

I will add this item to metadata slide deck and close it in the meeting.

Regards,
Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Charles Eckel (eckelcu)
> Sent: Thursday, November 03, 2011 9:09 AM
> To: Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: Re: [siprec] FW: New Version Notificationfordraft-eckel-
> siprec-rtp-rec-03.txt
>=20
> I think the CNAME would be useful for identifying the participant, in
> cases where the media packets from the participant make it to the SRS.
> I think the SSRC would be useful for identifying a stream from a
> participant, in cases where the media packets from the participant
make
> it to the SRS directly, or are incorporated into a mixed stream that
> ultimately make it to the SRS. In the second case, the SSRC from the
> stream sent by the participant to the SRC will be included as a CSRC
in
> the mixed stream sent by the SRC to the SRS.
> So I think both are useful, and the cases and ways in which they are
> useful varies depending on the functionality of the SRC.
>=20
> Cheers,
> Charles
>=20
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> > Sent: Wednesday, November 02, 2011 10:28 AM
> > To: Charles Eckel (eckelcu)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] FW: New Version Notification
> fordraft-eckel-siprec-rtp-rec-03.txt
> >
> > On 11/2/11 12:59 PM, Charles Eckel (eckelcu) wrote:
> > > Hi Paul,
> > >
> > > We certainly could. In general, you would have one CNAME value per
> > > participant. I suppose there may be cases in which a participant
> would
> > > use multiple CNAMEs despite the fact it is not recommended to do
> so.
> > > Including the CNAME in the participant info is a good thing. I do
> not
> > > know if we need to plan to support multiple CNAMEs per
participant.
> Is
> > > that your concern?
> >
> > This may just be my ignorance of how SSRC and CNAME are supposed to
> be
> > used. I understand that SSRC may change due to collision, and that
> then
> > CNAME is supposed to correlate the stream before/after the change. I
> > also gather that CNAME, rather than SSRC, is supposed to be used to
> > correlate related streams, like audio and video from same source.
> >
> > Does that mean that we should reference CNAME in metadata, rather,
or
> in
> > addition, to SSRC? Or if we update metadata when SSRC changes does
> that
> > eliminate CNAME for tracking the change?
> >
> > 	Thanks,
> > 	Paul
> >
> > > Cheers,
> > > Charles
> > >
> > >> -----Original Message-----
> > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Paul Kyzivat
> > >> Sent: Tuesday, November 01, 2011 2:06 PM
> > >> To: siprec@ietf.org
> > >> Subject: Re: [siprec] FW: New Version Notification
> > > fordraft-eckel-siprec-rtp-rec-03.txt
> > >>
> > >> Charles,
> > >>
> > >> While reading this I got wondering if we need more guidance on
the
> use
> > >> of CNAME. (As referenced in section 5.) Do we need guidance on
> mapping
> > >> of CNAME to participants?
> > >>
> > >> 	Thanks,
> > >> 	Paul
> > >>
> > >> On 10/31/11 2:00 PM, Charles Eckel (eckelcu) wrote:
> > >>> FYI, I have submitted the updated draft and it is available
> through
> > > the SIPREC documents page:
> > >>>
> > >
> http://proxy2974.my-
> addr.net/myaddrproxy.php/https/datatracker.ietf.org/
> > > wg/siprec/
> > >>>
> > >>> It contains editorial changes as well as additional text
> describing
> > > the handling of RTCP packets by
> > >> the SRC and UAs per the recent SIPREC list discussion.
> > >>>
> > >>> Cheers,
> > >>> Charles
> > >>>
> > >>> -----Original Message-----
> > >>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > >>> Sent: Monday, October 31, 2011 10:53 AM
> > >>> To: Charles Eckel (eckelcu)
> > >>> Cc: Charles Eckel (eckelcu)
> > >>> Subject: New Version Notification for
> > > draft-eckel-siprec-rtp-rec-03.txt
> > >>>
> > >>> A new version of I-D, draft-eckel-siprec-rtp-rec-03.txt has been
> > > successfully submitted by Charles
> > >> Eckel and posted to the IETF repository.
> > >>>
> > >>> Filename:	 draft-eckel-siprec-rtp-rec
> > >>> Revision:	 03
> > >>> Title:		 Real-time Transport Protocol (RTP)
> > > Recommendations for SIPREC
> > >>> Creation date:	 2011-10-31
> > >>> WG ID:		 Individual Submission
> > >>> Number of pages: 13
> > >>>
> > >>> Abstract:
> > >>>      This document provides recommendations and guidelines for
> RTP
> > > and
> > >>>      RTCP in the context of SIPREC.  This document exists as a
> > > standalone
> > >>>      document to facilitate discussion of the RTP
> recommendations,
> > > and it
> > >>>      is anticipated that portions of this document will be
> > > incorporated
> > >>>      into [I-D.ietf-siprec-protocol] rather than this document
> itself
> > >>>      being adopted as a working group document.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> The IETF Secretariat
> > >>> _______________________________________________
> > >>> 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
> > >
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From pravindran@sonusnet.com  Mon Nov 14 20:39:28 2011
Return-Path: <pravindran@sonusnet.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 D2BDA1F0DB0 for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 20:39:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.314
X-Spam-Level: 
X-Spam-Status: No, score=-2.314 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rh5Fqfm0ePk for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 20:39:28 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 45FAE1F0DA9 for <siprec@ietf.org>; Mon, 14 Nov 2011 20:39:28 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAF4e3pk013605 for <siprec@ietf.org>; Mon, 14 Nov 2011 23:40:03 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 23:39:23 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 10:09:37 +0530
Received: from INBA-HUB02.sonusnet.com (10.70.51.87) by inba-hub01.sonusnet.com (10.70.51.86) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 15 Nov 2011 10:09:36 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0339.001; Tue, 15 Nov 2011 10:09:36 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXQ==
Date: Tue, 15 Nov 2011 04:39:37 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Nov 2011 04:39:37.0034 (UTC) FILETIME=[94757AA0:01CCA350]
Subject: [siprec] Comment on draft-ietf-siprec-protocol-02
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: Tue, 15 Nov 2011 04:39:28 -0000

1) "may" is used instead of normative statement "MAY".
   a) Sec 4.2 Para 1 Line 2
   b) Sec 4.2 Para 3 Line 5

2) Figure 4: I guess that port 22458 "m" line is video instead of current a=
udio.

3) Please clarify the following statement in Sec 6.1.1 "Note that when a CS
   stream is muted/unmuted, this information is conveyed in the metadata
   by the SRC. " because I don't know how metadata convey this currently.

4) Whether the normative statement required for mute? Sec 6.1.1
   "The SRC SHOULD not modify the media stream with
   a=3Dinactive for mute since this operation is reserved for pausing the
   RS media."

5) Sec 4.2 and Sec 8.1 has duplicate information of metadata delivery which=
 shall=20
   be avoided.

6) content type shall be "application/rs-metadata+xml" instead of current=20
"application/rs-metadata"

7) full metadata snapshot shall be passed across using UPDATE as well. But =
the current
statement on Sec 8.1 misleading "When the SRC sends a full metadata snapsho=
t, the SRC MUST
   send an INVITE request with an SDP offer and the "recording-session"
   disposition."

8) Sec 8.2: whether rs-metadata-request body shall be changed as SIP header=
 or clear indication=20
within the message to indicate metadata request. Also, reason for logging c=
ould be mentioned explicitly like "logging: SRS internal error"

9) Sec 8.2: If logging is mandatory for SRS, Any recommendation of logging =
text from SRS for the generic request

Thanks
Partha

From leon.portman@gmail.com  Mon Nov 14 21:03:21 2011
Return-Path: <leon.portman@gmail.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 02CEB11E80EA for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 21:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D1BnQVmqHeif for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 21:03:20 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0E02111E80DE for <siprec@ietf.org>; Mon, 14 Nov 2011 21:03:19 -0800 (PST)
Received: by ywt34 with SMTP id 34so5743246ywt.31 for <siprec@ietf.org>; Mon, 14 Nov 2011 21:03:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=gPnII1JxpzKy+bOevYjNrba+jmPUSpCrjxUc9kbHCOM=; b=cFhJoIsdQgkW5rngJA7YCa4brv4t3MeN//dYTCMqOdHHNZmSaUQLbRUdr4PXYz4Dog 6bZlZ88UKzF3sLNMfktoh7ZCJr/FkbfXlwTWNTCj6hoBKPkwjxoP6YecHzHJgGw3/Cge VHEk5EfmWoNeGEVis2zCzU635B8jXH7+Ste54=
Received: by 10.101.27.3 with SMTP id e3mr845432anj.137.1321333399611; Mon, 14 Nov 2011 21:03:19 -0800 (PST)
Received: from ?IPv6:2001:df8::16:c131:10b3:c67f:b3ab? ([2001:df8:0:16:c131:10b3:c67f:b3ab]) by mx.google.com with ESMTPS id f32sm68887827ani.20.2011.11.14.21.03.17 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 21:03:19 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com>
Date: Tue, 15 Nov 2011 13:03:15 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>, henry.lum@genesyslab.com
X-Mailer: Apple Mail (2.1251.1)
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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: Tue, 15 Nov 2011 05:03:21 -0000

Partha Hi

Please see below

Regards

Leon
On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:

> 1) "may" is used instead of normative statement "MAY".
>   a) Sec 4.2 Para 1 Line 2
>   b) Sec 4.2 Para 3 Line 5
>=20
[Leon] I am not sure that we want to emphasize MAY in this specific =
section, it is an over part.

> 2) Figure 4: I guess that port 22458 "m" line is video instead of =
current audio.

[Leon] Yes, good catch. Thanks
>=20
> 3) Please clarify the following statement in Sec 6.1.1 "Note that when =
a CS
>   stream is muted/unmuted, this information is conveyed in the =
metadata
>   by the SRC. " because I don't know how metadata convey this =
currently.
>=20
[Leon] Yes, it is not defined yet in metadata. We should rephrase it to =
"may be conveyed in metadata"
> 4) Whether the normative statement required for mute? Sec 6.1.1
>   "The SRC SHOULD not modify the media stream with
>   a=3Dinactive for mute since this operation is reserved for pausing =
the
>   RS media."
>=20
[Leon] It is related to point #3 that "mute" should not be handled like =
"hold"

> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata delivery =
which shall=20
>   be avoided.

[Leon] 4.2 is the overview section. We could have some repetition here =
with detailed sections.
>=20
> 6) content type shall be "application/rs-metadata+xml" instead of =
current=20
> "application/rs-metadata"
>=20
[Leon] I am ok with that
> 7) full metadata snapshot shall be passed across using UPDATE as well. =
But the current
> statement on Sec 8.1 misleading "When the SRC sends a full metadata =
snapshot, the SRC MUST
>   send an INVITE request with an SDP offer and the "recording-session"
>   disposition."
>=20
[Leon] I remember having discussion to mandate INVITE in order to make =
sure that SDP will be present as well. Dont have any strong preferences =
here.

> 8) Sec 8.2: whether rs-metadata-request body shall be changed as SIP =
header or clear indication=20
> within the message to indicate metadata request. Also, reason for =
logging could be mentioned explicitly like "logging: SRS internal error"
>=20
[Leon]  I am ok with that. Any opinions?

> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation of =
logging text from SRS for the generic request

[Leon] Please elaborate.
>=20
> Thanks
> Partha
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From leon.portman@gmail.com  Mon Nov 14 21:15:25 2011
Return-Path: <leon.portman@gmail.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 E2DFB1F0D12 for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 21:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXhlXiC4noV1 for <siprec@ietfa.amsl.com>; Mon, 14 Nov 2011 21:15:25 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 62B701F0C4F for <siprec@ietf.org>; Mon, 14 Nov 2011 21:15:25 -0800 (PST)
Received: by yenq4 with SMTP id q4so4349160yen.31 for <siprec@ietf.org>; Mon, 14 Nov 2011 21:15:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=e19aqeJFUgUBLoLcrYaCkUZu7/dt8zWs9+WmBPsz7bk=; b=Ei6H/lqSw+r5mbtnj1KWg++r6dn6qmJNQ7akmmJmCbZ9PkDU55z69mXIVS4wYfeayu FkDOxvYqoCg3Nd0fi8Xkh9l+Ns2yWFwFCh6fhade5H95etth45MMyShEMQvDWSQMfNPa L/THxKPtic0QifBynPtrAPh/NK8j09MCLCTbU=
Received: by 10.100.12.4 with SMTP id 4mr842624anl.132.1321334125012; Mon, 14 Nov 2011 21:15:25 -0800 (PST)
Received: from dhcp-1398.meeting.ietf.org (dhcp-1398.meeting.ietf.org. [130.129.19.152]) by mx.google.com with ESMTPS id y1sm22648442anj.18.2011.11.14.21.15.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 21:15:24 -0800 (PST)
From: Leon Portman <leon.portman@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Nov 2011 13:15:20 +0800
Message-Id: <8B48235E-D881-4C75-83CF-E45E5FC5DDFD@gmail.com>
To: siprec@ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [siprec]  Using of feature and options tags in SIPREC protocol
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: Tue, 15 Nov 2011 05:15:26 -0000

Hello

I wanted to get opinions about main open items for the protocol draft =
regarding using of feature and options tags.

if i remember correctly, we wanted to solve two problems:

1. Ability to register SRS and SRC with right capabilities in order to =
be able to discovery (specially SRS) and route RS INVITES correctly.

Solution: We have defined feature tags: "+sip.src" and "+sip.srs" (right =
syntax after Paul comments) and they should be used in relevant contact =
fields.

2. Make sure that only SRS and SRC will handle RS INVITE and not brake =
other UAs in case of wrong configuration or midboxes.

Solution: add "siprec" option tag and have SRC/SRS to use it in =
Supported and Required headers accordingly.=20

Paul have suggested two have actually two options: src and srs in order =
to distinguish between SRC and SRS (we dont need it if requirement 1 =
stays).

Any opinions?

Thanks

Leon=

From pravindran@sonusnet.com  Tue Nov 15 16:16:37 2011
Return-Path: <pravindran@sonusnet.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 921B521F8AAC for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 16:16:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.309
X-Spam-Level: 
X-Spam-Status: No, score=-2.309 tagged_above=-999 required=5 tests=[AWL=-0.310, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kfh2UVuTkdrD for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 16:16:36 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id A964421F8AAA for <siprec@ietf.org>; Tue, 15 Nov 2011 16:16:33 -0800 (PST)
Received: from sonusmail04.sonusnet.com (sonusmail04.sonusnet.com [10.128.32.98]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAG0H7kk003816;  Tue, 15 Nov 2011 19:17:07 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail04.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 19:13:56 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 05:44:10 +0530
Received: from INBA-HUB02.sonusnet.com (10.70.51.87) by inba-hub01.sonusnet.com (10.70.51.86) with Microsoft SMTP Server (TLS) id 14.1.339.1; Wed, 16 Nov 2011 05:44:09 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0339.001; Wed, 16 Nov 2011 05:44:09 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Leon Portman <leon.portman@gmail.com>, "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVA=
Date: Wed, 16 Nov 2011 00:14:08 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com> <0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com>
In-Reply-To: <0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Nov 2011 00:14:10.0017 (UTC) FILETIME=[A9A14D10:01CCA3F4]
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 00:16:37 -0000

Leon,

Please read inline

Thanks
Partha

>-----Original Message-----
>From: Leon Portman [mailto:leon.portman@gmail.com]
>Sent: Tuesday, November 15, 2011 1:03 PM
>To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>Cc: siprec@ietf.org
>Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>
>
>Partha Hi
>
>Please see below
>
>Regards
>
>Leon
>On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>
>> 1) "may" is used instead of normative statement "MAY".
>>   a) Sec 4.2 Para 1 Line 2
>>   b) Sec 4.2 Para 3 Line 5
>>
>[Leon] I am not sure that we want to emphasize MAY in this specific
>section, it is an over part.
>
<partha> I'm not very sure whether it is appropriate to use "may" in the sp=
ecification.=20
</partha>

>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
>current audio.
>
>[Leon] Yes, good catch. Thanks
>>
>> 3) Please clarify the following statement in Sec 6.1.1 "Note that when
>a CS
>>   stream is muted/unmuted, this information is conveyed in the
>metadata
>>   by the SRC. " because I don't know how metadata convey this
>currently.
>>
>[Leon] Yes, it is not defined yet in metadata. We should rephrase it to
>"may be conveyed in metadata"
<partha> Currently, it is outside the scope of metadata and IMO, it is bett=
er
to remove "mute/unmute" from protocol spec </partha>

>> 4) Whether the normative statement required for mute? Sec 6.1.1
>>   "The SRC SHOULD not modify the media stream with
>>   a=3Dinactive for mute since this operation is reserved for pausing the
>>   RS media."
>>
>[Leon] It is related to point #3 that "mute" should not be handled like
>"hold"
>
<partha> IMO, there should be no normative statement related to mute </part=
ha>

>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata delivery
>which shall
>>   be avoided.
>
>[Leon] 4.2 is the overview section. We could have some repetition here
>with detailed sections.
>>
<partha> I can live with incase everybody wants with duplication on text
</partha>

>> 6) content type shall be "application/rs-metadata+xml" instead of
>> current "application/rs-metadata"
>>
>[Leon] I am ok with that
>> 7) full metadata snapshot shall be passed across using UPDATE as well.
>> But the current statement on Sec 8.1 misleading "When the SRC sends a
>full metadata snapshot, the SRC MUST
>>   send an INVITE request with an SDP offer and the "recording-session"
>>   disposition."
>>
>[Leon] I remember having discussion to mandate INVITE in order to make
>sure that SDP will be present as well. Dont have any strong preferences
>here.
>
<partha> We had the discussion during IETF-80 to mandate INVITE & UPDATE.
But I could not find the reason for not using UPDATE for full snapshot
Request </partha>

>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as SIP
>> header or clear indication within the message to indicate metadata
>request. Also, reason for logging could be mentioned explicitly like
>"logging: SRS internal error"
>>
>[Leon]  I am ok with that. Any opinions?
>
>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation of
>> logging text from SRS for the generic request
>
>[Leon] Please elaborate.
>>
<partha> Currently, it is plain text now whereas SRC has no means to=20
understand about  the logs. Some guidelines/suggestion about the text
 helps for the implementation by which SRC understand. </partha>=20
>> Thanks
>> Partha
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec


From leon.portman@gmail.com  Tue Nov 15 17:25:42 2011
Return-Path: <leon.portman@gmail.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 66D0711E80E3 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 17:25:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcaHBJgSWbFo for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 17:25:40 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 75BCB11E808D for <siprec@ietf.org>; Tue, 15 Nov 2011 17:25:40 -0800 (PST)
Received: by ggnr5 with SMTP id r5so3367792ggn.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 17:25:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=590TnZsn+pZyvaRs+W0Vs9cD5RWBYa8M6fC/ju4sqpI=; b=Gj1RnIIlOmtW1HDjZDiQG8VOqcVaHNVj8EQeJlBFoX1h+9LOe6HC8i510/sBDPpKmg mz3sMALE88PQPfdf7DAJrGcoPtQP5wb5wEjIkoj47zzsH1SHodrIvrA4/E4K/ETAz4Kl INwrYG3JYOnpxcdYnSFwPCAkzvtr+w2NtAWMc=
Received: by 10.146.219.32 with SMTP id r32mr5244687yag.25.1321406740008; Tue, 15 Nov 2011 17:25:40 -0800 (PST)
Received: from ?IPv6:2001:df8::16:9185:95b2:7df4:155a? ([2001:df8:0:16:9185:95b2:7df4:155a]) by mx.google.com with ESMTPS id b9sm79807967anb.7.2011.11.15.17.25.37 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 17:25:39 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com>
Date: Wed, 16 Nov 2011 09:25:36 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com> <0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com>
To: Parthasarathi Ravindran <pravindran@sonusnet.com>, henry.lum@genesyslab.com
X-Mailer: Apple Mail (2.1251.1)
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 01:25:42 -0000

Partha Thanks

Please see below

Leon

On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:

> Leon,
>=20
> Please read inline
>=20
> Thanks
> Partha
>=20
>> -----Original Message-----
>> From: Leon Portman [mailto:leon.portman@gmail.com]
>> Sent: Tuesday, November 15, 2011 1:03 PM
>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>> Cc: siprec@ietf.org
>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>>=20
>>=20
>> Partha Hi
>>=20
>> Please see below
>>=20
>> Regards
>>=20
>> Leon
>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>=20
>>> 1) "may" is used instead of normative statement "MAY".
>>>  a) Sec 4.2 Para 1 Line 2
>>>  b) Sec 4.2 Para 3 Line 5
>>>=20
>> [Leon] I am not sure that we want to emphasize MAY in this specific
>> section, it is an over part.
>>=20
> <partha> I'm not very sure whether it is appropriate to use "may" in =
the specification.=20
> </partha>

[Leon] I dont have any opinions on that
>=20
>>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
>> current audio.
>>=20
>> [Leon] Yes, good catch. Thanks
>>>=20
>>> 3) Please clarify the following statement in Sec 6.1.1 "Note that =
when
>> a CS
>>>  stream is muted/unmuted, this information is conveyed in the
>> metadata
>>>  by the SRC. " because I don't know how metadata convey this
>> currently.
>>>=20
>> [Leon] Yes, it is not defined yet in metadata. We should rephrase it =
to
>> "may be conveyed in metadata"
> <partha> Currently, it is outside the scope of metadata and IMO, it is =
better
> to remove "mute/unmute" from protocol spec </partha>

[Leon] I agree, Henry, what do you think?
>=20
>>> 4) Whether the normative statement required for mute? Sec 6.1.1
>>>  "The SRC SHOULD not modify the media stream with
>>>  a=3Dinactive for mute since this operation is reserved for pausing =
the
>>>  RS media."
>>>=20
>> [Leon] It is related to point #3 that "mute" should not be handled =
like
>> "hold"
>>=20
> <partha> IMO, there should be no normative statement related to mute =
</partha>
>=20
>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata =
delivery
>> which shall
>>>  be avoided.
>>=20
>> [Leon] 4.2 is the overview section. We could have some repetition =
here
>> with detailed sections.
>>>=20
> <partha> I can live with incase everybody wants with duplication on =
text
> </partha>
>=20
>>> 6) content type shall be "application/rs-metadata+xml" instead of
>>> current "application/rs-metadata"
>>>=20
>> [Leon] I am ok with that
>>> 7) full metadata snapshot shall be passed across using UPDATE as =
well.
>>> But the current statement on Sec 8.1 misleading "When the SRC sends =
a
>> full metadata snapshot, the SRC MUST
>>>  send an INVITE request with an SDP offer and the =
"recording-session"
>>>  disposition."
>>>=20
>> [Leon] I remember having discussion to mandate INVITE in order to =
make
>> sure that SDP will be present as well. Dont have any strong =
preferences
>> here.
>>=20
> <partha> We had the discussion during IETF-80 to mandate INVITE & =
UPDATE.
> But I could not find the reason for not using UPDATE for full snapshot
> Request </partha>

[Leon] I am ok with both
>=20
>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as SIP
>>> header or clear indication within the message to indicate metadata
>> request. Also, reason for logging could be mentioned explicitly like
>> "logging: SRS internal error"
>>>=20
>> [Leon]  I am ok with that. Any opinions?
>>=20
>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation of
>>> logging text from SRS for the generic request
>>=20
>> [Leon] Please elaborate.
>>>=20
> <partha> Currently, it is plain text now whereas SRC has no means to=20=

> understand about  the logs. Some guidelines/suggestion about the text
> helps for the implementation by which SRC understand. </partha>=20
>>> Thanks
>>> Partha
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec
>=20


From leon.portman@gmail.com  Tue Nov 15 18:45:37 2011
Return-Path: <leon.portman@gmail.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 108A81F0C60 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 18:45:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdjU2ZlMgKrg for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 18:45:33 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id DD2791F0C9E for <siprec@ietf.org>; Tue, 15 Nov 2011 18:45:32 -0800 (PST)
Received: by ggnr5 with SMTP id r5so3440950ggn.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 18:45:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=aYzrfhLQ8XEapxQSIPjb1JDW+mUt3rxehvE9LkVjM8A=; b=O3KyyWxAvnbRQ/ajC+H5L/46LoNw711te4wftyXJYzcHdoCipHQpmhhLDsvgUKYyfC OgFgni4+QSqhKy29wpkBX+xR6T01FXikQBs8Q5Yxwl4gn952nTjBDVpVRu5Q01xcRHQS mVo6P38cmInKqDzmYBvrv1cFW23J0H+yP/qS4=
Received: by 10.100.22.16 with SMTP id 16mr5139233anv.48.1321411532425; Tue, 15 Nov 2011 18:45:32 -0800 (PST)
Received: from dhcp-1398.meeting.ietf.org (dhcp-1398.meeting.ietf.org. [130.129.19.152]) by mx.google.com with ESMTPS id 4sm80494317ano.9.2011.11.15.18.45.30 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 18:45:31 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com>
Date: Wed, 16 Nov 2011 10:45:28 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com> <0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com> <B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com>
To: Parthasarathi Ravindran <pravindran@sonusnet.com>, henry.lum@genesyslab.com
X-Mailer: Apple Mail (2.1251.1)
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 02:45:37 -0000

Additional update on sending full metadata snapshot upon SRS request.

In section 8.2 we say:

"   When the SRC receives the request for a metadata snapshot, the SRC
   MUST provide a full metadata snapshot in a separate INVITE
   transaction, along with an SDP offer."

meaning that full metadata is actually separate INVITE transaction.

Leon


On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:

> Partha Thanks
>=20
> Please see below
>=20
> Leon
>=20
> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>=20
>> Leon,
>>=20
>> Please read inline
>>=20
>> Thanks
>> Partha
>>=20
>>> -----Original Message-----
>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>> Cc: siprec@ietf.org
>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>>>=20
>>>=20
>>> Partha Hi
>>>=20
>>> Please see below
>>>=20
>>> Regards
>>>=20
>>> Leon
>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>=20
>>>> 1) "may" is used instead of normative statement "MAY".
>>>> a) Sec 4.2 Para 1 Line 2
>>>> b) Sec 4.2 Para 3 Line 5
>>>>=20
>>> [Leon] I am not sure that we want to emphasize MAY in this specific
>>> section, it is an over part.
>>>=20
>> <partha> I'm not very sure whether it is appropriate to use "may" in =
the specification.=20
>> </partha>
>=20
> [Leon] I dont have any opinions on that
>>=20
>>>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
>>> current audio.
>>>=20
>>> [Leon] Yes, good catch. Thanks
>>>>=20
>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note that =
when
>>> a CS
>>>> stream is muted/unmuted, this information is conveyed in the
>>> metadata
>>>> by the SRC. " because I don't know how metadata convey this
>>> currently.
>>>>=20
>>> [Leon] Yes, it is not defined yet in metadata. We should rephrase it =
to
>>> "may be conveyed in metadata"
>> <partha> Currently, it is outside the scope of metadata and IMO, it =
is better
>> to remove "mute/unmute" from protocol spec </partha>
>=20
> [Leon] I agree, Henry, what do you think?
>>=20
>>>> 4) Whether the normative statement required for mute? Sec 6.1.1
>>>> "The SRC SHOULD not modify the media stream with
>>>> a=3Dinactive for mute since this operation is reserved for pausing =
the
>>>> RS media."
>>>>=20
>>> [Leon] It is related to point #3 that "mute" should not be handled =
like
>>> "hold"
>>>=20
>> <partha> IMO, there should be no normative statement related to mute =
</partha>
>>=20
>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata =
delivery
>>> which shall
>>>> be avoided.
>>>=20
>>> [Leon] 4.2 is the overview section. We could have some repetition =
here
>>> with detailed sections.
>>>>=20
>> <partha> I can live with incase everybody wants with duplication on =
text
>> </partha>
>>=20
>>>> 6) content type shall be "application/rs-metadata+xml" instead of
>>>> current "application/rs-metadata"
>>>>=20
>>> [Leon] I am ok with that
>>>> 7) full metadata snapshot shall be passed across using UPDATE as =
well.
>>>> But the current statement on Sec 8.1 misleading "When the SRC sends =
a
>>> full metadata snapshot, the SRC MUST
>>>> send an INVITE request with an SDP offer and the =
"recording-session"
>>>> disposition."
>>>>=20
>>> [Leon] I remember having discussion to mandate INVITE in order to =
make
>>> sure that SDP will be present as well. Dont have any strong =
preferences
>>> here.
>>>=20
>> <partha> We had the discussion during IETF-80 to mandate INVITE & =
UPDATE.
>> But I could not find the reason for not using UPDATE for full =
snapshot
>> Request </partha>
>=20
> [Leon] I am ok with both
>>=20
>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as =
SIP
>>>> header or clear indication within the message to indicate metadata
>>> request. Also, reason for logging could be mentioned explicitly like
>>> "logging: SRS internal error"
>>>>=20
>>> [Leon]  I am ok with that. Any opinions?
>>>=20
>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation of
>>>> logging text from SRS for the generic request
>>>=20
>>> [Leon] Please elaborate.
>>>>=20
>> <partha> Currently, it is plain text now whereas SRC has no means to=20=

>> understand about  the logs. Some guidelines/suggestion about the text
>> helps for the implementation by which SRC understand. </partha>=20
>>>> Thanks
>>>> Partha
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>=20
>=20


From leon.portman@gmail.com  Tue Nov 15 18:51:22 2011
Return-Path: <leon.portman@gmail.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 45F8411E8164 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 18:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Oyrb4SCMSB3 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 18:51:21 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8967511E8151 for <siprec@ietf.org>; Tue, 15 Nov 2011 18:51:17 -0800 (PST)
Received: by ggnr5 with SMTP id r5so3446517ggn.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 18:51:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=LHjqR32L9TeH9n+3IEZDjaEiIPh5r2JqwfYmWolm4cE=; b=WoMeJvuqHUrSD5TVzPffNri0FEjirdFg+U+VJguE6rHj/3rwCDnKaJf/j9hP90942q JR5VVwd5cdgWcPOmzon5NAS4wrHIE39Kbdjnspap7rxFWhkb6P9pip5vU8Vrk5/q4TJz VdDPde0TGrRl1LTBrtwabS6WqSgTse/egrh6A=
Received: by 10.101.105.15 with SMTP id h15mr8919509anm.105.1321411877086; Tue, 15 Nov 2011 18:51:17 -0800 (PST)
Received: from ?IPv6:2001:df8::16:9185:95b2:7df4:155a? ([2001:df8:0:16:9185:95b2:7df4:155a]) by mx.google.com with ESMTPS id u19sm80514834ank.11.2011.11.15.18.51.15 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 18:51:16 -0800 (PST)
From: Leon Portman <leon.portman@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Nov 2011 10:51:15 +0800
Message-Id: <E1BDF6FF-10B7-4F85-B34B-B59D63BF2EBA@gmail.com>
To: siprec@ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [siprec]  Metadata snapshot request extensions
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, 16 Nov 2011 02:51:22 -0000

Hello

Following Partha request to change SRS request for metadata snapshot to =
indicate actual request - current it is done only by Content-type:

Content-Type: application/rs-metadata-request with just simple text in =
the body.

Do we want to support more extendable mechanism where body will include =
more generic XML that can also contain for example list of CSs =
identifiers for which SRS want to receive updates or some other =
instructions?

pros: it can be useful for RS that includes lots of CS and SRS may have =
preserved during a failure theirs ids
cons: complication on SRC side and adding requirement to be able to =
parse XML, can be problematic.

Any opinions?

Regards

Leon=

From rmohanr@cisco.com  Tue Nov 15 18:56:19 2011
Return-Path: <rmohanr@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 17E1F11E81DC for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 18:56:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.802
X-Spam-Level: 
X-Spam-Status: No, score=-8.802 tagged_above=-999 required=5 tests=[AWL=1.197,  BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id enID381J7mxP for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 18:56:14 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 36CFF11E81D3 for <siprec@ietf.org>; Tue, 15 Nov 2011 18:56:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=5653; q=dns/txt; s=iport; t=1321412174; x=1322621774; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=ncB6PrHewBPkj59xXCJj6K3/arnjPL3mBZ9SRPlPYNc=; b=SYZTp5HP7FTeoAqnEJ09qqlKSv2qLJDgOjuqp0cAXXai2UkQBByvdqV4 kJq2gjuV6wLLCf5aS2mogwxDFHzzZHZhhwL3EecyMFY7qEJD/Izl8/CQ3 CK6l1QFvDFAElGtsEbFwy+tamRZEkPI2cdGybO4IErzwyTz5hxNtVFOQM 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnsAACslw05Io8US/2dsb2JhbABDmWqQCIEFgXIBAQEDAQEBAQ8BHQo0CwwEAgEIEQQBAQEKBhcBBgEgBh8JCAEBBAEKCAgah2AImkoBnlQEiTRjBIgSkWaFB4c5
X-IronPort-AV: E=Sophos;i="4.69,518,1315180800"; d="scan'208";a="121714264"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-1.cisco.com with ESMTP; 16 Nov 2011 02:56:12 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAG2uBoF029554; Wed, 16 Nov 2011 02:56:11 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 08:26:11 +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, 16 Nov 2011 08:26:09 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com>
In-Reply-To: <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcykCdgxpd4LzklRTqenj/F+HCCNJgAAU/HA
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <leon.portman@gmail.com>, "Parthasarathi Ravindran" <pravindran@sonusnet.com>, <henry.lum@genesyslab.com>
X-OriginalArrivalTime: 16 Nov 2011 02:56:11.0375 (UTC) FILETIME=[4C02CFF0:01CCA40B]
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 02:56:19 -0000

Leon,

Please see inline. I have a question here

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> Sent: Wednesday, November 16, 2011 10:45 AM
> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>=20
> Additional update on sending full metadata snapshot upon SRS request.
>=20
> In section 8.2 we say:
>=20
> "   When the SRC receives the request for a metadata snapshot, the SRC
>    MUST provide a full metadata snapshot in a separate INVITE
>    transaction, along with an SDP offer."
>=20
> meaning that full metadata is actually separate INVITE transaction.

Why should the snapshot be always sent in a separate INVITE. Can't it be
sent as a response to snapshot request from SRS ? Is there a reason why
you want to mandate that way ?

Ram

>=20
> Leon
>=20
>=20
> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>=20
> > Partha Thanks
> >
> > Please see below
> >
> > Leon
> >
> > On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
> >
> >> Leon,
> >>
> >> Please read inline
> >>
> >> Thanks
> >> Partha
> >>
> >>> -----Original Message-----
> >>> From: Leon Portman [mailto:leon.portman@gmail.com]
> >>> Sent: Tuesday, November 15, 2011 1:03 PM
> >>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
> >>> Cc: siprec@ietf.org
> >>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
> >>>
> >>>
> >>> Partha Hi
> >>>
> >>> Please see below
> >>>
> >>> Regards
> >>>
> >>> Leon
> >>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
> >>>
> >>>> 1) "may" is used instead of normative statement "MAY".
> >>>> a) Sec 4.2 Para 1 Line 2
> >>>> b) Sec 4.2 Para 3 Line 5
> >>>>
> >>> [Leon] I am not sure that we want to emphasize MAY in this
specific
> >>> section, it is an over part.
> >>>
> >> <partha> I'm not very sure whether it is appropriate to use "may"
in
> the specification.
> >> </partha>
> >
> > [Leon] I dont have any opinions on that
> >>
> >>>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
> >>> current audio.
> >>>
> >>> [Leon] Yes, good catch. Thanks
> >>>>
> >>>> 3) Please clarify the following statement in Sec 6.1.1 "Note that
> when
> >>> a CS
> >>>> stream is muted/unmuted, this information is conveyed in the
> >>> metadata
> >>>> by the SRC. " because I don't know how metadata convey this
> >>> currently.
> >>>>
> >>> [Leon] Yes, it is not defined yet in metadata. We should rephrase
> it to
> >>> "may be conveyed in metadata"
> >> <partha> Currently, it is outside the scope of metadata and IMO, it
> is better
> >> to remove "mute/unmute" from protocol spec </partha>
> >
> > [Leon] I agree, Henry, what do you think?
> >>
> >>>> 4) Whether the normative statement required for mute? Sec 6.1.1
> >>>> "The SRC SHOULD not modify the media stream with
> >>>> a=3Dinactive for mute since this operation is reserved for =
pausing
> the
> >>>> RS media."
> >>>>
> >>> [Leon] It is related to point #3 that "mute" should not be handled
> like
> >>> "hold"
> >>>
> >> <partha> IMO, there should be no normative statement related to
mute
> </partha>
> >>
> >>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
> delivery
> >>> which shall
> >>>> be avoided.
> >>>
> >>> [Leon] 4.2 is the overview section. We could have some repetition
> here
> >>> with detailed sections.
> >>>>
> >> <partha> I can live with incase everybody wants with duplication on
> text
> >> </partha>
> >>
> >>>> 6) content type shall be "application/rs-metadata+xml" instead of
> >>>> current "application/rs-metadata"
> >>>>
> >>> [Leon] I am ok with that
> >>>> 7) full metadata snapshot shall be passed across using UPDATE as
> well.
> >>>> But the current statement on Sec 8.1 misleading "When the SRC
> sends a
> >>> full metadata snapshot, the SRC MUST
> >>>> send an INVITE request with an SDP offer and the "recording-
> session"
> >>>> disposition."
> >>>>
> >>> [Leon] I remember having discussion to mandate INVITE in order to
> make
> >>> sure that SDP will be present as well. Dont have any strong
> preferences
> >>> here.
> >>>
> >> <partha> We had the discussion during IETF-80 to mandate INVITE &
> UPDATE.
> >> But I could not find the reason for not using UPDATE for full
> snapshot
> >> Request </partha>
> >
> > [Leon] I am ok with both
> >>
> >>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
> SIP
> >>>> header or clear indication within the message to indicate
metadata
> >>> request. Also, reason for logging could be mentioned explicitly
> like
> >>> "logging: SRS internal error"
> >>>>
> >>> [Leon]  I am ok with that. Any opinions?
> >>>
> >>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation
of
> >>>> logging text from SRS for the generic request
> >>>
> >>> [Leon] Please elaborate.
> >>>>
> >> <partha> Currently, it is plain text now whereas SRC has no means
to
> >> understand about  the logs. Some guidelines/suggestion about the
> text
> >> helps for the implementation by which SRC understand. </partha>
> >>>> Thanks
> >>>> Partha
> >>>> _______________________________________________
> >>>> siprec mailing list
> >>>> siprec@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/siprec
> >>
> >
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From pravindran@sonusnet.com  Tue Nov 15 19:08:34 2011
Return-Path: <pravindran@sonusnet.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 C253B21F9010 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.305
X-Spam-Level: 
X-Spam-Status: No, score=-2.305 tagged_above=-999 required=5 tests=[AWL=-0.306, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDQZA6WeBRSG for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:08:30 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2B621F900D for <siprec@ietf.org>; Tue, 15 Nov 2011 19:08:30 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAG392dY017492;  Tue, 15 Nov 2011 22:09:02 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 22:00:16 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 08:30:29 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Wed, 16 Nov 2011 08:30:29 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, Leon Portman <leon.portman@gmail.com>, "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVCAAfdcAIAAFlAAgAAC/YD//6LIIA==
Date: Wed, 16 Nov 2011 03:00:28 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Nov 2011 03:00:29.0783 (UTC) FILETIME=[E608BE70:01CCA40B]
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 03:08:35 -0000

Leon,

I agree with Ram.

It is possible to debate on this normative statement requirement as=20
multiple way to request the full snapshot from SRS. Some of the way
from SRS are as follows:

1) REVITE without SDP and siprec-metdata-request body (3 SIP messages)
2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP messages)
3) UPDATE without SDP and SIPREC-metadata-request body and
   Separate (4 SIP messages)

IIUC, current SIPREC protocol mechanism propose to use only OPTION 3
but I prefer to have the implementation choice. As mentioned above,=20
OPTION 1 & 2 has less SIP message required to achieve the same compare
to OPTION 3. Hope this clarifies.

Thanks
Partha

>-----Original Message-----
>From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>Sent: Wednesday, November 16, 2011 10:56 AM
>To: Leon Portman; Ravindran, Parthasarathi; henry.lum@genesyslab.com
>Cc: siprec@ietf.org
>Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>
>Leon,
>
>Please see inline. I have a question here
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Leon Portman
>> Sent: Wednesday, November 16, 2011 10:45 AM
>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>
>> Additional update on sending full metadata snapshot upon SRS request.
>>
>> In section 8.2 we say:
>>
>> "   When the SRC receives the request for a metadata snapshot, the SRC
>>    MUST provide a full metadata snapshot in a separate INVITE
>>    transaction, along with an SDP offer."
>>
>> meaning that full metadata is actually separate INVITE transaction.
>
>Why should the snapshot be always sent in a separate INVITE. Can't it be
>sent as a response to snapshot request from SRS ? Is there a reason why
>you want to mandate that way ?
>
>Ram
>
>>
>> Leon
>>
>>
>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>
>> > Partha Thanks
>> >
>> > Please see below
>> >
>> > Leon
>> >
>> > On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>> >
>> >> Leon,
>> >>
>> >> Please read inline
>> >>
>> >> Thanks
>> >> Partha
>> >>
>> >>> -----Original Message-----
>> >>> From: Leon Portman [mailto:leon.portman@gmail.com]
>> >>> Sent: Tuesday, November 15, 2011 1:03 PM
>> >>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>> >>> Cc: siprec@ietf.org
>> >>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>> >>>
>> >>>
>> >>> Partha Hi
>> >>>
>> >>> Please see below
>> >>>
>> >>> Regards
>> >>>
>> >>> Leon
>> >>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>> >>>
>> >>>> 1) "may" is used instead of normative statement "MAY".
>> >>>> a) Sec 4.2 Para 1 Line 2
>> >>>> b) Sec 4.2 Para 3 Line 5
>> >>>>
>> >>> [Leon] I am not sure that we want to emphasize MAY in this
>specific
>> >>> section, it is an over part.
>> >>>
>> >> <partha> I'm not very sure whether it is appropriate to use "may"
>in
>> the specification.
>> >> </partha>
>> >
>> > [Leon] I dont have any opinions on that
>> >>
>> >>>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
>> >>> current audio.
>> >>>
>> >>> [Leon] Yes, good catch. Thanks
>> >>>>
>> >>>> 3) Please clarify the following statement in Sec 6.1.1 "Note that
>> when
>> >>> a CS
>> >>>> stream is muted/unmuted, this information is conveyed in the
>> >>> metadata
>> >>>> by the SRC. " because I don't know how metadata convey this
>> >>> currently.
>> >>>>
>> >>> [Leon] Yes, it is not defined yet in metadata. We should rephrase
>> it to
>> >>> "may be conveyed in metadata"
>> >> <partha> Currently, it is outside the scope of metadata and IMO, it
>> is better
>> >> to remove "mute/unmute" from protocol spec </partha>
>> >
>> > [Leon] I agree, Henry, what do you think?
>> >>
>> >>>> 4) Whether the normative statement required for mute? Sec 6.1.1
>> >>>> "The SRC SHOULD not modify the media stream with a=3Dinactive for
>> >>>> mute since this operation is reserved for pausing
>> the
>> >>>> RS media."
>> >>>>
>> >>> [Leon] It is related to point #3 that "mute" should not be handled
>> like
>> >>> "hold"
>> >>>
>> >> <partha> IMO, there should be no normative statement related to
>mute
>> </partha>
>> >>
>> >>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>> delivery
>> >>> which shall
>> >>>> be avoided.
>> >>>
>> >>> [Leon] 4.2 is the overview section. We could have some repetition
>> here
>> >>> with detailed sections.
>> >>>>
>> >> <partha> I can live with incase everybody wants with duplication on
>> text
>> >> </partha>
>> >>
>> >>>> 6) content type shall be "application/rs-metadata+xml" instead of
>> >>>> current "application/rs-metadata"
>> >>>>
>> >>> [Leon] I am ok with that
>> >>>> 7) full metadata snapshot shall be passed across using UPDATE as
>> well.
>> >>>> But the current statement on Sec 8.1 misleading "When the SRC
>> sends a
>> >>> full metadata snapshot, the SRC MUST
>> >>>> send an INVITE request with an SDP offer and the "recording-
>> session"
>> >>>> disposition."
>> >>>>
>> >>> [Leon] I remember having discussion to mandate INVITE in order to
>> make
>> >>> sure that SDP will be present as well. Dont have any strong
>> preferences
>> >>> here.
>> >>>
>> >> <partha> We had the discussion during IETF-80 to mandate INVITE &
>> UPDATE.
>> >> But I could not find the reason for not using UPDATE for full
>> snapshot
>> >> Request </partha>
>> >
>> > [Leon] I am ok with both
>> >>
>> >>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
>> SIP
>> >>>> header or clear indication within the message to indicate
>metadata
>> >>> request. Also, reason for logging could be mentioned explicitly
>> like
>> >>> "logging: SRS internal error"
>> >>>>
>> >>> [Leon]  I am ok with that. Any opinions?
>> >>>
>> >>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation
>of
>> >>>> logging text from SRS for the generic request
>> >>>
>> >>> [Leon] Please elaborate.
>> >>>>
>> >> <partha> Currently, it is plain text now whereas SRC has no means
>to
>> >> understand about  the logs. Some guidelines/suggestion about the
>> text
>> >> helps for the implementation by which SRC understand. </partha>
>> >>>> Thanks
>> >>>> Partha
>> >>>> _______________________________________________
>> >>>> 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

From leon.portman@gmail.com  Tue Nov 15 19:13:20 2011
Return-Path: <leon.portman@gmail.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 A814711E80D4 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:13:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.149
X-Spam-Level: 
X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U0XkiXpzPWi3 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:13:16 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 83A5E11E80C7 for <siprec@ietf.org>; Tue, 15 Nov 2011 19:13:16 -0800 (PST)
Received: by ywt34 with SMTP id 34so7231013ywt.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 19:13:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=c3Ft1waSjmu4aF2HLXI+qAdEwfSIV0EPOEiFs05qHRw=; b=kRGZHHld6hGm6RWIJWAqyHU2bEyCuCk4lqaOwsUyjpvcFIfz28+ASOmkRX0AoE+Wd0 lNqSp2azI1WH25Z74mNqQP+ypxi7Q2d9vDycFh/9atGDe08mdXI21UkAKoifqiK3G4Tb hW8am8AmGOleQ0I2ytR8cCOSMZF3JR8/bAL08=
Received: by 10.101.59.6 with SMTP id m6mr8984860ank.118.1321413194198; Tue, 15 Nov 2011 19:13:14 -0800 (PST)
Received: from dhcp-1398.meeting.ietf.org (dhcp-1398.meeting.ietf.org. [130.129.19.152]) by mx.google.com with ESMTPS id 32sm80725829anu.10.2011.11.15.19.13.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 19:13:13 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com>
Date: Wed, 16 Nov 2011 11:13:10 +0800
Content-Transfer-Encoding: 7bit
Message-Id: <9F6839D6-A433-4786-B47B-B3612F8B3F51@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, henry.lum@genesyslab.com
X-Mailer: Apple Mail (2.1251.1)
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 03:13:20 -0000

Yes, please refer to:

http://www.ietf.org/mail-archive/web/siprec/current/msg02436.html



On Nov 16, 2011, at 10:56 AM, Ram Mohan R (rmohanr) wrote:

> Leon,
> 
> Please see inline. I have a question here
> 
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Leon Portman
>> Sent: Wednesday, November 16, 2011 10:45 AM
>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>> 
>> Additional update on sending full metadata snapshot upon SRS request.
>> 
>> In section 8.2 we say:
>> 
>> "   When the SRC receives the request for a metadata snapshot, the SRC
>>   MUST provide a full metadata snapshot in a separate INVITE
>>   transaction, along with an SDP offer."
>> 
>> meaning that full metadata is actually separate INVITE transaction.
> 
> Why should the snapshot be always sent in a separate INVITE. Can't it be
> sent as a response to snapshot request from SRS ? Is there a reason why
> you want to mandate that way ?
> 
> Ram
> 
>> 
>> Leon
>> 
>> 
>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>> 
>>> Partha Thanks
>>> 
>>> Please see below
>>> 
>>> Leon
>>> 
>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>> 
>>>> Leon,
>>>> 
>>>> Please read inline
>>>> 
>>>> Thanks
>>>> Partha
>>>> 
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>>>>> 
>>>>> 
>>>>> Partha Hi
>>>>> 
>>>>> Please see below
>>>>> 
>>>>> Regards
>>>>> 
>>>>> Leon
>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>> 
>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>> 
>>>>> [Leon] I am not sure that we want to emphasize MAY in this
> specific
>>>>> section, it is an over part.
>>>>> 
>>>> <partha> I'm not very sure whether it is appropriate to use "may"
> in
>> the specification.
>>>> </partha>
>>> 
>>> [Leon] I dont have any opinions on that
>>>> 
>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
>>>>> current audio.
>>>>> 
>>>>> [Leon] Yes, good catch. Thanks
>>>>>> 
>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note that
>> when
>>>>> a CS
>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>> metadata
>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>> currently.
>>>>>> 
>>>>> [Leon] Yes, it is not defined yet in metadata. We should rephrase
>> it to
>>>>> "may be conveyed in metadata"
>>>> <partha> Currently, it is outside the scope of metadata and IMO, it
>> is better
>>>> to remove "mute/unmute" from protocol spec </partha>
>>> 
>>> [Leon] I agree, Henry, what do you think?
>>>> 
>>>>>> 4) Whether the normative statement required for mute? Sec 6.1.1
>>>>>> "The SRC SHOULD not modify the media stream with
>>>>>> a=inactive for mute since this operation is reserved for pausing
>> the
>>>>>> RS media."
>>>>>> 
>>>>> [Leon] It is related to point #3 that "mute" should not be handled
>> like
>>>>> "hold"
>>>>> 
>>>> <partha> IMO, there should be no normative statement related to
> mute
>> </partha>
>>>> 
>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>> delivery
>>>>> which shall
>>>>>> be avoided.
>>>>> 
>>>>> [Leon] 4.2 is the overview section. We could have some repetition
>> here
>>>>> with detailed sections.
>>>>>> 
>>>> <partha> I can live with incase everybody wants with duplication on
>> text
>>>> </partha>
>>>> 
>>>>>> 6) content type shall be "application/rs-metadata+xml" instead of
>>>>>> current "application/rs-metadata"
>>>>>> 
>>>>> [Leon] I am ok with that
>>>>>> 7) full metadata snapshot shall be passed across using UPDATE as
>> well.
>>>>>> But the current statement on Sec 8.1 misleading "When the SRC
>> sends a
>>>>> full metadata snapshot, the SRC MUST
>>>>>> send an INVITE request with an SDP offer and the "recording-
>> session"
>>>>>> disposition."
>>>>>> 
>>>>> [Leon] I remember having discussion to mandate INVITE in order to
>> make
>>>>> sure that SDP will be present as well. Dont have any strong
>> preferences
>>>>> here.
>>>>> 
>>>> <partha> We had the discussion during IETF-80 to mandate INVITE &
>> UPDATE.
>>>> But I could not find the reason for not using UPDATE for full
>> snapshot
>>>> Request </partha>
>>> 
>>> [Leon] I am ok with both
>>>> 
>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
>> SIP
>>>>>> header or clear indication within the message to indicate
> metadata
>>>>> request. Also, reason for logging could be mentioned explicitly
>> like
>>>>> "logging: SRS internal error"
>>>>>> 
>>>>> [Leon]  I am ok with that. Any opinions?
>>>>> 
>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation
> of
>>>>>> logging text from SRS for the generic request
>>>>> 
>>>>> [Leon] Please elaborate.
>>>>>> 
>>>> <partha> Currently, it is plain text now whereas SRC has no means
> to
>>>> understand about  the logs. Some guidelines/suggestion about the
>> text
>>>> helps for the implementation by which SRC understand. </partha>
>>>>>> Thanks
>>>>>> Partha
>>>>>> _______________________________________________
>>>>>> 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


From leon.portman@gmail.com  Tue Nov 15 19:16:24 2011
Return-Path: <leon.portman@gmail.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 47CF911E80B0 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:16:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBnRZJwImHbS for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:16:22 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 41F1821F903D for <siprec@ietf.org>; Tue, 15 Nov 2011 19:16:22 -0800 (PST)
Received: by ywt34 with SMTP id 34so7233918ywt.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 19:16:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=FbWGxrRFyVpPVeYivWVcHFf5DuFoppan1nGSo2TfgRc=; b=HyZY9+yWUSvd30Id7F7yQ+vqRVNiimYnyJG9MBiBdkRXPYBJlgjzNrBKJFyasrsASY cshv3ghbLpbUTdgmMYnWNiJ7aCtHKDJfa4eWP0AVVb8KQ8iEheDrkos8N7UplwWeAT02 DdPWQ9gYPM4akn5c4JDj3XuBVZE6BdplhJF2g=
Received: by 10.101.197.3 with SMTP id z3mr9017822anp.136.1321413381651; Tue, 15 Nov 2011 19:16:21 -0800 (PST)
Received: from dhcp-1398.meeting.ietf.org (dhcp-1398.meeting.ietf.org. [130.129.19.152]) by mx.google.com with ESMTPS id 22sm80747111anp.12.2011.11.15.19.16.19 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 19:16:20 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com>
Date: Wed, 16 Nov 2011 11:16:18 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 03:16:24 -0000

Patha

Please see below

Leon

On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:

> Leon,
>=20
> I agree with Ram.
>=20
> It is possible to debate on this normative statement requirement as=20
> multiple way to request the full snapshot from SRS. Some of the way
> from SRS are as follows:
>=20
> 1) REVITE without SDP and siprec-metdata-request body (3 SIP messages)
In this case, is it legal for SRC to answer SDP less INVITE with SDP? =
Snapshot requires SDP
> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP messages)
What if SRS does not have SDP?
> 3) UPDATE without SDP and SIPREC-metadata-request body and
>   Separate (4 SIP messages)
>=20
> IIUC, current SIPREC protocol mechanism propose to use only OPTION 3
> but I prefer to have the implementation choice. As mentioned above,=20
> OPTION 1 & 2 has less SIP message required to achieve the same compare
> to OPTION 3. Hope this clarifies.
>=20
> Thanks
> Partha
>=20
>> -----Original Message-----
>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>> Sent: Wednesday, November 16, 2011 10:56 AM
>> To: Leon Portman; Ravindran, Parthasarathi; henry.lum@genesyslab.com
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>=20
>> Leon,
>>=20
>> Please see inline. I have a question here
>>=20
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf Of Leon Portman
>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>> Cc: siprec@ietf.org
>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>=20
>>> Additional update on sending full metadata snapshot upon SRS =
request.
>>>=20
>>> In section 8.2 we say:
>>>=20
>>> "   When the SRC receives the request for a metadata snapshot, the =
SRC
>>>   MUST provide a full metadata snapshot in a separate INVITE
>>>   transaction, along with an SDP offer."
>>>=20
>>> meaning that full metadata is actually separate INVITE transaction.
>>=20
>> Why should the snapshot be always sent in a separate INVITE. Can't it =
be
>> sent as a response to snapshot request from SRS ? Is there a reason =
why
>> you want to mandate that way ?
>>=20
>> Ram
>>=20
>>>=20
>>> Leon
>>>=20
>>>=20
>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>=20
>>>> Partha Thanks
>>>>=20
>>>> Please see below
>>>>=20
>>>> Leon
>>>>=20
>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>=20
>>>>> Leon,
>>>>>=20
>>>>> Please read inline
>>>>>=20
>>>>> Thanks
>>>>> Partha
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>> Cc: siprec@ietf.org
>>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>=20
>>>>>>=20
>>>>>> Partha Hi
>>>>>>=20
>>>>>> Please see below
>>>>>>=20
>>>>>> Regards
>>>>>>=20
>>>>>> Leon
>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>>>=20
>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>=20
>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>> specific
>>>>>> section, it is an over part.
>>>>>>=20
>>>>> <partha> I'm not very sure whether it is appropriate to use "may"
>> in
>>> the specification.
>>>>> </partha>
>>>>=20
>>>> [Leon] I dont have any opinions on that
>>>>>=20
>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video instead =
of
>>>>>> current audio.
>>>>>>=20
>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>=20
>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note =
that
>>> when
>>>>>> a CS
>>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>>> metadata
>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>> currently.
>>>>>>>=20
>>>>>> [Leon] Yes, it is not defined yet in metadata. We should rephrase
>>> it to
>>>>>> "may be conveyed in metadata"
>>>>> <partha> Currently, it is outside the scope of metadata and IMO, =
it
>>> is better
>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>=20
>>>> [Leon] I agree, Henry, what do you think?
>>>>>=20
>>>>>>> 4) Whether the normative statement required for mute? Sec 6.1.1
>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive =
for
>>>>>>> mute since this operation is reserved for pausing
>>> the
>>>>>>> RS media."
>>>>>>>=20
>>>>>> [Leon] It is related to point #3 that "mute" should not be =
handled
>>> like
>>>>>> "hold"
>>>>>>=20
>>>>> <partha> IMO, there should be no normative statement related to
>> mute
>>> </partha>
>>>>>=20
>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>>> delivery
>>>>>> which shall
>>>>>>> be avoided.
>>>>>>=20
>>>>>> [Leon] 4.2 is the overview section. We could have some repetition
>>> here
>>>>>> with detailed sections.
>>>>>>>=20
>>>>> <partha> I can live with incase everybody wants with duplication =
on
>>> text
>>>>> </partha>
>>>>>=20
>>>>>>> 6) content type shall be "application/rs-metadata+xml" instead =
of
>>>>>>> current "application/rs-metadata"
>>>>>>>=20
>>>>>> [Leon] I am ok with that
>>>>>>> 7) full metadata snapshot shall be passed across using UPDATE as
>>> well.
>>>>>>> But the current statement on Sec 8.1 misleading "When the SRC
>>> sends a
>>>>>> full metadata snapshot, the SRC MUST
>>>>>>> send an INVITE request with an SDP offer and the "recording-
>>> session"
>>>>>>> disposition."
>>>>>>>=20
>>>>>> [Leon] I remember having discussion to mandate INVITE in order to
>>> make
>>>>>> sure that SDP will be present as well. Dont have any strong
>>> preferences
>>>>>> here.
>>>>>>=20
>>>>> <partha> We had the discussion during IETF-80 to mandate INVITE &
>>> UPDATE.
>>>>> But I could not find the reason for not using UPDATE for full
>>> snapshot
>>>>> Request </partha>
>>>>=20
>>>> [Leon] I am ok with both
>>>>>=20
>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
>>> SIP
>>>>>>> header or clear indication within the message to indicate
>> metadata
>>>>>> request. Also, reason for logging could be mentioned explicitly
>>> like
>>>>>> "logging: SRS internal error"
>>>>>>>=20
>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>=20
>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation
>> of
>>>>>>> logging text from SRS for the generic request
>>>>>>=20
>>>>>> [Leon] Please elaborate.
>>>>>>>=20
>>>>> <partha> Currently, it is plain text now whereas SRC has no means
>> to
>>>>> understand about  the logs. Some guidelines/suggestion about the
>>> text
>>>>> helps for the implementation by which SRC understand. </partha>
>>>>>>> Thanks
>>>>>>> Partha
>>>>>>> _______________________________________________
>>>>>>> siprec mailing list
>>>>>>> siprec@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>=20
>>>>=20
>>>=20
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec


From rmohanr@cisco.com  Tue Nov 15 19:21:50 2011
Return-Path: <rmohanr@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 3482811E8117 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:21:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.841
X-Spam-Level: 
X-Spam-Status: No, score=-8.841 tagged_above=-999 required=5 tests=[AWL=1.158,  BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LywQ6mWCD8Xs for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:21:46 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 558CE11E80D4 for <siprec@ietf.org>; Tue, 15 Nov 2011 19:21:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=5469; q=dns/txt; s=iport; t=1321413705; x=1322623305; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=7Oo0BDJ4u+LknhMtHQyrheRRFukn2XUiXfExe6DrA78=; b=IbPBD9vkXgcCn9xq/zOhksrSInJXMHtl7xQDsf7QN5ecLGtfI5zPl7K4 IMDJ9wZLq9ymAwm563944cXiKKf++pRrUhpeXIS6QTb2B/vaWmt6C4qwn 0TFWZbW/ZQmiro1lG3Otj5MYm2GWn7EjJolVCulRx0FFJgbSQl26LvMcx Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnsAAJ8rw05Io8UR/2dsb2JhbABDmWqQCIEFgXIBAQEDAQEBAQ8BHQo0CwUHBAIBCBEEAQEBCgYXAQYBIAYfCQgBAQQBCggIGodgCJoyAZ5VBIk0YwSIEpFmhQeHOQ
X-IronPort-AV: E=Sophos;i="4.69,518,1315180800"; d="scan'208";a="59942771"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-2.cisco.com with ESMTP; 16 Nov 2011 03:21:43 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAG3LgiV015676; Wed, 16 Nov 2011 03:21:42 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 08:51:42 +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, 16 Nov 2011 08:51:40 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD086526CA@XMB-BGL-417.cisco.com>
In-Reply-To: <B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: Acyj/qv77sGvhNFrRPiIQeVemmDdowADSjaA
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com> <B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <leon.portman@gmail.com>, "Parthasarathi Ravindran" <pravindran@sonusnet.com>, <henry.lum@genesyslab.com>
X-OriginalArrivalTime: 16 Nov 2011 03:21:42.0504 (UTC) FILETIME=[DCA28E80:01CCA40E]
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 03:21:50 -0000

Hi Leon,

A comment on this point

>> [Leon] Yes, it is not defined yet in metadata. We should rephrase it=20
>> to "may be conveyed in metadata"
> <partha> Currently, it is outside the scope of metadata and IMO, it is

> better to remove "mute/unmute" from protocol spec </partha>

[Leon] I agree, Henry, what do you think?

IMO mute/unmute is a property of a device and it is better not to map it
to signaling. SRS could use alternate mechanisms to detect no media. I
would prefer it keep it outside the scope of SIPREC.
An SRC that has the capability to do this may send the information as an
extension data.

Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> Sent: Wednesday, November 16, 2011 9:26 AM
> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>=20
> Partha Thanks
>=20
> Please see below
>=20
> Leon
>=20
> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>=20
> > Leon,
> >
> > Please read inline
> >
> > Thanks
> > Partha
> >
> >> -----Original Message-----
> >> From: Leon Portman [mailto:leon.portman@gmail.com]
> >> Sent: Tuesday, November 15, 2011 1:03 PM
> >> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
> >> Cc: siprec@ietf.org
> >> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
> >>
> >>
> >> Partha Hi
> >>
> >> Please see below
> >>
> >> Regards
> >>
> >> Leon
> >> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
> >>
> >>> 1) "may" is used instead of normative statement "MAY".
> >>>  a) Sec 4.2 Para 1 Line 2
> >>>  b) Sec 4.2 Para 3 Line 5
> >>>
> >> [Leon] I am not sure that we want to emphasize MAY in this specific
> >> section, it is an over part.
> >>
> > <partha> I'm not very sure whether it is appropriate to use "may" in
> the specification.
> > </partha>
>=20
> [Leon] I dont have any opinions on that
> >
> >>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
> >> current audio.
> >>
> >> [Leon] Yes, good catch. Thanks
> >>>
> >>> 3) Please clarify the following statement in Sec 6.1.1 "Note that
> when
> >> a CS
> >>>  stream is muted/unmuted, this information is conveyed in the
> >> metadata
> >>>  by the SRC. " because I don't know how metadata convey this
> >> currently.
> >>>
> >> [Leon] Yes, it is not defined yet in metadata. We should rephrase
it
> to
> >> "may be conveyed in metadata"
> > <partha> Currently, it is outside the scope of metadata and IMO, it
> is better
> > to remove "mute/unmute" from protocol spec </partha>
>=20
> [Leon] I agree, Henry, what do you think?
> >
> >>> 4) Whether the normative statement required for mute? Sec 6.1.1
> >>>  "The SRC SHOULD not modify the media stream with
> >>>  a=3Dinactive for mute since this operation is reserved for =
pausing
> the
> >>>  RS media."
> >>>
> >> [Leon] It is related to point #3 that "mute" should not be handled
> like
> >> "hold"
> >>
> > <partha> IMO, there should be no normative statement related to mute
> </partha>
> >
> >>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
> delivery
> >> which shall
> >>>  be avoided.
> >>
> >> [Leon] 4.2 is the overview section. We could have some repetition
> here
> >> with detailed sections.
> >>>
> > <partha> I can live with incase everybody wants with duplication on
> text
> > </partha>
> >
> >>> 6) content type shall be "application/rs-metadata+xml" instead of
> >>> current "application/rs-metadata"
> >>>
> >> [Leon] I am ok with that
> >>> 7) full metadata snapshot shall be passed across using UPDATE as
> well.
> >>> But the current statement on Sec 8.1 misleading "When the SRC
sends
> a
> >> full metadata snapshot, the SRC MUST
> >>>  send an INVITE request with an SDP offer and the "recording-
> session"
> >>>  disposition."
> >>>
> >> [Leon] I remember having discussion to mandate INVITE in order to
> make
> >> sure that SDP will be present as well. Dont have any strong
> preferences
> >> here.
> >>
> > <partha> We had the discussion during IETF-80 to mandate INVITE &
> UPDATE.
> > But I could not find the reason for not using UPDATE for full
> snapshot
> > Request </partha>
>=20
> [Leon] I am ok with both
> >
> >>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
> SIP
> >>> header or clear indication within the message to indicate metadata
> >> request. Also, reason for logging could be mentioned explicitly
like
> >> "logging: SRS internal error"
> >>>
> >> [Leon]  I am ok with that. Any opinions?
> >>
> >>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation of
> >>> logging text from SRS for the generic request
> >>
> >> [Leon] Please elaborate.
> >>>
> > <partha> Currently, it is plain text now whereas SRC has no means to
> > understand about  the logs. Some guidelines/suggestion about the
text
> > helps for the implementation by which SRC understand. </partha>
> >>> Thanks
> >>> Partha
> >>> _______________________________________________
> >>> siprec mailing list
> >>> siprec@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/siprec
> >
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From andrew.hutton@siemens-enterprise.com  Tue Nov 15 19:31:13 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 316E711E8099 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:31:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6NjQS6RkqZ4B for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:31:09 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id ED17111E80E7 for <siprec@ietf.org>; Tue, 15 Nov 2011 19:31:08 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id D7E351EB8442 for <siprec@ietf.org>; Wed, 16 Nov 2011 04:31:05 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 16 Nov 2011 04:31:05 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Wed, 16 Nov 2011 04:31:03 +0100
Thread-Topic: IETF82 SIPREC Presentations.
Thread-Index: AcykECsF3HqrC1v8SgGZl20Zmcn15w==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAB66368@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FAB66368MCHP058Agloba_"
MIME-Version: 1.0
Subject: [siprec] IETF82 SIPREC Presentations.
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, 16 Nov 2011 03:31:13 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAB66368MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

All SIPREC related presentations for tomorrows IETF82 SIPREC meeting have b=
een uploaded and are available at https://datatracker.ietf.org/meeting/82/m=
aterials.html

Regards
Andy


--_000_101C6067BEC68246B0C3F6843BCCC1E311FAB66368MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri, sans-serif" size=3D"2">
<div>Hi All,</div>
<div>&nbsp;</div>
<div>All SIPREC related presentations for tomorrows IETF82 SIPREC meeting h=
ave been uploaded and are available at <a href=3D"https://datatracker.ietf.=
org/meeting/82/materials.html"><font color=3D"#0000FF"><u>https://datatrack=
er.ietf.org/meeting/82/materials.html</u></font></a></div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Andy</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAB66368MCHP058Agloba_--

From pravindran@sonusnet.com  Tue Nov 15 19:31:34 2011
Return-Path: <pravindran@sonusnet.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 C7D8711E8167 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[AWL=-0.302, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WaCLJt21Ch6j for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 19:31:30 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 85C8D11E80B1 for <siprec@ietf.org>; Tue, 15 Nov 2011 19:31:30 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAG3W3OQ000422;  Tue, 15 Nov 2011 22:32:03 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 22:27:57 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 08:58:10 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Wed, 16 Nov 2011 08:58:10 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Leon Portman <leon.portman@gmail.com>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVCAAfdcAIAAFlAAgAAC/YD//6LIIIAAYtkA//+jbqA=
Date: Wed, 16 Nov 2011 03:28:09 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com>
In-Reply-To: <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Nov 2011 03:28:10.0877 (UTC) FILETIME=[C41F92D0:01CCA40F]
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 03:31:34 -0000

Leon,=20

Please read inline.

Thanks
Partha

>-----Original Message-----
>From: Leon Portman [mailto:leon.portman@gmail.com]
>Sent: Wednesday, November 16, 2011 11:16 AM
>To: Ravindran, Parthasarathi
>Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com; siprec@ietf.org
>Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>
>Patha
>
>Please see below
>
>Leon
>
>On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>
>> Leon,
>>
>> I agree with Ram.
>>
>> It is possible to debate on this normative statement requirement as
>> multiple way to request the full snapshot from SRS. Some of the way
>> from SRS are as follows:
>>
>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP messages)
>In this case, is it legal for SRC to answer SDP less INVITE with SDP?
>Snapshot requires SDP
<partha> AFAIK, Re-INVITE without SDP is used to get offer from the remote
Side. Even Hadriel mail threads says the same. Could you please point out=20
RFC 3261 Section to point how RE-INVITE without offer/answer work? </partha=
>


>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP messages)
>What if SRS does not have SDP?
<partha> In that case, it will end-up in OPTION 1 or 3 but please note that
It is possible to SRS to send SDP in case it has the idea of what has to be
Recorded. </partha>


>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>   Separate (4 SIP messages)
>>

<partha> I have started thinking whether it is appropriate for UPDATE from =
SRC
to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the proposal =
mandates
action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas UPDATE is =
not
designed for that. I may be wrong here but we need careful analysis here </=
partha>

>> IIUC, current SIPREC protocol mechanism propose to use only OPTION 3
>> but I prefer to have the implementation choice. As mentioned above,
>> OPTION 1 & 2 has less SIP message required to achieve the same compare
>> to OPTION 3. Hope this clarifies.
>>
>> Thanks
>> Partha
>>
>>> -----Original Message-----
>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>> To: Leon Portman; Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>
>>> Leon,
>>>
>>> Please see inline. I have a question here
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>> Behalf Of Leon Portman
>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>
>>>> Additional update on sending full metadata snapshot upon SRS
>request.
>>>>
>>>> In section 8.2 we say:
>>>>
>>>> "   When the SRC receives the request for a metadata snapshot, the
>SRC
>>>>   MUST provide a full metadata snapshot in a separate INVITE
>>>>   transaction, along with an SDP offer."
>>>>
>>>> meaning that full metadata is actually separate INVITE transaction.
>>>
>>> Why should the snapshot be always sent in a separate INVITE. Can't it
>>> be sent as a response to snapshot request from SRS ? Is there a
>>> reason why you want to mandate that way ?
>>>
>>> Ram
>>>
>>>>
>>>> Leon
>>>>
>>>>
>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>
>>>>> Partha Thanks
>>>>>
>>>>> Please see below
>>>>>
>>>>> Leon
>>>>>
>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>
>>>>>> Leon,
>>>>>>
>>>>>> Please read inline
>>>>>>
>>>>>> Thanks
>>>>>> Partha
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>> Cc: siprec@ietf.org
>>>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>
>>>>>>>
>>>>>>> Partha Hi
>>>>>>>
>>>>>>> Please see below
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Leon
>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>>>>
>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>
>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>> specific
>>>>>>> section, it is an over part.
>>>>>>>
>>>>>> <partha> I'm not very sure whether it is appropriate to use "may"
>>> in
>>>> the specification.
>>>>>> </partha>
>>>>>
>>>>> [Leon] I dont have any opinions on that
>>>>>>
>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video instead
>>>>>>>> of
>>>>>>> current audio.
>>>>>>>
>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>
>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note
>>>>>>>> that
>>>> when
>>>>>>> a CS
>>>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>>>> metadata
>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>> currently.
>>>>>>>>
>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should rephrase
>>>> it to
>>>>>>> "may be conveyed in metadata"
>>>>>> <partha> Currently, it is outside the scope of metadata and IMO,
>>>>>> it
>>>> is better
>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>
>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>
>>>>>>>> 4) Whether the normative statement required for mute? Sec 6.1.1
>>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive for
>>>>>>>> mute since this operation is reserved for pausing
>>>> the
>>>>>>>> RS media."
>>>>>>>>
>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>> handled
>>>> like
>>>>>>> "hold"
>>>>>>>
>>>>>> <partha> IMO, there should be no normative statement related to
>>> mute
>>>> </partha>
>>>>>>
>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>>>> delivery
>>>>>>> which shall
>>>>>>>> be avoided.
>>>>>>>
>>>>>>> [Leon] 4.2 is the overview section. We could have some repetition
>>>> here
>>>>>>> with detailed sections.
>>>>>>>>
>>>>>> <partha> I can live with incase everybody wants with duplication
>>>>>> on
>>>> text
>>>>>> </partha>
>>>>>>
>>>>>>>> 6) content type shall be "application/rs-metadata+xml" instead
>>>>>>>> of current "application/rs-metadata"
>>>>>>>>
>>>>>>> [Leon] I am ok with that
>>>>>>>> 7) full metadata snapshot shall be passed across using UPDATE as
>>>> well.
>>>>>>>> But the current statement on Sec 8.1 misleading "When the SRC
>>>> sends a
>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>> send an INVITE request with an SDP offer and the "recording-
>>>> session"
>>>>>>>> disposition."
>>>>>>>>
>>>>>>> [Leon] I remember having discussion to mandate INVITE in order to
>>>> make
>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>> preferences
>>>>>>> here.
>>>>>>>
>>>>>> <partha> We had the discussion during IETF-80 to mandate INVITE &
>>>> UPDATE.
>>>>>> But I could not find the reason for not using UPDATE for full
>>>> snapshot
>>>>>> Request </partha>
>>>>>
>>>>> [Leon] I am ok with both
>>>>>>
>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
>>>> SIP
>>>>>>>> header or clear indication within the message to indicate
>>> metadata
>>>>>>> request. Also, reason for logging could be mentioned explicitly
>>>> like
>>>>>>> "logging: SRS internal error"
>>>>>>>>
>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>
>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation
>>> of
>>>>>>>> logging text from SRS for the generic request
>>>>>>>
>>>>>>> [Leon] Please elaborate.
>>>>>>>>
>>>>>> <partha> Currently, it is plain text now whereas SRC has no means
>>> to
>>>>>> understand about  the logs. Some guidelines/suggestion about the
>>>> text
>>>>>> helps for the implementation by which SRC understand. </partha>
>>>>>>>> Thanks
>>>>>>>> Partha
>>>>>>>> _______________________________________________
>>>>>>>> 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


From leon.portman@gmail.com  Tue Nov 15 21:34:18 2011
Return-Path: <leon.portman@gmail.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 9B5421F0CD5 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 21:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.179
X-Spam-Level: 
X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rTHV7EV+kr91 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 21:34:13 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5071F0C95 for <siprec@ietf.org>; Tue, 15 Nov 2011 21:34:12 -0800 (PST)
Received: by ggnr5 with SMTP id r5so3598125ggn.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 21:34:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=9HJF4ftNJ187fs+Y+foTnCZy28MaplUF9H3FA1HVZKE=; b=QJ2rRWcxH/8esa6IqnZoQuN6V8pi9eZyuY7GMGmA5I4fM85mhjmUDvQNGaJnN/XdG6 gJ0QMvT966kv7spgwj7B0Xp2LLG29mpgIG0RrTV/nFJ9B6ET8Pr7ZKoAB3Jwu2l3Sggj 5l8f4lTgyjJ6WOlzWScsq8XYZ8GH1BchhEXq8=
Received: by 10.101.54.9 with SMTP id g9mr3332905ank.50.1321421652637; Tue, 15 Nov 2011 21:34:12 -0800 (PST)
Received: from ?IPv6:2001:df8::16:f96b:4437:5128:9c18? ([2001:df8:0:16:f96b:4437:5128:9c18]) by mx.google.com with ESMTPS id l18sm53041441anb.22.2011.11.15.21.34.10 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 21:34:12 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com>
Date: Wed, 16 Nov 2011 13:34:10 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 05:34:18 -0000

If offer-less REINVITE works (it seems to be) i dont have problem with =
supporting option 1 as well. Any SIP experts opinions?

Leon

On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:

> Leon,=20
>=20
> Please read inline.
>=20
> Thanks
> Partha
>=20
>> -----Original Message-----
>> From: Leon Portman [mailto:leon.portman@gmail.com]
>> Sent: Wednesday, November 16, 2011 11:16 AM
>> To: Ravindran, Parthasarathi
>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com; siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>=20
>> Patha
>>=20
>> Please see below
>>=20
>> Leon
>>=20
>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>=20
>>> Leon,
>>>=20
>>> I agree with Ram.
>>>=20
>>> It is possible to debate on this normative statement requirement as
>>> multiple way to request the full snapshot from SRS. Some of the way
>>> from SRS are as follows:
>>>=20
>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP =
messages)
>> In this case, is it legal for SRC to answer SDP less INVITE with SDP?
>> Snapshot requires SDP
> <partha> AFAIK, Re-INVITE without SDP is used to get offer from the =
remote
> Side. Even Hadriel mail threads says the same. Could you please point =
out=20
> RFC 3261 Section to point how RE-INVITE without offer/answer work? =
</partha>
>=20
>=20
>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP messages)
>> What if SRS does not have SDP?
> <partha> In that case, it will end-up in OPTION 1 or 3 but please note =
that
> It is possible to SRS to send SDP in case it has the idea of what has =
to be
> Recorded. </partha>
>=20
>=20
>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>  Separate (4 SIP messages)
>>>=20
>=20
> <partha> I have started thinking whether it is appropriate for UPDATE =
from SRC
> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the =
proposal mandates
> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas =
UPDATE is not
> designed for that. I may be wrong here but we need careful analysis =
here </partha>
>=20
>>> IIUC, current SIPREC protocol mechanism propose to use only OPTION 3
>>> but I prefer to have the implementation choice. As mentioned above,
>>> OPTION 1 & 2 has less SIP message required to achieve the same =
compare
>>> to OPTION 3. Hope this clarifies.
>>>=20
>>> Thanks
>>> Partha
>>>=20
>>>> -----Original Message-----
>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>> To: Leon Portman; Ravindran, Parthasarathi; =
henry.lum@genesyslab.com
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>=20
>>>> Leon,
>>>>=20
>>>> Please see inline. I have a question here
>>>>=20
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>> Behalf Of Leon Portman
>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>=20
>>>>> Additional update on sending full metadata snapshot upon SRS
>> request.
>>>>>=20
>>>>> In section 8.2 we say:
>>>>>=20
>>>>> "   When the SRC receives the request for a metadata snapshot, the
>> SRC
>>>>>  MUST provide a full metadata snapshot in a separate INVITE
>>>>>  transaction, along with an SDP offer."
>>>>>=20
>>>>> meaning that full metadata is actually separate INVITE =
transaction.
>>>>=20
>>>> Why should the snapshot be always sent in a separate INVITE. Can't =
it
>>>> be sent as a response to snapshot request from SRS ? Is there a
>>>> reason why you want to mandate that way ?
>>>>=20
>>>> Ram
>>>>=20
>>>>>=20
>>>>> Leon
>>>>>=20
>>>>>=20
>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>=20
>>>>>> Partha Thanks
>>>>>>=20
>>>>>> Please see below
>>>>>>=20
>>>>>> Leon
>>>>>>=20
>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>=20
>>>>>>> Leon,
>>>>>>>=20
>>>>>>> Please read inline
>>>>>>>=20
>>>>>>> Thanks
>>>>>>> Partha
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Partha Hi
>>>>>>>>=20
>>>>>>>> Please see below
>>>>>>>>=20
>>>>>>>> Regards
>>>>>>>>=20
>>>>>>>> Leon
>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>>>>>=20
>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>=20
>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>> specific
>>>>>>>> section, it is an over part.
>>>>>>>>=20
>>>>>>> <partha> I'm not very sure whether it is appropriate to use =
"may"
>>>> in
>>>>> the specification.
>>>>>>> </partha>
>>>>>>=20
>>>>>> [Leon] I dont have any opinions on that
>>>>>>>=20
>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video instead
>>>>>>>>> of
>>>>>>>> current audio.
>>>>>>>>=20
>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>=20
>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note
>>>>>>>>> that
>>>>> when
>>>>>>>> a CS
>>>>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>>>>> metadata
>>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>>> currently.
>>>>>>>>>=20
>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should =
rephrase
>>>>> it to
>>>>>>>> "may be conveyed in metadata"
>>>>>>> <partha> Currently, it is outside the scope of metadata and IMO,
>>>>>>> it
>>>>> is better
>>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>>=20
>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>=20
>>>>>>>>> 4) Whether the normative statement required for mute? Sec =
6.1.1
>>>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive =
for
>>>>>>>>> mute since this operation is reserved for pausing
>>>>> the
>>>>>>>>> RS media."
>>>>>>>>>=20
>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>> handled
>>>>> like
>>>>>>>> "hold"
>>>>>>>>=20
>>>>>>> <partha> IMO, there should be no normative statement related to
>>>> mute
>>>>> </partha>
>>>>>>>=20
>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>>>>> delivery
>>>>>>>> which shall
>>>>>>>>> be avoided.
>>>>>>>>=20
>>>>>>>> [Leon] 4.2 is the overview section. We could have some =
repetition
>>>>> here
>>>>>>>> with detailed sections.
>>>>>>>>>=20
>>>>>>> <partha> I can live with incase everybody wants with duplication
>>>>>>> on
>>>>> text
>>>>>>> </partha>
>>>>>>>=20
>>>>>>>>> 6) content type shall be "application/rs-metadata+xml" instead
>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>=20
>>>>>>>> [Leon] I am ok with that
>>>>>>>>> 7) full metadata snapshot shall be passed across using UPDATE =
as
>>>>> well.
>>>>>>>>> But the current statement on Sec 8.1 misleading "When the SRC
>>>>> sends a
>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>> send an INVITE request with an SDP offer and the "recording-
>>>>> session"
>>>>>>>>> disposition."
>>>>>>>>>=20
>>>>>>>> [Leon] I remember having discussion to mandate INVITE in order =
to
>>>>> make
>>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>>> preferences
>>>>>>>> here.
>>>>>>>>=20
>>>>>>> <partha> We had the discussion during IETF-80 to mandate INVITE =
&
>>>>> UPDATE.
>>>>>>> But I could not find the reason for not using UPDATE for full
>>>>> snapshot
>>>>>>> Request </partha>
>>>>>>=20
>>>>>> [Leon] I am ok with both
>>>>>>>=20
>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed =
as
>>>>> SIP
>>>>>>>>> header or clear indication within the message to indicate
>>>> metadata
>>>>>>>> request. Also, reason for logging could be mentioned explicitly
>>>>> like
>>>>>>>> "logging: SRS internal error"
>>>>>>>>>=20
>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>=20
>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any =
recommendation
>>>> of
>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>=20
>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>=20
>>>>>>> <partha> Currently, it is plain text now whereas SRC has no =
means
>>>> to
>>>>>>> understand about  the logs. Some guidelines/suggestion about the
>>>>> text
>>>>>>> helps for the implementation by which SRC understand. </partha>
>>>>>>>>> Thanks
>>>>>>>>> Partha
>>>>>>>>> _______________________________________________
>>>>>>>>> siprec mailing list
>>>>>>>>> siprec@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> siprec mailing list
>>>>> siprec@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/siprec
>=20


From leon.portman@gmail.com  Tue Nov 15 21:41:09 2011
Return-Path: <leon.portman@gmail.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 D65D51F0CF8 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 21:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.074
X-Spam-Level: 
X-Spam-Status: No, score=-3.074 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cpgea5Yc9cZK for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 21:41:05 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6E70F1F0CF5 for <siprec@ietf.org>; Tue, 15 Nov 2011 21:41:02 -0800 (PST)
Received: by yenq4 with SMTP id q4so5971326yen.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 21:41:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=4ixVRyVTZ+7nHX4pdSbW758elElSHWZXRGmrXWcnYmU=; b=BpfEZu56DbELLOE/xKuufYuz1+6ugoP4ytZvOOXZsD/FxJGLmFJp3RnXTRWr7qnbnw h/ffFJt2CQp5mg4jIgv9s5zR672pXZU0jizhNFG4RSM1lNS5uZFfcowDZLjoBO0rgNvk TsvQhFWEtfQaUmFz0890vvrL5+PVXbNeX/9/0=
Received: by 10.100.22.16 with SMTP id 16mr5394318anv.48.1321422061947; Tue, 15 Nov 2011 21:41:01 -0800 (PST)
Received: from dhcp-1398.meeting.ietf.org (dhcp-1398.meeting.ietf.org. [130.129.19.152]) by mx.google.com with ESMTPS id m33sm82155211ann.4.2011.11.15.21.40.59 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 21:41:01 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com>
Date: Wed, 16 Nov 2011 13:40:58 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1CD4DCD-03F1-471B-8A9A-F699EB9F0AB4@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 05:41:10 -0000

Most important from SRS point of view, is to define a mechanism for =
snapshot request that will not terminate recording session even for =
shortest possible time.

My concern is if new INVITE will do that.

Leon

On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:

> If offer-less REINVITE works (it seems to be) i dont have problem with =
supporting option 1 as well. Any SIP experts opinions?
>=20
> Leon
>=20
> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>=20
>> Leon,=20
>>=20
>> Please read inline.
>>=20
>> Thanks
>> Partha
>>=20
>>> -----Original Message-----
>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>> To: Ravindran, Parthasarathi
>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com; siprec@ietf.org
>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>=20
>>> Patha
>>>=20
>>> Please see below
>>>=20
>>> Leon
>>>=20
>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>=20
>>>> Leon,
>>>>=20
>>>> I agree with Ram.
>>>>=20
>>>> It is possible to debate on this normative statement requirement as
>>>> multiple way to request the full snapshot from SRS. Some of the way
>>>> from SRS are as follows:
>>>>=20
>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP =
messages)
>>> In this case, is it legal for SRC to answer SDP less INVITE with =
SDP?
>>> Snapshot requires SDP
>> <partha> AFAIK, Re-INVITE without SDP is used to get offer from the =
remote
>> Side. Even Hadriel mail threads says the same. Could you please point =
out=20
>> RFC 3261 Section to point how RE-INVITE without offer/answer work? =
</partha>
>>=20
>>=20
>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP =
messages)
>>> What if SRS does not have SDP?
>> <partha> In that case, it will end-up in OPTION 1 or 3 but please =
note that
>> It is possible to SRS to send SDP in case it has the idea of what has =
to be
>> Recorded. </partha>
>>=20
>>=20
>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>> Separate (4 SIP messages)
>>>>=20
>>=20
>> <partha> I have started thinking whether it is appropriate for UPDATE =
from SRC
>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the =
proposal mandates
>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas =
UPDATE is not
>> designed for that. I may be wrong here but we need careful analysis =
here </partha>
>>=20
>>>> IIUC, current SIPREC protocol mechanism propose to use only OPTION =
3
>>>> but I prefer to have the implementation choice. As mentioned above,
>>>> OPTION 1 & 2 has less SIP message required to achieve the same =
compare
>>>> to OPTION 3. Hope this clarifies.
>>>>=20
>>>> Thanks
>>>> Partha
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>> To: Leon Portman; Ravindran, Parthasarathi; =
henry.lum@genesyslab.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>=20
>>>>> Leon,
>>>>>=20
>>>>> Please see inline. I have a question here
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>>> Behalf Of Leon Portman
>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>> Cc: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>=20
>>>>>> Additional update on sending full metadata snapshot upon SRS
>>> request.
>>>>>>=20
>>>>>> In section 8.2 we say:
>>>>>>=20
>>>>>> "   When the SRC receives the request for a metadata snapshot, =
the
>>> SRC
>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>> transaction, along with an SDP offer."
>>>>>>=20
>>>>>> meaning that full metadata is actually separate INVITE =
transaction.
>>>>>=20
>>>>> Why should the snapshot be always sent in a separate INVITE. Can't =
it
>>>>> be sent as a response to snapshot request from SRS ? Is there a
>>>>> reason why you want to mandate that way ?
>>>>>=20
>>>>> Ram
>>>>>=20
>>>>>>=20
>>>>>> Leon
>>>>>>=20
>>>>>>=20
>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>=20
>>>>>>> Partha Thanks
>>>>>>>=20
>>>>>>> Please see below
>>>>>>>=20
>>>>>>> Leon
>>>>>>>=20
>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>=20
>>>>>>>> Leon,
>>>>>>>>=20
>>>>>>>> Please read inline
>>>>>>>>=20
>>>>>>>> Thanks
>>>>>>>> Partha
>>>>>>>>=20
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>> Subject: Re: [sipprec] Comment on =
draft-ietf-siprec-protocol-02
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Partha Hi
>>>>>>>>>=20
>>>>>>>>> Please see below
>>>>>>>>>=20
>>>>>>>>> Regards
>>>>>>>>>=20
>>>>>>>>> Leon
>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>>>>>>=20
>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>=20
>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>> specific
>>>>>>>>> section, it is an over part.
>>>>>>>>>=20
>>>>>>>> <partha> I'm not very sure whether it is appropriate to use =
"may"
>>>>> in
>>>>>> the specification.
>>>>>>>> </partha>
>>>>>>>=20
>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>=20
>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video =
instead
>>>>>>>>>> of
>>>>>>>>> current audio.
>>>>>>>>>=20
>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>=20
>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note
>>>>>>>>>> that
>>>>>> when
>>>>>>>>> a CS
>>>>>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>>>>>> metadata
>>>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>>>> currently.
>>>>>>>>>>=20
>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should =
rephrase
>>>>>> it to
>>>>>>>>> "may be conveyed in metadata"
>>>>>>>> <partha> Currently, it is outside the scope of metadata and =
IMO,
>>>>>>>> it
>>>>>> is better
>>>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>>>=20
>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>=20
>>>>>>>>>> 4) Whether the normative statement required for mute? Sec =
6.1.1
>>>>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive =
for
>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>> the
>>>>>>>>>> RS media."
>>>>>>>>>>=20
>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>> handled
>>>>>> like
>>>>>>>>> "hold"
>>>>>>>>>=20
>>>>>>>> <partha> IMO, there should be no normative statement related to
>>>>> mute
>>>>>> </partha>
>>>>>>>>=20
>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>>>>>> delivery
>>>>>>>>> which shall
>>>>>>>>>> be avoided.
>>>>>>>>>=20
>>>>>>>>> [Leon] 4.2 is the overview section. We could have some =
repetition
>>>>>> here
>>>>>>>>> with detailed sections.
>>>>>>>>>>=20
>>>>>>>> <partha> I can live with incase everybody wants with =
duplication
>>>>>>>> on
>>>>>> text
>>>>>>>> </partha>
>>>>>>>>=20
>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml" =
instead
>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>=20
>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>> 7) full metadata snapshot shall be passed across using UPDATE =
as
>>>>>> well.
>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the SRC
>>>>>> sends a
>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>> send an INVITE request with an SDP offer and the "recording-
>>>>>> session"
>>>>>>>>>> disposition."
>>>>>>>>>>=20
>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in order =
to
>>>>>> make
>>>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>>>> preferences
>>>>>>>>> here.
>>>>>>>>>=20
>>>>>>>> <partha> We had the discussion during IETF-80 to mandate INVITE =
&
>>>>>> UPDATE.
>>>>>>>> But I could not find the reason for not using UPDATE for full
>>>>>> snapshot
>>>>>>>> Request </partha>
>>>>>>>=20
>>>>>>> [Leon] I am ok with both
>>>>>>>>=20
>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed =
as
>>>>>> SIP
>>>>>>>>>> header or clear indication within the message to indicate
>>>>> metadata
>>>>>>>>> request. Also, reason for logging could be mentioned =
explicitly
>>>>>> like
>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>=20
>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>=20
>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any =
recommendation
>>>>> of
>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>=20
>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>=20
>>>>>>>> <partha> Currently, it is plain text now whereas SRC has no =
means
>>>>> to
>>>>>>>> understand about  the logs. Some guidelines/suggestion about =
the
>>>>>> text
>>>>>>>> helps for the implementation by which SRC understand. </partha>
>>>>>>>>>> Thanks
>>>>>>>>>> Partha
>>>>>>>>>> _______________________________________________
>>>>>>>>>> siprec mailing list
>>>>>>>>>> siprec@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> siprec mailing list
>>>>>> siprec@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>=20
>=20


From leon.portman@gmail.com  Tue Nov 15 21:42:56 2011
Return-Path: <leon.portman@gmail.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 75CF31F0CF8 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 21:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.149
X-Spam-Level: 
X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMt7ecDKnG6N for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 21:42:52 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF491F0CF5 for <siprec@ietf.org>; Tue, 15 Nov 2011 21:42:51 -0800 (PST)
Received: by yenq4 with SMTP id q4so5973062yen.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 21:42:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=LYKj1UM12RcgXfvrhb7Y4nT7Hl+e15n9q5Lp/MNxWG0=; b=S9Al0KIhnYA7bbPBWIu0YgGLg9wfW1AGqMDdkUD1QW2fzpChNihFJ1xo/rKhpJHJMJ zmR8O3U7JihVXT+QD98Re0hJ7IIJlB+svJ6FBE7nDSuHHgz5gKlzbBJWDQ3cdYdF1V0u 9BQTIzp0fdz21NVxIxloCjTLTSjKkYkktbaVg=
Received: by 10.100.40.14 with SMTP id n14mr5905160ann.133.1321422171165; Tue, 15 Nov 2011 21:42:51 -0800 (PST)
Received: from ?IPv6:2001:df8::16:f96b:4437:5128:9c18? ([2001:df8:0:16:f96b:4437:5128:9c18]) by mx.google.com with ESMTPS id k20sm82119140ann.15.2011.11.15.21.42.49 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 21:42:50 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com>
Date: Wed, 16 Nov 2011 13:42:51 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 05:42:56 -0000

Most important from SRS point of view, is to define a mechanism for =
snapshot request that will not terminate recording session even for =
shortest possible time.

My concern is if new INVITE will do that

On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:

> If offer-less REINVITE works (it seems to be) i dont have problem with =
supporting option 1 as well. Any SIP experts opinions?
>=20
> Leon
>=20
> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>=20
>> Leon,=20
>>=20
>> Please read inline.
>>=20
>> Thanks
>> Partha
>>=20
>>> -----Original Message-----
>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>> To: Ravindran, Parthasarathi
>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com; siprec@ietf.org
>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>=20
>>> Patha
>>>=20
>>> Please see below
>>>=20
>>> Leon
>>>=20
>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>=20
>>>> Leon,
>>>>=20
>>>> I agree with Ram.
>>>>=20
>>>> It is possible to debate on this normative statement requirement as
>>>> multiple way to request the full snapshot from SRS. Some of the way
>>>> from SRS are as follows:
>>>>=20
>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP =
messages)
>>> In this case, is it legal for SRC to answer SDP less INVITE with =
SDP?
>>> Snapshot requires SDP
>> <partha> AFAIK, Re-INVITE without SDP is used to get offer from the =
remote
>> Side. Even Hadriel mail threads says the same. Could you please point =
out=20
>> RFC 3261 Section to point how RE-INVITE without offer/answer work? =
</partha>
>>=20
>>=20
>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP =
messages)
>>> What if SRS does not have SDP?
>> <partha> In that case, it will end-up in OPTION 1 or 3 but please =
note that
>> It is possible to SRS to send SDP in case it has the idea of what has =
to be
>> Recorded. </partha>
>>=20
>>=20
>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>> Separate (4 SIP messages)
>>>>=20
>>=20
>> <partha> I have started thinking whether it is appropriate for UPDATE =
from SRC
>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the =
proposal mandates
>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas =
UPDATE is not
>> designed for that. I may be wrong here but we need careful analysis =
here </partha>
>>=20
>>>> IIUC, current SIPREC protocol mechanism propose to use only OPTION =
3
>>>> but I prefer to have the implementation choice. As mentioned above,
>>>> OPTION 1 & 2 has less SIP message required to achieve the same =
compare
>>>> to OPTION 3. Hope this clarifies.
>>>>=20
>>>> Thanks
>>>> Partha
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>> To: Leon Portman; Ravindran, Parthasarathi; =
henry.lum@genesyslab.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>=20
>>>>> Leon,
>>>>>=20
>>>>> Please see inline. I have a question here
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>>> Behalf Of Leon Portman
>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>> Cc: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>=20
>>>>>> Additional update on sending full metadata snapshot upon SRS
>>> request.
>>>>>>=20
>>>>>> In section 8.2 we say:
>>>>>>=20
>>>>>> "   When the SRC receives the request for a metadata snapshot, =
the
>>> SRC
>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>> transaction, along with an SDP offer."
>>>>>>=20
>>>>>> meaning that full metadata is actually separate INVITE =
transaction.
>>>>>=20
>>>>> Why should the snapshot be always sent in a separate INVITE. Can't =
it
>>>>> be sent as a response to snapshot request from SRS ? Is there a
>>>>> reason why you want to mandate that way ?
>>>>>=20
>>>>> Ram
>>>>>=20
>>>>>>=20
>>>>>> Leon
>>>>>>=20
>>>>>>=20
>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>=20
>>>>>>> Partha Thanks
>>>>>>>=20
>>>>>>> Please see below
>>>>>>>=20
>>>>>>> Leon
>>>>>>>=20
>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>=20
>>>>>>>> Leon,
>>>>>>>>=20
>>>>>>>> Please read inline
>>>>>>>>=20
>>>>>>>> Thanks
>>>>>>>> Partha
>>>>>>>>=20
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>> Subject: Re: [sipprec] Comment on =
draft-ietf-siprec-protocol-02
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Partha Hi
>>>>>>>>>=20
>>>>>>>>> Please see below
>>>>>>>>>=20
>>>>>>>>> Regards
>>>>>>>>>=20
>>>>>>>>> Leon
>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>>>>>>=20
>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>=20
>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>> specific
>>>>>>>>> section, it is an over part.
>>>>>>>>>=20
>>>>>>>> <partha> I'm not very sure whether it is appropriate to use =
"may"
>>>>> in
>>>>>> the specification.
>>>>>>>> </partha>
>>>>>>>=20
>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>=20
>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video =
instead
>>>>>>>>>> of
>>>>>>>>> current audio.
>>>>>>>>>=20
>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>=20
>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note
>>>>>>>>>> that
>>>>>> when
>>>>>>>>> a CS
>>>>>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>>>>>> metadata
>>>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>>>> currently.
>>>>>>>>>>=20
>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should =
rephrase
>>>>>> it to
>>>>>>>>> "may be conveyed in metadata"
>>>>>>>> <partha> Currently, it is outside the scope of metadata and =
IMO,
>>>>>>>> it
>>>>>> is better
>>>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>>>=20
>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>=20
>>>>>>>>>> 4) Whether the normative statement required for mute? Sec =
6.1.1
>>>>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive =
for
>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>> the
>>>>>>>>>> RS media."
>>>>>>>>>>=20
>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>> handled
>>>>>> like
>>>>>>>>> "hold"
>>>>>>>>>=20
>>>>>>>> <partha> IMO, there should be no normative statement related to
>>>>> mute
>>>>>> </partha>
>>>>>>>>=20
>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>>>>>> delivery
>>>>>>>>> which shall
>>>>>>>>>> be avoided.
>>>>>>>>>=20
>>>>>>>>> [Leon] 4.2 is the overview section. We could have some =
repetition
>>>>>> here
>>>>>>>>> with detailed sections.
>>>>>>>>>>=20
>>>>>>>> <partha> I can live with incase everybody wants with =
duplication
>>>>>>>> on
>>>>>> text
>>>>>>>> </partha>
>>>>>>>>=20
>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml" =
instead
>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>=20
>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>> 7) full metadata snapshot shall be passed across using UPDATE =
as
>>>>>> well.
>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the SRC
>>>>>> sends a
>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>> send an INVITE request with an SDP offer and the "recording-
>>>>>> session"
>>>>>>>>>> disposition."
>>>>>>>>>>=20
>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in order =
to
>>>>>> make
>>>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>>>> preferences
>>>>>>>>> here.
>>>>>>>>>=20
>>>>>>>> <partha> We had the discussion during IETF-80 to mandate INVITE =
&
>>>>>> UPDATE.
>>>>>>>> But I could not find the reason for not using UPDATE for full
>>>>>> snapshot
>>>>>>>> Request </partha>
>>>>>>>=20
>>>>>>> [Leon] I am ok with both
>>>>>>>>=20
>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed =
as
>>>>>> SIP
>>>>>>>>>> header or clear indication within the message to indicate
>>>>> metadata
>>>>>>>>> request. Also, reason for logging could be mentioned =
explicitly
>>>>>> like
>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>=20
>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>=20
>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any =
recommendation
>>>>> of
>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>=20
>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>=20
>>>>>>>> <partha> Currently, it is plain text now whereas SRC has no =
means
>>>>> to
>>>>>>>> understand about  the logs. Some guidelines/suggestion about =
the
>>>>>> text
>>>>>>>> helps for the implementation by which SRC understand. </partha>
>>>>>>>>>> Thanks
>>>>>>>>>> Partha
>>>>>>>>>> _______________________________________________
>>>>>>>>>> siprec mailing list
>>>>>>>>>> siprec@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> siprec mailing list
>>>>>> siprec@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>=20
>=20


From andrew.hutton@siemens-enterprise.com  Tue Nov 15 22:25:06 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 B877D21F92AC for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0DLDtYt9Yh6B for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:25:02 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 315F121F92AA for <siprec@ietf.org>; Tue, 15 Nov 2011 22:25:02 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 4B16F1EB83FA; Wed, 16 Nov 2011 07:24:59 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 16 Nov 2011 07:24:59 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Leon Portman <leon.portman@gmail.com>, "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
Date: Wed, 16 Nov 2011 07:24:55 +0100
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcykIpoAssE0abxWRsi5cxqN75mBoAAAZeBw
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com>
In-Reply-To: <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 06:25:06 -0000

Hi,

If I understand this correctly the discussion is how should the SRS initiat=
e a snapshot from the SRC and how does this impact the offer/answer.

The snapshot has I believe to include both an SDP offer and the associated =
XML representing the metadata. The only way to initiate a new SDP offer wit=
hin the dialog is for the SRS to send a reINVITE without SDP to the SRC cau=
ses the SRC to respond with the SDP Offer and associated metadata snapshot =
in the 200OK which will of course cause the SRS to generate an SDP answer i=
n the ACK.

The SRS could also include an SDP offer in the reINVITE and have the SRC cr=
eate the answer.

In either case it should be that there is no change in the SDP from the pre=
vious offer/answer and therefore it is effectively a session refresh and do=
es not cause an media interruption.=20

Regards
Andy



> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> Sent: 16 November 2011 13:43
> To: Ravindran, Parthasarathi
> Cc: henry.lum@genesyslab.com; siprec@ietf.org
> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>=20
> Most important from SRS point of view, is to define a mechanism for
> snapshot request that will not terminate recording session even for
> shortest possible time.
>=20
> My concern is if new INVITE will do that
>=20
> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>=20
> > If offer-less REINVITE works (it seems to be) i dont have problem
> with supporting option 1 as well. Any SIP experts opinions?
> >
> > Leon
> >
> > On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
> >
> >> Leon,
> >>
> >> Please read inline.
> >>
> >> Thanks
> >> Partha
> >>
> >>> -----Original Message-----
> >>> From: Leon Portman [mailto:leon.portman@gmail.com]
> >>> Sent: Wednesday, November 16, 2011 11:16 AM
> >>> To: Ravindran, Parthasarathi
> >>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
> siprec@ietf.org
> >>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
> >>>
> >>> Patha
> >>>
> >>> Please see below
> >>>
> >>> Leon
> >>>
> >>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
> >>>
> >>>> Leon,
> >>>>
> >>>> I agree with Ram.
> >>>>
> >>>> It is possible to debate on this normative statement requirement
> as
> >>>> multiple way to request the full snapshot from SRS. Some of the
> way
> >>>> from SRS are as follows:
> >>>>
> >>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
> messages)
> >>> In this case, is it legal for SRC to answer SDP less INVITE with
> SDP?
> >>> Snapshot requires SDP
> >> <partha> AFAIK, Re-INVITE without SDP is used to get offer from the
> remote
> >> Side. Even Hadriel mail threads says the same. Could you please
> point out
> >> RFC 3261 Section to point how RE-INVITE without offer/answer work?
> </partha>
> >>
> >>
> >>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
> messages)
> >>> What if SRS does not have SDP?
> >> <partha> In that case, it will end-up in OPTION 1 or 3 but please
> note that
> >> It is possible to SRS to send SDP in case it has the idea of what
> has to be
> >> Recorded. </partha>
> >>
> >>
> >>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
> >>>> Separate (4 SIP messages)
> >>>>
> >>
> >> <partha> I have started thinking whether it is appropriate for
> UPDATE from SRC
> >> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
> proposal mandates
> >> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
> UPDATE is not
> >> designed for that. I may be wrong here but we need careful analysis
> here </partha>
> >>
> >>>> IIUC, current SIPREC protocol mechanism propose to use only OPTION
> 3
> >>>> but I prefer to have the implementation choice. As mentioned
> above,
> >>>> OPTION 1 & 2 has less SIP message required to achieve the same
> compare
> >>>> to OPTION 3. Hope this clarifies.
> >>>>
> >>>> Thanks
> >>>> Partha
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> >>>>> Sent: Wednesday, November 16, 2011 10:56 AM
> >>>>> To: Leon Portman; Ravindran, Parthasarathi;
> henry.lum@genesyslab.com
> >>>>> Cc: siprec@ietf.org
> >>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
> >>>>>
> >>>>> Leon,
> >>>>>
> >>>>> Please see inline. I have a question here
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> >>>>>> Behalf Of Leon Portman
> >>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
> >>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
> >>>>>> Cc: siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
> >>>>>>
> >>>>>> Additional update on sending full metadata snapshot upon SRS
> >>> request.
> >>>>>>
> >>>>>> In section 8.2 we say:
> >>>>>>
> >>>>>> "   When the SRC receives the request for a metadata snapshot,
> the
> >>> SRC
> >>>>>> MUST provide a full metadata snapshot in a separate INVITE
> >>>>>> transaction, along with an SDP offer."
> >>>>>>
> >>>>>> meaning that full metadata is actually separate INVITE
> transaction.
> >>>>>
> >>>>> Why should the snapshot be always sent in a separate INVITE.
> Can't it
> >>>>> be sent as a response to snapshot request from SRS ? Is there a
> >>>>> reason why you want to mandate that way ?
> >>>>>
> >>>>> Ram
> >>>>>
> >>>>>>
> >>>>>> Leon
> >>>>>>
> >>>>>>
> >>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
> >>>>>>
> >>>>>>> Partha Thanks
> >>>>>>>
> >>>>>>> Please see below
> >>>>>>>
> >>>>>>> Leon
> >>>>>>>
> >>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
> >>>>>>>
> >>>>>>>> Leon,
> >>>>>>>>
> >>>>>>>> Please read inline
> >>>>>>>>
> >>>>>>>> Thanks
> >>>>>>>> Partha
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
> >>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
> >>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
> >>>>>>>>> Cc: siprec@ietf.org
> >>>>>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-
> 02
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Partha Hi
> >>>>>>>>>
> >>>>>>>>> Please see below
> >>>>>>>>>
> >>>>>>>>> Regards
> >>>>>>>>>
> >>>>>>>>> Leon
> >>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
> >>>>>>>>>
> >>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
> >>>>>>>>>> a) Sec 4.2 Para 1 Line 2
> >>>>>>>>>> b) Sec 4.2 Para 3 Line 5
> >>>>>>>>>>
> >>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
> >>>>> specific
> >>>>>>>>> section, it is an over part.
> >>>>>>>>>
> >>>>>>>> <partha> I'm not very sure whether it is appropriate to use
> "may"
> >>>>> in
> >>>>>> the specification.
> >>>>>>>> </partha>
> >>>>>>>
> >>>>>>> [Leon] I dont have any opinions on that
> >>>>>>>>
> >>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
> instead
> >>>>>>>>>> of
> >>>>>>>>> current audio.
> >>>>>>>>>
> >>>>>>>>> [Leon] Yes, good catch. Thanks
> >>>>>>>>>>
> >>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note
> >>>>>>>>>> that
> >>>>>> when
> >>>>>>>>> a CS
> >>>>>>>>>> stream is muted/unmuted, this information is conveyed in the
> >>>>>>>>> metadata
> >>>>>>>>>> by the SRC. " because I don't know how metadata convey this
> >>>>>>>>> currently.
> >>>>>>>>>>
> >>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
> rephrase
> >>>>>> it to
> >>>>>>>>> "may be conveyed in metadata"
> >>>>>>>> <partha> Currently, it is outside the scope of metadata and
> IMO,
> >>>>>>>> it
> >>>>>> is better
> >>>>>>>> to remove "mute/unmute" from protocol spec </partha>
> >>>>>>>
> >>>>>>> [Leon] I agree, Henry, what do you think?
> >>>>>>>>
> >>>>>>>>>> 4) Whether the normative statement required for mute? Sec
> 6.1.1
> >>>>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive
> for
> >>>>>>>>>> mute since this operation is reserved for pausing
> >>>>>> the
> >>>>>>>>>> RS media."
> >>>>>>>>>>
> >>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
> >>>>>>>>> handled
> >>>>>> like
> >>>>>>>>> "hold"
> >>>>>>>>>
> >>>>>>>> <partha> IMO, there should be no normative statement related
> to
> >>>>> mute
> >>>>>> </partha>
> >>>>>>>>
> >>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
> >>>>>> delivery
> >>>>>>>>> which shall
> >>>>>>>>>> be avoided.
> >>>>>>>>>
> >>>>>>>>> [Leon] 4.2 is the overview section. We could have some
> repetition
> >>>>>> here
> >>>>>>>>> with detailed sections.
> >>>>>>>>>>
> >>>>>>>> <partha> I can live with incase everybody wants with
> duplication
> >>>>>>>> on
> >>>>>> text
> >>>>>>>> </partha>
> >>>>>>>>
> >>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
> instead
> >>>>>>>>>> of current "application/rs-metadata"
> >>>>>>>>>>
> >>>>>>>>> [Leon] I am ok with that
> >>>>>>>>>> 7) full metadata snapshot shall be passed across using
> UPDATE as
> >>>>>> well.
> >>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
> SRC
> >>>>>> sends a
> >>>>>>>>> full metadata snapshot, the SRC MUST
> >>>>>>>>>> send an INVITE request with an SDP offer and the "recording-
> >>>>>> session"
> >>>>>>>>>> disposition."
> >>>>>>>>>>
> >>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
> order to
> >>>>>> make
> >>>>>>>>> sure that SDP will be present as well. Dont have any strong
> >>>>>> preferences
> >>>>>>>>> here.
> >>>>>>>>>
> >>>>>>>> <partha> We had the discussion during IETF-80 to mandate
> INVITE &
> >>>>>> UPDATE.
> >>>>>>>> But I could not find the reason for not using UPDATE for full
> >>>>>> snapshot
> >>>>>>>> Request </partha>
> >>>>>>>
> >>>>>>> [Leon] I am ok with both
> >>>>>>>>
> >>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
> changed as
> >>>>>> SIP
> >>>>>>>>>> header or clear indication within the message to indicate
> >>>>> metadata
> >>>>>>>>> request. Also, reason for logging could be mentioned
> explicitly
> >>>>>> like
> >>>>>>>>> "logging: SRS internal error"
> >>>>>>>>>>
> >>>>>>>>> [Leon]  I am ok with that. Any opinions?
> >>>>>>>>>
> >>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
> recommendation
> >>>>> of
> >>>>>>>>>> logging text from SRS for the generic request
> >>>>>>>>>
> >>>>>>>>> [Leon] Please elaborate.
> >>>>>>>>>>
> >>>>>>>> <partha> Currently, it is plain text now whereas SRC has no
> means
> >>>>> to
> >>>>>>>> understand about  the logs. Some guidelines/suggestion about
> the
> >>>>>> text
> >>>>>>>> helps for the implementation by which SRC understand.
> </partha>
> >>>>>>>>>> Thanks
> >>>>>>>>>> Partha
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> 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
> >>
> >
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From andrew.hutton@siemens-enterprise.com  Tue Nov 15 22:31:15 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 81C5611E8123 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEFuSpN0bWbn for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:31:15 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id F2DEE11E8113 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:31:14 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 6775C1EB8417 for <siprec@ietf.org>; Wed, 16 Nov 2011 07:31:14 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 16 Nov 2011 07:31:14 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Wed, 16 Nov 2011 07:31:12 +0100
Thread-Topic: SIPREC Issue Tracker Policy.
Thread-Index: AcykKVWg8uCq8NOFRWe2H8msPty41g==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAB6638D@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] SIPREC Issue Tracker Policy.
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, 16 Nov 2011 06:31:15 -0000

Hi All,

The policy for using the SIPREC issue tracker is:

1. The draft editors and working group chairs should be the only people cre=
ating and modifying issues on the tracker.

2. All open issues requiring a decision should be logged in the tracker.

3. The tracker itself should not be used for discussion which should take p=
lace directly on the mailing list and when possible with a reference to the=
 issue number.

Regards
Andy

From trac+siprec@trac.tools.ietf.org  Tue Nov 15 22:36:01 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
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 4F14B11E816B for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:36:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I9I07WyQl+GL for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:35:57 -0800 (PST)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2A33911E8160 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:35:56 -0800 (PST)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1RQZ6B-0008Bl-47; Wed, 16 Nov 2011 01:35:55 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: leon.portman@nice.com, leonp@nice.com
X-Trac-Project: siprec
Date: Wed, 16 Nov 2011 06:35:54 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/siprec/trac/ticket/66#comment:2
Message-ID: <090.2f47571e795573ae3905f9b5bc79eb2f@trac.tools.ietf.org>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 66
In-Reply-To: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: leon.portman@nice.com, leonp@nice.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Cc: siprec@ietf.org
Subject: Re: [siprec] #66: Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2011 06:36:01 -0000

#66: Clarification of REQ-018 on indications to participants

Changes (by leonp@â€¦):

 * status:  new => closed
 * resolution:   => fixed


-- 
-----------------------------+-----------------------------
 Reporter:  john.elwell@â€¦    |       Owner:  leon.portman@â€¦
     Type:  defect           |      Status:  closed
 Priority:  major            |   Milestone:
Component:  Requirements     |     Version:
 Severity:  In WG Last Call  |  Resolution:  fixed
 Keywords:                   |
-----------------------------+-----------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/66#comment:2>
siprec <http://tools.ietf.org/siprec/>


From andrew.hutton@siemens-enterprise.com  Tue Nov 15 22:36:26 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 EDC0F11E816B for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:36:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tcM9wxCzsVtU for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:36:22 -0800 (PST)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 968E411E8160 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:36:22 -0800 (PST)
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 8673B23F04D4 for <siprec@ietf.org>; Wed, 16 Nov 2011 07:36:19 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 16 Nov 2011 07:36:19 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Wed, 16 Nov 2011 07:36:17 +0100
Thread-Topic: IETF82 SIPREC Presentations.
Thread-Index: AcykECsF3HqrC1v8SgGZl20Zmcn15wAGcCZA
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAB6638F@MCHP058A.global-ad.net>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAB66368@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAB66368@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FAB6638FMCHP058Agloba_"
MIME-Version: 1.0
Subject: Re: [siprec] IETF82 SIPREC Presentations.
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, 16 Nov 2011 06:36:27 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAB6638FMCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

An update to the protocol presentation has been uploaded.

Regards
Andy

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Hutton, Andrew
Sent: 16 November 2011 11:31
To: siprec@ietf.org
Subject: [siprec] IETF82 SIPREC Presentations.

Hi All,

All SIPREC related presentations for tomorrows IETF82 SIPREC meeting have b=
een uploaded and are available at https://datatracker.ietf.org/meeting/82/m=
aterials.html

Regards
Andy


--_000_101C6067BEC68246B0C3F6843BCCC1E311FAB6638FMCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi All,<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>An update to the protocol presentation has bee=
n uploaded.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'>Regards<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'>Andy<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid =
blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border=
-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b=
><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif"'>From:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif"'> siprec-bounces@ietf.org [mailto:siprec-bounces@=
ietf.org] <b>On Behalf Of </b>Hutton, Andrew<br><b>Sent:</b> 16 November 20=
11 11:31<br><b>To:</b> siprec@ietf.org<br><b>Subject:</b> [siprec] IETF82 S=
IPREC Presentations.<o:p></o:p></span></p></div></div><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Calibri","sans-serif"'>Hi All,<o:p></o:p></span></p></div>=
<div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cali=
bri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNor=
mal><span style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>All=
 SIPREC related presentations for tomorrows IETF82 SIPREC meeting have been=
 uploaded and are available at <a href=3D"https://datatracker.ietf.org/meet=
ing/82/materials.html">https://datatracker.ietf.org/meeting/82/materials.ht=
ml</a><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-=
family:"Calibri","sans-serif"'>Regards<o:p></o:p></span></p></div><div><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calibri","san=
s-serif"'>Andy<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o=
:p></span></p></div></div></div></body></html>=

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAB6638FMCHP058Agloba_--

From trac+siprec@trac.tools.ietf.org  Tue Nov 15 22:42:01 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
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 4E5FD1F0C51 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYjKllQ+gNpa for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:41:57 -0800 (PST)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 282FC1F0C44 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:41:57 -0800 (PST)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1RQZBv-000270-4C; Wed, 16 Nov 2011 01:41:51 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: draft-ietf-siprec-protocol@tools.ietf.org, leonp@nice.com
X-Trac-Project: siprec
Date: Wed, 16 Nov 2011 06:41:51 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/siprec/trac/ticket/78
Message-ID: <055.bd9bf14e48b183684fe7b426156f0089@trac.tools.ietf.org>
X-Trac-Ticket-ID: 78
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-siprec-protocol@tools.ietf.org, leonp@nice.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: 
Resent-Message-Id: <20111116064157.282FC1F0C44@ietfa.amsl.com>
Resent-Date: Tue, 15 Nov 2011 22:41:57 -0800 (PST)
Resent-From: trac+siprec@trac.tools.ietf.org
Cc: siprec@ietf.org
Subject: [siprec] #78: Using of feature and options tags in SIPREC protocol
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2011 06:42:01 -0000

#78: Using of feature and options tags in SIPREC protocol

 is it correct usage of feature tags?

 More details in:

 http://www.ietf.org/mail-archive/web/siprec/current/msg02885.html

  and

 http://www.ietf.org/mail-archive/web/siprec/current/msg02897.html

 Leon

-- 
----------------------+------------------------------------------
 Reporter:  leonp@â€¦   |      Owner:  draft-ietf-siprec-protocol@â€¦
     Type:  defect    |     Status:  new
 Priority:  major     |  Milestone:
Component:  protocol  |    Version:  2.0
 Severity:  -         |   Keywords:
----------------------+------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/78>
siprec <http://tools.ietf.org/siprec/>


From trac+siprec@trac.tools.ietf.org  Tue Nov 15 22:44:43 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
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 5C8DA21F931A for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:44:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3tM9kCoRZDBR for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:44:39 -0800 (PST)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA3B21F9319 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:44:39 -0800 (PST)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1RQZEb-0002AO-2t; Wed, 16 Nov 2011 01:44:37 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: draft-ietf-siprec-protocol@tools.ietf.org, leonp@nice.com
X-Trac-Project: siprec
Date: Wed, 16 Nov 2011 06:44:37 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/siprec/trac/ticket/79
Message-ID: <055.41c9f5d9c9a876b6ae1c772f80a78544@trac.tools.ietf.org>
X-Trac-Ticket-ID: 79
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-siprec-protocol@tools.ietf.org, leonp@nice.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: 
Resent-Message-Id: <20111116064439.3EA3B21F9319@ietfa.amsl.com>
Resent-Date: Tue, 15 Nov 2011 22:44:39 -0800 (PST)
Resent-From: trac+siprec@trac.tools.ietf.org
Cc: siprec@ietf.org
Subject: [siprec] #79: Review mechanism for triggering and responding for metadata snapshot request
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2011 06:44:43 -0000

#79: Review mechanism for triggering and responding for metadata snapshot
request

 More details:

 http://www.ietf.org/mail-archive/web/siprec/current/msg02904.html

 Leon

-- 
----------------------+------------------------------------------
 Reporter:  leonp@â€¦   |      Owner:  draft-ietf-siprec-protocol@â€¦
     Type:  defect    |     Status:  new
 Priority:  major     |  Milestone:
Component:  protocol  |    Version:  2.0
 Severity:  -         |   Keywords:
----------------------+------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/79>
siprec <http://tools.ietf.org/siprec/>


From leon.portman@gmail.com  Tue Nov 15 22:47:50 2011
Return-Path: <leon.portman@gmail.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 0F47D21F84FA for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.128
X-Spam-Level: 
X-Spam-Status: No, score=-3.128 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBx1ymyxtz7I for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:47:47 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2068C11E80FF for <siprec@ietf.org>; Tue, 15 Nov 2011 22:47:47 -0800 (PST)
Received: by ywt34 with SMTP id 34so7437448ywt.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:47:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=qQQQqIPAPEzCrIDQOrc93QSHR5fZK6qcA1Zc23wlVA0=; b=UILcYPuXabvbKJCb9RbJAVfJGvVCEn3DYV3feeuFaTD/ukZU773gB18xUS9fZ0hHLp FUrmPuWONHRgbjEJWAQN4ncaiJd553dSrOrPgivuRgoiuJ45x4pGgR48ksE4KJibjLCS FYCaOKX+zEDTuGSCKaw/LPjlw4mTVqASowLPU=
Received: by 10.146.48.37 with SMTP id v37mr1447189yav.6.1321426066564; Tue, 15 Nov 2011 22:47:46 -0800 (PST)
Received: from ?IPv6:2001:df8::16:cc58:c3ed:a546:8ce5? ([2001:df8:0:16:cc58:c3ed:a546:8ce5]) by mx.google.com with ESMTPS id k20sm82783772ann.15.2011.11.15.22.47.43 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 22:47:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net>
Date: Wed, 16 Nov 2011 14:47:43 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 06:47:50 -0000

If we will use OK response from SRC to SRS for reporting metadata =
snapshot and SRS will want to update SDP - for example because it needs =
to terminate or redirect one of the RS media streams, it will need to do =
it in separate REINVITE and UPDATE after ACK?

Leon

On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:

> Hi,
>=20
> If I understand this correctly the discussion is how should the SRS =
initiate a snapshot from the SRC and how does this impact the =
offer/answer.
>=20
> The snapshot has I believe to include both an SDP offer and the =
associated XML representing the metadata. The only way to initiate a new =
SDP offer within the dialog is for the SRS to send a reINVITE without =
SDP to the SRC causes the SRC to respond with the SDP Offer and =
associated metadata snapshot in the 200OK which will of course cause the =
SRS to generate an SDP answer in the ACK.
>=20
> The SRS could also include an SDP offer in the reINVITE and have the =
SRC create the answer.
>=20
> In either case it should be that there is no change in the SDP from =
the previous offer/answer and therefore it is effectively a session =
refresh and does not cause an media interruption.=20
>=20
> Regards
> Andy
>=20
>=20
>=20
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Leon Portman
>> Sent: 16 November 2011 13:43
>> To: Ravindran, Parthasarathi
>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>=20
>> Most important from SRS point of view, is to define a mechanism for
>> snapshot request that will not terminate recording session even for
>> shortest possible time.
>>=20
>> My concern is if new INVITE will do that
>>=20
>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>=20
>>> If offer-less REINVITE works (it seems to be) i dont have problem
>> with supporting option 1 as well. Any SIP experts opinions?
>>>=20
>>> Leon
>>>=20
>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>=20
>>>> Leon,
>>>>=20
>>>> Please read inline.
>>>>=20
>>>> Thanks
>>>> Partha
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>> To: Ravindran, Parthasarathi
>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>> siprec@ietf.org
>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>=20
>>>>> Patha
>>>>>=20
>>>>> Please see below
>>>>>=20
>>>>> Leon
>>>>>=20
>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>=20
>>>>>> Leon,
>>>>>>=20
>>>>>> I agree with Ram.
>>>>>>=20
>>>>>> It is possible to debate on this normative statement requirement
>> as
>>>>>> multiple way to request the full snapshot from SRS. Some of the
>> way
>>>>>> from SRS are as follows:
>>>>>>=20
>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>> messages)
>>>>> In this case, is it legal for SRC to answer SDP less INVITE with
>> SDP?
>>>>> Snapshot requires SDP
>>>> <partha> AFAIK, Re-INVITE without SDP is used to get offer from the
>> remote
>>>> Side. Even Hadriel mail threads says the same. Could you please
>> point out
>>>> RFC 3261 Section to point how RE-INVITE without offer/answer work?
>> </partha>
>>>>=20
>>>>=20
>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>> messages)
>>>>> What if SRS does not have SDP?
>>>> <partha> In that case, it will end-up in OPTION 1 or 3 but please
>> note that
>>>> It is possible to SRS to send SDP in case it has the idea of what
>> has to be
>>>> Recorded. </partha>
>>>>=20
>>>>=20
>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>> Separate (4 SIP messages)
>>>>>>=20
>>>>=20
>>>> <partha> I have started thinking whether it is appropriate for
>> UPDATE from SRC
>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
>> proposal mandates
>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>> UPDATE is not
>>>> designed for that. I may be wrong here but we need careful analysis
>> here </partha>
>>>>=20
>>>>>> IIUC, current SIPREC protocol mechanism propose to use only =
OPTION
>> 3
>>>>>> but I prefer to have the implementation choice. As mentioned
>> above,
>>>>>> OPTION 1 & 2 has less SIP message required to achieve the same
>> compare
>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>=20
>>>>>> Thanks
>>>>>> Partha
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>> henry.lum@genesyslab.com
>>>>>>> Cc: siprec@ietf.org
>>>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>=20
>>>>>>> Leon,
>>>>>>>=20
>>>>>>> Please see inline. I have a question here
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>> On
>>>>>>>> Behalf Of Leon Portman
>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>=20
>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>> request.
>>>>>>>>=20
>>>>>>>> In section 8.2 we say:
>>>>>>>>=20
>>>>>>>> "   When the SRC receives the request for a metadata snapshot,
>> the
>>>>> SRC
>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>=20
>>>>>>>> meaning that full metadata is actually separate INVITE
>> transaction.
>>>>>>>=20
>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>> Can't it
>>>>>>> be sent as a response to snapshot request from SRS ? Is there a
>>>>>>> reason why you want to mandate that way ?
>>>>>>>=20
>>>>>>> Ram
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Leon
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>=20
>>>>>>>>> Partha Thanks
>>>>>>>>>=20
>>>>>>>>> Please see below
>>>>>>>>>=20
>>>>>>>>> Leon
>>>>>>>>>=20
>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>=20
>>>>>>>>>> Leon,
>>>>>>>>>>=20
>>>>>>>>>> Please read inline
>>>>>>>>>>=20
>>>>>>>>>> Thanks
>>>>>>>>>> Partha
>>>>>>>>>>=20
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>> Subject: Re: [sipprec] Comment on =
draft-ietf-siprec-protocol-
>> 02
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>> Partha Hi
>>>>>>>>>>>=20
>>>>>>>>>>> Please see below
>>>>>>>>>>>=20
>>>>>>>>>>> Regards
>>>>>>>>>>>=20
>>>>>>>>>>> Leon
>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi =
wrote:
>>>>>>>>>>>=20
>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>>>> specific
>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>=20
>>>>>>>>>> <partha> I'm not very sure whether it is appropriate to use
>> "may"
>>>>>>> in
>>>>>>>> the specification.
>>>>>>>>>> </partha>
>>>>>>>>>=20
>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>=20
>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>> instead
>>>>>>>>>>>> of
>>>>>>>>>>> current audio.
>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>=20
>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 =
"Note
>>>>>>>>>>>> that
>>>>>>>> when
>>>>>>>>>>> a CS
>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in =
the
>>>>>>>>>>> metadata
>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>>>>>> currently.
>>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>> rephrase
>>>>>>>> it to
>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>> <partha> Currently, it is outside the scope of metadata and
>> IMO,
>>>>>>>>>> it
>>>>>>>> is better
>>>>>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>>>>>=20
>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>=20
>>>>>>>>>>>> 4) Whether the normative statement required for mute? Sec
>> 6.1.1
>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive=

>> for
>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>> the
>>>>>>>>>>>> RS media."
>>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>>>> handled
>>>>>>>> like
>>>>>>>>>>> "hold"
>>>>>>>>>>>=20
>>>>>>>>>> <partha> IMO, there should be no normative statement related
>> to
>>>>>>> mute
>>>>>>>> </partha>
>>>>>>>>>>=20
>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of =
metadata
>>>>>>>> delivery
>>>>>>>>>>> which shall
>>>>>>>>>>>> be avoided.
>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>> repetition
>>>>>>>> here
>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>=20
>>>>>>>>>> <partha> I can live with incase everybody wants with
>> duplication
>>>>>>>>>> on
>>>>>>>> text
>>>>>>>>>> </partha>
>>>>>>>>>>=20
>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>> instead
>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>> UPDATE as
>>>>>>>> well.
>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
>> SRC
>>>>>>>> sends a
>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>> send an INVITE request with an SDP offer and the =
"recording-
>>>>>>>> session"
>>>>>>>>>>>> disposition."
>>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>> order to
>>>>>>>> make
>>>>>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>>>>>> preferences
>>>>>>>>>>> here.
>>>>>>>>>>>=20
>>>>>>>>>> <partha> We had the discussion during IETF-80 to mandate
>> INVITE &
>>>>>>>> UPDATE.
>>>>>>>>>> But I could not find the reason for not using UPDATE for full
>>>>>>>> snapshot
>>>>>>>>>> Request </partha>
>>>>>>>>>=20
>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>=20
>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>> changed as
>>>>>>>> SIP
>>>>>>>>>>>> header or clear indication within the message to indicate
>>>>>>> metadata
>>>>>>>>>>> request. Also, reason for logging could be mentioned
>> explicitly
>>>>>>>> like
>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>=20
>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>=20
>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>> recommendation
>>>>>>> of
>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>=20
>>>>>>>>>> <partha> Currently, it is plain text now whereas SRC has no
>> means
>>>>>>> to
>>>>>>>>>> understand about  the logs. Some guidelines/suggestion about
>> the
>>>>>>>> text
>>>>>>>>>> helps for the implementation by which SRC understand.
>> </partha>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Partha
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> siprec mailing list
>>>>>>>>>>>> siprec@ietf.org
>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> _______________________________________________
>>>>>>>> siprec mailing list
>>>>>>>> siprec@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>=20
>>>=20
>>=20
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec


From trac+siprec@trac.tools.ietf.org  Tue Nov 15 22:57:59 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
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 390BA11E81AF for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9w2OkVaPv5Si for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:57:55 -0800 (PST)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2213011E81A1 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:57:54 -0800 (PST)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1RQZRR-000074-On; Wed, 16 Nov 2011 01:57:53 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: rmohanr@cisco.com
X-Trac-Project: siprec
Date: Wed, 16 Nov 2011 06:57:53 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/siprec/trac/ticket/73#comment:1
Message-ID: <073.e6288b288317bb3d2846cd3ca070043f@trac.tools.ietf.org>
References: <058.e0b3e161e85c5044e643018b27cab1f7@trac.tools.ietf.org>
X-Trac-Ticket-ID: 73
In-Reply-To: <058.e0b3e161e85c5044e643018b27cab1f7@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: rmohanr@cisco.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Cc: siprec@ietf.org
Subject: Re: [siprec] #73: How to represent CSRC attribute in XML ?
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2011 06:57:59 -0000

#73: How to represent CSRC attribute in XML ?

Changes (by rmohanr@â€¦):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 This is fixed in the new version ( ver 05) of the document. Hence closing
 the ticket

-- 
-------------------------+------------------------
 Reporter:  rmohanr@â€¦    |       Owner:  rmohanr@â€¦
     Type:  enhancement  |      Status:  closed
 Priority:  major        |   Milestone:
Component:  metadata     |     Version:
 Severity:  -            |  Resolution:  fixed
 Keywords:               |
-------------------------+------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/73#comment:1>
siprec <http://tools.ietf.org/siprec/>


From trac+siprec@trac.tools.ietf.org  Tue Nov 15 22:59:15 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
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 4917811E81C4 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:59:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tg5axpUsJyfS for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 22:59:11 -0800 (PST)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2C62311E81B7 for <siprec@ietf.org>; Tue, 15 Nov 2011 22:59:10 -0800 (PST)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1RQZSg-00007a-KZ; Wed, 16 Nov 2011 01:59:10 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: rmohanr@cisco.com
X-Trac-Project: siprec
Date: Wed, 16 Nov 2011 06:59:10 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/siprec/trac/ticket/76#comment:1
Message-ID: <073.0da57729af0a62aa885a2c1acef9f6c2@trac.tools.ietf.org>
References: <058.3ac61efd90865c277579249dd6a27efc@trac.tools.ietf.org>
X-Trac-Ticket-ID: 76
In-Reply-To: <058.3ac61efd90865c277579249dd6a27efc@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: rmohanr@cisco.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Cc: siprec@ietf.org
Subject: Re: [siprec] #76: Address rest of the John's comments sent on metadata-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2011 06:59:15 -0000

#76: Address rest of the John's comments sent on metadata-03

Changes (by rmohanr@â€¦):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 This is taken care in Ver 05 of the document

-- 
--------------------------------+------------------------
 Reporter:  rmohanr@â€¦           |       Owner:  rmohanr@â€¦
     Type:  defect              |      Status:  closed
 Priority:  minor               |   Milestone:
Component:  metadata            |     Version:
 Severity:  Active WG Document  |  Resolution:  fixed
 Keywords:                      |
--------------------------------+------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/76#comment:1>
siprec <http://tools.ietf.org/siprec/>


From pravindran@sonusnet.com  Tue Nov 15 23:31:01 2011
Return-Path: <pravindran@sonusnet.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 4569D11E80E0 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:31:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4BmSaJvyc5L for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:30:57 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id E17D411E80F5 for <siprec@ietf.org>; Tue, 15 Nov 2011 23:30:56 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAG7VU1x027373;  Wed, 16 Nov 2011 02:31:30 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 02:30:11 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 13:00:25 +0530
Received: from INBA-HUB02.sonusnet.com (10.70.51.87) by inba-hub01.sonusnet.com (10.70.51.86) with Microsoft SMTP Server (TLS) id 14.1.339.1; Wed, 16 Nov 2011 13:00:24 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0339.001; Wed, 16 Nov 2011 13:00:24 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Leon Portman <leon.portman@gmail.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVCAAfdcAIAAFlAAgAAC/YD//6LIIIAAYtkA//+jbqAAEGLoAAAATaOAAAF4G4AAAMvZgP//m1vw
Date: Wed, 16 Nov 2011 07:30:24 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com>
In-Reply-To: <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Nov 2011 07:30:25.0127 (UTC) FILETIME=[9B361F70:01CCA431]
Cc: "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 07:31:01 -0000

Leon,

Please read inline.

Thanks
Partha

>-----Original Message-----
>From: Leon Portman [mailto:leon.portman@gmail.com]
>Sent: Wednesday, November 16, 2011 2:48 PM
>To: Hutton, Andrew
>Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com; siprec@ietf.org
>Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>
>If we will use OK response from SRC to SRS for reporting metadata
>snapshot=20

<partha> We are in the same page till here </partha>

and SRS will want to update SDP - for example because it needs
>to terminate or redirect one of the RS media streams, it will need to do
>it in separate REINVITE and UPDATE after ACK?

<partha> IIUC, SRS will trigger one another offer/answer to terminate RS
Media stream. But I'm not very clear about the redirect of RS media stream
Scenario </partha>

>
>Leon
>
>On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>
>> Hi,
>>
>> If I understand this correctly the discussion is how should the SRS
>initiate a snapshot from the SRC and how does this impact the
>offer/answer.
>>
>> The snapshot has I believe to include both an SDP offer and the
>associated XML representing the metadata. The only way to initiate a new
>SDP offer within the dialog is for the SRS to send a reINVITE without
>SDP to the SRC causes the SRC to respond with the SDP Offer and
>associated metadata snapshot in the 200OK which will of course cause the
>SRS to generate an SDP answer in the ACK.
>>
>> The SRS could also include an SDP offer in the reINVITE and have the
>SRC create the answer.
>>
>> In either case it should be that there is no change in the SDP from
>the previous offer/answer and therefore it is effectively a session
>refresh and does not cause an media interruption.
>>
>> Regards
>> Andy
>>
>>
>>
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf Of Leon Portman
>>> Sent: 16 November 2011 13:43
>>> To: Ravindran, Parthasarathi
>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>
>>> Most important from SRS point of view, is to define a mechanism for
>>> snapshot request that will not terminate recording session even for
>>> shortest possible time.
>>>
>>> My concern is if new INVITE will do that
>>>
>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>
>>>> If offer-less REINVITE works (it seems to be) i dont have problem
>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>
>>>> Leon
>>>>
>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>
>>>>> Leon,
>>>>>
>>>>> Please read inline.
>>>>>
>>>>> Thanks
>>>>> Partha
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>> To: Ravindran, Parthasarathi
>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>> siprec@ietf.org
>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>
>>>>>> Patha
>>>>>>
>>>>>> Please see below
>>>>>>
>>>>>> Leon
>>>>>>
>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>>
>>>>>>> Leon,
>>>>>>>
>>>>>>> I agree with Ram.
>>>>>>>
>>>>>>> It is possible to debate on this normative statement requirement
>>> as
>>>>>>> multiple way to request the full snapshot from SRS. Some of the
>>> way
>>>>>>> from SRS are as follows:
>>>>>>>
>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>>> messages)
>>>>>> In this case, is it legal for SRC to answer SDP less INVITE with
>>> SDP?
>>>>>> Snapshot requires SDP
>>>>> <partha> AFAIK, Re-INVITE without SDP is used to get offer from the
>>> remote
>>>>> Side. Even Hadriel mail threads says the same. Could you please
>>> point out
>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer work?
>>> </partha>
>>>>>
>>>>>
>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>> messages)
>>>>>> What if SRS does not have SDP?
>>>>> <partha> In that case, it will end-up in OPTION 1 or 3 but please
>>> note that
>>>>> It is possible to SRS to send SDP in case it has the idea of what
>>> has to be
>>>>> Recorded. </partha>
>>>>>
>>>>>
>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>> Separate (4 SIP messages)
>>>>>>>
>>>>>
>>>>> <partha> I have started thinking whether it is appropriate for
>>> UPDATE from SRC
>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
>>> proposal mandates
>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>>> UPDATE is not
>>>>> designed for that. I may be wrong here but we need careful analysis
>>> here </partha>
>>>>>
>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>> OPTION
>>> 3
>>>>>>> but I prefer to have the implementation choice. As mentioned
>>> above,
>>>>>>> OPTION 1 & 2 has less SIP message required to achieve the same
>>> compare
>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Partha
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>> henry.lum@genesyslab.com
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>
>>>>>>>> Leon,
>>>>>>>>
>>>>>>>> Please see inline. I have a question here
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>>> On
>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>
>>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>>> request.
>>>>>>>>>
>>>>>>>>> In section 8.2 we say:
>>>>>>>>>
>>>>>>>>> "   When the SRC receives the request for a metadata snapshot,
>>> the
>>>>>> SRC
>>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>>
>>>>>>>>> meaning that full metadata is actually separate INVITE
>>> transaction.
>>>>>>>>
>>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>>> Can't it
>>>>>>>> be sent as a response to snapshot request from SRS ? Is there a
>>>>>>>> reason why you want to mandate that way ?
>>>>>>>>
>>>>>>>> Ram
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Leon
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>
>>>>>>>>>> Partha Thanks
>>>>>>>>>>
>>>>>>>>>> Please see below
>>>>>>>>>>
>>>>>>>>>> Leon
>>>>>>>>>>
>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>>
>>>>>>>>>>> Leon,
>>>>>>>>>>>
>>>>>>>>>>> Please read inline
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Partha
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>> 02
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>
>>>>>>>>>>>> Please see below
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>>
>>>>>>>>>>>> Leon
>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>>>>> specific
>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>
>>>>>>>>>>> <partha> I'm not very sure whether it is appropriate to use
>>> "may"
>>>>>>>> in
>>>>>>>>> the specification.
>>>>>>>>>>> </partha>
>>>>>>>>>>
>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>
>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>>> instead
>>>>>>>>>>>>> of
>>>>>>>>>>>> current audio.
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1
>>>>>>>>>>>>> "Note that
>>>>>>>>> when
>>>>>>>>>>>> a CS
>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in
>>>>>>>>>>>>> the
>>>>>>>>>>>> metadata
>>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>>>>>>> currently.
>>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>>> rephrase
>>>>>>>>> it to
>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>> <partha> Currently, it is outside the scope of metadata and
>>> IMO,
>>>>>>>>>>> it
>>>>>>>>> is better
>>>>>>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>>>>>>
>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>
>>>>>>>>>>>>> 4) Whether the normative statement required for mute? Sec
>>> 6.1.1
>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with a=3Dinactive
>>> for
>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>> the
>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>>>>> handled
>>>>>>>>> like
>>>>>>>>>>>> "hold"
>>>>>>>>>>>>
>>>>>>>>>>> <partha> IMO, there should be no normative statement related
>>> to
>>>>>>>> mute
>>>>>>>>> </partha>
>>>>>>>>>>>
>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>> metadata
>>>>>>>>> delivery
>>>>>>>>>>>> which shall
>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>> repetition
>>>>>>>>> here
>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>
>>>>>>>>>>> <partha> I can live with incase everybody wants with
>>> duplication
>>>>>>>>>>> on
>>>>>>>>> text
>>>>>>>>>>> </partha>
>>>>>>>>>>>
>>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>>> instead
>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>>> UPDATE as
>>>>>>>>> well.
>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
>>> SRC
>>>>>>>>> sends a
>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>> "recording-
>>>>>>>>> session"
>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>>> order to
>>>>>>>>> make
>>>>>>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>>>>>>> preferences
>>>>>>>>>>>> here.
>>>>>>>>>>>>
>>>>>>>>>>> <partha> We had the discussion during IETF-80 to mandate
>>> INVITE &
>>>>>>>>> UPDATE.
>>>>>>>>>>> But I could not find the reason for not using UPDATE for full
>>>>>>>>> snapshot
>>>>>>>>>>> Request </partha>
>>>>>>>>>>
>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>
>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>> changed as
>>>>>>>>> SIP
>>>>>>>>>>>>> header or clear indication within the message to indicate
>>>>>>>> metadata
>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>> explicitly
>>>>>>>>> like
>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>
>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>
>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>> recommendation
>>>>>>>> of
>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>
>>>>>>>>>>> <partha> Currently, it is plain text now whereas SRC has no
>>> means
>>>>>>>> to
>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion about
>>> the
>>>>>>>>> text
>>>>>>>>>>> helps for the implementation by which SRC understand.
>>> </partha>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Partha
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> 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


From leon.portman@gmail.com  Tue Nov 15 23:35:40 2011
Return-Path: <leon.portman@gmail.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 5936E1F0C7D for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:35:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.112
X-Spam-Level: 
X-Spam-Status: No, score=-3.112 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-bMwXPcXoN4 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:35:36 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id F0FCA1F0C75 for <siprec@ietf.org>; Tue, 15 Nov 2011 23:35:35 -0800 (PST)
Received: by ggnr5 with SMTP id r5so3722575ggn.31 for <siprec@ietf.org>; Tue, 15 Nov 2011 23:35:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=WCVPBlrlkLsRkf8QKL6TIR1dL/WAUlaBb9t8IYduPMM=; b=P+UButH59cniZlS55ztCK7W3SuM9jympcjk3RJrM3qL9lIMWYv4/eyCIqIdZToACy7 mFaDcRl9FrlfblpHR1iVEFR8yzNgah45VXSC3ocOXQnct7iYydjXntHyhB1bSkpfGXrX 52DQ45EZDsUsNSdpwGk+kUV4KplK7RSxWxwLE=
Received: by 10.101.132.21 with SMTP id j21mr9408692ann.131.1321428935462; Tue, 15 Nov 2011 23:35:35 -0800 (PST)
Received: from ?IPv6:2001:df8::16:3438:dd49:55ac:fb2f? ([2001:df8:0:16:3438:dd49:55ac:fb2f]) by mx.google.com with ESMTPS id 36sm83318940anz.2.2011.11.15.23.35.33 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 23:35:34 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com>
Date: Wed, 16 Nov 2011 15:35:33 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com>
To: Parthasarathi Ravindran <pravindran@sonusnet.com>, henry.lum@genesyslab.com
X-Mailer: Apple Mail (2.1251.1)
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 07:35:40 -0000

Partha

It seems to be that we are converging into solution where SRS will send =
offer-less INVITE with snapshot request and SRC will response with OK =
including metadata snapshot XML and SDP and SRS will ACK this SDP. If =
any media updates are required from SRS , they will be carried in =
separate INVITE/UPDATE as you have mention below. So we are converging =
into your option 1 solution.

Please note that it complicates little bit SRC implementation.

Any concerns and comments?

Thank you for raising this issue.

Leon

On Nov 16, 2011, at 3:30 PM, Ravindran, Parthasarathi wrote:

> Leon,
>=20
> Please read inline.
>=20
> Thanks
> Partha
>=20
>> -----Original Message-----
>> From: Leon Portman [mailto:leon.portman@gmail.com]
>> Sent: Wednesday, November 16, 2011 2:48 PM
>> To: Hutton, Andrew
>> Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com; =
siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>=20
>> If we will use OK response from SRC to SRS for reporting metadata
>> snapshot=20
>=20
> <partha> We are in the same page till here </partha>
>=20
> and SRS will want to update SDP - for example because it needs
>> to terminate or redirect one of the RS media streams, it will need to =
do
>> it in separate REINVITE and UPDATE after ACK?
>=20
> <partha> IIUC, SRS will trigger one another offer/answer to terminate =
RS
> Media stream. But I'm not very clear about the redirect of RS media =
stream
> Scenario </partha>
>=20
>>=20
>> Leon
>>=20
>> On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>>=20
>>> Hi,
>>>=20
>>> If I understand this correctly the discussion is how should the SRS
>> initiate a snapshot from the SRC and how does this impact the
>> offer/answer.
>>>=20
>>> The snapshot has I believe to include both an SDP offer and the
>> associated XML representing the metadata. The only way to initiate a =
new
>> SDP offer within the dialog is for the SRS to send a reINVITE without
>> SDP to the SRC causes the SRC to respond with the SDP Offer and
>> associated metadata snapshot in the 200OK which will of course cause =
the
>> SRS to generate an SDP answer in the ACK.
>>>=20
>>> The SRS could also include an SDP offer in the reINVITE and have the
>> SRC create the answer.
>>>=20
>>> In either case it should be that there is no change in the SDP from
>> the previous offer/answer and therefore it is effectively a session
>> refresh and does not cause an media interruption.
>>>=20
>>> Regards
>>> Andy
>>>=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>> Behalf Of Leon Portman
>>>> Sent: 16 November 2011 13:43
>>>> To: Ravindran, Parthasarathi
>>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>=20
>>>> Most important from SRS point of view, is to define a mechanism for
>>>> snapshot request that will not terminate recording session even for
>>>> shortest possible time.
>>>>=20
>>>> My concern is if new INVITE will do that
>>>>=20
>>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>>=20
>>>>> If offer-less REINVITE works (it seems to be) i dont have problem
>>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>>=20
>>>>> Leon
>>>>>=20
>>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>>=20
>>>>>> Leon,
>>>>>>=20
>>>>>> Please read inline.
>>>>>>=20
>>>>>> Thanks
>>>>>> Partha
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>>> To: Ravindran, Parthasarathi
>>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>>> siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>=20
>>>>>>> Patha
>>>>>>>=20
>>>>>>> Please see below
>>>>>>>=20
>>>>>>> Leon
>>>>>>>=20
>>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>>>=20
>>>>>>>> Leon,
>>>>>>>>=20
>>>>>>>> I agree with Ram.
>>>>>>>>=20
>>>>>>>> It is possible to debate on this normative statement =
requirement
>>>> as
>>>>>>>> multiple way to request the full snapshot from SRS. Some of the
>>>> way
>>>>>>>> from SRS are as follows:
>>>>>>>>=20
>>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>>>> messages)
>>>>>>> In this case, is it legal for SRC to answer SDP less INVITE with
>>>> SDP?
>>>>>>> Snapshot requires SDP
>>>>>> <partha> AFAIK, Re-INVITE without SDP is used to get offer from =
the
>>>> remote
>>>>>> Side. Even Hadriel mail threads says the same. Could you please
>>>> point out
>>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer =
work?
>>>> </partha>
>>>>>>=20
>>>>>>=20
>>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>>> messages)
>>>>>>> What if SRS does not have SDP?
>>>>>> <partha> In that case, it will end-up in OPTION 1 or 3 but please
>>>> note that
>>>>>> It is possible to SRS to send SDP in case it has the idea of what
>>>> has to be
>>>>>> Recorded. </partha>
>>>>>>=20
>>>>>>=20
>>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>>> Separate (4 SIP messages)
>>>>>>>>=20
>>>>>>=20
>>>>>> <partha> I have started thinking whether it is appropriate for
>>>> UPDATE from SRC
>>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
>>>> proposal mandates
>>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>>>> UPDATE is not
>>>>>> designed for that. I may be wrong here but we need careful =
analysis
>>>> here </partha>
>>>>>>=20
>>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>>> OPTION
>>>> 3
>>>>>>>> but I prefer to have the implementation choice. As mentioned
>>>> above,
>>>>>>>> OPTION 1 & 2 has less SIP message required to achieve the same
>>>> compare
>>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>>=20
>>>>>>>> Thanks
>>>>>>>> Partha
>>>>>>>>=20
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>>> henry.lum@genesyslab.com
>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>=20
>>>>>>>>> Leon,
>>>>>>>>>=20
>>>>>>>>> Please see inline. I have a question here
>>>>>>>>>=20
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: siprec-bounces@ietf.org =
[mailto:siprec-bounces@ietf.org]
>>>> On
>>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>> Subject: Re: [siprec] Comment on =
draft-ietf-siprec-protocol-02
>>>>>>>>>>=20
>>>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>>>> request.
>>>>>>>>>>=20
>>>>>>>>>> In section 8.2 we say:
>>>>>>>>>>=20
>>>>>>>>>> "   When the SRC receives the request for a metadata =
snapshot,
>>>> the
>>>>>>> SRC
>>>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>>>=20
>>>>>>>>>> meaning that full metadata is actually separate INVITE
>>>> transaction.
>>>>>>>>>=20
>>>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>>>> Can't it
>>>>>>>>> be sent as a response to snapshot request from SRS ? Is there =
a
>>>>>>>>> reason why you want to mandate that way ?
>>>>>>>>>=20
>>>>>>>>> Ram
>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> Leon
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>>=20
>>>>>>>>>>> Partha Thanks
>>>>>>>>>>>=20
>>>>>>>>>>> Please see below
>>>>>>>>>>>=20
>>>>>>>>>>> Leon
>>>>>>>>>>>=20
>>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>>>=20
>>>>>>>>>>>> Leon,
>>>>>>>>>>>>=20
>>>>>>>>>>>> Please read inline
>>>>>>>>>>>>=20
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Partha
>>>>>>>>>>>>=20
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>>> 02
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Leon
>>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>> wrote:
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>>>>>> specific
>>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>>=20
>>>>>>>>>>>> <partha> I'm not very sure whether it is appropriate to use
>>>> "may"
>>>>>>>>> in
>>>>>>>>>> the specification.
>>>>>>>>>>>> </partha>
>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>>>> instead
>>>>>>>>>>>>>> of
>>>>>>>>>>>>> current audio.
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1
>>>>>>>>>>>>>> "Note that
>>>>>>>>>> when
>>>>>>>>>>>>> a CS
>>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in
>>>>>>>>>>>>>> the
>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey =
this
>>>>>>>>>>>>> currently.
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>>>> rephrase
>>>>>>>>>> it to
>>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>>> <partha> Currently, it is outside the scope of metadata and
>>>> IMO,
>>>>>>>>>>>> it
>>>>>>>>>> is better
>>>>>>>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 4) Whether the normative statement required for mute? Sec
>>>> 6.1.1
>>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with =
a=3Dinactive
>>>> for
>>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>>> the
>>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>>>>>> handled
>>>>>>>>>> like
>>>>>>>>>>>>> "hold"
>>>>>>>>>>>>>=20
>>>>>>>>>>>> <partha> IMO, there should be no normative statement =
related
>>>> to
>>>>>>>>> mute
>>>>>>>>>> </partha>
>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>>> metadata
>>>>>>>>>> delivery
>>>>>>>>>>>>> which shall
>>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>>> repetition
>>>>>>>>>> here
>>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>>=20
>>>>>>>>>>>> <partha> I can live with incase everybody wants with
>>>> duplication
>>>>>>>>>>>> on
>>>>>>>>>> text
>>>>>>>>>>>> </partha>
>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>>>> instead
>>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>>>> UPDATE as
>>>>>>>>>> well.
>>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
>>>> SRC
>>>>>>>>>> sends a
>>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>>> "recording-
>>>>>>>>>> session"
>>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>>>> order to
>>>>>>>>>> make
>>>>>>>>>>>>> sure that SDP will be present as well. Dont have any =
strong
>>>>>>>>>> preferences
>>>>>>>>>>>>> here.
>>>>>>>>>>>>>=20
>>>>>>>>>>>> <partha> We had the discussion during IETF-80 to mandate
>>>> INVITE &
>>>>>>>>>> UPDATE.
>>>>>>>>>>>> But I could not find the reason for not using UPDATE for =
full
>>>>>>>>>> snapshot
>>>>>>>>>>>> Request </partha>
>>>>>>>>>>>=20
>>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>>> changed as
>>>>>>>>>> SIP
>>>>>>>>>>>>>> header or clear indication within the message to indicate
>>>>>>>>> metadata
>>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>>> explicitly
>>>>>>>>>> like
>>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>>> recommendation
>>>>>>>>> of
>>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>>=20
>>>>>>>>>>>> <partha> Currently, it is plain text now whereas SRC has no
>>>> means
>>>>>>>>> to
>>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion =
about
>>>> the
>>>>>>>>>> text
>>>>>>>>>>>> helps for the implementation by which SRC understand.
>>>> </partha>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> siprec mailing list
>>>>>>>>>>>>>> siprec@ietf.org
>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> _______________________________________________
>>>>>>>>>> siprec mailing list
>>>>>>>>>> siprec@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>=20
>>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>=20


From pkyzivat@alum.mit.edu  Tue Nov 15 23:49:14 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 8235911E811F for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dt4TXfV+6n4i for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:49:10 -0800 (PST)
Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by ietfa.amsl.com (Postfix) with ESMTP id A7D3E11E80F9 for <siprec@ietf.org>; Tue, 15 Nov 2011 23:49:10 -0800 (PST)
Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta11.emeryville.ca.mail.comcast.net with comcast id xjp01h0020S2fkCABjp3Fx; Wed, 16 Nov 2011 07:49:03 +0000
Received: from dhcp-16f3.meeting.ietf.org ([130.129.22.243]) by omta09.emeryville.ca.mail.comcast.net with comcast id xjpK1h00H5EhBnE8VjpNVZ; Wed, 16 Nov 2011 07:49:27 +0000
Message-ID: <4EC36AEA.4070304@alum.mit.edu>
Date: Wed, 16 Nov 2011 15:48:58 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 07:49:14 -0000

On 11/16/11 10:56 AM, Ram Mohan R (rmohanr) wrote:
> Leon,
>
> Please see inline. I have a question here
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Leon Portman
>> Sent: Wednesday, November 16, 2011 10:45 AM
>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>
>> Additional update on sending full metadata snapshot upon SRS request.
>>
>> In section 8.2 we say:
>>
>> "   When the SRC receives the request for a metadata snapshot, the SRC
>>     MUST provide a full metadata snapshot in a separate INVITE
>>     transaction, along with an SDP offer."
>>
>> meaning that full metadata is actually separate INVITE transaction.
>
> Why should the snapshot be always sent in a separate INVITE. Can't it be
> sent as a response to snapshot request from SRS ? Is there a reason why
> you want to mandate that way ?

I guess *a* reason is that the snapshot will need to contain SDP. And 
since it might be changed SDP, it needs to be an offer so that it can be 
answered.

It would still be possible to do this in response to an INVITE, as long 
as the INVITE has no offer.

	Thanks,
	Paul

> Ram
>
>>
>> Leon
>>
>>
>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>
>>> Partha Thanks
>>>
>>> Please see below
>>>
>>> Leon
>>>
>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>
>>>> Leon,
>>>>
>>>> Please read inline
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
>>>>>
>>>>>
>>>>> Partha Hi
>>>>>
>>>>> Please see below
>>>>>
>>>>> Regards
>>>>>
>>>>> Leon
>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>>
>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>
>>>>> [Leon] I am not sure that we want to emphasize MAY in this
> specific
>>>>> section, it is an over part.
>>>>>
>>>> <partha>  I'm not very sure whether it is appropriate to use "may"
> in
>> the specification.
>>>> </partha>
>>>
>>> [Leon] I dont have any opinions on that
>>>>
>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video instead of
>>>>> current audio.
>>>>>
>>>>> [Leon] Yes, good catch. Thanks
>>>>>>
>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note that
>> when
>>>>> a CS
>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>> metadata
>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>> currently.
>>>>>>
>>>>> [Leon] Yes, it is not defined yet in metadata. We should rephrase
>> it to
>>>>> "may be conveyed in metadata"
>>>> <partha>  Currently, it is outside the scope of metadata and IMO, it
>> is better
>>>> to remove "mute/unmute" from protocol spec</partha>
>>>
>>> [Leon] I agree, Henry, what do you think?
>>>>
>>>>>> 4) Whether the normative statement required for mute? Sec 6.1.1
>>>>>> "The SRC SHOULD not modify the media stream with
>>>>>> a=inactive for mute since this operation is reserved for pausing
>> the
>>>>>> RS media."
>>>>>>
>>>>> [Leon] It is related to point #3 that "mute" should not be handled
>> like
>>>>> "hold"
>>>>>
>>>> <partha>  IMO, there should be no normative statement related to
> mute
>> </partha>
>>>>
>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>> delivery
>>>>> which shall
>>>>>> be avoided.
>>>>>
>>>>> [Leon] 4.2 is the overview section. We could have some repetition
>> here
>>>>> with detailed sections.
>>>>>>
>>>> <partha>  I can live with incase everybody wants with duplication on
>> text
>>>> </partha>
>>>>
>>>>>> 6) content type shall be "application/rs-metadata+xml" instead of
>>>>>> current "application/rs-metadata"
>>>>>>
>>>>> [Leon] I am ok with that
>>>>>> 7) full metadata snapshot shall be passed across using UPDATE as
>> well.
>>>>>> But the current statement on Sec 8.1 misleading "When the SRC
>> sends a
>>>>> full metadata snapshot, the SRC MUST
>>>>>> send an INVITE request with an SDP offer and the "recording-
>> session"
>>>>>> disposition."
>>>>>>
>>>>> [Leon] I remember having discussion to mandate INVITE in order to
>> make
>>>>> sure that SDP will be present as well. Dont have any strong
>> preferences
>>>>> here.
>>>>>
>>>> <partha>  We had the discussion during IETF-80 to mandate INVITE&
>> UPDATE.
>>>> But I could not find the reason for not using UPDATE for full
>> snapshot
>>>> Request</partha>
>>>
>>> [Leon] I am ok with both
>>>>
>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
>> SIP
>>>>>> header or clear indication within the message to indicate
> metadata
>>>>> request. Also, reason for logging could be mentioned explicitly
>> like
>>>>> "logging: SRS internal error"
>>>>>>
>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>
>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation
> of
>>>>>> logging text from SRS for the generic request
>>>>>
>>>>> [Leon] Please elaborate.
>>>>>>
>>>> <partha>  Currently, it is plain text now whereas SRC has no means
> to
>>>> understand about  the logs. Some guidelines/suggestion about the
>> text
>>>> helps for the implementation by which SRC understand.</partha>
>>>>>> Thanks
>>>>>> Partha
>>>>>> _______________________________________________
>>>>>> 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
>


From pravindran@sonusnet.com  Tue Nov 15 23:56:28 2011
Return-Path: <pravindran@sonusnet.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 4B78911E8138 for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.294
X-Spam-Level: 
X-Spam-Status: No, score=-2.294 tagged_above=-999 required=5 tests=[AWL=-0.295, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuTsgd7ECF7L for <siprec@ietfa.amsl.com>; Tue, 15 Nov 2011 23:56:24 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id F12A211E815D for <siprec@ietf.org>; Tue, 15 Nov 2011 23:56:23 -0800 (PST)
Received: from sonusmail07.sonusnet.com (sonusmail07.sonusnet.com [10.128.32.157]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAG7uwm8011040;  Wed, 16 Nov 2011 02:56:58 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail07.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 02:56:21 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 13:26:34 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Wed, 16 Nov 2011 13:26:34 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Leon Portman <leon.portman@gmail.com>, "henry.lum@genesyslab.com" <henry.lum@genesyslab.com>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVCAAfdcAIAAFlAAgAAC/YD//6LIIIAAYtkA//+jbqAAEGLoAAAATaOAAAF4G4AAAMvZgP//m1vw//+N/YD//ro7YA==
Date: Wed, 16 Nov 2011 07:56:34 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE8FBD@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com>
In-Reply-To: <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Nov 2011 07:56:34.0627 (UTC) FILETIME=[42B4D130:01CCA435]
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 07:56:28 -0000

Leon,

I'm fine with OPTION 1. Let us discuss in SIPREC meeting on tomorrow to clo=
se this open item if possible.

Thanks
Partha

>-----Original Message-----
>From: Leon Portman [mailto:leon.portman@gmail.com]
>Sent: Wednesday, November 16, 2011 3:36 PM
>To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>Cc: Andrew Hutton; siprec@ietf.org
>Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>
>Partha
>
>It seems to be that we are converging into solution where SRS will send
>offer-less INVITE with snapshot request and SRC will response with OK
>including metadata snapshot XML and SDP and SRS will ACK this SDP. If
>any media updates are required from SRS , they will be carried in
>separate INVITE/UPDATE as you have mention below. So we are converging
>into your option 1 solution.
>
>Please note that it complicates little bit SRC implementation.
>
>Any concerns and comments?
>
>Thank you for raising this issue.
>
>Leon
>
>On Nov 16, 2011, at 3:30 PM, Ravindran, Parthasarathi wrote:
>
>> Leon,
>>
>> Please read inline.
>>
>> Thanks
>> Partha
>>
>>> -----Original Message-----
>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>> Sent: Wednesday, November 16, 2011 2:48 PM
>>> To: Hutton, Andrew
>>> Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com;
>>> siprec@ietf.org
>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>
>>> If we will use OK response from SRC to SRS for reporting metadata
>>> snapshot
>>
>> <partha> We are in the same page till here </partha>
>>
>> and SRS will want to update SDP - for example because it needs
>>> to terminate or redirect one of the RS media streams, it will need to
>>> do it in separate REINVITE and UPDATE after ACK?
>>
>> <partha> IIUC, SRS will trigger one another offer/answer to terminate
>> RS Media stream. But I'm not very clear about the redirect of RS media
>> stream Scenario </partha>
>>
>>>
>>> Leon
>>>
>>> On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>>>
>>>> Hi,
>>>>
>>>> If I understand this correctly the discussion is how should the SRS
>>> initiate a snapshot from the SRC and how does this impact the
>>> offer/answer.
>>>>
>>>> The snapshot has I believe to include both an SDP offer and the
>>> associated XML representing the metadata. The only way to initiate a
>>> new SDP offer within the dialog is for the SRS to send a reINVITE
>>> without SDP to the SRC causes the SRC to respond with the SDP Offer
>>> and associated metadata snapshot in the 200OK which will of course
>>> cause the SRS to generate an SDP answer in the ACK.
>>>>
>>>> The SRS could also include an SDP offer in the reINVITE and have the
>>> SRC create the answer.
>>>>
>>>> In either case it should be that there is no change in the SDP from
>>> the previous offer/answer and therefore it is effectively a session
>>> refresh and does not cause an media interruption.
>>>>
>>>> Regards
>>>> Andy
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>> Behalf Of Leon Portman
>>>>> Sent: 16 November 2011 13:43
>>>>> To: Ravindran, Parthasarathi
>>>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>
>>>>> Most important from SRS point of view, is to define a mechanism for
>>>>> snapshot request that will not terminate recording session even for
>>>>> shortest possible time.
>>>>>
>>>>> My concern is if new INVITE will do that
>>>>>
>>>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>>>
>>>>>> If offer-less REINVITE works (it seems to be) i dont have problem
>>>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>>>
>>>>>> Leon
>>>>>>
>>>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>>>
>>>>>>> Leon,
>>>>>>>
>>>>>>> Please read inline.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Partha
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>>>> siprec@ietf.org
>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>
>>>>>>>> Patha
>>>>>>>>
>>>>>>>> Please see below
>>>>>>>>
>>>>>>>> Leon
>>>>>>>>
>>>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>
>>>>>>>>> Leon,
>>>>>>>>>
>>>>>>>>> I agree with Ram.
>>>>>>>>>
>>>>>>>>> It is possible to debate on this normative statement
>>>>>>>>> requirement
>>>>> as
>>>>>>>>> multiple way to request the full snapshot from SRS. Some of the
>>>>> way
>>>>>>>>> from SRS are as follows:
>>>>>>>>>
>>>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>>>>> messages)
>>>>>>>> In this case, is it legal for SRC to answer SDP less INVITE with
>>>>> SDP?
>>>>>>>> Snapshot requires SDP
>>>>>>> <partha> AFAIK, Re-INVITE without SDP is used to get offer from
>>>>>>> the
>>>>> remote
>>>>>>> Side. Even Hadriel mail threads says the same. Could you please
>>>>> point out
>>>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer
>work?
>>>>> </partha>
>>>>>>>
>>>>>>>
>>>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>>>> messages)
>>>>>>>> What if SRS does not have SDP?
>>>>>>> <partha> In that case, it will end-up in OPTION 1 or 3 but please
>>>>> note that
>>>>>>> It is possible to SRS to send SDP in case it has the idea of what
>>>>> has to be
>>>>>>> Recorded. </partha>
>>>>>>>
>>>>>>>
>>>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>>>> Separate (4 SIP messages)
>>>>>>>>>
>>>>>>>
>>>>>>> <partha> I have started thinking whether it is appropriate for
>>>>> UPDATE from SRC
>>>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
>>>>> proposal mandates
>>>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>>>>> UPDATE is not
>>>>>>> designed for that. I may be wrong here but we need careful
>>>>>>> analysis
>>>>> here </partha>
>>>>>>>
>>>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>>>> OPTION
>>>>> 3
>>>>>>>>> but I prefer to have the implementation choice. As mentioned
>>>>> above,
>>>>>>>>> OPTION 1 & 2 has less SIP message required to achieve the same
>>>>> compare
>>>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Partha
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>>>> henry.lum@genesyslab.com
>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>>
>>>>>>>>>> Leon,
>>>>>>>>>>
>>>>>>>>>> Please see inline. I have a question here
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>>>>>>> [mailto:siprec-bounces@ietf.org]
>>>>> On
>>>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>> Subject: Re: [siprec] Comment on
>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>
>>>>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>>>>> request.
>>>>>>>>>>>
>>>>>>>>>>> In section 8.2 we say:
>>>>>>>>>>>
>>>>>>>>>>> "   When the SRC receives the request for a metadata
>snapshot,
>>>>> the
>>>>>>>> SRC
>>>>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>>>>
>>>>>>>>>>> meaning that full metadata is actually separate INVITE
>>>>> transaction.
>>>>>>>>>>
>>>>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>>>>> Can't it
>>>>>>>>>> be sent as a response to snapshot request from SRS ? Is there
>>>>>>>>>> a reason why you want to mandate that way ?
>>>>>>>>>>
>>>>>>>>>> Ram
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Leon
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Partha Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> Please see below
>>>>>>>>>>>>
>>>>>>>>>>>> Leon
>>>>>>>>>>>>
>>>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please read inline
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>>>> 02
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>>>>>>> specific
>>>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha> I'm not very sure whether it is appropriate to use
>>>>> "may"
>>>>>>>>>> in
>>>>>>>>>>> the specification.
>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>>>>> instead
>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>> current audio.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1
>>>>>>>>>>>>>>> "Note that
>>>>>>>>>>> when
>>>>>>>>>>>>>> a CS
>>>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey
>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>> currently.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>>>>> rephrase
>>>>>>>>>>> it to
>>>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>>>> <partha> Currently, it is outside the scope of metadata and
>>>>> IMO,
>>>>>>>>>>>>> it
>>>>>>>>>>> is better
>>>>>>>>>>>>> to remove "mute/unmute" from protocol spec </partha>
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 4) Whether the normative statement required for mute? Sec
>>>>> 6.1.1
>>>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with
>>>>>>>>>>>>>>> a=3Dinactive
>>>>> for
>>>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>>>> the
>>>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>>>>>>> handled
>>>>>>>>>>> like
>>>>>>>>>>>>>> "hold"
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha> IMO, there should be no normative statement
>>>>>>>>>>>>> related
>>>>> to
>>>>>>>>>> mute
>>>>>>>>>>> </partha>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>>>> metadata
>>>>>>>>>>> delivery
>>>>>>>>>>>>>> which shall
>>>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>>>> repetition
>>>>>>>>>>> here
>>>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha> I can live with incase everybody wants with
>>>>> duplication
>>>>>>>>>>>>> on
>>>>>>>>>>> text
>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>>>>> instead
>>>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>>>>> UPDATE as
>>>>>>>>>>> well.
>>>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
>>>>> SRC
>>>>>>>>>>> sends a
>>>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>>>> "recording-
>>>>>>>>>>> session"
>>>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>>>>> order to
>>>>>>>>>>> make
>>>>>>>>>>>>>> sure that SDP will be present as well. Dont have any
>>>>>>>>>>>>>> strong
>>>>>>>>>>> preferences
>>>>>>>>>>>>>> here.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha> We had the discussion during IETF-80 to mandate
>>>>> INVITE &
>>>>>>>>>>> UPDATE.
>>>>>>>>>>>>> But I could not find the reason for not using UPDATE for
>>>>>>>>>>>>> full
>>>>>>>>>>> snapshot
>>>>>>>>>>>>> Request </partha>
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>>>> changed as
>>>>>>>>>>> SIP
>>>>>>>>>>>>>>> header or clear indication within the message to indicate
>>>>>>>>>> metadata
>>>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>>>> explicitly
>>>>>>>>>>> like
>>>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>>>> recommendation
>>>>>>>>>> of
>>>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha> Currently, it is plain text now whereas SRC has no
>>>>> means
>>>>>>>>>> to
>>>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion
>>>>>>>>>>>>> about
>>>>> the
>>>>>>>>>>> text
>>>>>>>>>>>>> helps for the implementation by which SRC understand.
>>>>> </partha>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> 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
>>


From pkyzivat@alum.mit.edu  Wed Nov 16 00:07:13 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 27A3511E81F4 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.213
X-Spam-Level: 
X-Spam-Status: No, score=-2.213 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x06gVMHl0Sv9 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:07:09 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id ED5B011E81EB for <siprec@ietf.org>; Wed, 16 Nov 2011 00:07:08 -0800 (PST)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta13.westchester.pa.mail.comcast.net with comcast id xk691h00F1swQuc5Dk79js; Wed, 16 Nov 2011 08:07:09 +0000
Received: from dhcp-16f3.meeting.ietf.org ([130.129.22.243]) by omta15.westchester.pa.mail.comcast.net with comcast id xk6x1h00Q5EhBnE3bk71jx; Wed, 16 Nov 2011 08:07:07 +0000
Message-ID: <4EC36F1F.4000605@alum.mit.edu>
Date: Wed, 16 Nov 2011 16:06:55 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com>
In-Reply-To: <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 08:07:13 -0000

The reply I just sent was written earlier and just now sent, before I 
caught up on reading and found the subject already much evolved.

On 11/16/11 3:35 PM, Leon Portman wrote:
> Partha
>
> It seems to be that we are converging into solution where SRS will send offer-less INVITE with snapshot request and SRC will response with OK including metadata snapshot XML and SDP and SRS will ACK this SDP. If any media updates are required from SRS , they will be carried in separate INVITE/UPDATE as you have mention below. So we are converging into your option 1 solution.
>
> Please note that it complicates little bit SRC implementation.

Another consideration is that it might take time to prepare the shapshot 
for sending, and it is desired not to delay response to the request. 
That is another reason to decouple sending the snapshot from the 
response to the snapshot request.

IMO the SRC should at least have the *option* to defer sending the snapshot.

I'm ok with *allowing* the SRC to send the shapshot with the response if 
it is capable of doing so.

	Thanks,
	Paul

> Any concerns and comments?
>
> Thank you for raising this issue.
>
> Leon
>
> On Nov 16, 2011, at 3:30 PM, Ravindran, Parthasarathi wrote:
>
>> Leon,
>>
>> Please read inline.
>>
>> Thanks
>> Partha
>>
>>> -----Original Message-----
>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>> Sent: Wednesday, November 16, 2011 2:48 PM
>>> To: Hutton, Andrew
>>> Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com; siprec@ietf.org
>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>
>>> If we will use OK response from SRC to SRS for reporting metadata
>>> snapshot
>>
>> <partha>  We are in the same page till here</partha>
>>
>> and SRS will want to update SDP - for example because it needs
>>> to terminate or redirect one of the RS media streams, it will need to do
>>> it in separate REINVITE and UPDATE after ACK?
>>
>> <partha>  IIUC, SRS will trigger one another offer/answer to terminate RS
>> Media stream. But I'm not very clear about the redirect of RS media stream
>> Scenario</partha>
>>
>>>
>>> Leon
>>>
>>> On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>>>
>>>> Hi,
>>>>
>>>> If I understand this correctly the discussion is how should the SRS
>>> initiate a snapshot from the SRC and how does this impact the
>>> offer/answer.
>>>>
>>>> The snapshot has I believe to include both an SDP offer and the
>>> associated XML representing the metadata. The only way to initiate a new
>>> SDP offer within the dialog is for the SRS to send a reINVITE without
>>> SDP to the SRC causes the SRC to respond with the SDP Offer and
>>> associated metadata snapshot in the 200OK which will of course cause the
>>> SRS to generate an SDP answer in the ACK.
>>>>
>>>> The SRS could also include an SDP offer in the reINVITE and have the
>>> SRC create the answer.
>>>>
>>>> In either case it should be that there is no change in the SDP from
>>> the previous offer/answer and therefore it is effectively a session
>>> refresh and does not cause an media interruption.
>>>>
>>>> Regards
>>>> Andy
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>> Behalf Of Leon Portman
>>>>> Sent: 16 November 2011 13:43
>>>>> To: Ravindran, Parthasarathi
>>>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>
>>>>> Most important from SRS point of view, is to define a mechanism for
>>>>> snapshot request that will not terminate recording session even for
>>>>> shortest possible time.
>>>>>
>>>>> My concern is if new INVITE will do that
>>>>>
>>>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>>>
>>>>>> If offer-less REINVITE works (it seems to be) i dont have problem
>>>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>>>
>>>>>> Leon
>>>>>>
>>>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>>>
>>>>>>> Leon,
>>>>>>>
>>>>>>> Please read inline.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Partha
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>>>> siprec@ietf.org
>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>
>>>>>>>> Patha
>>>>>>>>
>>>>>>>> Please see below
>>>>>>>>
>>>>>>>> Leon
>>>>>>>>
>>>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>
>>>>>>>>> Leon,
>>>>>>>>>
>>>>>>>>> I agree with Ram.
>>>>>>>>>
>>>>>>>>> It is possible to debate on this normative statement requirement
>>>>> as
>>>>>>>>> multiple way to request the full snapshot from SRS. Some of the
>>>>> way
>>>>>>>>> from SRS are as follows:
>>>>>>>>>
>>>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>>>>> messages)
>>>>>>>> In this case, is it legal for SRC to answer SDP less INVITE with
>>>>> SDP?
>>>>>>>> Snapshot requires SDP
>>>>>>> <partha>  AFAIK, Re-INVITE without SDP is used to get offer from the
>>>>> remote
>>>>>>> Side. Even Hadriel mail threads says the same. Could you please
>>>>> point out
>>>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer work?
>>>>> </partha>
>>>>>>>
>>>>>>>
>>>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>>>> messages)
>>>>>>>> What if SRS does not have SDP?
>>>>>>> <partha>  In that case, it will end-up in OPTION 1 or 3 but please
>>>>> note that
>>>>>>> It is possible to SRS to send SDP in case it has the idea of what
>>>>> has to be
>>>>>>> Recorded.</partha>
>>>>>>>
>>>>>>>
>>>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>>>> Separate (4 SIP messages)
>>>>>>>>>
>>>>>>>
>>>>>>> <partha>  I have started thinking whether it is appropriate for
>>>>> UPDATE from SRC
>>>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
>>>>> proposal mandates
>>>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>>>>> UPDATE is not
>>>>>>> designed for that. I may be wrong here but we need careful analysis
>>>>> here</partha>
>>>>>>>
>>>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>>>> OPTION
>>>>> 3
>>>>>>>>> but I prefer to have the implementation choice. As mentioned
>>>>> above,
>>>>>>>>> OPTION 1&  2 has less SIP message required to achieve the same
>>>>> compare
>>>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Partha
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>>>> henry.lum@genesyslab.com
>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>>
>>>>>>>>>> Leon,
>>>>>>>>>>
>>>>>>>>>> Please see inline. I have a question here
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>>>>> On
>>>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>>>
>>>>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>>>>> request.
>>>>>>>>>>>
>>>>>>>>>>> In section 8.2 we say:
>>>>>>>>>>>
>>>>>>>>>>> "   When the SRC receives the request for a metadata snapshot,
>>>>> the
>>>>>>>> SRC
>>>>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>>>>
>>>>>>>>>>> meaning that full metadata is actually separate INVITE
>>>>> transaction.
>>>>>>>>>>
>>>>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>>>>> Can't it
>>>>>>>>>> be sent as a response to snapshot request from SRS ? Is there a
>>>>>>>>>> reason why you want to mandate that way ?
>>>>>>>>>>
>>>>>>>>>> Ram
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Leon
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Partha Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> Please see below
>>>>>>>>>>>>
>>>>>>>>>>>> Leon
>>>>>>>>>>>>
>>>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please read inline
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>>>> 02
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>>>>>>> specific
>>>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha>  I'm not very sure whether it is appropriate to use
>>>>> "may"
>>>>>>>>>> in
>>>>>>>>>>> the specification.
>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>>>>> instead
>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>> current audio.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1
>>>>>>>>>>>>>>> "Note that
>>>>>>>>>>> when
>>>>>>>>>>>>>> a CS
>>>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>>>>>>>>> currently.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>>>>> rephrase
>>>>>>>>>>> it to
>>>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>>>> <partha>  Currently, it is outside the scope of metadata and
>>>>> IMO,
>>>>>>>>>>>>> it
>>>>>>>>>>> is better
>>>>>>>>>>>>> to remove "mute/unmute" from protocol spec</partha>
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 4) Whether the normative statement required for mute? Sec
>>>>> 6.1.1
>>>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with a=inactive
>>>>> for
>>>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>>>> the
>>>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>>>>>>> handled
>>>>>>>>>>> like
>>>>>>>>>>>>>> "hold"
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha>  IMO, there should be no normative statement related
>>>>> to
>>>>>>>>>> mute
>>>>>>>>>>> </partha>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>>>> metadata
>>>>>>>>>>> delivery
>>>>>>>>>>>>>> which shall
>>>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>>>> repetition
>>>>>>>>>>> here
>>>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha>  I can live with incase everybody wants with
>>>>> duplication
>>>>>>>>>>>>> on
>>>>>>>>>>> text
>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>>>>> instead
>>>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>>>>> UPDATE as
>>>>>>>>>>> well.
>>>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
>>>>> SRC
>>>>>>>>>>> sends a
>>>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>>>> "recording-
>>>>>>>>>>> session"
>>>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>>>>> order to
>>>>>>>>>>> make
>>>>>>>>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>>>>>>>>> preferences
>>>>>>>>>>>>>> here.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha>  We had the discussion during IETF-80 to mandate
>>>>> INVITE&
>>>>>>>>>>> UPDATE.
>>>>>>>>>>>>> But I could not find the reason for not using UPDATE for full
>>>>>>>>>>> snapshot
>>>>>>>>>>>>> Request</partha>
>>>>>>>>>>>>
>>>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>>>> changed as
>>>>>>>>>>> SIP
>>>>>>>>>>>>>>> header or clear indication within the message to indicate
>>>>>>>>>> metadata
>>>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>>>> explicitly
>>>>>>>>>>> like
>>>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>>>> recommendation
>>>>>>>>>> of
>>>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> <partha>  Currently, it is plain text now whereas SRC has no
>>>>> means
>>>>>>>>>> to
>>>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion about
>>>>> the
>>>>>>>>>>> text
>>>>>>>>>>>>> helps for the implementation by which SRC understand.
>>>>> </partha>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> 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
>>
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>


From pravindran@sonusnet.com  Wed Nov 16 00:17:28 2011
Return-Path: <pravindran@sonusnet.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 EB88D1F0C41 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.29
X-Spam-Level: 
X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5 tests=[AWL=-0.291,  BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vDuTVtk2LD8O for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:17:03 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id C41141F0C3F for <siprec@ietf.org>; Wed, 16 Nov 2011 00:17:01 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAG8HbJ6024168;  Wed, 16 Nov 2011 03:17:37 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 03:16:45 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 13:46:59 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Wed, 16 Nov 2011 13:46:59 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVCAAfdcAIAAFlAAgAAC/YD//6LIIIAAYtkA//+jbqAAEGLoAAAATaOAAAF4G4AAAMvZgP//m1vw//+N/YD//xM3gP/9x/qg
Date: Wed, 16 Nov 2011 08:16:57 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com> <4EC36F1F.4000605@alum.mit.edu>
In-Reply-To: <4EC36F1F.4000605@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Nov 2011 08:16:59.0252 (UTC) FILETIME=[1CA3C340:01CCA438]
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 08:17:28 -0000

Paul,

IIUC, SRC has to send its current snapshot. I could not understand=20
the reason to defer at this stage. Of course, 100 response shall be sent fo=
r
RE-INVITE of metadata snapshot request by which will help to defer even if=
=20
required.

Thanks
Partha

>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>Of Paul Kyzivat
>Sent: Wednesday, November 16, 2011 4:07 PM
>To: siprec@ietf.org
>Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>
>The reply I just sent was written earlier and just now sent, before I
>caught up on reading and found the subject already much evolved.
>
>On 11/16/11 3:35 PM, Leon Portman wrote:
>> Partha
>>
>> It seems to be that we are converging into solution where SRS will
>send offer-less INVITE with snapshot request and SRC will response with
>OK including metadata snapshot XML and SDP and SRS will ACK this SDP. If
>any media updates are required from SRS , they will be carried in
>separate INVITE/UPDATE as you have mention below. So we are converging
>into your option 1 solution.
>>
>> Please note that it complicates little bit SRC implementation.
>
>Another consideration is that it might take time to prepare the shapshot
>for sending, and it is desired not to delay response to the request.
>That is another reason to decouple sending the snapshot from the
>response to the snapshot request.
>
>IMO the SRC should at least have the *option* to defer sending the
>snapshot.
>
>I'm ok with *allowing* the SRC to send the shapshot with the response if
>it is capable of doing so.
>
>	Thanks,
>	Paul
>
>> Any concerns and comments?
>>
>> Thank you for raising this issue.
>>
>> Leon
>>
>> On Nov 16, 2011, at 3:30 PM, Ravindran, Parthasarathi wrote:
>>
>>> Leon,
>>>
>>> Please read inline.
>>>
>>> Thanks
>>> Partha
>>>
>>>> -----Original Message-----
>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>> Sent: Wednesday, November 16, 2011 2:48 PM
>>>> To: Hutton, Andrew
>>>> Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com;
>>>> siprec@ietf.org
>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>
>>>> If we will use OK response from SRC to SRS for reporting metadata
>>>> snapshot
>>>
>>> <partha>  We are in the same page till here</partha>
>>>
>>> and SRS will want to update SDP - for example because it needs
>>>> to terminate or redirect one of the RS media streams, it will need
>>>> to do it in separate REINVITE and UPDATE after ACK?
>>>
>>> <partha>  IIUC, SRS will trigger one another offer/answer to
>>> terminate RS Media stream. But I'm not very clear about the redirect
>>> of RS media stream Scenario</partha>
>>>
>>>>
>>>> Leon
>>>>
>>>> On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> If I understand this correctly the discussion is how should the SRS
>>>> initiate a snapshot from the SRC and how does this impact the
>>>> offer/answer.
>>>>>
>>>>> The snapshot has I believe to include both an SDP offer and the
>>>> associated XML representing the metadata. The only way to initiate a
>>>> new SDP offer within the dialog is for the SRS to send a reINVITE
>>>> without SDP to the SRC causes the SRC to respond with the SDP Offer
>>>> and associated metadata snapshot in the 200OK which will of course
>>>> cause the SRS to generate an SDP answer in the ACK.
>>>>>
>>>>> The SRS could also include an SDP offer in the reINVITE and have
>>>>> the
>>>> SRC create the answer.
>>>>>
>>>>> In either case it should be that there is no change in the SDP from
>>>> the previous offer/answer and therefore it is effectively a session
>>>> refresh and does not cause an media interruption.
>>>>>
>>>>> Regards
>>>>> Andy
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>>> Behalf Of Leon Portman
>>>>>> Sent: 16 November 2011 13:43
>>>>>> To: Ravindran, Parthasarathi
>>>>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>
>>>>>> Most important from SRS point of view, is to define a mechanism
>>>>>> for snapshot request that will not terminate recording session
>>>>>> even for shortest possible time.
>>>>>>
>>>>>> My concern is if new INVITE will do that
>>>>>>
>>>>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>>>>
>>>>>>> If offer-less REINVITE works (it seems to be) i dont have problem
>>>>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>>>>
>>>>>>> Leon
>>>>>>>
>>>>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>>>>
>>>>>>>> Leon,
>>>>>>>>
>>>>>>>> Please read inline.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Partha
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>>>>> siprec@ietf.org
>>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>
>>>>>>>>> Patha
>>>>>>>>>
>>>>>>>>> Please see below
>>>>>>>>>
>>>>>>>>> Leon
>>>>>>>>>
>>>>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>
>>>>>>>>>> Leon,
>>>>>>>>>>
>>>>>>>>>> I agree with Ram.
>>>>>>>>>>
>>>>>>>>>> It is possible to debate on this normative statement
>>>>>>>>>> requirement
>>>>>> as
>>>>>>>>>> multiple way to request the full snapshot from SRS. Some of
>>>>>>>>>> the
>>>>>> way
>>>>>>>>>> from SRS are as follows:
>>>>>>>>>>
>>>>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>>>>>> messages)
>>>>>>>>> In this case, is it legal for SRC to answer SDP less INVITE
>>>>>>>>> with
>>>>>> SDP?
>>>>>>>>> Snapshot requires SDP
>>>>>>>> <partha>  AFAIK, Re-INVITE without SDP is used to get offer from
>>>>>>>> the
>>>>>> remote
>>>>>>>> Side. Even Hadriel mail threads says the same. Could you please
>>>>>> point out
>>>>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer
>work?
>>>>>> </partha>
>>>>>>>>
>>>>>>>>
>>>>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>>>>> messages)
>>>>>>>>> What if SRS does not have SDP?
>>>>>>>> <partha>  In that case, it will end-up in OPTION 1 or 3 but
>>>>>>>> please
>>>>>> note that
>>>>>>>> It is possible to SRS to send SDP in case it has the idea of
>>>>>>>> what
>>>>>> has to be
>>>>>>>> Recorded.</partha>
>>>>>>>>
>>>>>>>>
>>>>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>>>>> Separate (4 SIP messages)
>>>>>>>>>>
>>>>>>>>
>>>>>>>> <partha>  I have started thinking whether it is appropriate for
>>>>>> UPDATE from SRC
>>>>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM,
>>>>>>>> the
>>>>>> proposal mandates
>>>>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>>>>>> UPDATE is not
>>>>>>>> designed for that. I may be wrong here but we need careful
>>>>>>>> analysis
>>>>>> here</partha>
>>>>>>>>
>>>>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>>>>> OPTION
>>>>>> 3
>>>>>>>>>> but I prefer to have the implementation choice. As mentioned
>>>>>> above,
>>>>>>>>>> OPTION 1&  2 has less SIP message required to achieve the same
>>>>>> compare
>>>>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>> Partha
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>>>>> henry.lum@genesyslab.com
>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>> Subject: RE: [siprec] Comment on
>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>
>>>>>>>>>>> Leon,
>>>>>>>>>>>
>>>>>>>>>>> Please see inline. I have a question here
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>>>>>>>> [mailto:siprec-bounces@ietf.org]
>>>>>> On
>>>>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>> Subject: Re: [siprec] Comment on
>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>
>>>>>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>>>>>> request.
>>>>>>>>>>>>
>>>>>>>>>>>> In section 8.2 we say:
>>>>>>>>>>>>
>>>>>>>>>>>> "   When the SRC receives the request for a metadata
>snapshot,
>>>>>> the
>>>>>>>>> SRC
>>>>>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>>>>>
>>>>>>>>>>>> meaning that full metadata is actually separate INVITE
>>>>>> transaction.
>>>>>>>>>>>
>>>>>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>>>>>> Can't it
>>>>>>>>>>> be sent as a response to snapshot request from SRS ? Is there
>>>>>>>>>>> a reason why you want to mandate that way ?
>>>>>>>>>>>
>>>>>>>>>>> Ram
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Leon
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Partha Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>
>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi
>wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please read inline
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>>>>> 02
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in
>>>>>>>>>>>>>>> this
>>>>>>>>>>> specific
>>>>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <partha>  I'm not very sure whether it is appropriate to
>>>>>>>>>>>>>> use
>>>>>> "may"
>>>>>>>>>>> in
>>>>>>>>>>>> the specification.
>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>>>>>> instead
>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>> current audio.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1
>>>>>>>>>>>>>>>> "Note that
>>>>>>>>>>>> when
>>>>>>>>>>>>>>> a CS
>>>>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey
>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>> currently.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>>>>>> rephrase
>>>>>>>>>>>> it to
>>>>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>>>>> <partha>  Currently, it is outside the scope of metadata
>>>>>>>>>>>>>> and
>>>>>> IMO,
>>>>>>>>>>>>>> it
>>>>>>>>>>>> is better
>>>>>>>>>>>>>> to remove "mute/unmute" from protocol spec</partha>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 4) Whether the normative statement required for mute?
>>>>>>>>>>>>>>>> Sec
>>>>>> 6.1.1
>>>>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with
>>>>>>>>>>>>>>>> a=3Dinactive
>>>>>> for
>>>>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not
>>>>>>>>>>>>>>> be handled
>>>>>>>>>>>> like
>>>>>>>>>>>>>>> "hold"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <partha>  IMO, there should be no normative statement
>>>>>>>>>>>>>> related
>>>>>> to
>>>>>>>>>>> mute
>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>> delivery
>>>>>>>>>>>>>>> which shall
>>>>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>>>>> repetition
>>>>>>>>>>>> here
>>>>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <partha>  I can live with incase everybody wants with
>>>>>> duplication
>>>>>>>>>>>>>> on
>>>>>>>>>>>> text
>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>>>>>> instead
>>>>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>>>>>> UPDATE as
>>>>>>>>>>>> well.
>>>>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When
>>>>>>>>>>>>>>>> the
>>>>>> SRC
>>>>>>>>>>>> sends a
>>>>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>>>>> "recording-
>>>>>>>>>>>> session"
>>>>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>>>>>> order to
>>>>>>>>>>>> make
>>>>>>>>>>>>>>> sure that SDP will be present as well. Dont have any
>>>>>>>>>>>>>>> strong
>>>>>>>>>>>> preferences
>>>>>>>>>>>>>>> here.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <partha>  We had the discussion during IETF-80 to mandate
>>>>>> INVITE&
>>>>>>>>>>>> UPDATE.
>>>>>>>>>>>>>> But I could not find the reason for not using UPDATE for
>>>>>>>>>>>>>> full
>>>>>>>>>>>> snapshot
>>>>>>>>>>>>>> Request</partha>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>>>>> changed as
>>>>>>>>>>>> SIP
>>>>>>>>>>>>>>>> header or clear indication within the message to
>>>>>>>>>>>>>>>> indicate
>>>>>>>>>>> metadata
>>>>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>>>>> explicitly
>>>>>>>>>>>> like
>>>>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>>>>> recommendation
>>>>>>>>>>> of
>>>>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <partha>  Currently, it is plain text now whereas SRC has
>>>>>>>>>>>>>> no
>>>>>> means
>>>>>>>>>>> to
>>>>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion
>>>>>>>>>>>>>> about
>>>>>> the
>>>>>>>>>>>> text
>>>>>>>>>>>>>> helps for the implementation by which SRC understand.
>>>>>> </partha>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> 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
>>>
>>
>> _______________________________________________
>> 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

From pkyzivat@alum.mit.edu  Wed Nov 16 00:42:13 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 3BB4921F94CF for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:42:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.187
X-Spam-Level: 
X-Spam-Status: No, score=-2.187 tagged_above=-999 required=5 tests=[AWL=-0.188, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XoD2ylQBJq6O for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:42:12 -0800 (PST)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id 1152921F94B8 for <siprec@ietf.org>; Wed, 16 Nov 2011 00:42:11 -0800 (PST)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta01.westchester.pa.mail.comcast.net with comcast id xkhE1h0030ldTLk51kiCbF; Wed, 16 Nov 2011 08:42:12 +0000
Received: from dhcp-16f3.meeting.ietf.org ([130.129.22.243]) by omta04.westchester.pa.mail.comcast.net with comcast id xkhz1h00X5EhBnE3Qki373; Wed, 16 Nov 2011 08:42:10 +0000
Message-ID: <4EC37755.3060403@alum.mit.edu>
Date: Wed, 16 Nov 2011 16:41:57 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 08:42:13 -0000

On 11/16/11 2:24 PM, Hutton, Andrew wrote:
> Hi,
>
> If I understand this correctly the discussion is how should the SRS initiate a snapshot from the SRC and how does this impact the offer/answer.
>
> The snapshot has I believe to include both an SDP offer and the associated XML representing the metadata. The only way to initiate a new SDP offer within the dialog is for the SRS to send a reINVITE without SDP to the SRC causes the SRC to respond with the SDP Offer and associated metadata snapshot in the 200OK which will of course cause the SRS to generate an SDP answer in the ACK.
>
> The SRS could also include an SDP offer in the reINVITE and have the SRC create the answer.
>
> In either case it should be that there is no change in the SDP from the previous offer/answer and therefore it is effectively a session refresh and does not cause an media interruption.

IMO you can't assume that.
Its possible that there have been changes that have not yet been 
reported. Would you require that it send the snapshot of only the old 
stuff, not the changes?

	Thanks,
	Paul

> Regards
> Andy
>
>
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Leon Portman
>> Sent: 16 November 2011 13:43
>> To: Ravindran, Parthasarathi
>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>
>> Most important from SRS point of view, is to define a mechanism for
>> snapshot request that will not terminate recording session even for
>> shortest possible time.
>>
>> My concern is if new INVITE will do that
>>
>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>
>>> If offer-less REINVITE works (it seems to be) i dont have problem
>> with supporting option 1 as well. Any SIP experts opinions?
>>>
>>> Leon
>>>
>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>
>>>> Leon,
>>>>
>>>> Please read inline.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>> To: Ravindran, Parthasarathi
>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>> siprec@ietf.org
>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>
>>>>> Patha
>>>>>
>>>>> Please see below
>>>>>
>>>>> Leon
>>>>>
>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>
>>>>>> Leon,
>>>>>>
>>>>>> I agree with Ram.
>>>>>>
>>>>>> It is possible to debate on this normative statement requirement
>> as
>>>>>> multiple way to request the full snapshot from SRS. Some of the
>> way
>>>>>> from SRS are as follows:
>>>>>>
>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>> messages)
>>>>> In this case, is it legal for SRC to answer SDP less INVITE with
>> SDP?
>>>>> Snapshot requires SDP
>>>> <partha>  AFAIK, Re-INVITE without SDP is used to get offer from the
>> remote
>>>> Side. Even Hadriel mail threads says the same. Could you please
>> point out
>>>> RFC 3261 Section to point how RE-INVITE without offer/answer work?
>> </partha>
>>>>
>>>>
>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>> messages)
>>>>> What if SRS does not have SDP?
>>>> <partha>  In that case, it will end-up in OPTION 1 or 3 but please
>> note that
>>>> It is possible to SRS to send SDP in case it has the idea of what
>> has to be
>>>> Recorded.</partha>
>>>>
>>>>
>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>> Separate (4 SIP messages)
>>>>>>
>>>>
>>>> <partha>  I have started thinking whether it is appropriate for
>> UPDATE from SRC
>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
>> proposal mandates
>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>> UPDATE is not
>>>> designed for that. I may be wrong here but we need careful analysis
>> here</partha>
>>>>
>>>>>> IIUC, current SIPREC protocol mechanism propose to use only OPTION
>> 3
>>>>>> but I prefer to have the implementation choice. As mentioned
>> above,
>>>>>> OPTION 1&  2 has less SIP message required to achieve the same
>> compare
>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>
>>>>>> Thanks
>>>>>> Partha
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>> henry.lum@genesyslab.com
>>>>>>> Cc: siprec@ietf.org
>>>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>
>>>>>>> Leon,
>>>>>>>
>>>>>>> Please see inline. I have a question here
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>> On
>>>>>>>> Behalf Of Leon Portman
>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>
>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>> request.
>>>>>>>>
>>>>>>>> In section 8.2 we say:
>>>>>>>>
>>>>>>>> "   When the SRC receives the request for a metadata snapshot,
>> the
>>>>> SRC
>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>
>>>>>>>> meaning that full metadata is actually separate INVITE
>> transaction.
>>>>>>>
>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>> Can't it
>>>>>>> be sent as a response to snapshot request from SRS ? Is there a
>>>>>>> reason why you want to mandate that way ?
>>>>>>>
>>>>>>> Ram
>>>>>>>
>>>>>>>>
>>>>>>>> Leon
>>>>>>>>
>>>>>>>>
>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>
>>>>>>>>> Partha Thanks
>>>>>>>>>
>>>>>>>>> Please see below
>>>>>>>>>
>>>>>>>>> Leon
>>>>>>>>>
>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>
>>>>>>>>>> Leon,
>>>>>>>>>>
>>>>>>>>>> Please read inline
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>> Partha
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-
>> 02
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Partha Hi
>>>>>>>>>>>
>>>>>>>>>>> Please see below
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>> Leon
>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
>>>>>>>>>>>
>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>
>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
>>>>>>> specific
>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>
>>>>>>>>>> <partha>  I'm not very sure whether it is appropriate to use
>> "may"
>>>>>>> in
>>>>>>>> the specification.
>>>>>>>>>> </partha>
>>>>>>>>>
>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>
>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>> instead
>>>>>>>>>>>> of
>>>>>>>>>>> current audio.
>>>>>>>>>>>
>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1 "Note
>>>>>>>>>>>> that
>>>>>>>> when
>>>>>>>>>>> a CS
>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in the
>>>>>>>>>>> metadata
>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey this
>>>>>>>>>>> currently.
>>>>>>>>>>>>
>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>> rephrase
>>>>>>>> it to
>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>> <partha>  Currently, it is outside the scope of metadata and
>> IMO,
>>>>>>>>>> it
>>>>>>>> is better
>>>>>>>>>> to remove "mute/unmute" from protocol spec</partha>
>>>>>>>>>
>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>
>>>>>>>>>>>> 4) Whether the normative statement required for mute? Sec
>> 6.1.1
>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with a=inactive
>> for
>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>> the
>>>>>>>>>>>> RS media."
>>>>>>>>>>>>
>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
>>>>>>>>>>> handled
>>>>>>>> like
>>>>>>>>>>> "hold"
>>>>>>>>>>>
>>>>>>>>>> <partha>  IMO, there should be no normative statement related
>> to
>>>>>>> mute
>>>>>>>> </partha>
>>>>>>>>>>
>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
>>>>>>>> delivery
>>>>>>>>>>> which shall
>>>>>>>>>>>> be avoided.
>>>>>>>>>>>
>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>> repetition
>>>>>>>> here
>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>
>>>>>>>>>> <partha>  I can live with incase everybody wants with
>> duplication
>>>>>>>>>> on
>>>>>>>> text
>>>>>>>>>> </partha>
>>>>>>>>>>
>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>> instead
>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>
>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>> UPDATE as
>>>>>>>> well.
>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
>> SRC
>>>>>>>> sends a
>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>> send an INVITE request with an SDP offer and the "recording-
>>>>>>>> session"
>>>>>>>>>>>> disposition."
>>>>>>>>>>>>
>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>> order to
>>>>>>>> make
>>>>>>>>>>> sure that SDP will be present as well. Dont have any strong
>>>>>>>> preferences
>>>>>>>>>>> here.
>>>>>>>>>>>
>>>>>>>>>> <partha>  We had the discussion during IETF-80 to mandate
>> INVITE&
>>>>>>>> UPDATE.
>>>>>>>>>> But I could not find the reason for not using UPDATE for full
>>>>>>>> snapshot
>>>>>>>>>> Request</partha>
>>>>>>>>>
>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>
>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>> changed as
>>>>>>>> SIP
>>>>>>>>>>>> header or clear indication within the message to indicate
>>>>>>> metadata
>>>>>>>>>>> request. Also, reason for logging could be mentioned
>> explicitly
>>>>>>>> like
>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>
>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>
>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>> recommendation
>>>>>>> of
>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>
>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>
>>>>>>>>>> <partha>  Currently, it is plain text now whereas SRC has no
>> means
>>>>>>> to
>>>>>>>>>> understand about  the logs. Some guidelines/suggestion about
>> the
>>>>>>>> text
>>>>>>>>>> helps for the implementation by which SRC understand.
>> </partha>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Partha
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>


From pkyzivat@alum.mit.edu  Wed Nov 16 00:46:25 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 B5C5E21F94EB for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:46:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GTTlyrdfpg4F for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 00:46:24 -0800 (PST)
Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by ietfa.amsl.com (Postfix) with ESMTP id 6B15721F94E3 for <siprec@ietf.org>; Wed, 16 Nov 2011 00:46:24 -0800 (PST)
Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta14.emeryville.ca.mail.comcast.net with comcast id xklx1h00E1smiN4AEkmHpv; Wed, 16 Nov 2011 08:46:17 +0000
Received: from dhcp-16f3.meeting.ietf.org ([130.129.22.243]) by omta20.emeryville.ca.mail.comcast.net with comcast id xkTg1h00Y5EhBnE8gkTjhq; Wed, 16 Nov 2011 08:27:51 +0000
Message-ID: <4EC37852.60809@alum.mit.edu>
Date: Wed, 16 Nov 2011 16:46:10 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com> <4EC36F1F.4000605@alum.mit.edu> <387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 08:46:25 -0000

On 11/16/11 4:16 PM, Ravindran, Parthasarathi wrote:
> Paul,
>
> IIUC, SRC has to send its current snapshot. I could not understand
> the reason to defer at this stage. Of course, 100 response shall be sent for
> RE-INVITE of metadata snapshot request by which will help to defer even if
> required.

I think we had this discussion once before.
The application that formats the metadata is a different layer from the 
stack, and may be decoupled from it. We shouldn't assume anything about 
the latency between them.

Is there a *problem* with leaving this as an option for the SRC?
Is it going to matter to the SRS that it must wait for the snapshot?

	Thanks,
	Paul

> Thanks
> Partha
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>> Of Paul Kyzivat
>> Sent: Wednesday, November 16, 2011 4:07 PM
>> To: siprec@ietf.org
>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>
>> The reply I just sent was written earlier and just now sent, before I
>> caught up on reading and found the subject already much evolved.
>>
>> On 11/16/11 3:35 PM, Leon Portman wrote:
>>> Partha
>>>
>>> It seems to be that we are converging into solution where SRS will
>> send offer-less INVITE with snapshot request and SRC will response with
>> OK including metadata snapshot XML and SDP and SRS will ACK this SDP. If
>> any media updates are required from SRS , they will be carried in
>> separate INVITE/UPDATE as you have mention below. So we are converging
>> into your option 1 solution.
>>>
>>> Please note that it complicates little bit SRC implementation.
>>
>> Another consideration is that it might take time to prepare the shapshot
>> for sending, and it is desired not to delay response to the request.
>> That is another reason to decouple sending the snapshot from the
>> response to the snapshot request.
>>
>> IMO the SRC should at least have the *option* to defer sending the
>> snapshot.
>>
>> I'm ok with *allowing* the SRC to send the shapshot with the response if
>> it is capable of doing so.
>>
>> 	Thanks,
>> 	Paul
>>
>>> Any concerns and comments?
>>>
>>> Thank you for raising this issue.
>>>
>>> Leon
>>>
>>> On Nov 16, 2011, at 3:30 PM, Ravindran, Parthasarathi wrote:
>>>
>>>> Leon,
>>>>
>>>> Please read inline.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>> Sent: Wednesday, November 16, 2011 2:48 PM
>>>>> To: Hutton, Andrew
>>>>> Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com;
>>>>> siprec@ietf.org
>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>
>>>>> If we will use OK response from SRC to SRS for reporting metadata
>>>>> snapshot
>>>>
>>>> <partha>   We are in the same page till here</partha>
>>>>
>>>> and SRS will want to update SDP - for example because it needs
>>>>> to terminate or redirect one of the RS media streams, it will need
>>>>> to do it in separate REINVITE and UPDATE after ACK?
>>>>
>>>> <partha>   IIUC, SRS will trigger one another offer/answer to
>>>> terminate RS Media stream. But I'm not very clear about the redirect
>>>> of RS media stream Scenario</partha>
>>>>
>>>>>
>>>>> Leon
>>>>>
>>>>> On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> If I understand this correctly the discussion is how should the SRS
>>>>> initiate a snapshot from the SRC and how does this impact the
>>>>> offer/answer.
>>>>>>
>>>>>> The snapshot has I believe to include both an SDP offer and the
>>>>> associated XML representing the metadata. The only way to initiate a
>>>>> new SDP offer within the dialog is for the SRS to send a reINVITE
>>>>> without SDP to the SRC causes the SRC to respond with the SDP Offer
>>>>> and associated metadata snapshot in the 200OK which will of course
>>>>> cause the SRS to generate an SDP answer in the ACK.
>>>>>>
>>>>>> The SRS could also include an SDP offer in the reINVITE and have
>>>>>> the
>>>>> SRC create the answer.
>>>>>>
>>>>>> In either case it should be that there is no change in the SDP from
>>>>> the previous offer/answer and therefore it is effectively a session
>>>>> refresh and does not cause an media interruption.
>>>>>>
>>>>>> Regards
>>>>>> Andy
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>>>> Behalf Of Leon Portman
>>>>>>> Sent: 16 November 2011 13:43
>>>>>>> To: Ravindran, Parthasarathi
>>>>>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>
>>>>>>> Most important from SRS point of view, is to define a mechanism
>>>>>>> for snapshot request that will not terminate recording session
>>>>>>> even for shortest possible time.
>>>>>>>
>>>>>>> My concern is if new INVITE will do that
>>>>>>>
>>>>>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>>>>>
>>>>>>>> If offer-less REINVITE works (it seems to be) i dont have problem
>>>>>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>>>>>
>>>>>>>> Leon
>>>>>>>>
>>>>>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>
>>>>>>>>> Leon,
>>>>>>>>>
>>>>>>>>> Please read inline.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Partha
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>>>>>> siprec@ietf.org
>>>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>>
>>>>>>>>>> Patha
>>>>>>>>>>
>>>>>>>>>> Please see below
>>>>>>>>>>
>>>>>>>>>> Leon
>>>>>>>>>>
>>>>>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>>
>>>>>>>>>>> Leon,
>>>>>>>>>>>
>>>>>>>>>>> I agree with Ram.
>>>>>>>>>>>
>>>>>>>>>>> It is possible to debate on this normative statement
>>>>>>>>>>> requirement
>>>>>>> as
>>>>>>>>>>> multiple way to request the full snapshot from SRS. Some of
>>>>>>>>>>> the
>>>>>>> way
>>>>>>>>>>> from SRS are as follows:
>>>>>>>>>>>
>>>>>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
>>>>>>> messages)
>>>>>>>>>> In this case, is it legal for SRC to answer SDP less INVITE
>>>>>>>>>> with
>>>>>>> SDP?
>>>>>>>>>> Snapshot requires SDP
>>>>>>>>> <partha>   AFAIK, Re-INVITE without SDP is used to get offer from
>>>>>>>>> the
>>>>>>> remote
>>>>>>>>> Side. Even Hadriel mail threads says the same. Could you please
>>>>>>> point out
>>>>>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer
>> work?
>>>>>>> </partha>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>>>>>> messages)
>>>>>>>>>> What if SRS does not have SDP?
>>>>>>>>> <partha>   In that case, it will end-up in OPTION 1 or 3 but
>>>>>>>>> please
>>>>>>> note that
>>>>>>>>> It is possible to SRS to send SDP in case it has the idea of
>>>>>>>>> what
>>>>>>> has to be
>>>>>>>>> Recorded.</partha>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>>>>>> Separate (4 SIP messages)
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <partha>   I have started thinking whether it is appropriate for
>>>>>>> UPDATE from SRC
>>>>>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM,
>>>>>>>>> the
>>>>>>> proposal mandates
>>>>>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
>>>>>>> UPDATE is not
>>>>>>>>> designed for that. I may be wrong here but we need careful
>>>>>>>>> analysis
>>>>>>> here</partha>
>>>>>>>>>
>>>>>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>>>>>> OPTION
>>>>>>> 3
>>>>>>>>>>> but I prefer to have the implementation choice. As mentioned
>>>>>>> above,
>>>>>>>>>>> OPTION 1&   2 has less SIP message required to achieve the same
>>>>>>> compare
>>>>>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Partha
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>>>>>> henry.lum@genesyslab.com
>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>> Subject: RE: [siprec] Comment on
>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>
>>>>>>>>>>>> Leon,
>>>>>>>>>>>>
>>>>>>>>>>>> Please see inline. I have a question here
>>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>>>>>>>>> [mailto:siprec-bounces@ietf.org]
>>>>>>> On
>>>>>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>> Subject: Re: [siprec] Comment on
>>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>>
>>>>>>>>>>>>> Additional update on sending full metadata snapshot upon SRS
>>>>>>>>>> request.
>>>>>>>>>>>>>
>>>>>>>>>>>>> In section 8.2 we say:
>>>>>>>>>>>>>
>>>>>>>>>>>>> "   When the SRC receives the request for a metadata
>> snapshot,
>>>>>>> the
>>>>>>>>>> SRC
>>>>>>>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
>>>>>>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>>>>>>
>>>>>>>>>>>>> meaning that full metadata is actually separate INVITE
>>>>>>> transaction.
>>>>>>>>>>>>
>>>>>>>>>>>> Why should the snapshot be always sent in a separate INVITE.
>>>>>>> Can't it
>>>>>>>>>>>> be sent as a response to snapshot request from SRS ? Is there
>>>>>>>>>>>> a reason why you want to mandate that way ?
>>>>>>>>>>>>
>>>>>>>>>>>> Ram
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Partha Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi
>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please read inline
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>>>>>> 02
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
>>>>>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in
>>>>>>>>>>>>>>>> this
>>>>>>>>>>>> specific
>>>>>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <partha>   I'm not very sure whether it is appropriate to
>>>>>>>>>>>>>>> use
>>>>>>> "may"
>>>>>>>>>>>> in
>>>>>>>>>>>>> the specification.
>>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
>>>>>>> instead
>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>> current audio.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1
>>>>>>>>>>>>>>>>> "Note that
>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>> a CS
>>>>>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>>>> by the SRC. " because I don't know how metadata convey
>>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>> currently.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
>>>>>>> rephrase
>>>>>>>>>>>>> it to
>>>>>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>>>>>> <partha>   Currently, it is outside the scope of metadata
>>>>>>>>>>>>>>> and
>>>>>>> IMO,
>>>>>>>>>>>>>>> it
>>>>>>>>>>>>> is better
>>>>>>>>>>>>>>> to remove "mute/unmute" from protocol spec</partha>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 4) Whether the normative statement required for mute?
>>>>>>>>>>>>>>>>> Sec
>>>>>>> 6.1.1
>>>>>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with
>>>>>>>>>>>>>>>>> a=inactive
>>>>>>> for
>>>>>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not
>>>>>>>>>>>>>>>> be handled
>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>> "hold"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <partha>   IMO, there should be no normative statement
>>>>>>>>>>>>>>> related
>>>>>>> to
>>>>>>>>>>>> mute
>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>> delivery
>>>>>>>>>>>>>>>> which shall
>>>>>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>>>>>> repetition
>>>>>>>>>>>>> here
>>>>>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <partha>   I can live with incase everybody wants with
>>>>>>> duplication
>>>>>>>>>>>>>>> on
>>>>>>>>>>>>> text
>>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
>>>>>>> instead
>>>>>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
>>>>>>> UPDATE as
>>>>>>>>>>>>> well.
>>>>>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When
>>>>>>>>>>>>>>>>> the
>>>>>>> SRC
>>>>>>>>>>>>> sends a
>>>>>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>>>>>> "recording-
>>>>>>>>>>>>> session"
>>>>>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
>>>>>>> order to
>>>>>>>>>>>>> make
>>>>>>>>>>>>>>>> sure that SDP will be present as well. Dont have any
>>>>>>>>>>>>>>>> strong
>>>>>>>>>>>>> preferences
>>>>>>>>>>>>>>>> here.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <partha>   We had the discussion during IETF-80 to mandate
>>>>>>> INVITE&
>>>>>>>>>>>>> UPDATE.
>>>>>>>>>>>>>>> But I could not find the reason for not using UPDATE for
>>>>>>>>>>>>>>> full
>>>>>>>>>>>>> snapshot
>>>>>>>>>>>>>>> Request</partha>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>>>>>> changed as
>>>>>>>>>>>>> SIP
>>>>>>>>>>>>>>>>> header or clear indication within the message to
>>>>>>>>>>>>>>>>> indicate
>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>>>>>> explicitly
>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>>>>>> recommendation
>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <partha>   Currently, it is plain text now whereas SRC has
>>>>>>>>>>>>>>> no
>>>>>>> means
>>>>>>>>>>>> to
>>>>>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion
>>>>>>>>>>>>>>> about
>>>>>>> the
>>>>>>>>>>>>> text
>>>>>>>>>>>>>>> helps for the implementation by which SRC understand.
>>>>>>> </partha>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> 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
>>>>
>>>
>>> _______________________________________________
>>> 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
>


From eckelcu@cisco.com  Wed Nov 16 01:58:38 2011
Return-Path: <eckelcu@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 C3BEC21F95AB for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 01:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.237
X-Spam-Level: 
X-Spam-Status: No, score=-6.237 tagged_above=-999 required=5 tests=[AWL=0.362,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qS+Gl6DHFaLz for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 01:58:37 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id AC05421F957C for <siprec@ietf.org>; Wed, 16 Nov 2011 01:58:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=8187; q=dns/txt; s=iport; t=1321437517; x=1322647117; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=OD07T0ax4ssQztD95hVcBXsMdKTba/i4GsB8gnw4E7c=; b=PmF8jkwdUZRdJch/7L8fpMQu44Bosc03vwUTtzhAcyBTQaEXQ5e7PaP7 KANzBA0CHVogEBS9FGQJzSa6PAgkKFnj2MbyRGjEBjTFpI9gBYGP8C8eY SCuz5CbBRFzxoj/p9sM8iRITqeL7mdENpVIwAThZEVMT7/HkNsXbYe3In Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoAAK6Iw06rRDoH/2dsb2JhbABDDplgkAWBBYFyAQEBAwEBAQEPAR0KNAsMBAIBCBEEAQEBCgYXAQYBJh8JCAEBBAESCBqHYAiaXQGeVgSJNGMEiBSRZIwBWA
X-IronPort-AV: E=Sophos;i="4.69,520,1315180800"; d="scan'208";a="14516504"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 16 Nov 2011 09:58:37 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAG9wbXL016403; Wed, 16 Nov 2011 09:58:37 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 01:58:37 -0800
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, 16 Nov 2011 01:58:34 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05C13C55@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <C51D12EB-40A2-4B84-819D-F7485FD307D5@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] draft-ietf-siprec-protocol-02
Thread-Index: AcyibsCwEWoqafN3TuqEXr/Rz9uiqQB1sjfA
References: <4EBDAC36.1090007@alum.mit.edu> <C51D12EB-40A2-4B84-819D-F7485FD307D5@gmail.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Leon Portman" <leon.portman@gmail.com>, "Paul Kyzivat" <pkyzivat@alum.mit.edu>
X-OriginalArrivalTime: 16 Nov 2011 09:58:37.0402 (UTC) FILETIME=[4F6B9BA0:01CCA446]
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ietf-siprec-protocol-02
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, 16 Nov 2011 09:58:38 -0000

Sorry, just catching up things now. Regarding this snippet:

> > Section 9:
> >
> >   ... In order
> >   not to lose the NAT bindings for the RTP/RTCP ports opened for the
> >   recorded streams, the SRC and SRS SHOULD follow the
recommendations
> >   provided in [RFC6263] to maintain the NAT bindings.
> >
> > The recommendation involves also enabling multiplexing of rtcp and
rtp. If that is what we are going
> to do it would be worth calling that out, and showing it in the
examples.
> >
> > But that document also only applies when ICE isn't used.
> >
> > Maybe this should all be addressed as part of
draft-eckel-siprec-rtp-rec.
>=20
> [Leon] I am ok with that

draft-eckel-siprec-rtp-rec-03, section 10, reads as follows:

   It is anticipated that media streams in SIPREC may exist in inactive
   states for extended periods of times for an of a number of valid
   reasons.  In order for the bindings and any pinholes in NATs/
   firewalls to remain active during such intervals, it is RECOMMENDED
   to follow the keep-alive procedure recommended in "Application
   Mechanism for Keeping Alive the NAT Mappings Associated to RTP/RTP
   Control Protocol (RTCP) Flows" [RFC6263] for all RTP media streams.

Cheers,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Leon Portman
> Sent: Monday, November 14, 2011 9:43 AM
> To: Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: Re: [siprec] draft-ietf-siprec-protocol-02
>=20
> Paul Hi
>=20
> Thank you for the review. Please see below
>=20
> Leon
>=20
> On Nov 11, 2011, at 6:13 PM, Paul Kyzivat wrote:
>=20
> > I was just reviewing draft-ietf-siprec-protocol-02, and the
following are things I noted along the
> way:
> >
> > Section 4.2:
> >
> >   Metadata is transported in the body of INVITE or UPDATE messages.
> >   Certain metadata, such as the attributes of the recorded media
stream
> >   are located in the SDP of the recording session.
> >
> > I think we should point out that this is typically going to require
multipart support. Perhaps:
> >
> >   Metadata is transported within the body of INVITE or UPDATE
messages
> >   for the recording session. Most metadata is located in a siprec
> >   specific body part, but certain metadata, such as the attributes
> >   of the recorded media stream, are located in the SDP offer or
answer.
> >   In many cases this means a message will contain both a siprec
> >   specific part as well as an SDP part, contained within a body of
> >   type multipart/mixed.
>=20
> [Leon] I agree
>=20
> >
> > Figure 3:
> >
> > Shouldn't the first message be:
> >    (1) INVITE (metadata snapshot(1) + SDP offer)
> >
> [Leon] Correct ,it is also true for persistent recording use case
>=20
> > Section 5.1:
> >
> >   An SRS uses the presence of the 'src' feature
> >   tag in dialog creating and modifying requests and responses to
> >   confirm that the dialog being created is for the purpose of a
> >   Recording Session. ... Other SIP Recording extensions and
behaviors
> >   can be triggered by the presence of this feature tag.
> >
> > This is an abuse of the feature tag mechanism. The tag indicates a
*capability*. It shouldn't be
> used to infer intent. OTOH, I think it would be ok to interpret the
presence of metadata in the
> message as an indication that request is intended for the purpose of
establishing an RS.
> >
> > Also, the option tag should be "sip.src". (Indicated as "+sip.src"
in the Contact header.)
> >
> [Leon] I will add it to open items to the IETF 82 presentation. The
main question is if we always have
> metadata in RS INVITE. I think we always should have also for
persistent use case as well, even it
> only describes preallocated media sessions and not specific CS.
>=20
> >   Since SIP Caller Preferences extensions are optional to implement
for
> >   routing proxies, there is no guarantee that a recording session
will
> >   be routed to an SRC or SRS.  A new options tag is introduced:
> >   "siprec".  As per [RFC3261], only an SRC or an SRS can accept this
> >   option tag in a recording session.  An SRC SHOULD include the
> >   "siprec" option tag in the Require header when initiating a
Recording
> >   Session so that other types of user agents can simply reject the
> >   INVITE request with a 420 Bad Extension.
> >
> > This doesn't distinguish between SRC and SRS behavior. It might be
better to have two option tags:
> src and srs.
> >
> > If that was done, its not evident that the feature tags add
anything. It would be simpler to have
> the INVITE contain:
> >
> > 	Supported: src
> > 	Require: srs
> >
> > (An RS initiated by the SRS would invert those.)
>=20
> [Leon] Will add as an open item to the presentation
> >
> > 6.1
> >
> > Given the work that is being done in other WGs on multiplexing media
streams on RTP streams, I
> wonder if we ought to revisit our decision to always map a CS media
stream uniquely to an RS m-line,
> and instead consider allowing multiplexing. (But doing this would
require more description in metadata
> and/or SDP.)
> >
> [Leon] I believe the decision was not to prevent support for
multiplexing but just not to require it.
> > 6.1.1
> >
> >   ... To
> >   add a recorded stream to the recording session, the SRC sends a
new
> >   SDP offer by adding a new media stream description or by reusing
an
> >   old media stream which had been previously disabled, according to
the
> >   procedures in [RFC3264].
> >
> > Its not necessary to disable one before reusing it. You can
repurpose a stream in one step. How
> about:
> >
> >   ... To
> >   add a recorded stream to the recording session, the SRC sends a
new
> >   SDP offer by adding a new media stream description or by reusing
an
> >   media stream which had been previously disabled or that is no
> >   longer needed, according to the procedures in [RFC3264].
> >
> [Leon] I am ok with that
>=20
> > Section 9:
> >
> >   ... In order
> >   not to lose the NAT bindings for the RTP/RTCP ports opened for the
> >   recorded streams, the SRC and SRS SHOULD follow the
recommendations
> >   provided in [RFC6263] to maintain the NAT bindings.
> >
> > The recommendation involves also enabling multiplexing of rtcp and
rtp. If that is what we are going
> to do it would be worth calling that out, and showing it in the
examples.
> >
> > But that document also only applies when ICE isn't used.
> >
> > Maybe this should all be addressed as part of
draft-eckel-siprec-rtp-rec.
>=20
> [Leon] I am ok with that
> >
> > Section 10.1.1
> >
> >   A new SDP attribute "recordpref" is introduced.  The SDP attribute
> >   appears at the media level and can appear in an SDP offer or
answer.
> >   The recording indication applies to the specified media stream
only.
> >   The following is the ABNF of the recordpref attribute:
> >
> > IMO this attribute should be permitted at either session or media
level, with session level
> establishing a default for all media. (Thus only one session level
attribute need be supplied to
> request that all media should/shouldn't be recorded.)
>=20
> [Leon] I am ok with that
> >
> > Section 10.2.1
> >
> > The comments above for "recordpref" also apply to "record".
> >
> >   The recording attribute is a declaration by an endpoint in the CS
to
> >   indicate whether recording is taking place.
> >
> > This seems wrong. The indication is from the SRC toward and
endpoint. How about:
> >
> >   The recording attribute is a declaration by the SRC to an endpoint
> >   in the CS to indicate whether recording is taking place.  For
> >   example, if a UA (A)
> >
> [Leon] Agree, we should fix it in the document
> > 	Thanks,
> > 	Paul
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From leon.portman@gmail.com  Wed Nov 16 05:07:25 2011
Return-Path: <leon.portman@gmail.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 05EAE11E80CE for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 05:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.38
X-Spam-Level: 
X-Spam-Status: No, score=-2.38 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4dOUlQmFENx for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 05:07:23 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2C911E80C7 for <siprec@ietf.org>; Wed, 16 Nov 2011 05:07:23 -0800 (PST)
Received: by ywt34 with SMTP id 34so7872676ywt.31 for <siprec@ietf.org>; Wed, 16 Nov 2011 05:07:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=sf5IiiFlWgBI7xMpDc/xfiMC5BOEmPM5b2zkEhYknwE=; b=GasNdw4/MuL8r7ce6iYZeIGyb8C3OM86dBJBPu9eygwMrWRM/JzHaOZ9FtjrhyhfWX sB33g8tviHMVwGJgGlQ5frBj+/kGONUbldY8ASKQtQQ6y7YhGrcj6uZNpgKS7OY2XIWC Jd/YFm74KzFj7jYEcuUhiyPpd70FnNXqcpzW4=
Received: by 10.236.192.135 with SMTP id i7mr1082052yhn.13.1321448843192; Wed, 16 Nov 2011 05:07:23 -0800 (PST)
Received: from [192.168.100.222] (61-220-70-183.HINET-IP.hinet.net. [61.220.70.183]) by mx.google.com with ESMTPS id o50sm483616yhl.9.2011.11.16.05.07.20 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 Nov 2011 05:07:22 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <4EC37852.60809@alum.mit.edu>
Date: Wed, 16 Nov 2011 21:07:20 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B81B0AE1-E84E-4159-90A5-4C87766E7317@gmail.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com> <4EC36F1F.4000605@alum.mit.edu> <387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com> <4EC37852.60809@ alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1251.1)
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 13:07:25 -0000

Very good point, i have completely forgot about it. =46rom SRS point of =
view, we can support both modes of operation: immediate response or =
another re-invite

Leon

On Nov 16, 2011, at 4:46 PM, Paul Kyzivat wrote:

> On 11/16/11 4:16 PM, Ravindran, Parthasarathi wrote:
>> Paul,
>>=20
>> IIUC, SRC has to send its current snapshot. I could not understand
>> the reason to defer at this stage. Of course, 100 response shall be =
sent for
>> RE-INVITE of metadata snapshot request by which will help to defer =
even if
>> required.
>=20
> I think we had this discussion once before.
> The application that formats the metadata is a different layer from =
the stack, and may be decoupled from it. We shouldn't assume anything =
about the latency between them.
>=20
> Is there a *problem* with leaving this as an option for the SRC?
> Is it going to matter to the SRS that it must wait for the snapshot?
>=20
> 	Thanks,
> 	Paul
>=20
>> Thanks
>> Partha
>>=20
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On =
Behalf
>>> Of Paul Kyzivat
>>> Sent: Wednesday, November 16, 2011 4:07 PM
>>> To: siprec@ietf.org
>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>=20
>>> The reply I just sent was written earlier and just now sent, before =
I
>>> caught up on reading and found the subject already much evolved.
>>>=20
>>> On 11/16/11 3:35 PM, Leon Portman wrote:
>>>> Partha
>>>>=20
>>>> It seems to be that we are converging into solution where SRS will
>>> send offer-less INVITE with snapshot request and SRC will response =
with
>>> OK including metadata snapshot XML and SDP and SRS will ACK this =
SDP. If
>>> any media updates are required from SRS , they will be carried in
>>> separate INVITE/UPDATE as you have mention below. So we are =
converging
>>> into your option 1 solution.
>>>>=20
>>>> Please note that it complicates little bit SRC implementation.
>>>=20
>>> Another consideration is that it might take time to prepare the =
shapshot
>>> for sending, and it is desired not to delay response to the request.
>>> That is another reason to decouple sending the snapshot from the
>>> response to the snapshot request.
>>>=20
>>> IMO the SRC should at least have the *option* to defer sending the
>>> snapshot.
>>>=20
>>> I'm ok with *allowing* the SRC to send the shapshot with the =
response if
>>> it is capable of doing so.
>>>=20
>>> 	Thanks,
>>> 	Paul
>>>=20
>>>> Any concerns and comments?
>>>>=20
>>>> Thank you for raising this issue.
>>>>=20
>>>> Leon
>>>>=20
>>>> On Nov 16, 2011, at 3:30 PM, Ravindran, Parthasarathi wrote:
>>>>=20
>>>>> Leon,
>>>>>=20
>>>>> Please read inline.
>>>>>=20
>>>>> Thanks
>>>>> Partha
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>> Sent: Wednesday, November 16, 2011 2:48 PM
>>>>>> To: Hutton, Andrew
>>>>>> Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com;
>>>>>> siprec@ietf.org
>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>=20
>>>>>> If we will use OK response from SRC to SRS for reporting metadata
>>>>>> snapshot
>>>>>=20
>>>>> <partha>   We are in the same page till here</partha>
>>>>>=20
>>>>> and SRS will want to update SDP - for example because it needs
>>>>>> to terminate or redirect one of the RS media streams, it will =
need
>>>>>> to do it in separate REINVITE and UPDATE after ACK?
>>>>>=20
>>>>> <partha>   IIUC, SRS will trigger one another offer/answer to
>>>>> terminate RS Media stream. But I'm not very clear about the =
redirect
>>>>> of RS media stream Scenario</partha>
>>>>>=20
>>>>>>=20
>>>>>> Leon
>>>>>>=20
>>>>>> On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>>>>>>=20
>>>>>>> Hi,
>>>>>>>=20
>>>>>>> If I understand this correctly the discussion is how should the =
SRS
>>>>>> initiate a snapshot from the SRC and how does this impact the
>>>>>> offer/answer.
>>>>>>>=20
>>>>>>> The snapshot has I believe to include both an SDP offer and the
>>>>>> associated XML representing the metadata. The only way to =
initiate a
>>>>>> new SDP offer within the dialog is for the SRS to send a reINVITE
>>>>>> without SDP to the SRC causes the SRC to respond with the SDP =
Offer
>>>>>> and associated metadata snapshot in the 200OK which will of =
course
>>>>>> cause the SRS to generate an SDP answer in the ACK.
>>>>>>>=20
>>>>>>> The SRS could also include an SDP offer in the reINVITE and have
>>>>>>> the
>>>>>> SRC create the answer.
>>>>>>>=20
>>>>>>> In either case it should be that there is no change in the SDP =
from
>>>>>> the previous offer/answer and therefore it is effectively a =
session
>>>>>> refresh and does not cause an media interruption.
>>>>>>>=20
>>>>>>> Regards
>>>>>>> Andy
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] =
On
>>>>>>>> Behalf Of Leon Portman
>>>>>>>> Sent: 16 November 2011 13:43
>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>=20
>>>>>>>> Most important from SRS point of view, is to define a mechanism
>>>>>>>> for snapshot request that will not terminate recording session
>>>>>>>> even for shortest possible time.
>>>>>>>>=20
>>>>>>>> My concern is if new INVITE will do that
>>>>>>>>=20
>>>>>>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>>>>>>=20
>>>>>>>>> If offer-less REINVITE works (it seems to be) i dont have =
problem
>>>>>>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>>>>>>=20
>>>>>>>>> Leon
>>>>>>>>>=20
>>>>>>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>=20
>>>>>>>>>> Leon,
>>>>>>>>>>=20
>>>>>>>>>> Please read inline.
>>>>>>>>>>=20
>>>>>>>>>> Thanks
>>>>>>>>>> Partha
>>>>>>>>>>=20
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>>>>>>> siprec@ietf.org
>>>>>>>>>>> Subject: Re: [siprec] Comment on =
draft-ietf-siprec-protocol-02
>>>>>>>>>>>=20
>>>>>>>>>>> Patha
>>>>>>>>>>>=20
>>>>>>>>>>> Please see below
>>>>>>>>>>>=20
>>>>>>>>>>> Leon
>>>>>>>>>>>=20
>>>>>>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi =
wrote:
>>>>>>>>>>>=20
>>>>>>>>>>>> Leon,
>>>>>>>>>>>>=20
>>>>>>>>>>>> I agree with Ram.
>>>>>>>>>>>>=20
>>>>>>>>>>>> It is possible to debate on this normative statement
>>>>>>>>>>>> requirement
>>>>>>>> as
>>>>>>>>>>>> multiple way to request the full snapshot from SRS. Some of
>>>>>>>>>>>> the
>>>>>>>> way
>>>>>>>>>>>> from SRS are as follows:
>>>>>>>>>>>>=20
>>>>>>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 =
SIP
>>>>>>>> messages)
>>>>>>>>>>> In this case, is it legal for SRC to answer SDP less INVITE
>>>>>>>>>>> with
>>>>>>>> SDP?
>>>>>>>>>>> Snapshot requires SDP
>>>>>>>>>> <partha>   AFAIK, Re-INVITE without SDP is used to get offer =
from
>>>>>>>>>> the
>>>>>>>> remote
>>>>>>>>>> Side. Even Hadriel mail threads says the same. Could you =
please
>>>>>>>> point out
>>>>>>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer
>>> work?
>>>>>>>> </partha>
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>>>>>>> messages)
>>>>>>>>>>> What if SRS does not have SDP?
>>>>>>>>>> <partha>   In that case, it will end-up in OPTION 1 or 3 but
>>>>>>>>>> please
>>>>>>>> note that
>>>>>>>>>> It is possible to SRS to send SDP in case it has the idea of
>>>>>>>>>> what
>>>>>>>> has to be
>>>>>>>>>> Recorded.</partha>
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>>>>>>> Separate (4 SIP messages)
>>>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> <partha>   I have started thinking whether it is appropriate =
for
>>>>>>>> UPDATE from SRC
>>>>>>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM,
>>>>>>>>>> the
>>>>>>>> proposal mandates
>>>>>>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE =
whereas
>>>>>>>> UPDATE is not
>>>>>>>>>> designed for that. I may be wrong here but we need careful
>>>>>>>>>> analysis
>>>>>>>> here</partha>
>>>>>>>>>>=20
>>>>>>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>>>>>>> OPTION
>>>>>>>> 3
>>>>>>>>>>>> but I prefer to have the implementation choice. As =
mentioned
>>>>>>>> above,
>>>>>>>>>>>> OPTION 1&   2 has less SIP message required to achieve the =
same
>>>>>>>> compare
>>>>>>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>>>>>>=20
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Partha
>>>>>>>>>>>>=20
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>>>>>>> henry.lum@genesyslab.com
>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>> Subject: RE: [siprec] Comment on
>>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Please see inline. I have a question here
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>>>>>>>>>> [mailto:siprec-bounces@ietf.org]
>>>>>>>> On
>>>>>>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>> Subject: Re: [siprec] Comment on
>>>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> Additional update on sending full metadata snapshot upon =
SRS
>>>>>>>>>>> request.
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> In section 8.2 we say:
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> "   When the SRC receives the request for a metadata
>>> snapshot,
>>>>>>>> the
>>>>>>>>>>> SRC
>>>>>>>>>>>>>> MUST provide a full metadata snapshot in a separate =
INVITE
>>>>>>>>>>>>>> transaction, along with an SDP offer."
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> meaning that full metadata is actually separate INVITE
>>>>>>>> transaction.
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Why should the snapshot be always sent in a separate =
INVITE.
>>>>>>>> Can't it
>>>>>>>>>>>>> be sent as a response to snapshot request from SRS ? Is =
there
>>>>>>>>>>>>> a reason why you want to mandate that way ?
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> Ram
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> Partha Thanks
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi
>>> wrote:
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> Please read inline
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>>>>>>> 02
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>>>>>> wrote:
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 1) "may" is used instead of normative statement =
"MAY".
>>>>>>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in
>>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>> specific
>>>>>>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> <partha>   I'm not very sure whether it is appropriate =
to
>>>>>>>>>>>>>>>> use
>>>>>>>> "may"
>>>>>>>>>>>>> in
>>>>>>>>>>>>>> the specification.
>>>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is =
video
>>>>>>>> instead
>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>> current audio.
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 3) Please clarify the following statement in Sec =
6.1.1
>>>>>>>>>>>>>>>>>> "Note that
>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>> a CS
>>>>>>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed =
in
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>>>>> by the SRC. " because I don't know how metadata =
convey
>>>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>>> currently.
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We =
should
>>>>>>>> rephrase
>>>>>>>>>>>>>> it to
>>>>>>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>>>>>>> <partha>   Currently, it is outside the scope of =
metadata
>>>>>>>>>>>>>>>> and
>>>>>>>> IMO,
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>> is better
>>>>>>>>>>>>>>>> to remove "mute/unmute" from protocol spec</partha>
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 4) Whether the normative statement required for mute?
>>>>>>>>>>>>>>>>>> Sec
>>>>>>>> 6.1.1
>>>>>>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with
>>>>>>>>>>>>>>>>>> a=3Dinactive
>>>>>>>> for
>>>>>>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should =
not
>>>>>>>>>>>>>>>>> be handled
>>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>>> "hold"
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> <partha>   IMO, there should be no normative statement
>>>>>>>>>>>>>>>> related
>>>>>>>> to
>>>>>>>>>>>>> mute
>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>> delivery
>>>>>>>>>>>>>>>>> which shall
>>>>>>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>>>>>>> repetition
>>>>>>>>>>>>>> here
>>>>>>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> <partha>   I can live with incase everybody wants with
>>>>>>>> duplication
>>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>> text
>>>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 6) content type shall be =
"application/rs-metadata+xml"
>>>>>>>> instead
>>>>>>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across =
using
>>>>>>>> UPDATE as
>>>>>>>>>>>>>> well.
>>>>>>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When
>>>>>>>>>>>>>>>>>> the
>>>>>>>> SRC
>>>>>>>>>>>>>> sends a
>>>>>>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>>>>>>> "recording-
>>>>>>>>>>>>>> session"
>>>>>>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE =
in
>>>>>>>> order to
>>>>>>>>>>>>>> make
>>>>>>>>>>>>>>>>> sure that SDP will be present as well. Dont have any
>>>>>>>>>>>>>>>>> strong
>>>>>>>>>>>>>> preferences
>>>>>>>>>>>>>>>>> here.
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> <partha>   We had the discussion during IETF-80 to =
mandate
>>>>>>>> INVITE&
>>>>>>>>>>>>>> UPDATE.
>>>>>>>>>>>>>>>> But I could not find the reason for not using UPDATE =
for
>>>>>>>>>>>>>>>> full
>>>>>>>>>>>>>> snapshot
>>>>>>>>>>>>>>>> Request</partha>
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>>>>>>> changed as
>>>>>>>>>>>>>> SIP
>>>>>>>>>>>>>>>>>> header or clear indication within the message to
>>>>>>>>>>>>>>>>>> indicate
>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>>>>>>> explicitly
>>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>>>>>>> recommendation
>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> <partha>   Currently, it is plain text now whereas SRC =
has
>>>>>>>>>>>>>>>> no
>>>>>>>> means
>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion
>>>>>>>>>>>>>>>> about
>>>>>>>> the
>>>>>>>>>>>>>> text
>>>>>>>>>>>>>>>> helps for the implementation by which SRC understand.
>>>>>>>> </partha>
>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>> siprec mailing list
>>>>>>>>>>>>>>>>>> siprec@ietf.org
>>>>>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> siprec mailing list
>>>>>>>>>>>>>> siprec@ietf.org
>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> _______________________________________________
>>>>>>>> siprec mailing list
>>>>>>>> siprec@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>=20
>>>=20
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec
>>=20
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From pravindran@sonusnet.com  Wed Nov 16 06:07:12 2011
Return-Path: <pravindran@sonusnet.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 7AE0E21F96C6 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 06:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.287
X-Spam-Level: 
X-Spam-Status: No, score=-2.287 tagged_above=-999 required=5 tests=[AWL=-0.288, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfRlMDwe5gVW for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 06:07:11 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id D7E8921F8CB5 for <siprec@ietf.org>; Wed, 16 Nov 2011 06:07:10 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAGE7kUs024746;  Wed, 16 Nov 2011 09:07:46 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 09:07:03 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 19:37:17 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Wed, 16 Nov 2011 19:37:17 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Leon Portman <leon.portman@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVCAAfdcAIAAFlAAgAAC/YD//6LIIIAAYtkA//+jbqAAEGLoAAAATaOAAAF4G4AAAMvZgP//m1vw//+N/YD//xM3gP/9x/qg//vjcAD/933oAP/unqmA
Date: Wed, 16 Nov 2011 14:07:17 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE92FF@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com> <4EC36F1F.4000605@alum.mit.edu> <387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com> <4EC37852.60809@alum.mit.edu> <B81B0AE1-E84E-4159-90A5-4C87766E7317@gmail.com>
In-Reply-To: <B81B0AE1-E84E-4159-90A5-4C87766E7317@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Nov 2011 14:07:17.0698 (UTC) FILETIME=[0C9C1A20:01CCA469]
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 14:07:12 -0000

Paul/Leon,
=20
We have discussed about decoupling of "metadata" & "SDP" for SRS but
here it is SRC. Even in case of SRS, we agreed upon that there is no=20
need to defer the responses for metadata processing and RE-INVITE/UPDATE
is agreed upon based on this assumption. Snapshot request may be used as=20
deferred mechanism to correct metadata.

SRC implementation shall maintain "metadata" & "SDP" in different layer=20
but the latency problem is solved by sending "100 trying" for RE-INVITE=20
in SRC. The problem with two different transaction (request/response) is th=
at
the possibility of a offer/answer race condition is higher. Apart from=20
latency, Could you please specify any advantage in two transaction approach=
.
Also, two transactions makes me to feel like invoking action in SRC as the
Second transaction is triggered based on the first UPDATE/RE-INVITE with
Snapshot request.

Let us get others opinion for the need of two separate transaction=20
(request/response) in SRC.

Thanks
Partha

>-----Original Message-----
>From: Leon Portman [mailto:leon.portman@gmail.com]
>Sent: Wednesday, November 16, 2011 9:07 PM
>To: Paul Kyzivat
>Cc: Ravindran, Parthasarathi; siprec@ietf.org
>Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>
>Very good point, i have completely forgot about it. From SRS point of
>view, we can support both modes of operation: immediate response or
>another re-invite
>
>Leon
>
>On Nov 16, 2011, at 4:46 PM, Paul Kyzivat wrote:
>
>> On 11/16/11 4:16 PM, Ravindran, Parthasarathi wrote:
>>> Paul,
>>>
>>> IIUC, SRC has to send its current snapshot. I could not understand
>>> the reason to defer at this stage. Of course, 100 response shall be
>>> sent for RE-INVITE of metadata snapshot request by which will help to
>>> defer even if required.
>>
>> I think we had this discussion once before.
>> The application that formats the metadata is a different layer from
>the stack, and may be decoupled from it. We shouldn't assume anything
>about the latency between them.
>>
>> Is there a *problem* with leaving this as an option for the SRC?
>> Is it going to matter to the SRS that it must wait for the snapshot?
>>
>> 	Thanks,
>> 	Paul
>>
>>> Thanks
>>> Partha
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>> Behalf Of Paul Kyzivat
>>>> Sent: Wednesday, November 16, 2011 4:07 PM
>>>> To: siprec@ietf.org
>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>
>>>> The reply I just sent was written earlier and just now sent, before
>>>> I caught up on reading and found the subject already much evolved.
>>>>
>>>> On 11/16/11 3:35 PM, Leon Portman wrote:
>>>>> Partha
>>>>>
>>>>> It seems to be that we are converging into solution where SRS will
>>>> send offer-less INVITE with snapshot request and SRC will response
>>>> with OK including metadata snapshot XML and SDP and SRS will ACK
>>>> this SDP. If any media updates are required from SRS , they will be
>>>> carried in separate INVITE/UPDATE as you have mention below. So we
>>>> are converging into your option 1 solution.
>>>>>
>>>>> Please note that it complicates little bit SRC implementation.
>>>>
>>>> Another consideration is that it might take time to prepare the
>>>> shapshot for sending, and it is desired not to delay response to the
>request.
>>>> That is another reason to decouple sending the snapshot from the
>>>> response to the snapshot request.
>>>>
>>>> IMO the SRC should at least have the *option* to defer sending the
>>>> snapshot.
>>>>
>>>> I'm ok with *allowing* the SRC to send the shapshot with the
>>>> response if it is capable of doing so.
>>>>
>>>> 	Thanks,
>>>> 	Paul
>>>>
>>>>> Any concerns and comments?
>>>>>
>>>>> Thank you for raising this issue.
>>>>>
>>>>> Leon
>>>>>
>>>>> On Nov 16, 2011, at 3:30 PM, Ravindran, Parthasarathi wrote:
>>>>>
>>>>>> Leon,
>>>>>>
>>>>>> Please read inline.
>>>>>>
>>>>>> Thanks
>>>>>> Partha
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>> Sent: Wednesday, November 16, 2011 2:48 PM
>>>>>>> To: Hutton, Andrew
>>>>>>> Cc: Ravindran, Parthasarathi; henry.lum@genesyslab.com;
>>>>>>> siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>
>>>>>>> If we will use OK response from SRC to SRS for reporting metadata
>>>>>>> snapshot
>>>>>>
>>>>>> <partha>   We are in the same page till here</partha>
>>>>>>
>>>>>> and SRS will want to update SDP - for example because it needs
>>>>>>> to terminate or redirect one of the RS media streams, it will
>>>>>>> need to do it in separate REINVITE and UPDATE after ACK?
>>>>>>
>>>>>> <partha>   IIUC, SRS will trigger one another offer/answer to
>>>>>> terminate RS Media stream. But I'm not very clear about the
>>>>>> redirect of RS media stream Scenario</partha>
>>>>>>
>>>>>>>
>>>>>>> Leon
>>>>>>>
>>>>>>> On Nov 16, 2011, at 2:24 PM, Hutton, Andrew wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> If I understand this correctly the discussion is how should the
>>>>>>>> SRS
>>>>>>> initiate a snapshot from the SRC and how does this impact the
>>>>>>> offer/answer.
>>>>>>>>
>>>>>>>> The snapshot has I believe to include both an SDP offer and the
>>>>>>> associated XML representing the metadata. The only way to
>>>>>>> initiate a new SDP offer within the dialog is for the SRS to send
>>>>>>> a reINVITE without SDP to the SRC causes the SRC to respond with
>>>>>>> the SDP Offer and associated metadata snapshot in the 200OK which
>>>>>>> will of course cause the SRS to generate an SDP answer in the
>ACK.
>>>>>>>>
>>>>>>>> The SRS could also include an SDP offer in the reINVITE and have
>>>>>>>> the
>>>>>>> SRC create the answer.
>>>>>>>>
>>>>>>>> In either case it should be that there is no change in the SDP
>>>>>>>> from
>>>>>>> the previous offer/answer and therefore it is effectively a
>>>>>>> session refresh and does not cause an media interruption.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Andy
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>>>>>>>>> On Behalf Of Leon Portman
>>>>>>>>> Sent: 16 November 2011 13:43
>>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>>> Cc: henry.lum@genesyslab.com; siprec@ietf.org
>>>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>>>>>>>>>
>>>>>>>>> Most important from SRS point of view, is to define a mechanism
>>>>>>>>> for snapshot request that will not terminate recording session
>>>>>>>>> even for shortest possible time.
>>>>>>>>>
>>>>>>>>> My concern is if new INVITE will do that
>>>>>>>>>
>>>>>>>>> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
>>>>>>>>>
>>>>>>>>>> If offer-less REINVITE works (it seems to be) i dont have
>>>>>>>>>> problem
>>>>>>>>> with supporting option 1 as well. Any SIP experts opinions?
>>>>>>>>>>
>>>>>>>>>> Leon
>>>>>>>>>>
>>>>>>>>>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
>>>>>>>>>>
>>>>>>>>>>> Leon,
>>>>>>>>>>>
>>>>>>>>>>> Please read inline.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Partha
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 11:16 AM
>>>>>>>>>>>> To: Ravindran, Parthasarathi
>>>>>>>>>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
>>>>>>>>> siprec@ietf.org
>>>>>>>>>>>> Subject: Re: [siprec] Comment on
>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>
>>>>>>>>>>>> Patha
>>>>>>>>>>>>
>>>>>>>>>>>> Please see below
>>>>>>>>>>>>
>>>>>>>>>>>> Leon
>>>>>>>>>>>>
>>>>>>>>>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi
>wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I agree with Ram.
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is possible to debate on this normative statement
>>>>>>>>>>>>> requirement
>>>>>>>>> as
>>>>>>>>>>>>> multiple way to request the full snapshot from SRS. Some of
>>>>>>>>>>>>> the
>>>>>>>>> way
>>>>>>>>>>>>> from SRS are as follows:
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1) REVITE without SDP and siprec-metdata-request body (3
>>>>>>>>>>>>> SIP
>>>>>>>>> messages)
>>>>>>>>>>>> In this case, is it legal for SRC to answer SDP less INVITE
>>>>>>>>>>>> with
>>>>>>>>> SDP?
>>>>>>>>>>>> Snapshot requires SDP
>>>>>>>>>>> <partha>   AFAIK, Re-INVITE without SDP is used to get offer
>from
>>>>>>>>>>> the
>>>>>>>>> remote
>>>>>>>>>>> Side. Even Hadriel mail threads says the same. Could you
>>>>>>>>>>> please
>>>>>>>>> point out
>>>>>>>>>>> RFC 3261 Section to point how RE-INVITE without offer/answer
>>>> work?
>>>>>>>>> </partha>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
>>>>>>>>> messages)
>>>>>>>>>>>> What if SRS does not have SDP?
>>>>>>>>>>> <partha>   In that case, it will end-up in OPTION 1 or 3 but
>>>>>>>>>>> please
>>>>>>>>> note that
>>>>>>>>>>> It is possible to SRS to send SDP in case it has the idea of
>>>>>>>>>>> what
>>>>>>>>> has to be
>>>>>>>>>>> Recorded.</partha>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
>>>>>>>>>>>>> Separate (4 SIP messages)
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <partha>   I have started thinking whether it is appropriate
>for
>>>>>>>>> UPDATE from SRC
>>>>>>>>>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM,
>>>>>>>>>>> the
>>>>>>>>> proposal mandates
>>>>>>>>>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE
>>>>>>>>>>> whereas
>>>>>>>>> UPDATE is not
>>>>>>>>>>> designed for that. I may be wrong here but we need careful
>>>>>>>>>>> analysis
>>>>>>>>> here</partha>
>>>>>>>>>>>
>>>>>>>>>>>>> IIUC, current SIPREC protocol mechanism propose to use only
>>>>>>>>>>>>> OPTION
>>>>>>>>> 3
>>>>>>>>>>>>> but I prefer to have the implementation choice. As
>>>>>>>>>>>>> mentioned
>>>>>>>>> above,
>>>>>>>>>>>>> OPTION 1&   2 has less SIP message required to achieve the
>same
>>>>>>>>> compare
>>>>>>>>>>>>> to OPTION 3. Hope this clarifies.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
>>>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
>>>>>>>>>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
>>>>>>>>> henry.lum@genesyslab.com
>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>> Subject: RE: [siprec] Comment on
>>>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please see inline. I have a question here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>> From: siprec-bounces@ietf.org
>>>>>>>>>>>>>>> [mailto:siprec-bounces@ietf.org]
>>>>>>>>> On
>>>>>>>>>>>>>>> Behalf Of Leon Portman
>>>>>>>>>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
>>>>>>>>>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
>>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>>> Subject: Re: [siprec] Comment on
>>>>>>>>>>>>>>> draft-ietf-siprec-protocol-02
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Additional update on sending full metadata snapshot upon
>>>>>>>>>>>>>>> SRS
>>>>>>>>>>>> request.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> In section 8.2 we say:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "   When the SRC receives the request for a metadata
>>>> snapshot,
>>>>>>>>> the
>>>>>>>>>>>> SRC
>>>>>>>>>>>>>>> MUST provide a full metadata snapshot in a separate
>>>>>>>>>>>>>>> INVITE transaction, along with an SDP offer."
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> meaning that full metadata is actually separate INVITE
>>>>>>>>> transaction.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Why should the snapshot be always sent in a separate
>INVITE.
>>>>>>>>> Can't it
>>>>>>>>>>>>>> be sent as a response to snapshot request from SRS ? Is
>>>>>>>>>>>>>> there a reason why you want to mandate that way ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ram
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Partha Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi
>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Leon,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please read inline
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
>>>>>>>>>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
>>>>>>>>>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
>>>>>>>>>>>>>>>>>> Cc: siprec@ietf.org
>>>>>>>>>>>>>>>>>> Subject: Re: [sipprec] Comment on
>>>>>>>>>>>>>>>>>> draft-ietf-siprec-protocol-
>>>>>>>>> 02
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Partha Hi
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Please see below
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Leon
>>>>>>>>>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 1) "may" is used instead of normative statement
>"MAY".
>>>>>>>>>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
>>>>>>>>>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in
>>>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>> specific
>>>>>>>>>>>>>>>>>> section, it is an over part.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <partha>   I'm not very sure whether it is appropriate
>to
>>>>>>>>>>>>>>>>> use
>>>>>>>>> "may"
>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>> the specification.
>>>>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] I dont have any opinions on that
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is
>>>>>>>>>>>>>>>>>>> video
>>>>>>>>> instead
>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> current audio.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] Yes, good catch. Thanks
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 3) Please clarify the following statement in Sec
>>>>>>>>>>>>>>>>>>> 6.1.1 "Note that
>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>> a CS
>>>>>>>>>>>>>>>>>>> stream is muted/unmuted, this information is conveyed
>>>>>>>>>>>>>>>>>>> in the
>>>>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>>>>>> by the SRC. " because I don't know how metadata
>>>>>>>>>>>>>>>>>>> convey this
>>>>>>>>>>>>>>>>>> currently.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We
>>>>>>>>>>>>>>>>>> should
>>>>>>>>> rephrase
>>>>>>>>>>>>>>> it to
>>>>>>>>>>>>>>>>>> "may be conveyed in metadata"
>>>>>>>>>>>>>>>>> <partha>   Currently, it is outside the scope of
>metadata
>>>>>>>>>>>>>>>>> and
>>>>>>>>> IMO,
>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>> is better
>>>>>>>>>>>>>>>>> to remove "mute/unmute" from protocol spec</partha>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] I agree, Henry, what do you think?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 4) Whether the normative statement required for mute?
>>>>>>>>>>>>>>>>>>> Sec
>>>>>>>>> 6.1.1
>>>>>>>>>>>>>>>>>>> "The SRC SHOULD not modify the media stream with
>>>>>>>>>>>>>>>>>>> a=3Dinactive
>>>>>>>>> for
>>>>>>>>>>>>>>>>>>> mute since this operation is reserved for pausing
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> RS media."
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] It is related to point #3 that "mute" should
>>>>>>>>>>>>>>>>>> not be handled
>>>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>>>> "hold"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <partha>   IMO, there should be no normative statement
>>>>>>>>>>>>>>>>> related
>>>>>>>>> to
>>>>>>>>>>>>>> mute
>>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
>>>>>>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>> delivery
>>>>>>>>>>>>>>>>>> which shall
>>>>>>>>>>>>>>>>>>> be avoided.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
>>>>>>>>> repetition
>>>>>>>>>>>>>>> here
>>>>>>>>>>>>>>>>>> with detailed sections.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <partha>   I can live with incase everybody wants with
>>>>>>>>> duplication
>>>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>> text
>>>>>>>>>>>>>>>>> </partha>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 6) content type shall be "application/rs-
>metadata+xml"
>>>>>>>>> instead
>>>>>>>>>>>>>>>>>>> of current "application/rs-metadata"
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] I am ok with that
>>>>>>>>>>>>>>>>>>> 7) full metadata snapshot shall be passed across
>>>>>>>>>>>>>>>>>>> using
>>>>>>>>> UPDATE as
>>>>>>>>>>>>>>> well.
>>>>>>>>>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>> SRC
>>>>>>>>>>>>>>> sends a
>>>>>>>>>>>>>>>>>> full metadata snapshot, the SRC MUST
>>>>>>>>>>>>>>>>>>> send an INVITE request with an SDP offer and the
>>>>>>>>>>>>>>>>>>> "recording-
>>>>>>>>>>>>>>> session"
>>>>>>>>>>>>>>>>>>> disposition."
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE
>>>>>>>>>>>>>>>>>> in
>>>>>>>>> order to
>>>>>>>>>>>>>>> make
>>>>>>>>>>>>>>>>>> sure that SDP will be present as well. Dont have any
>>>>>>>>>>>>>>>>>> strong
>>>>>>>>>>>>>>> preferences
>>>>>>>>>>>>>>>>>> here.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <partha>   We had the discussion during IETF-80 to
>mandate
>>>>>>>>> INVITE&
>>>>>>>>>>>>>>> UPDATE.
>>>>>>>>>>>>>>>>> But I could not find the reason for not using UPDATE
>>>>>>>>>>>>>>>>> for full
>>>>>>>>>>>>>>> snapshot
>>>>>>>>>>>>>>>>> Request</partha>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Leon] I am ok with both
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
>>>>>>>>> changed as
>>>>>>>>>>>>>>> SIP
>>>>>>>>>>>>>>>>>>> header or clear indication within the message to
>>>>>>>>>>>>>>>>>>> indicate
>>>>>>>>>>>>>> metadata
>>>>>>>>>>>>>>>>>> request. Also, reason for logging could be mentioned
>>>>>>>>> explicitly
>>>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>>>> "logging: SRS internal error"
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
>>>>>>>>> recommendation
>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>> logging text from SRS for the generic request
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [Leon] Please elaborate.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <partha>   Currently, it is plain text now whereas SRC
>has
>>>>>>>>>>>>>>>>> no
>>>>>>>>> means
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>> understand about  the logs. Some guidelines/suggestion
>>>>>>>>>>>>>>>>> about
>>>>>>>>> the
>>>>>>>>>>>>>>> text
>>>>>>>>>>>>>>>>> helps for the implementation by which SRC understand.
>>>>>>>>> </partha>
>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>> Partha
>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>> 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
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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


From andrew.hutton@siemens-enterprise.com  Wed Nov 16 06:08:59 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 94DA921F94F9 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 06:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djwLSZ38RSbA for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 06:08:58 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id B662B21F94F0 for <siprec@ietf.org>; Wed, 16 Nov 2011 06:08:57 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id C05B11EB84BD; Wed, 16 Nov 2011 15:08:51 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 16 Nov 2011 15:08:51 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Date: Wed, 16 Nov 2011 15:08:47 +0100
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcykO6XL9TGSIlTdSBCbGojnw8jPfQALUOxA
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAB66748@MCHP058A.global-ad.net>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com><B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <4EC37755.3060403@alum.mit.edu>
In-Reply-To: <4EC37755.3060403@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 14:08:59 -0000

See below.

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: 16 November 2011 16:42
> To: siprec@ietf.org
> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>=20
> On 11/16/11 2:24 PM, Hutton, Andrew wrote:
> > Hi,
> >
> > If I understand this correctly the discussion is how should the SRS
> initiate a snapshot from the SRC and how does this impact the
> offer/answer.
> >
> > The snapshot has I believe to include both an SDP offer and the
> associated XML representing the metadata. The only way to initiate a
> new SDP offer within the dialog is for the SRS to send a reINVITE
> without SDP to the SRC causes the SRC to respond with the SDP Offer and
> associated metadata snapshot in the 200OK which will of course cause
> the SRS to generate an SDP answer in the ACK.
> >
> > The SRS could also include an SDP offer in the reINVITE and have the
> SRC create the answer.
> >
> > In either case it should be that there is no change in the SDP from
> the previous offer/answer and therefore it is effectively a session
> refresh and does not cause an media interruption.
>=20
> IMO you can't assume that.
> Its possible that there have been changes that have not yet been
> reported. Would you require that it send the snapshot of only the old
> stuff, not the changes?

[AndyH] - You are right I was thinking of the case of a snapshot when there=
 has been no change since the last offer/answer. I think it is a corner cas=
e but I agree that there could be changes to report in the new offer.


>=20
> 	Thanks,
> 	Paul
>=20
> > Regards
> > Andy
> >
> >
> >
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> >> Behalf Of Leon Portman
> >> Sent: 16 November 2011 13:43
> >> To: Ravindran, Parthasarathi
> >> Cc: henry.lum@genesyslab.com; siprec@ietf.org
> >> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
> >>
> >> Most important from SRS point of view, is to define a mechanism for
> >> snapshot request that will not terminate recording session even for
> >> shortest possible time.
> >>
> >> My concern is if new INVITE will do that
> >>
> >> On Nov 16, 2011, at 1:34 PM, Leon Portman wrote:
> >>
> >>> If offer-less REINVITE works (it seems to be) i dont have problem
> >> with supporting option 1 as well. Any SIP experts opinions?
> >>>
> >>> Leon
> >>>
> >>> On Nov 16, 2011, at 11:28 AM, Ravindran, Parthasarathi wrote:
> >>>
> >>>> Leon,
> >>>>
> >>>> Please read inline.
> >>>>
> >>>> Thanks
> >>>> Partha
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
> >>>>> Sent: Wednesday, November 16, 2011 11:16 AM
> >>>>> To: Ravindran, Parthasarathi
> >>>>> Cc: Ram Mohan R (rmohanr); henry.lum@genesyslab.com;
> >> siprec@ietf.org
> >>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
> >>>>>
> >>>>> Patha
> >>>>>
> >>>>> Please see below
> >>>>>
> >>>>> Leon
> >>>>>
> >>>>> On Nov 16, 2011, at 11:00 AM, Ravindran, Parthasarathi wrote:
> >>>>>
> >>>>>> Leon,
> >>>>>>
> >>>>>> I agree with Ram.
> >>>>>>
> >>>>>> It is possible to debate on this normative statement requirement
> >> as
> >>>>>> multiple way to request the full snapshot from SRS. Some of the
> >> way
> >>>>>> from SRS are as follows:
> >>>>>>
> >>>>>> 1) REVITE without SDP and siprec-metdata-request body (3 SIP
> >> messages)
> >>>>> In this case, is it legal for SRC to answer SDP less INVITE with
> >> SDP?
> >>>>> Snapshot requires SDP
> >>>> <partha>  AFAIK, Re-INVITE without SDP is used to get offer from
> the
> >> remote
> >>>> Side. Even Hadriel mail threads says the same. Could you please
> >> point out
> >>>> RFC 3261 Section to point how RE-INVITE without offer/answer work?
> >> </partha>
> >>>>
> >>>>
> >>>>>> 2) UPDATE with SDP and SIPREC-metadata-request body (2 SIP
> >> messages)
> >>>>> What if SRS does not have SDP?
> >>>> <partha>  In that case, it will end-up in OPTION 1 or 3 but please
> >> note that
> >>>> It is possible to SRS to send SDP in case it has the idea of what
> >> has to be
> >>>> Recorded.</partha>
> >>>>
> >>>>
> >>>>>> 3) UPDATE without SDP and SIPREC-metadata-request body and
> >>>>>> Separate (4 SIP messages)
> >>>>>>
> >>>>
> >>>> <partha>  I have started thinking whether it is appropriate for
> >> UPDATE from SRC
> >>>> to ask SRC to trigger new Re-INVITE/UPDATE towards SRS. ISTM, the
> >> proposal mandates
> >>>> action in SRC to be invoke Re-INVITE/UPDATE using UPDATE whereas
> >> UPDATE is not
> >>>> designed for that. I may be wrong here but we need careful
> analysis
> >> here</partha>
> >>>>
> >>>>>> IIUC, current SIPREC protocol mechanism propose to use only
> OPTION
> >> 3
> >>>>>> but I prefer to have the implementation choice. As mentioned
> >> above,
> >>>>>> OPTION 1&  2 has less SIP message required to achieve the same
> >> compare
> >>>>>> to OPTION 3. Hope this clarifies.
> >>>>>>
> >>>>>> Thanks
> >>>>>> Partha
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> >>>>>>> Sent: Wednesday, November 16, 2011 10:56 AM
> >>>>>>> To: Leon Portman; Ravindran, Parthasarathi;
> >> henry.lum@genesyslab.com
> >>>>>>> Cc: siprec@ietf.org
> >>>>>>> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
> >>>>>>>
> >>>>>>> Leon,
> >>>>>>>
> >>>>>>> Please see inline. I have a question here
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> >> On
> >>>>>>>> Behalf Of Leon Portman
> >>>>>>>> Sent: Wednesday, November 16, 2011 10:45 AM
> >>>>>>>> To: Parthasarathi Ravindran; henry.lum@genesyslab.com
> >>>>>>>> Cc: siprec@ietf.org
> >>>>>>>> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
> >>>>>>>>
> >>>>>>>> Additional update on sending full metadata snapshot upon SRS
> >>>>> request.
> >>>>>>>>
> >>>>>>>> In section 8.2 we say:
> >>>>>>>>
> >>>>>>>> "   When the SRC receives the request for a metadata snapshot,
> >> the
> >>>>> SRC
> >>>>>>>> MUST provide a full metadata snapshot in a separate INVITE
> >>>>>>>> transaction, along with an SDP offer."
> >>>>>>>>
> >>>>>>>> meaning that full metadata is actually separate INVITE
> >> transaction.
> >>>>>>>
> >>>>>>> Why should the snapshot be always sent in a separate INVITE.
> >> Can't it
> >>>>>>> be sent as a response to snapshot request from SRS ? Is there a
> >>>>>>> reason why you want to mandate that way ?
> >>>>>>>
> >>>>>>> Ram
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Leon
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Nov 16, 2011, at 9:25 AM, Leon Portman wrote:
> >>>>>>>>
> >>>>>>>>> Partha Thanks
> >>>>>>>>>
> >>>>>>>>> Please see below
> >>>>>>>>>
> >>>>>>>>> Leon
> >>>>>>>>>
> >>>>>>>>> On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
> >>>>>>>>>
> >>>>>>>>>> Leon,
> >>>>>>>>>>
> >>>>>>>>>> Please read inline
> >>>>>>>>>>
> >>>>>>>>>> Thanks
> >>>>>>>>>> Partha
> >>>>>>>>>>
> >>>>>>>>>>> -----Original Message-----
> >>>>>>>>>>> From: Leon Portman [mailto:leon.portman@gmail.com]
> >>>>>>>>>>> Sent: Tuesday, November 15, 2011 1:03 PM
> >>>>>>>>>>> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
> >>>>>>>>>>> Cc: siprec@ietf.org
> >>>>>>>>>>> Subject: Re: [sipprec] Comment on draft-ietf-siprec-
> protocol-
> >> 02
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Partha Hi
> >>>>>>>>>>>
> >>>>>>>>>>> Please see below
> >>>>>>>>>>>
> >>>>>>>>>>> Regards
> >>>>>>>>>>>
> >>>>>>>>>>> Leon
> >>>>>>>>>>> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi
> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> 1) "may" is used instead of normative statement "MAY".
> >>>>>>>>>>>> a) Sec 4.2 Para 1 Line 2
> >>>>>>>>>>>> b) Sec 4.2 Para 3 Line 5
> >>>>>>>>>>>>
> >>>>>>>>>>> [Leon] I am not sure that we want to emphasize MAY in this
> >>>>>>> specific
> >>>>>>>>>>> section, it is an over part.
> >>>>>>>>>>>
> >>>>>>>>>> <partha>  I'm not very sure whether it is appropriate to use
> >> "may"
> >>>>>>> in
> >>>>>>>> the specification.
> >>>>>>>>>> </partha>
> >>>>>>>>>
> >>>>>>>>> [Leon] I dont have any opinions on that
> >>>>>>>>>>
> >>>>>>>>>>>> 2) Figure 4: I guess that port 22458 "m" line is video
> >> instead
> >>>>>>>>>>>> of
> >>>>>>>>>>> current audio.
> >>>>>>>>>>>
> >>>>>>>>>>> [Leon] Yes, good catch. Thanks
> >>>>>>>>>>>>
> >>>>>>>>>>>> 3) Please clarify the following statement in Sec 6.1.1
> "Note
> >>>>>>>>>>>> that
> >>>>>>>> when
> >>>>>>>>>>> a CS
> >>>>>>>>>>>> stream is muted/unmuted, this information is conveyed in
> the
> >>>>>>>>>>> metadata
> >>>>>>>>>>>> by the SRC. " because I don't know how metadata convey
> this
> >>>>>>>>>>> currently.
> >>>>>>>>>>>>
> >>>>>>>>>>> [Leon] Yes, it is not defined yet in metadata. We should
> >> rephrase
> >>>>>>>> it to
> >>>>>>>>>>> "may be conveyed in metadata"
> >>>>>>>>>> <partha>  Currently, it is outside the scope of metadata and
> >> IMO,
> >>>>>>>>>> it
> >>>>>>>> is better
> >>>>>>>>>> to remove "mute/unmute" from protocol spec</partha>
> >>>>>>>>>
> >>>>>>>>> [Leon] I agree, Henry, what do you think?
> >>>>>>>>>>
> >>>>>>>>>>>> 4) Whether the normative statement required for mute? Sec
> >> 6.1.1
> >>>>>>>>>>>> "The SRC SHOULD not modify the media stream with
> a=3Dinactive
> >> for
> >>>>>>>>>>>> mute since this operation is reserved for pausing
> >>>>>>>> the
> >>>>>>>>>>>> RS media."
> >>>>>>>>>>>>
> >>>>>>>>>>> [Leon] It is related to point #3 that "mute" should not be
> >>>>>>>>>>> handled
> >>>>>>>> like
> >>>>>>>>>>> "hold"
> >>>>>>>>>>>
> >>>>>>>>>> <partha>  IMO, there should be no normative statement
> related
> >> to
> >>>>>>> mute
> >>>>>>>> </partha>
> >>>>>>>>>>
> >>>>>>>>>>>> 5) Sec 4.2 and Sec 8.1 has duplicate information of
> metadata
> >>>>>>>> delivery
> >>>>>>>>>>> which shall
> >>>>>>>>>>>> be avoided.
> >>>>>>>>>>>
> >>>>>>>>>>> [Leon] 4.2 is the overview section. We could have some
> >> repetition
> >>>>>>>> here
> >>>>>>>>>>> with detailed sections.
> >>>>>>>>>>>>
> >>>>>>>>>> <partha>  I can live with incase everybody wants with
> >> duplication
> >>>>>>>>>> on
> >>>>>>>> text
> >>>>>>>>>> </partha>
> >>>>>>>>>>
> >>>>>>>>>>>> 6) content type shall be "application/rs-metadata+xml"
> >> instead
> >>>>>>>>>>>> of current "application/rs-metadata"
> >>>>>>>>>>>>
> >>>>>>>>>>> [Leon] I am ok with that
> >>>>>>>>>>>> 7) full metadata snapshot shall be passed across using
> >> UPDATE as
> >>>>>>>> well.
> >>>>>>>>>>>> But the current statement on Sec 8.1 misleading "When the
> >> SRC
> >>>>>>>> sends a
> >>>>>>>>>>> full metadata snapshot, the SRC MUST
> >>>>>>>>>>>> send an INVITE request with an SDP offer and the
> "recording-
> >>>>>>>> session"
> >>>>>>>>>>>> disposition."
> >>>>>>>>>>>>
> >>>>>>>>>>> [Leon] I remember having discussion to mandate INVITE in
> >> order to
> >>>>>>>> make
> >>>>>>>>>>> sure that SDP will be present as well. Dont have any strong
> >>>>>>>> preferences
> >>>>>>>>>>> here.
> >>>>>>>>>>>
> >>>>>>>>>> <partha>  We had the discussion during IETF-80 to mandate
> >> INVITE&
> >>>>>>>> UPDATE.
> >>>>>>>>>> But I could not find the reason for not using UPDATE for
> full
> >>>>>>>> snapshot
> >>>>>>>>>> Request</partha>
> >>>>>>>>>
> >>>>>>>>> [Leon] I am ok with both
> >>>>>>>>>>
> >>>>>>>>>>>> 8) Sec 8.2: whether rs-metadata-request body shall be
> >> changed as
> >>>>>>>> SIP
> >>>>>>>>>>>> header or clear indication within the message to indicate
> >>>>>>> metadata
> >>>>>>>>>>> request. Also, reason for logging could be mentioned
> >> explicitly
> >>>>>>>> like
> >>>>>>>>>>> "logging: SRS internal error"
> >>>>>>>>>>>>
> >>>>>>>>>>> [Leon]  I am ok with that. Any opinions?
> >>>>>>>>>>>
> >>>>>>>>>>>> 9) Sec 8.2: If logging is mandatory for SRS, Any
> >> recommendation
> >>>>>>> of
> >>>>>>>>>>>> logging text from SRS for the generic request
> >>>>>>>>>>>
> >>>>>>>>>>> [Leon] Please elaborate.
> >>>>>>>>>>>>
> >>>>>>>>>> <partha>  Currently, it is plain text now whereas SRC has no
> >> means
> >>>>>>> to
> >>>>>>>>>> understand about  the logs. Some guidelines/suggestion about
> >> the
> >>>>>>>> text
> >>>>>>>>>> helps for the implementation by which SRC understand.
> >> </partha>
> >>>>>>>>>>>> Thanks
> >>>>>>>>>>>> Partha
> >>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>> 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
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From Henry.Lum@alcatel-lucent.com  Wed Nov 16 08:41:57 2011
Return-Path: <Henry.Lum@alcatel-lucent.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 71A7311E80B4 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 08:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id laNRhH7hHGxC for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 08:41:52 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8DAE111E8085 for <siprec@ietf.org>; Wed, 16 Nov 2011 08:41:52 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id pAGGfo9m007506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2011 10:41:50 -0600 (CST)
Received: from relay-out1.wc.genesyslab.com (relay-out1.wc.genesyslab.com [172.22.70.114]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pAGGfmAd002310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 Nov 2011 10:41:50 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.wc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id pAGGfmEU001528; Wed, 16 Nov 2011 08:41:48 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.92]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 08:41:47 -0800
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, 16 Nov 2011 08:41:46 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7407CDAD96@NAHALD.us.int.genesyslab.com>
In-Reply-To: <C51D12EB-40A2-4B84-819D-F7485FD307D5@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] draft-ietf-siprec-protocol-02
Thread-Index: Acyibr0dQiDIqpcSQM6B1s5qWwsECwCDjmvw
References: <4EBDAC36.1090007@alum.mit.edu> <C51D12EB-40A2-4B84-819D-F7485FD307D5@gmail.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Leon Portman" <leon.portman@gmail.com>, "Paul Kyzivat" <pkyzivat@alum.mit.edu>
X-OriginalArrivalTime: 16 Nov 2011 16:41:47.0484 (UTC) FILETIME=[A1D531C0:01CCA47E]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ietf-siprec-protocol-02
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, 16 Nov 2011 16:41:57 -0000

Just trying to catch up on the messages. I agree with the comments below
and will make the changes suggested.

Regarding the snippet on feature and option tags:

> > If that was done, its not evident that the feature tags add
anything.
> It would be simpler to have the INVITE contain:
> >
> > 	Supported: src
> > 	Require: srs
> >
> > (An RS initiated by the SRS would invert those.)

I like the idea of simplifying the intent as options tags only using
separate options tags for src and srs. This way we are sure only an SRS
can accept the recording session coming from an SRC.

The feature tag can still be useful for registration purposes so the
registrar knows that a contact is an SRS.

Regards,
Henry

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> Sent: November-13-11 8:43 PM
> To: Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: Re: [siprec] draft-ietf-siprec-protocol-02
>=20
> Paul Hi
>=20
> Thank you for the review. Please see below
>=20
> Leon
>=20
> On Nov 11, 2011, at 6:13 PM, Paul Kyzivat wrote:
>=20
> > I was just reviewing draft-ietf-siprec-protocol-02, and the
following
> are things I noted along the way:
> >
> > Section 4.2:
> >
> >   Metadata is transported in the body of INVITE or UPDATE messages.
> >   Certain metadata, such as the attributes of the recorded media
> stream
> >   are located in the SDP of the recording session.
> >
> > I think we should point out that this is typically going to require
> multipart support. Perhaps:
> >
> >   Metadata is transported within the body of INVITE or UPDATE
> messages
> >   for the recording session. Most metadata is located in a siprec
> >   specific body part, but certain metadata, such as the attributes
> >   of the recorded media stream, are located in the SDP offer or
> answer.
> >   In many cases this means a message will contain both a siprec
> >   specific part as well as an SDP part, contained within a body of
> >   type multipart/mixed.
>=20
> [Leon] I agree
>=20
> >
> > Figure 3:
> >
> > Shouldn't the first message be:
> >    (1) INVITE (metadata snapshot(1) + SDP offer)
> >
> [Leon] Correct ,it is also true for persistent recording use case
>=20
> > Section 5.1:
> >
> >   An SRS uses the presence of the 'src' feature
> >   tag in dialog creating and modifying requests and responses to
> >   confirm that the dialog being created is for the purpose of a
> >   Recording Session. ... Other SIP Recording extensions and
behaviors
> >   can be triggered by the presence of this feature tag.
> >
> > This is an abuse of the feature tag mechanism. The tag indicates a
> *capability*. It shouldn't be used to infer intent. OTOH, I think it
> would be ok to interpret the presence of metadata in the message as an
> indication that request is intended for the purpose of establishing an
> RS.
> >
> > Also, the option tag should be "sip.src". (Indicated as "+sip.src"
in
> the Contact header.)
> >
> [Leon] I will add it to open items to the IETF 82 presentation. The
> main question is if we always have metadata in RS INVITE. I think we
> always should have also for persistent use case as well, even it only
> describes preallocated media sessions and not specific CS.
>=20
> >   Since SIP Caller Preferences extensions are optional to implement
> for
> >   routing proxies, there is no guarantee that a recording session
> will
> >   be routed to an SRC or SRS.  A new options tag is introduced:
> >   "siprec".  As per [RFC3261], only an SRC or an SRS can accept this
> >   option tag in a recording session.  An SRC SHOULD include the
> >   "siprec" option tag in the Require header when initiating a
> Recording
> >   Session so that other types of user agents can simply reject the
> >   INVITE request with a 420 Bad Extension.
> >
> > This doesn't distinguish between SRC and SRS behavior. It might be
> better to have two option tags: src and srs.
> >
> > If that was done, its not evident that the feature tags add
anything.
> It would be simpler to have the INVITE contain:
> >
> > 	Supported: src
> > 	Require: srs
> >
> > (An RS initiated by the SRS would invert those.)
>=20
> [Leon] Will add as an open item to the presentation
> >
> > 6.1
> >
> > Given the work that is being done in other WGs on multiplexing media
> streams on RTP streams, I wonder if we ought to revisit our decision
to
> always map a CS media stream uniquely to an RS m-line, and instead
> consider allowing multiplexing. (But doing this would require more
> description in metadata and/or SDP.)
> >
> [Leon] I believe the decision was not to prevent support for
> multiplexing but just not to require it.
> > 6.1.1
> >
> >   ... To
> >   add a recorded stream to the recording session, the SRC sends a
new
> >   SDP offer by adding a new media stream description or by reusing
an
> >   old media stream which had been previously disabled, according to
> the
> >   procedures in [RFC3264].
> >
> > Its not necessary to disable one before reusing it. You can
repurpose
> a stream in one step. How about:
> >
> >   ... To
> >   add a recorded stream to the recording session, the SRC sends a
new
> >   SDP offer by adding a new media stream description or by reusing
an
> >   media stream which had been previously disabled or that is no
> >   longer needed, according to the procedures in [RFC3264].
> >
> [Leon] I am ok with that
>=20
> > Section 9:
> >
> >   ... In order
> >   not to lose the NAT bindings for the RTP/RTCP ports opened for the
> >   recorded streams, the SRC and SRS SHOULD follow the
recommendations
> >   provided in [RFC6263] to maintain the NAT bindings.
> >
> > The recommendation involves also enabling multiplexing of rtcp and
> rtp. If that is what we are going to do it would be worth calling that
> out, and showing it in the examples.
> >
> > But that document also only applies when ICE isn't used.
> >
> > Maybe this should all be addressed as part of
draft-eckel-siprec-rtp-
> rec.
>=20
> [Leon] I am ok with that
> >
> > Section 10.1.1
> >
> >   A new SDP attribute "recordpref" is introduced.  The SDP attribute
> >   appears at the media level and can appear in an SDP offer or
> answer.
> >   The recording indication applies to the specified media stream
> only.
> >   The following is the ABNF of the recordpref attribute:
> >
> > IMO this attribute should be permitted at either session or media
> level, with session level establishing a default for all media. (Thus
> only one session level attribute need be supplied to request that all
> media should/shouldn't be recorded.)
>=20
> [Leon] I am ok with that
> >
> > Section 10.2.1
> >
> > The comments above for "recordpref" also apply to "record".
> >
> >   The recording attribute is a declaration by an endpoint in the CS
> to
> >   indicate whether recording is taking place.
> >
> > This seems wrong. The indication is from the SRC toward and
endpoint.
> How about:
> >
> >   The recording attribute is a declaration by the SRC to an endpoint
> >   in the CS to indicate whether recording is taking place.  For
> >   example, if a UA (A)
> >
> [Leon] Agree, we should fix it in the document
> > 	Thanks,
> > 	Paul
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From ietf@meetecho.com  Wed Nov 16 09:01:12 2011
Return-Path: <ietf@meetecho.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 EE80A21F936C for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 09:01:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qva4bnBxwsy for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 09:01:08 -0800 (PST)
Received: from smtplq03.aruba.it (smtplqs-out5.aruba.it [62.149.158.45]) by ietfa.amsl.com (Postfix) with SMTP id A5A0D21F9333 for <siprec@ietf.org>; Wed, 16 Nov 2011 09:01:07 -0800 (PST)
Received: (qmail 23669 invoked by uid 89); 16 Nov 2011 17:01:03 -0000
Received: from unknown (HELO smtp3.aruba.it) (62.149.158.223) by smtplq03.aruba.it with SMTP; 16 Nov 2011 17:01:03 -0000
Received: (qmail 19898 invoked by uid 89); 16 Nov 2011 17:01:03 -0000
Received: from unknown (HELO ?192.168.15.117?) (ietf@meetecho.com@114.24.8.77) by smtp3.ad.aruba.it with SMTP; 16 Nov 2011 17:01:02 -0000
Message-ID: <4EC3EC46.8080304@meetecho.com>
Date: Wed, 16 Nov 2011 18:00:54 +0100
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtp3.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq03.aruba.it 1.6.2 0/1000/N
Subject: [siprec] Meetecho support for SIPREC WG meeting session
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, 16 Nov 2011 17:01:13 -0000

Hi all,

a virtual room has been reserved on the Meetecho system for Thursday's 
SIPREC WG meeting session.

Access to the on-line session (including audio and video streams) will 
be available from 3:20pm at:
http://www.meetecho.com/ietf82/siprec

The Meetecho session automatically logs you into the standard IETF 
jabber room. So, from there, you can have an integrated experience 
involving all media and allowing you to interact with the room.

A tutorial of interactivity features of the tool can be found at:
http://www.meetecho.com/ietf82/tutorials

For further information you can contact us at ietf-support@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From Henry.Lum@alcatel-lucent.com  Wed Nov 16 09:10:59 2011
Return-Path: <Henry.Lum@alcatel-lucent.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 7B39621F94A0 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 09:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQceN32paE2V for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 09:10:58 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 83BC621F8BFB for <siprec@ietf.org>; Wed, 16 Nov 2011 09:10:58 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pAGHAqmK018864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2011 11:10:52 -0600 (CST)
Received: from relay-out1.wc.genesyslab.com (relay-out1.wc.genesyslab.com [172.22.70.114]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pAGHAnxW017063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 Nov 2011 11:10:50 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.wc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id pAGHAlrc004289; Wed, 16 Nov 2011 09:10:48 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.92]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 09:10:48 -0800
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, 16 Nov 2011 09:10:47 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7407CDADBD@NAHALD.us.int.genesyslab.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD086526CA@XMB-BGL-417.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: Acyj/qv77sGvhNFrRPiIQeVemmDdowADSjaAAB01/RA=
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com> <B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526CA@XMB-BGL-417.cisco.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <leon.portman@gmail.com>, "Parthasarathi Ravindran" <pravindran@sonusnet.com>
X-OriginalArrivalTime: 16 Nov 2011 17:10:48.0770 (UTC) FILETIME=[AFB85A20:01CCA482]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 17:10:59 -0000

I agree that the meaning of mute/unmute of CS streams has a lot to do
with the implementation of the endpoint itself. We can keep it outside
of the protocol but I think we should still mention it in the spec so
that we don't confuse the meaning of a=3Dinactive in the recording sessio=
n
as the same thing as muting in CS stream.

Old text:
   The SRC can temporarily discontinue streaming and collection of
   recorded media from the SRC to the SRS for reason such as masking the
   recording.  In this case, the SRC sends a new SDP offer and sets the
   media stream to inactive (a=3Dinactive) for each recorded stream to be=

   paused, as per the procedures in [RFC3264].  To resume streaming and
   collection of recorded media, the SRC sends a new SDP offer and sets
   the media streams with a=3Dsendonly attribute.  Note that when a CS
   stream is muted/unmuted, this information is conveyed in the metadata
   by the SRC.  The SRC SHOULD not modify the media stream with
   a=3Dinactive for mute since this operation is reserved for pausing the=

   RS media.

Proposed changes:

   The SRC can temporarily discontinue streaming and collection of
   recorded media from the SRC to the SRS for reason such as masking the
   recording.  Masking the recording is different than a CS participant
muting its media stream; the decision to mask a recording is a matter of
local policy at the SRC. For example, the SRC may mask the recording
when a participant in the CS is collecting sensitive information.
   To temporarily discontinue recording, the SRC sends a new SDP offer
and sets the
   media stream to inactive (a=3Dinactive) for each recorded stream to be=

   paused, as per the procedures in [RFC3264].  To resume streaming and
   collection of recorded media, the SRC sends a new SDP offer and sets
   the media streams with a=3Dsendonly attribute. =20


Regards,
Henry

> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> Sent: November-15-11 10:22 PM
> To: Leon Portman; Parthasarathi Ravindran; Henry Lum
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>=20
> Hi Leon,
>=20
> A comment on this point
>=20
> >> [Leon] Yes, it is not defined yet in metadata. We should rephrase
it
> >> to "may be conveyed in metadata"
> > <partha> Currently, it is outside the scope of metadata and IMO, it
> is
>=20
> > better to remove "mute/unmute" from protocol spec </partha>
>=20
> [Leon] I agree, Henry, what do you think?
>=20
> IMO mute/unmute is a property of a device and it is better not to map
> it
> to signaling. SRS could use alternate mechanisms to detect no media. I
> would prefer it keep it outside the scope of SIPREC.
> An SRC that has the capability to do this may send the information as
> an
> extension data.
>=20
> Ram
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Leon Portman
> > Sent: Wednesday, November 16, 2011 9:26 AM
> > To: Parthasarathi Ravindran; henry.lum@genesyslab.com
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
> >
> > Partha Thanks
> >
> > Please see below
> >
> > Leon
> >
> > On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
> >
> > > Leon,
> > >
> > > Please read inline
> > >
> > > Thanks
> > > Partha
> > >
> > >> -----Original Message-----
> > >> From: Leon Portman [mailto:leon.portman@gmail.com]
> > >> Sent: Tuesday, November 15, 2011 1:03 PM
> > >> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
> > >> Cc: siprec@ietf.org
> > >> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
> > >>
> > >>
> > >> Partha Hi
> > >>
> > >> Please see below
> > >>
> > >> Regards
> > >>
> > >> Leon
> > >> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
> > >>
> > >>> 1) "may" is used instead of normative statement "MAY".
> > >>>  a) Sec 4.2 Para 1 Line 2
> > >>>  b) Sec 4.2 Para 3 Line 5
> > >>>
> > >> [Leon] I am not sure that we want to emphasize MAY in this
> specific
> > >> section, it is an over part.
> > >>
> > > <partha> I'm not very sure whether it is appropriate to use "may"
> in
> > the specification.
> > > </partha>
> >
> > [Leon] I dont have any opinions on that
> > >
> > >>> 2) Figure 4: I guess that port 22458 "m" line is video instead
of
> > >> current audio.
> > >>
> > >> [Leon] Yes, good catch. Thanks
> > >>>
> > >>> 3) Please clarify the following statement in Sec 6.1.1 "Note
that
> > when
> > >> a CS
> > >>>  stream is muted/unmuted, this information is conveyed in the
> > >> metadata
> > >>>  by the SRC. " because I don't know how metadata convey this
> > >> currently.
> > >>>
> > >> [Leon] Yes, it is not defined yet in metadata. We should rephrase
> it
> > to
> > >> "may be conveyed in metadata"
> > > <partha> Currently, it is outside the scope of metadata and IMO,
it
> > is better
> > > to remove "mute/unmute" from protocol spec </partha>
> >
> > [Leon] I agree, Henry, what do you think?
> > >
> > >>> 4) Whether the normative statement required for mute? Sec 6.1.1
> > >>>  "The SRC SHOULD not modify the media stream with
> > >>>  a=3Dinactive for mute since this operation is reserved for
pausing
> > the
> > >>>  RS media."
> > >>>
> > >> [Leon] It is related to point #3 that "mute" should not be
handled
> > like
> > >> "hold"
> > >>
> > > <partha> IMO, there should be no normative statement related to
> mute
> > </partha>
> > >
> > >>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
> > delivery
> > >> which shall
> > >>>  be avoided.
> > >>
> > >> [Leon] 4.2 is the overview section. We could have some repetition
> > here
> > >> with detailed sections.
> > >>>
> > > <partha> I can live with incase everybody wants with duplication
on
> > text
> > > </partha>
> > >
> > >>> 6) content type shall be "application/rs-metadata+xml" instead
of
> > >>> current "application/rs-metadata"
> > >>>
> > >> [Leon] I am ok with that
> > >>> 7) full metadata snapshot shall be passed across using UPDATE as
> > well.
> > >>> But the current statement on Sec 8.1 misleading "When the SRC
> sends
> > a
> > >> full metadata snapshot, the SRC MUST
> > >>>  send an INVITE request with an SDP offer and the "recording-
> > session"
> > >>>  disposition."
> > >>>
> > >> [Leon] I remember having discussion to mandate INVITE in order to
> > make
> > >> sure that SDP will be present as well. Dont have any strong
> > preferences
> > >> here.
> > >>
> > > <partha> We had the discussion during IETF-80 to mandate INVITE &
> > UPDATE.
> > > But I could not find the reason for not using UPDATE for full
> > snapshot
> > > Request </partha>
> >
> > [Leon] I am ok with both
> > >
> > >>> 8) Sec 8.2: whether rs-metadata-request body shall be changed as
> > SIP
> > >>> header or clear indication within the message to indicate
> metadata
> > >> request. Also, reason for logging could be mentioned explicitly
> like
> > >> "logging: SRS internal error"
> > >>>
> > >> [Leon]  I am ok with that. Any opinions?
> > >>
> > >>> 9) Sec 8.2: If logging is mandatory for SRS, Any recommendation
> of
> > >>> logging text from SRS for the generic request
> > >>
> > >> [Leon] Please elaborate.
> > >>>
> > > <partha> Currently, it is plain text now whereas SRC has no means
> to
> > > understand about  the logs. Some guidelines/suggestion about the
> text
> > > helps for the implementation by which SRC understand. </partha>
> > >>> Thanks
> > >>> Partha
> > >>> _______________________________________________
> > >>> 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

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From pkyzivat@alum.mit.edu  Wed Nov 16 11:47:19 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 1524F21F9197 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 11:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level: 
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q2ZUSLTBTwO7 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 11:47:18 -0800 (PST)
Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by ietfa.amsl.com (Postfix) with ESMTP id 32BBA21F916A for <siprec@ietf.org>; Wed, 16 Nov 2011 11:47:18 -0800 (PST)
Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta12.emeryville.ca.mail.comcast.net with comcast id xviW1h0050b6N64ACvnBfn; Wed, 16 Nov 2011 19:47:11 +0000
Received: from dhcp-471c.meeting.ietf.org ([130.129.71.28]) by omta03.emeryville.ca.mail.comcast.net with comcast id xvoN1h00v0ccXAy8PvoRUn; Wed, 16 Nov 2011 19:48:34 +0000
Message-ID: <4EC41338.9060004@alum.mit.edu>
Date: Thu, 17 Nov 2011 03:47:04 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Henry Lum <Henry.Lum@alcatel-lucent.com>
References: <4EBDAC36.1090007@alum.mit.edu> <C51D12EB-40A2-4B84-819D-F7485FD307D5@gmail.com> <059AF07365DC474393A19A3AF187DF7407CDAD96@NAHALD.us.int.genesyslab.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7407CDAD96@NAHALD.us.int.genesyslab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ietf-siprec-protocol-02
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, 16 Nov 2011 19:47:19 -0000

I hope we can have a live discussion of this during our meeting.
Its getting hard to figure out who has what in mind now.

	Thanks,
	Paul

On 11/17/11 12:41 AM, Henry Lum wrote:
> Just trying to catch up on the messages. I agree with the comments below
> and will make the changes suggested.
>
> Regarding the snippet on feature and option tags:
>
>>> If that was done, its not evident that the feature tags add
> anything.
>> It would be simpler to have the INVITE contain:
>>>
>>> 	Supported: src
>>> 	Require: srs
>>>
>>> (An RS initiated by the SRS would invert those.)
>
> I like the idea of simplifying the intent as options tags only using
> separate options tags for src and srs. This way we are sure only an SRS
> can accept the recording session coming from an SRC.
>
> The feature tag can still be useful for registration purposes so the
> registrar knows that a contact is an SRS.
>
> Regards,
> Henry
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Leon Portman
>> Sent: November-13-11 8:43 PM
>> To: Paul Kyzivat
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] draft-ietf-siprec-protocol-02
>>
>> Paul Hi
>>
>> Thank you for the review. Please see below
>>
>> Leon
>>
>> On Nov 11, 2011, at 6:13 PM, Paul Kyzivat wrote:
>>
>>> I was just reviewing draft-ietf-siprec-protocol-02, and the
> following
>> are things I noted along the way:
>>>
>>> Section 4.2:
>>>
>>>    Metadata is transported in the body of INVITE or UPDATE messages.
>>>    Certain metadata, such as the attributes of the recorded media
>> stream
>>>    are located in the SDP of the recording session.
>>>
>>> I think we should point out that this is typically going to require
>> multipart support. Perhaps:
>>>
>>>    Metadata is transported within the body of INVITE or UPDATE
>> messages
>>>    for the recording session. Most metadata is located in a siprec
>>>    specific body part, but certain metadata, such as the attributes
>>>    of the recorded media stream, are located in the SDP offer or
>> answer.
>>>    In many cases this means a message will contain both a siprec
>>>    specific part as well as an SDP part, contained within a body of
>>>    type multipart/mixed.
>>
>> [Leon] I agree
>>
>>>
>>> Figure 3:
>>>
>>> Shouldn't the first message be:
>>>     (1) INVITE (metadata snapshot(1) + SDP offer)
>>>
>> [Leon] Correct ,it is also true for persistent recording use case
>>
>>> Section 5.1:
>>>
>>>    An SRS uses the presence of the 'src' feature
>>>    tag in dialog creating and modifying requests and responses to
>>>    confirm that the dialog being created is for the purpose of a
>>>    Recording Session. ... Other SIP Recording extensions and
> behaviors
>>>    can be triggered by the presence of this feature tag.
>>>
>>> This is an abuse of the feature tag mechanism. The tag indicates a
>> *capability*. It shouldn't be used to infer intent. OTOH, I think it
>> would be ok to interpret the presence of metadata in the message as an
>> indication that request is intended for the purpose of establishing an
>> RS.
>>>
>>> Also, the option tag should be "sip.src". (Indicated as "+sip.src"
> in
>> the Contact header.)
>>>
>> [Leon] I will add it to open items to the IETF 82 presentation. The
>> main question is if we always have metadata in RS INVITE. I think we
>> always should have also for persistent use case as well, even it only
>> describes preallocated media sessions and not specific CS.
>>
>>>    Since SIP Caller Preferences extensions are optional to implement
>> for
>>>    routing proxies, there is no guarantee that a recording session
>> will
>>>    be routed to an SRC or SRS.  A new options tag is introduced:
>>>    "siprec".  As per [RFC3261], only an SRC or an SRS can accept this
>>>    option tag in a recording session.  An SRC SHOULD include the
>>>    "siprec" option tag in the Require header when initiating a
>> Recording
>>>    Session so that other types of user agents can simply reject the
>>>    INVITE request with a 420 Bad Extension.
>>>
>>> This doesn't distinguish between SRC and SRS behavior. It might be
>> better to have two option tags: src and srs.
>>>
>>> If that was done, its not evident that the feature tags add
> anything.
>> It would be simpler to have the INVITE contain:
>>>
>>> 	Supported: src
>>> 	Require: srs
>>>
>>> (An RS initiated by the SRS would invert those.)
>>
>> [Leon] Will add as an open item to the presentation
>>>
>>> 6.1
>>>
>>> Given the work that is being done in other WGs on multiplexing media
>> streams on RTP streams, I wonder if we ought to revisit our decision
> to
>> always map a CS media stream uniquely to an RS m-line, and instead
>> consider allowing multiplexing. (But doing this would require more
>> description in metadata and/or SDP.)
>>>
>> [Leon] I believe the decision was not to prevent support for
>> multiplexing but just not to require it.
>>> 6.1.1
>>>
>>>    ... To
>>>    add a recorded stream to the recording session, the SRC sends a
> new
>>>    SDP offer by adding a new media stream description or by reusing
> an
>>>    old media stream which had been previously disabled, according to
>> the
>>>    procedures in [RFC3264].
>>>
>>> Its not necessary to disable one before reusing it. You can
> repurpose
>> a stream in one step. How about:
>>>
>>>    ... To
>>>    add a recorded stream to the recording session, the SRC sends a
> new
>>>    SDP offer by adding a new media stream description or by reusing
> an
>>>    media stream which had been previously disabled or that is no
>>>    longer needed, according to the procedures in [RFC3264].
>>>
>> [Leon] I am ok with that
>>
>>> Section 9:
>>>
>>>    ... In order
>>>    not to lose the NAT bindings for the RTP/RTCP ports opened for the
>>>    recorded streams, the SRC and SRS SHOULD follow the
> recommendations
>>>    provided in [RFC6263] to maintain the NAT bindings.
>>>
>>> The recommendation involves also enabling multiplexing of rtcp and
>> rtp. If that is what we are going to do it would be worth calling that
>> out, and showing it in the examples.
>>>
>>> But that document also only applies when ICE isn't used.
>>>
>>> Maybe this should all be addressed as part of
> draft-eckel-siprec-rtp-
>> rec.
>>
>> [Leon] I am ok with that
>>>
>>> Section 10.1.1
>>>
>>>    A new SDP attribute "recordpref" is introduced.  The SDP attribute
>>>    appears at the media level and can appear in an SDP offer or
>> answer.
>>>    The recording indication applies to the specified media stream
>> only.
>>>    The following is the ABNF of the recordpref attribute:
>>>
>>> IMO this attribute should be permitted at either session or media
>> level, with session level establishing a default for all media. (Thus
>> only one session level attribute need be supplied to request that all
>> media should/shouldn't be recorded.)
>>
>> [Leon] I am ok with that
>>>
>>> Section 10.2.1
>>>
>>> The comments above for "recordpref" also apply to "record".
>>>
>>>    The recording attribute is a declaration by an endpoint in the CS
>> to
>>>    indicate whether recording is taking place.
>>>
>>> This seems wrong. The indication is from the SRC toward and
> endpoint.
>> How about:
>>>
>>>    The recording attribute is a declaration by the SRC to an endpoint
>>>    in the CS to indicate whether recording is taking place.  For
>>>    example, if a UA (A)
>>>
>> [Leon] Agree, we should fix it in the document
>>> 	Thanks,
>>> 	Paul
>>> _______________________________________________
>>> 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
>
> 					
> -------------------------------------------------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
> 					
>


From pkyzivat@alum.mit.edu  Wed Nov 16 12:32:59 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 799E421F8F68 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 12:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWOyOzTNqaft for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 12:32:58 -0800 (PST)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by ietfa.amsl.com (Postfix) with ESMTP id AB0A221F8F51 for <siprec@ietf.org>; Wed, 16 Nov 2011 12:32:58 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta06.westchester.pa.mail.comcast.net with comcast id xojP1h00B1c6gX856wYzKD; Wed, 16 Nov 2011 20:32:59 +0000
Received: from dhcp-471c.meeting.ietf.org ([130.129.71.28]) by omta23.westchester.pa.mail.comcast.net with comcast id xwYk1h01V0ccXAy3jwYn09; Wed, 16 Nov 2011 20:32:56 +0000
Message-ID: <4EC41DEC.8060707@alum.mit.edu>
Date: Thu, 17 Nov 2011 04:32:44 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com> <4EC36F1F.4000605@alum.mit.edu> <387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com> <4EC37852.60809@alum.mit.edu> <B81B0AE1-E84E-4159-90A5-4C87766E7317@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE92FF@inba-mail01.sonusnet.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE92FF@inba-mail01.sonusnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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, 16 Nov 2011 20:32:59 -0000

On 11/16/11 10:07 PM, Ravindran, Parthasarathi wrote:
> Paul/Leon,
>
> We have discussed about decoupling of "metadata"&  "SDP" for SRS but
> here it is SRC. Even in case of SRS, we agreed upon that there is no
> need to defer the responses for metadata processing and RE-INVITE/UPDATE
> is agreed upon based on this assumption. Snapshot request may be used as
> deferred mechanism to correct metadata.

I think that is consistent with what I recall. The point was that the 
SRS need not process the metadata before replying.

> SRC implementation shall maintain "metadata"&  "SDP" in different layer
> but the latency problem is solved by sending "100 trying" for RE-INVITE
> in SRC.

Yes, you *can* extend the reinvite transaction by sending provisionals. 
But it still gets ugly then in terms of interaction between layers.

> The problem with two different transaction (request/response) is that
> the possibility of a offer/answer race condition is higher.

Why is that? What sort of race condition? Its of course always possible 
for reinvite to be launched simultaneously by both src and srs, 
resulting in o/a glare. But that is independent of this question. (But 
it does remind me that we probably ought to discuss somewhere the 
implications of a glare case on metadata processing, though in some 
sense it is obvious.)

Are you assuming the snapshot request always comes in an offerless-reinvite?

If it comes in a reinvite with an offer, and the snapshot is required in 
the answer, then the shapshot is required to be consistent with the SDP 
in the offer. That could be a problem. I suppose we could draw up a 
bunch of constraints to prevent that, but its extra work, so why bother? 
If we don't require the snapshot in the response, then we avoid that - 
the src can wait until it can send reinvite with suitable offer.

If snapshot request comes in a reinvite without offer, then there are no 
signaling difficulties with returning the snapshot in the response with 
the offer. And I am fine with *allowing* that, but not requiring it.

If the snapshot request comes in a reinvite without offer, and the 
response does NOT contain the shapshot, then probably it contains an 
offer same as last time, and the answer can as well. At that point, what 
sort of race are you concerned about? It seems the only one would be if 
the SRS send *another* reinvite before the snapshot is received. But I 
see no new problem with that.

The complexities I see are:

- SRS sends reinvite with offer that is different from last agreed,
   regardless of whether this contains a snapshot request or not.

- SRS sends reinvite without offer, the offer in the response
   differs from what was last agreed, and does not contain metadata.

- SRC sends reinvite with offer different from last agreed,
   and without metadata.

- SRC sends reinvite without offer, with or without metadata.

We might want to lay down some rules, such as that the snapshot request 
must never contain an offer, or must always contain an offer identical 
to what was last agreed. But even that may take some consideration - 
some SBCs might take an offerless invite and fill in an offer. :-(

> Apart from
> latency, Could you please specify any advantage in two transaction approach.

Potentially easier implementation for the SRC.

> Also, two transactions makes me to feel like invoking action in SRC as the
> Second transaction is triggered based on the first UPDATE/RE-INVITE with
> Snapshot request.

Yes. What is wrong with that?
We do such things all the time. (E.g. SUBSCRIBE triggers NOTIFY.)

> Let us get others opinion for the need of two separate transaction
> (request/response) in SRC.

I'm arguing to allow flexibility on the part of the SRC.
If you are building an SRC, and you want to implement it to always 
return the snapshot in the response, then you can build it that way.

	Thanks,
	Paul

From rmohanr@cisco.com  Wed Nov 16 17:38:50 2011
Return-Path: <rmohanr@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 0C4C611E8081 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 17:38:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.577
X-Spam-Level: 
X-Spam-Status: No, score=-6.577 tagged_above=-999 required=5 tests=[AWL=-1.178, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OvwhANuLKeI7 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 17:38:49 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 36E6811E8082 for <siprec@ietf.org>; Wed, 16 Nov 2011 17:38:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=9981; q=dns/txt; s=iport; t=1321493928; x=1322703528; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=tKbRRfgZeAW8GaLMd/ruAyeZ2hXpAzaztnP2pD4lJ3o=; b=GCOq0qeL86GrpwKrO8NxVO0k3gVM09jpGQLYqmMIlSRQx7INFEOnKGUm Tx6/Yq8OR4XmK5L9tO4er/6e8xLoIhiWIlnIAl9j2Z0MX5mJ6JWkCDKNL hd4vJgksDcAFAgMkaN8jywWDDCr9xtL74WsUOxyo2ynPMU4rPbBCOMM/u 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AowAAKJkxE5Io8UT/2dsb2JhbABCmXiQDoEFgXIBAQEDAQEBAQ8BHQo0AgkMBAIBCBEEAQEBCgYXAQYBIAYfCQgBAQQBCggIGodgCJRvAZ5kBIk0YwSIEpFmhQeHOQ
X-IronPort-AV: E=Sophos;i="4.69,524,1315180800";  d="scan'208";a="3271862"
Received: from bgl-core-4.cisco.com ([72.163.197.19]) by ams-iport-4.cisco.com with ESMTP; 17 Nov 2011 01:38:45 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAH1cjhl011212; Thu, 17 Nov 2011 01:38:45 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Nov 2011 07:08:45 +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: Thu, 17 Nov 2011 07:04:13 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD08652AC8@XMB-BGL-417.cisco.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7407CDADBD@NAHALD.us.int.genesyslab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: Acyj/qv77sGvhNFrRPiIQeVemmDdowADSjaAAB01/RAAEg2aEA==
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><0B6A7A35-3394-4CDA-9885-48ABDB9051C6@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8A82@inba-mail01.sonusnet.com> <B71052D8-8D31-42EA-8588-35EFDA47561F@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526CA@XMB-BGL-417.cisco.com> <059AF07365DC474393A19A3AF187DF7407CDADBD@NAHALD.us.int.genesyslab.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Leon Portman" <leon.portman@gmail.com>, "Parthasarathi Ravindran" <pravindran@sonusnet.com>
X-OriginalArrivalTime: 17 Nov 2011 01:38:45.0094 (UTC) FILETIME=[A5065860:01CCA4C9]
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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: Thu, 17 Nov 2011 01:38:50 -0000

Please see inline

> -----Original Message-----
> From: Henry Lum [mailto:Henry.Lum@alcatel-lucent.com]
> Sent: Thursday, November 17, 2011 1:11 AM
> To: Ram Mohan R (rmohanr); Leon Portman; Parthasarathi Ravindran
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
>=20
> I agree that the meaning of mute/unmute of CS streams has a lot to do
> with the implementation of the endpoint itself. We can keep it outside
> of the protocol but I think we should still mention it in the spec so
> that we don't confuse the meaning of a=3Dinactive in the recording
> session
> as the same thing as muting in CS stream.
>=20
> Old text:
>    The SRC can temporarily discontinue streaming and collection of
>    recorded media from the SRC to the SRS for reason such as masking
> the
>    recording.  In this case, the SRC sends a new SDP offer and sets
the
>    media stream to inactive (a=3Dinactive) for each recorded stream to
be
>    paused, as per the procedures in [RFC3264].  To resume streaming
and
>    collection of recorded media, the SRC sends a new SDP offer and
sets
>    the media streams with a=3Dsendonly attribute.  Note that when a CS
>    stream is muted/unmuted, this information is conveyed in the
> metadata
>    by the SRC.  The SRC SHOULD not modify the media stream with
>    a=3Dinactive for mute since this operation is reserved for pausing
the
>    RS media.
>=20
> Proposed changes:
>=20
>    The SRC can temporarily discontinue streaming and collection of
>    recorded media from the SRC to the SRS for reason such as masking
> the
>    recording.  Masking the recording is different than a CS
participant
> muting its media stream; the decision to mask a recording is a matter
> of
> local policy at the SRC. For example, the SRC may mask the recording
> when a participant in the CS is collecting sensitive information.
>    To temporarily discontinue recording, the SRC sends a new SDP offer
> and sets the
>    media stream to inactive (a=3Dinactive) for each recorded stream to
be
>    paused, as per the procedures in [RFC3264].  To resume streaming
and
>    collection of recorded media, the SRC sends a new SDP offer and
sets
>    the media streams with a=3Dsendonly attribute.

 This is fine as long as we don't mandate an SRC to do this. IMO we can
leave it as a policy and if a SRC is compliant with the policy(due to
regulations in some places) it may support the above behavior.

Thanks,
Ram

>=20
>=20
> Regards,
> Henry
>=20
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: November-15-11 10:22 PM
> > To: Leon Portman; Parthasarathi Ravindran; Henry Lum
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Comment on draft-ietf-siprec-protocol-02
> >
> > Hi Leon,
> >
> > A comment on this point
> >
> > >> [Leon] Yes, it is not defined yet in metadata. We should rephrase
> it
> > >> to "may be conveyed in metadata"
> > > <partha> Currently, it is outside the scope of metadata and IMO,
it
> > is
> >
> > > better to remove "mute/unmute" from protocol spec </partha>
> >
> > [Leon] I agree, Henry, what do you think?
> >
> > IMO mute/unmute is a property of a device and it is better not to
map
> > it
> > to signaling. SRS could use alternate mechanisms to detect no media.
> I
> > would prefer it keep it outside the scope of SIPREC.
> > An SRC that has the capability to do this may send the information
as
> > an
> > extension data.
> >
> > Ram
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Leon Portman
> > > Sent: Wednesday, November 16, 2011 9:26 AM
> > > To: Parthasarathi Ravindran; henry.lum@genesyslab.com
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
> > >
> > > Partha Thanks
> > >
> > > Please see below
> > >
> > > Leon
> > >
> > > On Nov 16, 2011, at 8:14 AM, Ravindran, Parthasarathi wrote:
> > >
> > > > Leon,
> > > >
> > > > Please read inline
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > >> -----Original Message-----
> > > >> From: Leon Portman [mailto:leon.portman@gmail.com]
> > > >> Sent: Tuesday, November 15, 2011 1:03 PM
> > > >> To: Ravindran, Parthasarathi; henry.lum@genesyslab.com
> > > >> Cc: siprec@ietf.org
> > > >> Subject: Re: [sipprec] Comment on draft-ietf-siprec-protocol-02
> > > >>
> > > >>
> > > >> Partha Hi
> > > >>
> > > >> Please see below
> > > >>
> > > >> Regards
> > > >>
> > > >> Leon
> > > >> On Nov 15, 2011, at 12:39 PM, Ravindran, Parthasarathi wrote:
> > > >>
> > > >>> 1) "may" is used instead of normative statement "MAY".
> > > >>>  a) Sec 4.2 Para 1 Line 2
> > > >>>  b) Sec 4.2 Para 3 Line 5
> > > >>>
> > > >> [Leon] I am not sure that we want to emphasize MAY in this
> > specific
> > > >> section, it is an over part.
> > > >>
> > > > <partha> I'm not very sure whether it is appropriate to use
"may"
> > in
> > > the specification.
> > > > </partha>
> > >
> > > [Leon] I dont have any opinions on that
> > > >
> > > >>> 2) Figure 4: I guess that port 22458 "m" line is video instead
> of
> > > >> current audio.
> > > >>
> > > >> [Leon] Yes, good catch. Thanks
> > > >>>
> > > >>> 3) Please clarify the following statement in Sec 6.1.1 "Note
> that
> > > when
> > > >> a CS
> > > >>>  stream is muted/unmuted, this information is conveyed in the
> > > >> metadata
> > > >>>  by the SRC. " because I don't know how metadata convey this
> > > >> currently.
> > > >>>
> > > >> [Leon] Yes, it is not defined yet in metadata. We should
> rephrase
> > it
> > > to
> > > >> "may be conveyed in metadata"
> > > > <partha> Currently, it is outside the scope of metadata and IMO,
> it
> > > is better
> > > > to remove "mute/unmute" from protocol spec </partha>
> > >
> > > [Leon] I agree, Henry, what do you think?
> > > >
> > > >>> 4) Whether the normative statement required for mute? Sec
6.1.1
> > > >>>  "The SRC SHOULD not modify the media stream with
> > > >>>  a=3Dinactive for mute since this operation is reserved for
> pausing
> > > the
> > > >>>  RS media."
> > > >>>
> > > >> [Leon] It is related to point #3 that "mute" should not be
> handled
> > > like
> > > >> "hold"
> > > >>
> > > > <partha> IMO, there should be no normative statement related to
> > mute
> > > </partha>
> > > >
> > > >>> 5) Sec 4.2 and Sec 8.1 has duplicate information of metadata
> > > delivery
> > > >> which shall
> > > >>>  be avoided.
> > > >>
> > > >> [Leon] 4.2 is the overview section. We could have some
> repetition
> > > here
> > > >> with detailed sections.
> > > >>>
> > > > <partha> I can live with incase everybody wants with duplication
> on
> > > text
> > > > </partha>
> > > >
> > > >>> 6) content type shall be "application/rs-metadata+xml" instead
> of
> > > >>> current "application/rs-metadata"
> > > >>>
> > > >> [Leon] I am ok with that
> > > >>> 7) full metadata snapshot shall be passed across using UPDATE
> as
> > > well.
> > > >>> But the current statement on Sec 8.1 misleading "When the SRC
> > sends
> > > a
> > > >> full metadata snapshot, the SRC MUST
> > > >>>  send an INVITE request with an SDP offer and the "recording-
> > > session"
> > > >>>  disposition."
> > > >>>
> > > >> [Leon] I remember having discussion to mandate INVITE in order
> to
> > > make
> > > >> sure that SDP will be present as well. Dont have any strong
> > > preferences
> > > >> here.
> > > >>
> > > > <partha> We had the discussion during IETF-80 to mandate INVITE
&
> > > UPDATE.
> > > > But I could not find the reason for not using UPDATE for full
> > > snapshot
> > > > Request </partha>
> > >
> > > [Leon] I am ok with both
> > > >
> > > >>> 8) Sec 8.2: whether rs-metadata-request body shall be changed
> as
> > > SIP
> > > >>> header or clear indication within the message to indicate
> > metadata
> > > >> request. Also, reason for logging could be mentioned explicitly
> > like
> > > >> "logging: SRS internal error"
> > > >>>
> > > >> [Leon]  I am ok with that. Any opinions?
> > > >>
> > > >>> 9) Sec 8.2: If logging is mandatory for SRS, Any
recommendation
> > of
> > > >>> logging text from SRS for the generic request
> > > >>
> > > >> [Leon] Please elaborate.
> > > >>>
> > > > <partha> Currently, it is plain text now whereas SRC has no
means
> > to
> > > > understand about  the logs. Some guidelines/suggestion about the
> > text
> > > > helps for the implementation by which SRC understand. </partha>
> > > >>> Thanks
> > > >>> Partha
> > > >>> _______________________________________________
> > > >>> 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
>=20
>=20
>
-----------------------------------------------------------------------
> --------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
> confidential and proprietary information of Alcatel-Lucent and/or its
> affiliated entities. Access by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
> from acting, on any information contained in this e-mail is hereby
> excluded. If you are not the intended recipient, please notify the
> sender immediately, destroy the original transmission and its
> attachments and do not disclose the contents to any other person, use
> it for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
> and/or its affiliated entities.
>=20

From rmohanr@cisco.com  Wed Nov 16 18:41:50 2011
Return-Path: <rmohanr@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 B60021F0C54 for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 18:41:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.841
X-Spam-Level: 
X-Spam-Status: No, score=-6.841 tagged_above=-999 required=5 tests=[AWL=-0.842, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZM6slIpHKWdb for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 18:41:49 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id E6F101F0C53 for <siprec@ietf.org>; Wed, 16 Nov 2011 18:41:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=5012; q=dns/txt; s=iport; t=1321497709; x=1322707309; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=XXxIEwIHLXChVBTkEdmMzYUntGBffBTLIej6gFCJzWY=; b=lkvWx3Qpsu460oB4DY5fOrHup0s6FIiYC1mHBS+S5EDQ07jQt1R9Q1h2 HoLYrSfMz3Rl3P8h/cSTJ2dS1e6vDUMQdXLsnWI70063cDVHERXlX8+AZ Z1NiRKKA/+5v6WMpB0BvD9LFG3c9Iggm0ArH6q+RVevwCFTPOX2qOQ+/M o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQAABhzxE5Io8UQ/2dsb2JhbABCDplqkA6BBYFyAQEBBAEBAQ8BHQo0CwwEAgEIDgMEAQEBCgIEFwEGASYfCQgBAQQLCAgah2iUfAGeYgSJNGMEiBKRZowBPw
X-IronPort-AV: E=Sophos;i="4.69,524,1315180800";  d="scan'208";a="3272915"
Received: from bgl-core-1.cisco.com ([72.163.197.16]) by ams-iport-3.cisco.com with ESMTP; 17 Nov 2011 02:41:47 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAH2fkih029527; Thu, 17 Nov 2011 02:41:46 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Nov 2011 08:11:46 +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: Thu, 17 Nov 2011 08:11:44 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD08652ADA@XMB-BGL-417.cisco.com>
In-Reply-To: <4EC41DEC.8060707@alum.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyknvRGrmUjPIL1T5yEZADPS2VZ/AAMtu0A
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><AB720611-E545-4B5B-8B94-322269C6553E@gmail.com><35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com><C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com><95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com><3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com><101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net><770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com><A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com><4EC36F1F.4000605@alum.mit.edu><387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com><4EC37852.60809@alum.mit.edu><B81B0AE1-E84E-4159-90A5-4C87766E7317@gmail.com><387F9047F55E8C42850AD6B3A7A03C6C01CE92FF@inba-mail01.sonusnet.com> <4EC41DEC.8060707@alum.mit.edu>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>, "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
X-OriginalArrivalTime: 17 Nov 2011 02:41:46.0268 (UTC) FILETIME=[72C7B5C0:01CCA4D2]
Cc: siprec@ietf.org
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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: Thu, 17 Nov 2011 02:41:51 -0000

My thoughts on this topic of asynchronous processing/sending of
metadata:

I am in favor of having a flexibility on the part of both SRC and SRS.
So that we allow implementations where SRS can respond without
processing snapshot and SRC can respond first(for a snapshot request)
without metadata and can send metadata later.

Regards,
Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: Thursday, November 17, 2011 4:33 AM
> To: Ravindran, Parthasarathi
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>=20
> On 11/16/11 10:07 PM, Ravindran, Parthasarathi wrote:
> > Paul/Leon,
> >
> > We have discussed about decoupling of "metadata"&  "SDP" for SRS but
> > here it is SRC. Even in case of SRS, we agreed upon that there is no
> > need to defer the responses for metadata processing and RE-
> INVITE/UPDATE
> > is agreed upon based on this assumption. Snapshot request may be
used
> as
> > deferred mechanism to correct metadata.
>=20
> I think that is consistent with what I recall. The point was that the
> SRS need not process the metadata before replying.
>=20
> > SRC implementation shall maintain "metadata"&  "SDP" in different
> layer
> > but the latency problem is solved by sending "100 trying" for RE-
> INVITE
> > in SRC.
>=20
> Yes, you *can* extend the reinvite transaction by sending
provisionals.
> But it still gets ugly then in terms of interaction between layers.
>=20
> > The problem with two different transaction (request/response) is
that
> > the possibility of a offer/answer race condition is higher.
>=20
> Why is that? What sort of race condition? Its of course always
possible
> for reinvite to be launched simultaneously by both src and srs,
> resulting in o/a glare. But that is independent of this question. (But
> it does remind me that we probably ought to discuss somewhere the
> implications of a glare case on metadata processing, though in some
> sense it is obvious.)
>=20
> Are you assuming the snapshot request always comes in an offerless-
> reinvite?
>=20
> If it comes in a reinvite with an offer, and the snapshot is required
> in
> the answer, then the shapshot is required to be consistent with the
SDP
> in the offer. That could be a problem. I suppose we could draw up a
> bunch of constraints to prevent that, but its extra work, so why
> bother?
> If we don't require the snapshot in the response, then we avoid that -
> the src can wait until it can send reinvite with suitable offer.
>=20
> If snapshot request comes in a reinvite without offer, then there are
> no
> signaling difficulties with returning the snapshot in the response
with
> the offer. And I am fine with *allowing* that, but not requiring it.
>=20
> If the snapshot request comes in a reinvite without offer, and the
> response does NOT contain the shapshot, then probably it contains an
> offer same as last time, and the answer can as well. At that point,
> what
> sort of race are you concerned about? It seems the only one would be
if
> the SRS send *another* reinvite before the snapshot is received. But I
> see no new problem with that.
>=20
> The complexities I see are:
>=20
> - SRS sends reinvite with offer that is different from last agreed,
>    regardless of whether this contains a snapshot request or not.
>=20
> - SRS sends reinvite without offer, the offer in the response
>    differs from what was last agreed, and does not contain metadata.
>=20
> - SRC sends reinvite with offer different from last agreed,
>    and without metadata.
>=20
> - SRC sends reinvite without offer, with or without metadata.
>=20
> We might want to lay down some rules, such as that the snapshot
request
> must never contain an offer, or must always contain an offer identical
> to what was last agreed. But even that may take some consideration -
> some SBCs might take an offerless invite and fill in an offer. :-(
>=20
> > Apart from
> > latency, Could you please specify any advantage in two transaction
> approach.
>=20
> Potentially easier implementation for the SRC.
>=20
> > Also, two transactions makes me to feel like invoking action in SRC
> as the
> > Second transaction is triggered based on the first UPDATE/RE-INVITE
> with
> > Snapshot request.
>=20
> Yes. What is wrong with that?
> We do such things all the time. (E.g. SUBSCRIBE triggers NOTIFY.)
>=20
> > Let us get others opinion for the need of two separate transaction
> > (request/response) in SRC.
>=20
> I'm arguing to allow flexibility on the part of the SRC.
> If you are building an SRC, and you want to implement it to always
> return the snapshot in the response, then you can build it that way.
>=20
> 	Thanks,
> 	Paul
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From pravindran@sonusnet.com  Wed Nov 16 22:25:03 2011
Return-Path: <pravindran@sonusnet.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 4DA6C11E811E for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 22:25:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.283
X-Spam-Level: 
X-Spam-Status: No, score=-2.283 tagged_above=-999 required=5 tests=[AWL=-0.284, BAYES_00=-2.599, J_CHICKENPOX_55=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O11TLbwjVrfA for <siprec@ietfa.amsl.com>; Wed, 16 Nov 2011 22:24:58 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 19CC211E811F for <siprec@ietf.org>; Wed, 16 Nov 2011 22:24:57 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pAH6PWbv014337;  Thu, 17 Nov 2011 01:25:32 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Nov 2011 01:24:28 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Nov 2011 11:54:42 +0530
Received: from INBA-HUB02.sonusnet.com (10.70.51.87) by inba-hub01.sonusnet.com (10.70.51.86) with Microsoft SMTP Server (TLS) id 14.1.339.1; Thu, 17 Nov 2011 11:54:42 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0339.001; Thu, 17 Nov 2011 11:54:42 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [siprec] Comment on draft-ietf-siprec-protocol-02
Thread-Index: AcyjUIJcmV7uSjkHQUeI2ksxqXriXf//qouA//9eKVCAAfdcAIAAFlAAgAAC/YD//6LIIIAAYtkA//+jbqAAEGLoAAAATaOAAAF4G4AAAMvZgP//m1vw//+N/YD//xM3gP/9x/qg//vjcAD/933oAP/unqmA/90eCAD/uUN9UA==
Date: Thu, 17 Nov 2011 06:24:41 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE95B6@inba-mail01.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C01CE8662@inba-mail01.sonusnet.com><AB720611-E545-4B5B-8B94-322269C6553E@gmail.com> <35BCE99A477D6A4986FB2216D8CF2CFD086526BF@XMB-BGL-417.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C21@inba-mail01.sonusnet.com> <C58C5AB6-83EA-4F9B-8832-771F8386D455@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8C8B@inba-mail01.sonusnet.com> <95285409-38D2-4353-B5BD-6280A50AE2C4@gmail.com> <3740ABE1-238E-4F6E-A8A1-072C977AF2AE@gmail.com> <101C6067BEC68246B0C3F6843BCCC1E311FAB6638A@MCHP058A.global-ad.net> <770C5303-340F-4724-BD38-AC099FD9CA86@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE8F8A@inba-mail01.sonusnet.com> <A927EDA9-9856-4608-82BA-7621B9BE661D@gmail.com> <4EC36F1F.4000605@alum.mit.edu> <387F9047F55E8C42850AD6B3A7A03C6C01CE8FE8@inba-mail01.sonusnet.com> <4EC37852.60809@alum.mit.edu> <B81B0AE1-E84E-4159-90A5-4C87766E7317@gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE92FF@inba-mail01.sonusnet.com> <4EC41DEC.8060707@alum.mit.edu>
In-Reply-To: <4EC41DEC.8060707@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Nov 2011 06:24:42.0775 (UTC) FILETIME=[97CCB270:01CCA4F1]
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
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: Thu, 17 Nov 2011 06:25:03 -0000

Paul,

Please read inline.

Thanks
Partha

>-----Original Message-----
>From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>Sent: Thursday, November 17, 2011 4:33 AM
>To: Ravindran, Parthasarathi
>Cc: Leon Portman; siprec@ietf.org
>Subject: Re: [siprec] Comment on draft-ietf-siprec-protocol-02
>
>On 11/16/11 10:07 PM, Ravindran, Parthasarathi wrote:
>> Paul/Leon,
>>
>> We have discussed about decoupling of "metadata"&  "SDP" for SRS but
>> here it is SRC. Even in case of SRS, we agreed upon that there is no
>> need to defer the responses for metadata processing and
>> RE-INVITE/UPDATE is agreed upon based on this assumption. Snapshot
>> request may be used as deferred mechanism to correct metadata.
>
>I think that is consistent with what I recall. The point was that the
>SRS need not process the metadata before replying.
>
>> SRC implementation shall maintain "metadata"&  "SDP" in different
>> layer but the latency problem is solved by sending "100 trying" for
>> RE-INVITE in SRC.
>
>Yes, you *can* extend the reinvite transaction by sending provisionals.
>But it still gets ugly then in terms of interaction between layers.
>
<partha> I doubt because SRC is a real-time and the query is about its call
Control state. </partha>

>> The problem with two different transaction (request/response) is that
>> the possibility of a offer/answer race condition is higher.
>
>Why is that? What sort of race condition? Its of course always possible
>for reinvite to be launched simultaneously by both src and srs,
>resulting in o/a glare. But that is independent of this question.

<partha> ISTM, we are defining the protocol which may often end-up in
Glare which shall be avoided </partha>

 (But
>it does remind me that we probably ought to discuss somewhere the
>implications of a glare case on metadata processing, though in some
>sense it is obvious.)
>
<partha> It will be good to discuss and define in the protocol document=20
</partha>


>Are you assuming the snapshot request always comes in an offerless-
>reinvite?
>
<partha> No </partha>

>If it comes in a reinvite with an offer, and the snapshot is required in
>the answer, then the shapshot is required to be consistent with the SDP
>in the offer. That could be a problem.=20

<partha> It should not be a problem because SRS knows what it wants at this
Stage and there is no provide extra information if SRS is not interested.=20
In case SRS asks for audio only, SRC shall send audio as a negotiation
Even though earlier it was negotiated for audio+video negotiation</partha>

I suppose we could draw up a
>bunch of constraints to prevent that, but its extra work, so why bother?
>If we don't require the snapshot in the response, then we avoid that -
>the src can wait until it can send reinvite with suitable offer.
>
>If snapshot request comes in a reinvite without offer, then there are no
>signaling difficulties with returning the snapshot in the response with
>the offer. And I am fine with *allowing* that, but not requiring it.
>
<partha> Hope we have agreement here </partha>

>If the snapshot request comes in a reinvite without offer, and the
>response does NOT contain the shapshot, then probably it contains an
>offer same as last time, and the answer can as well. At that point, what
>sort of race are you concerned about? It seems the only one would be if
>the SRS send *another* reinvite before the snapshot is received.=20
=09
<partha> IMO, it is problem introduced due to this design of capability
Request in one transaction and capability response in another transaction.=
=20
</partha>

But I
>see no new problem with that.
>
=20
>The complexities I see are:
>
>- SRS sends reinvite with offer that is different from last agreed,
>   regardless of whether this contains a snapshot request or not.
</partha> It is fine and SRS has the way to change=20
</partha>
>
>- SRS sends reinvite without offer, the offer in the response
>   differs from what was last agreed, and does not contain metadata.
>
>- SRC sends reinvite with offer different from last agreed,
>   and without metadata.
>
<partha> Here, atleast there is a need to indication from SRC that=20
Metadata will be sent later. Something like 202 OK response or some
Message body indication </partha>

>- SRC sends reinvite without offer, with or without metadata.
>
>We might want to lay down some rules, such as that the snapshot request
>must never contain an offer, or must always contain an offer identical
>to what was last agreed.

<partha> I agreed that it is bad and it is not required as well </partha>

 But even that may take some consideration -
>some SBCs might take an offerless invite and fill in an offer. :-(
>
<partha> It is a messy SBC feature ;-) </partha>

>> Apart from
>> latency, Could you please specify any advantage in two transaction
>approach.
>
>Potentially easier implementation for the SRC.
>
>> Also, two transactions makes me to feel like invoking action in SRC as
>> the Second transaction is triggered based on the first
>> UPDATE/RE-INVITE with Snapshot request.
>
</partha> Howz the relationship between these two transaction are set.=20
</partha>

>Yes. What is wrong with that?
>We do such things all the time. (E.g. SUBSCRIBE triggers NOTIFY.)
>
<partha> SUB/NOT framework clearly specify how NOTIFY shall=20
be created using the new transaction for SUBSCRIBE whereas in SIPREC,=20
we need to do using REINVITE/UPDATE for separate transaction. I'm fine
in case we are defining such framework and it is not clear in the=20
current specification. </partha>  =20

>> Let us get others opinion for the need of two separate transaction
>> (request/response) in SRC.
>
>I'm arguing to allow flexibility on the part of the SRC.
>If you are building an SRC, and you want to implement it to always
>return the snapshot in the response, then you can build it that way.
>
>	Thanks,
>	Paul

From john.r.elwell@gmail.com  Thu Nov 17 01:15:01 2011
Return-Path: <john.r.elwell@gmail.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 0AB7821F9B3D for <siprec@ietfa.amsl.com>; Thu, 17 Nov 2011 01:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.182
X-Spam-Level: 
X-Spam-Status: No, score=-2.182 tagged_above=-999 required=5 tests=[AWL=-0.998, BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxZZp3uoOxhs for <siprec@ietfa.amsl.com>; Thu, 17 Nov 2011 01:15:00 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id D788421F9AF2 for <siprec@ietf.org>; Thu, 17 Nov 2011 01:14:59 -0800 (PST)
Received: by wyf28 with SMTP id 28so1924853wyf.31 for <siprec@ietf.org>; Thu, 17 Nov 2011 01:14:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :content-transfer-encoding:x-priority:x-msmail-priority:x-mailer :x-mimeole; bh=7dCDqf/XuQELbAJfdVbtlRIKCWCdczJFCZtTQOLG0O0=; b=tObZbuLo0x2GHsKEVraoAc4ceuCuW9GOQwb7HF04WZxaSY0VUmWt8DMafKB3vBRpjp HvaOb3FXxnEYH78wm/khczeXDcfTrswD5A0AAbN7ocRIkbfn9gpu8C148iISERJKgilY B9peuXxY1mV1PHAC5pT5HCpLhxWf2NWUnRmgM=
Received: by 10.227.203.148 with SMTP id fi20mr11026963wbb.27.1321521298981; Thu, 17 Nov 2011 01:14:58 -0800 (PST)
Received: from JohnsComputer (cpc1-clif8-2-0-cust418.12-4.cable.virginmedia.com. [82.25.209.163]) by mx.google.com with ESMTPS id eu16sm35996317wbb.7.2011.11.17.01.14.57 (version=SSLv3 cipher=OTHER); Thu, 17 Nov 2011 01:14:58 -0800 (PST)
Message-ID: <B20359D2613947B69891A631964F8457@JohnsComputer>
From: "John Elwell" <john.r.elwell@gmail.com>
To: <siprec@ietf.org>
Date: Thu, 17 Nov 2011 09:15:08 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Subject: [siprec] Transport of snapshot request
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: Thu, 17 Nov 2011 09:15:01 -0000

There has been a long thread discussing the SIP messages for snapshot 
requests.

First, I see no reason to tie the snapshot request and the metadata 
transmission to the same transaction (request/response). If they are tied 
together, this imposes unncessary time and architectural constraints on the 
SRC. I much prefer an approach similar to the subscribe/notify approach of 
RFC 3265 - use different transactions. I am rather unsympathetic to 
allowing, as an option, metadata transmission in a response. Apart from the 
timing and arcchitectural concerns, there is no means of responding to a 
response if anything is wrong. Keep it simple, and allow metadata 
transmission only in requests, as in NOTIFY.

Second, I think it is an SRC decision whether it needs a further 
offer-answer exchange. When sending the request containing the metadata, the 
SRC must ensure that any references to media description labels are 
consistent with the last SDP sent by the SRC - if not, the SRC can initiate 
a further offer-answer exchange at the same time as the metadata 
transmission.

Perhaps it is my imagination, but I thought we had on the table at one time 
the notion of:
- SRS sends snapshot request in an UPDATE request.
- SRC sends medata in an UPDATE request (with offer if it needs to change 
SDP, otherwise without).

I have lost track of how we came to diverge from this simple model.

John


From leon.portman@gmail.com  Thu Nov 17 01:46:36 2011
Return-Path: <leon.portman@gmail.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 74F2F21F9B55 for <siprec@ietfa.amsl.com>; Thu, 17 Nov 2011 01:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level: 
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fmkeo3V7hw4O for <siprec@ietfa.amsl.com>; Thu, 17 Nov 2011 01:46:36 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id DD7FC21F9B37 for <siprec@ietf.org>; Thu, 17 Nov 2011 01:46:35 -0800 (PST)
Received: by ywt34 with SMTP id 34so945064ywt.31 for <siprec@ietf.org>; Thu, 17 Nov 2011 01:46:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=D3BrceX3xjaJGoDs2l1/zsXKdGNIFk/oLvZ9QFuqD/E=; b=ShQ0/mh89qZXt8qKzIIxD34RUbgtHigdvF0E2MzC0xKJ0pxGp3EnrNv9Z/uWYoqLv6 kW3W+4CYgMP7gPEg2avh/I4Bj2l71yyBmgVSOtG9XPcDG9/J7rfzdPaOcWFaoXCrgELX 4gM3WCktAS/FAmvFTNR+ZbMXmPjqpmpdzCSZw=
Received: by 10.236.114.195 with SMTP id c43mr7788080yhh.12.1321523195543; Thu, 17 Nov 2011 01:46:35 -0800 (PST)
Received: from ?IPv6:2001:df8::16:d61:d786:e454:2b04? ([2001:df8:0:16:d61:d786:e454:2b04]) by mx.google.com with ESMTPS id 11sm9004379anz.20.2011.11.17.01.46.33 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Nov 2011 01:46:34 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Leon Portman <leon.portman@gmail.com>
X-Priority: 3
In-Reply-To: <B20359D2613947B69891A631964F8457@JohnsComputer>
Date: Thu, 17 Nov 2011 17:46:37 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com>
References: <B20359D2613947B69891A631964F8457@JohnsComputer>
To: "John Elwell" <john.r.elwell@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: siprec@ietf.org
Subject: Re: [siprec] Transport of snapshot request
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: Thu, 17 Nov 2011 09:46:36 -0000

John, Nice to have you back on the list.

Actually discussion during IETF meeting was started to converge to =
similar as you describe below.

Regards

Leon

On Nov 17, 2011, at 5:15 PM, John Elwell wrote:

> There has been a long thread discussing the SIP messages for snapshot =
requests.
>=20
> First, I see no reason to tie the snapshot request and the metadata =
transmission to the same transaction (request/response). If they are =
tied together, this imposes unncessary time and architectural =
constraints on the SRC. I much prefer an approach similar to the =
subscribe/notify approach of RFC 3265 - use different transactions. I am =
rather unsympathetic to allowing, as an option, metadata transmission in =
a response. Apart from the timing and arcchitectural concerns, there is =
no means of responding to a response if anything is wrong. Keep it =
simple, and allow metadata transmission only in requests, as in NOTIFY.
>=20
> Second, I think it is an SRC decision whether it needs a further =
offer-answer exchange. When sending the request containing the metadata, =
the SRC must ensure that any references to media description labels are =
consistent with the last SDP sent by the SRC - if not, the SRC can =
initiate a further offer-answer exchange at the same time as the =
metadata transmission.
>=20
> Perhaps it is my imagination, but I thought we had on the table at one =
time the notion of:
> - SRS sends snapshot request in an UPDATE request.
> - SRC sends medata in an UPDATE request (with offer if it needs to =
change SDP, otherwise without).
>=20
> I have lost track of how we came to diverge from this simple model.
>=20
> John
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From ietf@meetecho.com  Tue Nov 22 02:21:02 2011
Return-Path: <ietf@meetecho.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 A871B21F8DA1 for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 02:21:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.45
X-Spam-Level: 
X-Spam-Status: No, score=-0.45 tagged_above=-999 required=5 tests=[AWL=0.269,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1REzhH3JS+Fp for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 02:20:59 -0800 (PST)
Received: from smtplq04.aruba.it (smtplq-out19.aruba.it [62.149.158.39]) by ietfa.amsl.com (Postfix) with SMTP id 65E0C21F8D8A for <siprec@ietf.org>; Tue, 22 Nov 2011 02:20:57 -0800 (PST)
Received: (qmail 13286 invoked by uid 89); 22 Nov 2011 10:20:56 -0000
Received: from unknown (HELO smtp1.aruba.it) (62.149.158.221) by smtplq04.aruba.it with SMTP; 22 Nov 2011 10:20:56 -0000
Received: (qmail 20563 invoked by uid 89); 22 Nov 2011 10:20:56 -0000
Received: from unknown (HELO ?143.225.229.189?) (ietf@meetecho.com@143.225.229.189) by smtp1.ad.aruba.it with SMTP; 22 Nov 2011 10:20:56 -0000
Message-ID: <4ECB7777.9020402@meetecho.com>
Date: Tue, 22 Nov 2011 11:20:39 +0100
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtp1.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N
Subject: [siprec] SIPREC session recording available
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: Tue, 22 Nov 2011 10:21:02 -0000

Dear all,

the full recording (synchronized video, audio, slides and jabber room)
of SIPREC session at IETF-82 is available.

You can watch it by either clicking the proper link on the remote 
participation page 
(http://www.ietf.org/meeting/82/remote-participation.html#Meetecho), or 
by directly accessing the following URL:
http://www.meetecho.com/ietf82/recordings#SIPREC

For the chair(s): please feel free to put the link to the recording in 
the minutes, if you think this might be useful.

In case of problems with the playout, just drop an e-mail to
ietf-support@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From andrew.hutton@siemens-enterprise.com  Tue Nov 22 02:29:22 2011
Return-Path: <andrew.hutton@siemens-enterprise.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 7FE0421F8D46 for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 02:29:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L35C90AYBDqC for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 02:29:22 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id C513821F8D20 for <siprec@ietf.org>; Tue, 22 Nov 2011 02:29:21 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id AAE151EB8474 for <siprec@ietf.org>; Tue, 22 Nov 2011 11:29:18 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 22 Nov 2011 11:29:18 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 22 Nov 2011 11:29:44 +0100
Thread-Topic: SIPREC Interim
Thread-Index: AcypAabEIfGw5XswTvCtMJNzW+X9cg==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAC502DD@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FAC502DDMCHP058Agloba_"
MIME-Version: 1.0
Subject: [siprec] SIPREC Interim
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: Tue, 22 Nov 2011 10:29:22 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAC502DDMCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

After the SIPREC meeting at IETF82 a few people expressed an interest in ha=
ving a face to face SIPREC interim meeting probably in January or February.

You might have noticed that both RTCWEB and CLUE working groups are plannin=
g to hold face to face interims and if these happen it would seem to make s=
ense to try and co-locate on the meetings.

Please could you let me know if you think you would attend such a face to f=
ace interim?

Would co-locating such a SIPREC meeting with RTCWEB/CLUE meetings be a good=
 idea?

I will setup a doodle poll depending on the feedback I get.

Regards
Andy (Co-Chair).


--_000_101C6067BEC68246B0C3F6843BCCC1E311FAC502DDMCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri, sans-serif" size=3D"2">
<div>Hi All,</div>
<div>&nbsp;</div>
<div>After the SIPREC meeting at IETF82 a few people expressed an interest =
in having a face to face SIPREC interim meeting probably in January or Febr=
uary.</div>
<div>&nbsp;</div>
<div>You might have noticed that both RTCWEB and CLUE working groups are pl=
anning to hold face to face interims and if these happen it would seem to m=
ake sense to try and co-locate on the meetings.</div>
<div>&nbsp;</div>
<div>Please could you let me know if you think you would attend such a face=
 to face interim?</div>
<div>&nbsp;</div>
<div>Would co-locating such a SIPREC meeting with RTCWEB/CLUE meetings be a=
 good idea?</div>
<div>&nbsp;</div>
<div>I will setup a doodle poll depending on the feedback I get.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Andy (Co-Chair).</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAC502DDMCHP058Agloba_--

From leon.portman@gmail.com  Tue Nov 22 03:30:30 2011
Return-Path: <leon.portman@gmail.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 C130621F8DB8 for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 03:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.419
X-Spam-Level: 
X-Spam-Status: No, score=-3.419 tagged_above=-999 required=5 tests=[AWL=0.180,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPHMEilWKFd1 for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 03:30:30 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id EFD1221F8DAE for <siprec@ietf.org>; Tue, 22 Nov 2011 03:30:29 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so101651vcb.31 for <siprec@ietf.org>; Tue, 22 Nov 2011 03:30:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=q1idmCres9geIeOaF3WmGQsFdxje1GF0lr+E0TAxJ94=; b=tcMCdLZOnIoSj+bBf8FOhLVyXdjoUsX/aDcbncjgiKmA5mDOd7eq5dKBsJfBeMpbUE bTj7ApEvpUP518xAuiDVyAkpJWk2m50cffdgS8oPfPcaYx9Zw/WjzQ599icHnqEQ4hy4 oVyZYGvvQ/H6teB8BhKtkDfo1O+rsrCZUF/NI=
MIME-Version: 1.0
Received: by 10.52.29.207 with SMTP id m15mr19755678vdh.100.1321961429243; Tue, 22 Nov 2011 03:30:29 -0800 (PST)
Received: by 10.220.188.13 with HTTP; Tue, 22 Nov 2011 03:30:29 -0800 (PST)
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAC502DD@MCHP058A.global-ad.net>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAC502DD@MCHP058A.global-ad.net>
Date: Tue, 22 Nov 2011 13:30:29 +0200
Message-ID: <CAL0XzEL96uZ8oY=TZGOfr1Ez9tvC8=6GwAvNbU7+sTUKwZWKCw@mail.gmail.com>
From: Leon Portman <leon.portman@gmail.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>,  "siprec@ietf.org" <siprec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [siprec] SIPREC Interim
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: Tue, 22 Nov 2011 11:30:30 -0000

I think it is a good idea.

Leon

On 11/22/11, Hutton, Andrew <andrew.hutton@siemens-enterprise.com> wrote:
> Hi All,
>
> After the SIPREC meeting at IETF82 a few people expressed an interest in
> having a face to face SIPREC interim meeting probably in January or
> February.
>
> You might have noticed that both RTCWEB and CLUE working groups are planning
> to hold face to face interims and if these happen it would seem to make
> sense to try and co-locate on the meetings.
>
> Please could you let me know if you think you would attend such a face to
> face interim?
>
> Would co-locating such a SIPREC meeting with RTCWEB/CLUE meetings be a good
> idea?
>
> I will setup a doodle poll depending on the feedback I get.
>
> Regards
> Andy (Co-Chair).
>
>

-- 
Sent from my mobile device

From HKaplan@acmepacket.com  Tue Nov 22 10:12:39 2011
Return-Path: <HKaplan@acmepacket.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 3342921F8B9A for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 10:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzGtCuHJvCca for <siprec@ietfa.amsl.com>; Tue, 22 Nov 2011 10:12:38 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2825821F8B94 for <siprec@ietf.org>; Tue, 22 Nov 2011 10:12:37 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 22 Nov 2011 13:12:36 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Tue, 22 Nov 2011 13:12:36 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Andrew Hutton <andrew.hutton@siemens-enterprise.com>
Thread-Topic: [siprec] SIPREC Interim
Thread-Index: AcypAabEIfGw5XswTvCtMJNzW+X9cg==
Date: Tue, 22 Nov 2011 18:12:35 +0000
Message-ID: <92A790DD-5894-4D56-8AF7-9D83892A21E9@acmepacket.com>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAC502DD@MCHP058A.global-ad.net> <CAL0XzEL96uZ8oY=TZGOfr1Ez9tvC8=6GwAvNbU7+sTUKwZWKCw@mail.gmail.com>
In-Reply-To: <CAL0XzEL96uZ8oY=TZGOfr1Ez9tvC8=6GwAvNbU7+sTUKwZWKCw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3EDFF1E9641EA441B3A6916EAA86AEEE@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "siprec@ietf.org Recording\) WG" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC Interim
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: Tue, 22 Nov 2011 18:12:39 -0000

+1

On Nov 22, 2011, at 6:30 AM, Leon Portman wrote:

> I think it is a good idea.
>=20
> Leon
>=20
> On 11/22/11, Hutton, Andrew <andrew.hutton@siemens-enterprise.com> wrote:
>> Hi All,
>>=20
>> After the SIPREC meeting at IETF82 a few people expressed an interest in
>> having a face to face SIPREC interim meeting probably in January or
>> February.
>>=20
>> You might have noticed that both RTCWEB and CLUE working groups are plan=
ning
>> to hold face to face interims and if these happen it would seem to make
>> sense to try and co-locate on the meetings.
>>=20
>> Please could you let me know if you think you would attend such a face t=
o
>> face interim?
>>=20
>> Would co-locating such a SIPREC meeting with RTCWEB/CLUE meetings be a g=
ood
>> idea?
>>=20
>> I will setup a doodle poll depending on the feedback I get.
>>=20
>> Regards
>> Andy (Co-Chair).
>>=20
>>=20
>=20
> --=20
> Sent from my mobile device
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From bwinslow@acmepacket.com  Wed Nov 23 08:52:45 2011
Return-Path: <bwinslow@acmepacket.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 EB31111E80A3 for <siprec@ietfa.amsl.com>; Wed, 23 Nov 2011 08:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boLADQX7Qj6x for <siprec@ietfa.amsl.com>; Wed, 23 Nov 2011 08:52:45 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 183C311E807F for <siprec@ietf.org>; Wed, 23 Nov 2011 08:52:44 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 23 Nov 2011 11:52:41 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 23 Nov 2011 11:52:41 -0500
From: Brad Winslow <bwinslow@acmepacket.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Transport of snapshot request
Thread-Index: AQHMpQlkT9D4yCyZxUusX9fhVSBFK5WxJVeAgAmOlNA=
Date: Wed, 23 Nov 2011 16:52:41 +0000
Message-ID: <622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com>
References: <B20359D2613947B69891A631964F8457@JohnsComputer> <6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com>
In-Reply-To: <6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Subject: Re: [siprec] Transport of snapshot request
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, 23 Nov 2011 16:52:46 -0000

Hi Folks,

In the situation where the SRS needs a metadata update, it most likely will=
 need an SDP update, as there is no guarantee the metadata-only update woul=
d be consistent with the current SDP label attributes of the SRS, aren't we=
 asking for trouble if we allow a metadata-only update?  If we decide on a =
full update, metadata + SDP, should we settle on UPDATE or INVITE to transm=
it the update from SRC to SRS?

As an aside, there is an expectation that the SRC behaves as a SIP UA, in t=
his case it should be able to respond to an offer-less re-INVITE from the S=
RS and provide metadata and SDP in the response.

Finally, if the SRS receives an INVITE for a new recording session, should =
we have an error code response which indicates the SRS is not interested in=
 recording the session, not as a failure status, just as a status to termin=
ate the recording.  This presupposes the SRS may make policy decisions for =
recording.

Thanks in advance for your thoughts,
Brad

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Leon Portman
Sent: Thursday, November 17, 2011 4:47 AM
To: John Elwell
Cc: siprec@ietf.org
Subject: Re: [siprec] Transport of snapshot request

John, Nice to have you back on the list.

Actually discussion during IETF meeting was started to converge to similar =
as you describe below.

Regards

Leon

On Nov 17, 2011, at 5:15 PM, John Elwell wrote:

> There has been a long thread discussing the SIP messages for snapshot req=
uests.
>=20
> First, I see no reason to tie the snapshot request and the metadata trans=
mission to the same transaction (request/response). If they are tied togeth=
er, this imposes unncessary time and architectural constraints on the SRC. =
I much prefer an approach similar to the subscribe/notify approach of RFC 3=
265 - use different transactions. I am rather unsympathetic to allowing, as=
 an option, metadata transmission in a response. Apart from the timing and =
arcchitectural concerns, there is no means of responding to a response if a=
nything is wrong. Keep it simple, and allow metadata transmission only in r=
equests, as in NOTIFY.
>=20
> Second, I think it is an SRC decision whether it needs a further offer-an=
swer exchange. When sending the request containing the metadata, the SRC mu=
st ensure that any references to media description labels are consistent wi=
th the last SDP sent by the SRC - if not, the SRC can initiate a further of=
fer-answer exchange at the same time as the metadata transmission.
>=20
> Perhaps it is my imagination, but I thought we had on the table at one ti=
me the notion of:
> - SRS sends snapshot request in an UPDATE request.
> - SRC sends medata in an UPDATE request (with offer if it needs to change=
 SDP, otherwise without).
>=20
> I have lost track of how we came to diverge from this simple model.
>=20
> John
>=20
> _______________________________________________
> 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

From pkyzivat@alum.mit.edu  Wed Nov 23 10:43:36 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 4004B21F8B0A for <siprec@ietfa.amsl.com>; Wed, 23 Nov 2011 10:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level: 
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sKTBUmABnU59 for <siprec@ietfa.amsl.com>; Wed, 23 Nov 2011 10:43:35 -0800 (PST)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id 1B00621F8B06 for <siprec@ietf.org>; Wed, 23 Nov 2011 10:43:35 -0800 (PST)
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta01.westchester.pa.mail.comcast.net with comcast id 0iVH1i0030cZkys51ijbWt; Wed, 23 Nov 2011 18:43:35 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta10.westchester.pa.mail.comcast.net with comcast id 0ijb1i00607duvL3WijbXd; Wed, 23 Nov 2011 18:43:35 +0000
Message-ID: <4ECD3ED9.20404@alum.mit.edu>
Date: Thu, 24 Nov 2011 02:43:37 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <101C6067BEC68246B0C3F6843BCCC1E311FAC502DD@MCHP058A.global-ad.net> <CAL0XzEL96uZ8oY=TZGOfr1Ez9tvC8=6GwAvNbU7+sTUKwZWKCw@mail.gmail.com>
In-Reply-To: <CAL0XzEL96uZ8oY=TZGOfr1Ez9tvC8=6GwAvNbU7+sTUKwZWKCw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] SIPREC Interim
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, 23 Nov 2011 18:43:36 -0000

It could be useful, though I think we can also make good progress by 
email and teleconference.

I can attend if and only if its in the boston area.

	Thanks,
	Paul

On 11/22/11 7:30 PM, Leon Portman wrote:
> I think it is a good idea.
>
> Leon
>
> On 11/22/11, Hutton, Andrew<andrew.hutton@siemens-enterprise.com>  wrote:
>> Hi All,
>>
>> After the SIPREC meeting at IETF82 a few people expressed an interest in
>> having a face to face SIPREC interim meeting probably in January or
>> February.
>>
>> You might have noticed that both RTCWEB and CLUE working groups are planning
>> to hold face to face interims and if these happen it would seem to make
>> sense to try and co-locate on the meetings.
>>
>> Please could you let me know if you think you would attend such a face to
>> face interim?
>>
>> Would co-locating such a SIPREC meeting with RTCWEB/CLUE meetings be a good
>> idea?
>>
>> I will setup a doodle poll depending on the feedback I get.
>>
>> Regards
>> Andy (Co-Chair).
>>
>>
>


From eckelcu@cisco.com  Sat Nov 26 13:02:23 2011
Return-Path: <eckelcu@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 CD7CA21F8C06 for <siprec@ietfa.amsl.com>; Sat, 26 Nov 2011 13:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.261
X-Spam-Level: 
X-Spam-Status: No, score=-6.261 tagged_above=-999 required=5 tests=[AWL=0.338,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDuc-7Um0RKs for <siprec@ietfa.amsl.com>; Sat, 26 Nov 2011 13:02:23 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 3C74621F8BF6 for <siprec@ietf.org>; Sat, 26 Nov 2011 13:02:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1275; q=dns/txt; s=iport; t=1322341343; x=1323550943; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=zdFPDlwOl9GOpoDldegy72N+mp6JxqeMSaygUKdSrSA=; b=StvyNEjpNyvErxMk0EcGEMUBsdgJ5SJhe9z9jLnpgiYJVarSfdHOVUjt A9mIvjsFFXFsr/tBzhKDbIgOGE6RU0IVm0xIXhIpi5raaRWex/KjY/w8L a/eLkkd4Y5XNKeVpUIwrr8h1DfATzYfEKMwOvPaaFeVjqoHmPaM/4+DPT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIAALpT0U6rRDoG/2dsb2JhbABEmlCQMIEFgXIBAQEEEgEdCksEAgEIEQQBAQsGFwEGAUUJCAEBBAESCBqfTAGdTYl/YwSIIZ5V
X-IronPort-AV: E=Sophos;i="4.69,576,1315180800"; d="scan'208";a="16346606"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 26 Nov 2011 21:02:11 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAQL2BUE019097; Sat, 26 Nov 2011 21:02:11 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Nov 2011 13:02:11 -0800
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: Sat, 26 Nov 2011 13:02:11 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05D81250@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAC502DD@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] SIPREC Interim
Thread-Index: AcypAabEIfGw5XswTvCtMJNzW+X9cgDQjE3w
References: <101C6067BEC68246B0C3F6843BCCC1E311FAC502DD@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 26 Nov 2011 21:02:11.0480 (UTC) FILETIME=[AA974980:01CCAC7E]
Subject: Re: [siprec] SIPREC Interim
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: Sat, 26 Nov 2011 21:02:23 -0000

Hi Andy,

I think it is a good idea to have an interim, and definitely a plus if
the meeting can be co-located with CLUE and/or RTCWEB. I do not think
the latter is as critical from a subject matter perspective as it is
from a time/travel perspective for folks hoping to participate in more
than one of the individual interims.

Cheers,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Hutton, Andrew
> Sent: Tuesday, November 22, 2011 2:30 AM
> To: siprec@ietf.org
> Subject: [siprec] SIPREC Interim
>=20
> Hi All,
>=20
> After the SIPREC meeting at IETF82 a few people expressed an interest
in having a face to face SIPREC
> interim meeting probably in January or February.
>=20
> You might have noticed that both RTCWEB and CLUE working groups are
planning to hold face to face
> interims and if these happen it would seem to make sense to try and
co-locate on the meetings.
>=20
> Please could you let me know if you think you would attend such a face
to face interim?
>=20
> Would co-locating such a SIPREC meeting with RTCWEB/CLUE meetings be a
good idea?
>=20
> I will setup a doodle poll depending on the feedback I get.
>=20
> Regards
> Andy (Co-Chair).
>=20

From pravindran@sonusnet.com  Wed Nov 30 16:47:10 2011
Return-Path: <pravindran@sonusnet.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 624311F0C36 for <siprec@ietfa.amsl.com>; Wed, 30 Nov 2011 16:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wTiQmNGTvJL for <siprec@ietfa.amsl.com>; Wed, 30 Nov 2011 16:47:08 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 783971F0C35 for <siprec@ietf.org>; Wed, 30 Nov 2011 16:47:08 -0800 (PST)
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com [10.128.32.156]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pB10ljc3027469;  Wed, 30 Nov 2011 19:47:45 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail06.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Nov 2011 19:47:06 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Dec 2011 06:17:29 +0530
Received: from INBA-MAIL02.sonusnet.com ([fe80::f8d4:7090:f632:bbbc]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Thu, 1 Dec 2011 06:17:29 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Brad Winslow <bwinslow@acmepacket.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Transport of snapshot request
Thread-Index: AQHMpQlw6ij0KenvQEu7JOWM9t6Oh5WwdVKAgAnlCICACaZFEA==
Date: Thu, 1 Dec 2011 00:47:28 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com>
References: <B20359D2613947B69891A631964F8457@JohnsComputer> <6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com> <622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com>
In-Reply-To: <622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Dec 2011 00:47:29.0846 (UTC) FILETIME=[CDD13D60:01CCAFC2]
Subject: Re: [siprec] Transport of snapshot request
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: Thu, 01 Dec 2011 00:47:10 -0000

Hi all,

I agree with UPDATE without SDP based snapshot request in case there is=20
an agreement that SRS will never generate offer as there is no possibility
of offer-answer race condition based on snapshot request mechanism. So,
I'm interested in hearing everybody opinion on "no offer from SRS" stance
For SIPREC.=20

Brad/John,

Please read inline.

Thanks
Partha

>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>Of Brad Winslow
>Sent: Wednesday, November 23, 2011 10:23 PM
>To: siprec@ietf.org
>Subject: Re: [siprec] Transport of snapshot request
>
>Hi Folks,
>
>In the situation where the SRS needs a metadata update, it most likely
>will need an SDP update, as there is no guarantee the metadata-only
>update would be consistent with the current SDP label attributes of the
>SRS, aren't we asking for trouble if we allow a metadata-only update?
<partha> Snapshot request UPDATE without SDP from SRS is used to trigger
Metadata request in SRC using RE-INVITE or UPDATE method=20
</partha>

>If we decide on a full update, metadata + SDP, should we settle on
>UPDATE or INVITE to transmit the update from SRC to SRS?
<partha> We have common understanding here </partha>

>
>As an aside, there is an expectation that the SRC behaves as a SIP UA,
>in this case it should be able to respond to an offer-less re-INVITE
>from the SRS and provide metadata and SDP in the response.
>
<partha> offerless Re-INVITE with 100 + 200 response is currently considere=
d=20
as alternative Proposal to UPDATE without SDP snapshot request </partha>

>Finally, if the SRS receives an INVITE for a new recording session,
>should we have an error code response which indicates the SRS is not
>interested in recording the session, not as a failure status, just as a
>status to terminate the recording. =20

<partha> It will be negative response in case INVITE with require:siprec is=
=20
not accepted using 200 OK right? Do we need the new server negative 5xx=20
response code for this policy decision? </partha>
=20
This presupposes the SRS may make
>policy decisions for recording.
>
>Thanks in advance for your thoughts,
>Brad
>
>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>Of Leon Portman
>Sent: Thursday, November 17, 2011 4:47 AM
>To: John Elwell
>Cc: siprec@ietf.org
>Subject: Re: [siprec] Transport of snapshot request
>
>John, Nice to have you back on the list.
>
>Actually discussion during IETF meeting was started to converge to
>similar as you describe below.
>
>Regards
>
>Leon
>
>On Nov 17, 2011, at 5:15 PM, John Elwell wrote:
>
>> There has been a long thread discussing the SIP messages for snapshot
>requests.
>>
>> First, I see no reason to tie the snapshot request and the metadata
>transmission to the same transaction (request/response). If they are
>tied together, this imposes unnecessary time and architectural
>constraints on the SRC.=20

<partha> The model proposed is request/provisional response/response
Wherein RE-INVITE/100/200 trying shall be used wherein there is no
Immediate response to SRS. </partha>

I much prefer an approach similar to the
>subscribe/notify approach of RFC 3265 - use different transactions.

<partha> The downside of this approach is 4 SIP messages per every
Service. I'm seeing the middle ground of offerless RE-INVITE with
Provisional response (100) and final response wherein 3 messages are=20
Involved but there is no extra offer/answer race condition from SRS.=20

Having said that, in case it is confirmed that SRS will never offer
Then I'm fine with UPDATE based snapshot request </partha>

 I am
>rather unsympathetic to allowing, as an option, metadata transmission in
>a response. Apart from the timing and architectural concerns, there is
>no means of responding to a response if anything is wrong. Keep it
>simple, and allow metadata transmission only in requests, as in NOTIFY.
>>
>> Second, I think it is an SRC decision whether it needs a further
>offer-answer exchange. When sending the request containing the metadata,
>the SRC must ensure that any references to media description labels are
>consistent with the last SDP sent by the SRC - if not, the SRC can
>initiate a further offer-answer exchange at the same time as the
>metadata transmission.
>>
>> Perhaps it is my imagination, but I thought we had on the table at one
>time the notion of:
>> - SRS sends snapshot request in an UPDATE request.
>> - SRC sends medata in an UPDATE request (with offer if it needs to
>change SDP, otherwise without).
>>
>> I have lost track of how we came to diverge from this simple model.
>>
>> John
>>
>> _______________________________________________
>> 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

From pkyzivat@alum.mit.edu  Wed Nov 30 18:47:03 2011
Return-Path: <pkyzivat@alum.mit.edu>
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 6841F21F8B02 for <siprec@ietfa.amsl.com>; Wed, 30 Nov 2011 18:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level: 
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5rdnJTT4-fA for <siprec@ietfa.amsl.com>; Wed, 30 Nov 2011 18:47:02 -0800 (PST)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by ietfa.amsl.com (Postfix) with ESMTP id 6C36221F8AFF for <siprec@ietf.org>; Wed, 30 Nov 2011 18:47:01 -0800 (PST)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta07.westchester.pa.mail.comcast.net with comcast id 3efS1i0020xGWP857en1jd; Thu, 01 Dec 2011 02:47:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta12.westchester.pa.mail.comcast.net with comcast id 3en11i01107duvL3Yen1RC; Thu, 01 Dec 2011 02:47:01 +0000
Message-ID: <4ED6EAA3.6060708@alum.mit.edu>
Date: Thu, 01 Dec 2011 10:46:59 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <B20359D2613947B69891A631964F8457@JohnsComputer> <6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com> <622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Transport of snapshot request
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: Thu, 01 Dec 2011 02:47:03 -0000

On 12/1/11 8:47 AM, Ravindran, Parthasarathi wrote:
> Hi all,
>
> I agree with UPDATE without SDP based snapshot request in case there is
> an agreement that SRS will never generate offer as there is no possibility
> of offer-answer race condition based on snapshot request mechanism. So,
> I'm interested in hearing everybody opinion on "no offer from SRS" stance
> For SIPREC.

I don't see how it would ever make sense for the SRS to make an offer to 
the SRC, so I'm fine with declaring that invalid SRS behavior.

As far as a snapshot without SDP, I agree it is unlikely that a snapshot 
would not require an SDP update. But I see no reason to exclude it in 
the unlikely event that a case comes up when it is valid.

This would be a problem if a snapshot request was in an UPDATE without 
SDP and the snapshot was required to be in the reply. But as long as the 
SRC can wait and send the snapshot in a request it initiates, it can 
make any offer it needs to, or potentially it could do the snapshot in 
an UPDATE without SDP if no SDP was needed.

	Thanks,
	Paul

> Brad/John,
>
> Please read inline.
>
> Thanks
> Partha
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>> Of Brad Winslow
>> Sent: Wednesday, November 23, 2011 10:23 PM
>> To: siprec@ietf.org
>> Subject: Re: [siprec] Transport of snapshot request
>>
>> Hi Folks,
>>
>> In the situation where the SRS needs a metadata update, it most likely
>> will need an SDP update, as there is no guarantee the metadata-only
>> update would be consistent with the current SDP label attributes of the
>> SRS, aren't we asking for trouble if we allow a metadata-only update?
> <partha>  Snapshot request UPDATE without SDP from SRS is used to trigger
> Metadata request in SRC using RE-INVITE or UPDATE method
> </partha>
>
>> If we decide on a full update, metadata + SDP, should we settle on
>> UPDATE or INVITE to transmit the update from SRC to SRS?
> <partha>  We have common understanding here</partha>
>
>>
>> As an aside, there is an expectation that the SRC behaves as a SIP UA,
>> in this case it should be able to respond to an offer-less re-INVITE
>>from the SRS and provide metadata and SDP in the response.
>>
> <partha>  offerless Re-INVITE with 100 + 200 response is currently considered
> as alternative Proposal to UPDATE without SDP snapshot request</partha>
>
>> Finally, if the SRS receives an INVITE for a new recording session,
>> should we have an error code response which indicates the SRS is not
>> interested in recording the session, not as a failure status, just as a
>> status to terminate the recording.
>
> <partha>  It will be negative response in case INVITE with require:siprec is
> not accepted using 200 OK right? Do we need the new server negative 5xx
> response code for this policy decision?</partha>
>
> This presupposes the SRS may make
>> policy decisions for recording.
>>
>> Thanks in advance for your thoughts,
>> Brad
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>> Of Leon Portman
>> Sent: Thursday, November 17, 2011 4:47 AM
>> To: John Elwell
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Transport of snapshot request
>>
>> John, Nice to have you back on the list.
>>
>> Actually discussion during IETF meeting was started to converge to
>> similar as you describe below.
>>
>> Regards
>>
>> Leon
>>
>> On Nov 17, 2011, at 5:15 PM, John Elwell wrote:
>>
>>> There has been a long thread discussing the SIP messages for snapshot
>> requests.
>>>
>>> First, I see no reason to tie the snapshot request and the metadata
>> transmission to the same transaction (request/response). If they are
>> tied together, this imposes unnecessary time and architectural
>> constraints on the SRC.
>
> <partha>  The model proposed is request/provisional response/response
> Wherein RE-INVITE/100/200 trying shall be used wherein there is no
> Immediate response to SRS.</partha>
>
> I much prefer an approach similar to the
>> subscribe/notify approach of RFC 3265 - use different transactions.
>
> <partha>  The downside of this approach is 4 SIP messages per every
> Service. I'm seeing the middle ground of offerless RE-INVITE with
> Provisional response (100) and final response wherein 3 messages are
> Involved but there is no extra offer/answer race condition from SRS.
>
> Having said that, in case it is confirmed that SRS will never offer
> Then I'm fine with UPDATE based snapshot request</partha>
>
>   I am
>> rather unsympathetic to allowing, as an option, metadata transmission in
>> a response. Apart from the timing and architectural concerns, there is
>> no means of responding to a response if anything is wrong. Keep it
>> simple, and allow metadata transmission only in requests, as in NOTIFY.
>>>
>>> Second, I think it is an SRC decision whether it needs a further
>> offer-answer exchange. When sending the request containing the metadata,
>> the SRC must ensure that any references to media description labels are
>> consistent with the last SDP sent by the SRC - if not, the SRC can
>> initiate a further offer-answer exchange at the same time as the
>> metadata transmission.
>>>
>>> Perhaps it is my imagination, but I thought we had on the table at one
>> time the notion of:
>>> - SRS sends snapshot request in an UPDATE request.
>>> - SRC sends medata in an UPDATE request (with offer if it needs to
>> change SDP, otherwise without).
>>>
>>> I have lost track of how we came to diverge from this simple model.
>>>
>>> John
>>>
>>> _______________________________________________
>>> 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
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>

