Re: [dispatch] Session recording in SIP

[Roni Even <[e-mail]>]

Andy,
You have a term called communication system in the proposal
Can you clarify what it is? Is this the end points in the call is this some
type of a proxy, application aware middle box?

There is also a recorder in the proposal, is this a SIP UA or is it just a
RTP terminating device like a "media server" in which case this is similar
to mediactrl WG work


Roni Even

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf
Of Hutton, Andrew
Sent: Thursday, June 11, 2009 5:36 PM
To: Roni Even; Alan Johnston; Romascanu, Dan (Dan)
Cc: Leon Portman; [e-mail]; Jain, Rajnish; Hadriel Kaplan
Subject: Re: [dispatch] Session recording in SIP

Hi,

I am sure that there are aspects of session recording that could require
work in AVT but I don't see that this is the focus of this proposed work
item which I think is to define the SIP requirements and possible SIP
protocol extensions that might be needed. 

I find it harder to see how this relates to XCON.

Regards
Andy
 

>-----Original Message-----
>From: Roni Even [mailto:[e-mail]] 
>Sent: 11 June 2009 11:48
>To: Hutton, Andrew; 'Alan Johnston'; 'Romascanu, Dan (Dan)'
>Cc: 'Leon Portman'; [e-mail]; 'Jain,Rajnish'; 'Hadriel Kaplan'
>Subject: RE: [dispatch] Session recording in SIP
>
>Hi,
>I looked at the suggested text and this is why I think it can 
>be done in
>XCON and that there are AVT aspects
>
>The solution wants to record not only point to point calls 
>since call center
>scenarios include multipoint so it can be done in XCON instead 
>of forming a
>new WG . XCON is finishing its current charter and may get 
>this as a new
>charter.
>
>As for the media, if you want to record multimedia RTP streams 
>you need to
>be able to synchronize between the separate streams (done in 
>RTCP now), I
>think Jonathan made this comment. You may also need to address 
>the SRTP keys
>if you want to keep the information secure. There is some drafts on the
>topics currently in AVT. If not RTP is going to stored, you 
>need to address
>the storage format and require some transcoding capabilities 
>on the record
>server for audio and video unless you only want a G.711 
>solution. So if some
>other packetization is needed maybe this is also AVT work
>
>
>Roni Even
>
>-----Original Message-----
>From: Hutton, Andrew [mailto:[e-mail]] 
>Sent: Thursday, June 11, 2009 12:08 PM
>To: Roni Even; Alan Johnston; Romascanu, Dan (Dan)
>Cc: Leon Portman; [e-mail]; Jain,Rajnish; Hadriel Kaplan
>Subject: RE: [dispatch] Session recording in SIP
>
>Hi,
>
>I think that currently this discussion should continue to be in the
>dispatch WG as the current status seems to fit exactly the Dispatch
>charter.
>
>In my opinion it does not belong in AVT as it does not require any
>changes to media formats and I also don't think it belongs in 
>XCON as it
>really is not conferencing although I would agree it has some
>similarity.
>
>Regards
>Andy
> 
>
>>-----Original Message-----
>>From: [e-mail] 
>>[mailto:[e-mail]] On Behalf Of Roni Even
>>Sent: 10 June 2009 22:28
>>To: 'Alan Johnston'; 'Romascanu, Dan (Dan)'
>>Cc: 'Leon Portman'; [e-mail]; 'Jain,Rajnish'; 
>'Hadriel Kaplan'
>>Subject: Re: [dispatch] Session recording in SIP
>>
>>Hi,
>>I agree that this is an important work but I am not sure about 
>>a WG. This
>>may be done in XCON and AVT.
>>Note that the recording is not only for point to point call 
>>but at least for
>>three parties like in call center scenarios
>>
>>I also did not notice any mention of the playback part but it 
>>should also be
>>addressed
>>
>>Roni Even
>>
>>-----Original Message-----
>>From: [e-mail] 
>>[mailto:[e-mail]] On Behalf
>>Of Alan Johnston
>>Sent: Wednesday, June 10, 2009 4:42 PM
>>To: Romascanu, Dan (Dan)
>>Cc: Leon Portman; [e-mail]; Jain, Rajnish; Hadriel Kaplan
>>Subject: Re: [dispatch] Session recording in SIP
>>
>>This is important work to be done in RAI.  Key management for secure 
>>recording is an important component that needs to be addressed.
>>
>>draft-wing-sipping-srtp-key-04 addresses many of these topics.
>>
>>Thanks,
>>Alan
>>
>>
>>Romascanu, Dan (Dan) wrote:
>>> I believe that this is an important application, and I support doing
>>> work in this direction. 
>>>
>>> Three comments on the preliminary words: 
>>>
>>> 1. The requirement is for both signaling and media recording, right?
>>> Probably good to say it. 
>>> 2. Security and regulations on how the information is accessed and
>>> protected are of high importance. They would probably be 
>reflected in
>>> the requirements, but explicit wording in the future charter 
>>can help.
>>> 3. I suggest that we look at the IPFIX protocol as a 
>>possible technology
>>> to re-use
>>>
>>> Dan
>>>  
>>>
>>>   
>>>> -----Original Message-----
>>>> From: [e-mail] 
>>>> [mailto:[e-mail]] On Behalf Of Vijay K. Gurbani
>>>> Sent: Wednesday, June 10, 2009 12:02 AM
>>>> To: [e-mail]
>>>> Cc: Leon Portman; Jain,Rajnish; Hadriel Kaplan
>>>> Subject: [dispatch] Session recording in SIP
>>>>
>>>> Hi: I realize that the deadline for charter proposals was 
>>>> yesterday, but I hope that it is not too late to submit one more.
>>>>
>>>> A few interested people (Hadriel Kaplan, Dan Wing, Rajnish 
>>>> Jain, Leon Portman, Andrew Hutton and I) have been interested 
>>>> in RTP session recording in SIP.  The requirement draft will 
>>>> be released shortly.
>>>>
>>>> We would like to request agenda time in dispatch to propose 
>>>> the formation of a new working group to define protocol 
>>>> extensions and an architecture for RTP recording.
>>>>
>>>> Session recording in SIP
>>>> Mailing Lists: TBD
>>>> Chairs: TBD
>>>> Area Directorate: Real Time Applications (RAI)
>>>>
>>>> Purpose:
>>>>
>>>> Session recording is a critical operational requirement in 
>>>> many businesses, especially where voice is used as a medium 
>>>> for commerce and customer support. A prime example where 
>>>> voice is used for trade is the financial industry. The call 
>>>> recording requirements in this industry are quite stringent. 
>>>> The recorded calls are used for dispute resolution and 
>>>> regulatory compliance. Other businesses such as customer 
>>>> support call centers typically employ call recording for 
>>>> quality control or business analytics.
>>>>
>>>> Depending on the country and its regulatory requirements, 
>>>> financial trading floors typically must record all calls. The 
>>>> recorded media content must be an exact copy of the actual 
>>>> conversation (i.e.
>>>> clipping and loss of media are unacceptable).  Some 
>>>> deployments and regulations require that calls be aborted or 
>>>> rejected if the recording device is unavailable.
>>>>
>>>> This group will specify requirements for a SIP based protocol 
>>>> interface between a communications system and a recorder. The 
>>>> Communications System is responsible for establishing media 
>>>> sessions where the actual business is conducted. The Recorder 
>>>> is the sink of the recorded media.
>>>>
>>>> The recorded sessions can be of any kind such as voice, video 
>>>> and instant messaging. A recorded session is typically 
>>>> comprised of actual media content and the call metadata. The 
>>>> call metadata allows recording archives to be searched and 
>>>> filtered at a later time.
>>>> The conveyance of call metadata from the communications 
>>>> system to the recorder is outside the scope of this document.
>>>>
>>>> This group will only looks into active recording, where the 
>>>> recorded system purposefully streams media to a recording 
>>>> device. Passive recording, where a recording device detects 
>>>> media directly from the network, is outside the scope of this 
>>>> document. In addition, lawful intercept is outside the scope 
>>>> of the group.
>>>>
>>>> Proposed deliverables:
>>>>
>>>> 1) Requirements document;
>>>> 2) Solutions document, including reference architecture.
>>>>
>>>> Thanks,
>>>>
>>>> - vijay
>>>> --
>>>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 
>>>> Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
>>>> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
>>>> Web:   http://ect.bell-labs.com/who/vkg/
>>>> _______________________________________________
>>>> dispatch mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>>
>>>>     
>>> _______________________________________________
>>> dispatch mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>
>>>   
>>
>>_______________________________________________
>>dispatch mailing list
>>[e-mail]
>>https://www.ietf.org/mailman/listinfo/dispatch
>>
>>
>>_______________________________________________
>>dispatch mailing list
>>[e-mail]
>>https://www.ietf.org/mailman/listinfo/dispatch
>>
>
>
_______________________________________________
dispatch mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dispatch