[dispatch] Charter proposal: Session Recording Protocol
"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Mon, 21 September 2009 13:32 UTC
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id D5DDE3A63D3 for <dispatch@core3.amsl.com>;
Mon, 21 Sep 2009 06:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.162,
BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWElCtzJBoha for
<dispatch@core3.amsl.com>; Mon, 21 Sep 2009 06:32:40 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by
core3.amsl.com (Postfix) with ESMTP id 8339628C0E4 for <dispatch@ietf.org>;
Mon, 21 Sep 2009 06:32:40 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by
ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id n8LDXeXY012518
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for
<dispatch@ietf.org>; Mon, 21 Sep 2009 08:33:40 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by
umail.lucent.com (8.13.8/TPES) with ESMTP id n8LDXeZi001460 for
<dispatch@ietf.org>; Mon, 21 Sep 2009 08:33:40 -0500 (CDT)
Message-ID: <4AB780B4.3000601@alcatel-lucent.com>
Date: Mon, 21 Sep 2009 08:33:40 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "dispatch@ietf.org" <dispatch@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: [dispatch] Charter proposal: Session Recording Protocol
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>,
<mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>,
<mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2009 13:32:42 -0000
Hi: The following charter proposal is a continuation of the work presented on the same topic (SIP Session Recording) at the Stockholm IETF. Regards, The Session Recording Protocol (SRP) working group is chartered to define a SIP-based protocol for controlling a session (media) recorder. Session recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons. In others, calls may be recorded for quality control, business analytics, or consumer protection. Recording is typically done by sending a copy of the media to the recording devices. The working group will produce a specification for a protocol that will manage delivery of media from an end-point that originates media or that has access to it to a recording device. PBX and recording vendors today implement proprietary, incompatible mechanisms to facilitate recording. A standard protocol will reduce the complexity and cost of providing such recording services. The Session Recording problem presents certain unique requirements that are not addressed in the current SIP protocol specification. These include requirements such as the need for a distinction between the session that is being recorded versus the session that has been established for recording. The SRP Working Group will thoroughly identify use cases, provide example system architectures and deployment scenarios, and define requirements. The scope of the activity includes: * Recorder Control * Session metadata content and format * Security mechanisms, including transport and media encryption * Negotiation of recording media streams Privacy and security of conversations are significant concerns. The group will define these issues and rationalize with IETF standards and practices. This includes privacy concerns (including RAVEN), encryption, NAT traversal, SIP-enabled firewalls, authorization, and security. The group will produce: * Updated Requirements, Use Cases, Architecture draft * Specification for Session Recording Protocol Timeline: Apr 2010 Requirements, Use Cases, Architecture to IESG as Informational Draft Nov 2010 Submit protocol draft to IESG as standards track - 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] Charter proposal: Session Recording Pr… Vijay K. Gurbani
- Re: [dispatch] Charter proposal: Session Recordin… Lorenzo Miniero
- Re: [dispatch] Charter proposal: Session Recordin… Vijay K. Gurbani
- Re: [dispatch] Charter proposal: Session Recordin… Scott Lawrence
- Re: [dispatch] Charter proposal: Session Recordin… Hutton, Andrew