[dispatch] Summary on Session Recording in SIP

Vijay Gurbani <vkg@alcatel-lucent.com> Mon, 22 June 2009 04:08 UTC

Message-ID: <4A3F03F6.6060505@alcatel-lucent.com>
Date: Sun, 21 Jun 2009 23:09:26 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: dispatch@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [dispatch] Summary on Session Recording in SIP
Precedence: list

All: Here is the summary of the Session Recording thread from June 9
to June 19, 2009.  If I misrepresented anything, please let me know.

There was a fair amount of discussion on where to conduct this
work.  In the end, it was decided to continue discussions on
dispatch, further decisions what to do -- new working group or
put this work in an existing working group -- will be decided
later.  Regardless of where the work is done, opinions were
expressed that the work is important that it should commence
in the IETF.

Need to be crisp about the purpose of this work: is it that users
record sessions to hear later, or sessions need to be recorded
because of some business needs?  Or both?  Is SRTP covered or
only RTP?

Solutions should cover:
  Always on recording
  Recording on demand
  Required recording
  Pause and resume recording
  Playback facilities and how they interact with recording
  Recording formats and protocols for controlling the stored recording.

A lot of discussion ensued on the specific architecture or
architectures that would be possible.  No decision was reached on
which specific architecture is good or bad, although various opinions
were expressed in support for each.

There are essentially four architectures to realize recording
services: two that discuss where the media stream is forked
out to the recorder -- at the UA or in a middlebox of some
sort are outlined here:
   http://www.ietf.org/mail-archive/web/dispatch/current/msg00226.html

The third architecture has both UAs sending media to a
recorder.  See:
     http://www.ietf.org/mail-archive/web/dispatch/current/msg00236.html

A fourth architecture that is a superset of the third one is at:
     http://www.ietf.org/mail-archive/web/dispatch/current/msg00256.html

- 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}
WWW:   http://ect.bell-labs.com/who/vkg

Re: [dispatch] Summary on Session Recording in SIP Spencer Dawkins
Re: [dispatch] Summary on Session Recording in SIP Vijay K. Gurbani
[dispatch] Summary on Session Recording in SIP Vijay Gurbani
Re: [dispatch] Summary on Session Recording in SIP Paul Kyzivat
Re: [dispatch] Summary on Session Recording in SIP Joel M. Halpern
Re: [dispatch] Summary on Session Recording in SIP Hutton, Andrew
Re: [dispatch] Summary on Session Recording in SIP Elwell, John
Re: [dispatch] Session Recording in SIP Jain, Rajnish
Re: [dispatch] Session Recording in SIP spromano
Re: [dispatch] Session Recording in SIP Doken, Serhad
Re: [dispatch] Session Recording in SIP Jain, Rajnish
Re: [dispatch] Session Recording in SIP Doken, Serhad
Re: [dispatch] Session Recording in SIP Jain, Rajnish
Re: [dispatch] Session Recording in SIP Doken, Serhad