WG Action: Rechartered SIP Recording (siprec)

The IESG <iesg-secretary@ietf.org> Wed, 11 June 2014 22:30 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 1AB8F1A02ED; Wed, 11 Jun 2014 15:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jykzrsm9m4Xk; Wed, 11 Jun 2014 15:30:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B8C651B28A8; Wed, 11 Jun 2014 15:30:16 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Action: Rechartered SIP Recording (siprec)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140611223016.21924.52450.idtracker@ietfa.amsl.com>
Date: Wed, 11 Jun 2014 15:30:16 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/XFMT6tkutyJx2D1r2T4mkXM1qmk
Cc: siprec WG <siprec@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jun 2014 22:30:19 -0000

The SIP Recording (siprec) working group in the Real-time Applications
and Infrastructure Area of the IETF has been rechartered. For additional
information please contact the Area Directors or the WG Chairs.

SIP Recording (siprec)
Current Status: Active WG

  Brian Rosen <br@brianrosen.net>
  Andrew Hutton <andrew.hutton@unify.com>

Technical advisors:
  Peter Saint-Andre <stpeter@stpeter.im>

Assigned Area Director:
  Alissa Cooper <alissa@cooperw.in>

Mailing list
  Address: siprec@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/siprec
  Archive: http://www.ietf.org/mail-archive/web/siprec/


The Session Recording Protocol (SIPREC) 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 determine requirements and produce a 
specification for a protocol that will manage delivery of media 
(including audio, video, MSRP instant message sessions, and real-time 
text), in SIP-based systems 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.

Privacy and security of conversations are significant concerns. The 
working group will make sure that any protocol specified addresses these 
concerns and includes mechanisms to alert users to the fact that a 
session they are participating in is being recorded. In addition the 
working group will take account of RFC 7258 concerning pervasive 

The working group must take care that the session recording requirements 
and protocol does not conflict with the IETF statement on wiretapping 
contained in RFC 2804.

The SIPREC Working Group will thoroughly identify use cases, provide 
example system architectures and deployment scenarios, and define 
The scope of the activity includes:

* Recorder Control

* Session metadata content and format

* Security mechanisms, including transport and media encryption

* Privacy concerns, including end-user notification

* Negotiation of recording media streams

The group will define these issues and rationalize with IETF standards 
and practices. This includes encryption, NAT traversal, operations and
manageability, SIP-enabled firewalls, authorization, and security.

The group will produce:

* Updated Requirements, Use Cases, Architecture draft

* Specification for Session Recording Protocol

  Done     - Use Cases and Requirements to IESG as Informational RFC
  Done     - Submit Architecture to IESG as Informational RFC
  Jul 2014 - Submit protocol draft to IESG as Proposed Standard RFC
  Sep 2014 - Submit Metadata model and format to IESG as Proposed
Standard RFC
  Sep 2014 - Submit SIPREC Call Flows draft to IESG as an informational
  Dec 2014 - Conference Recording Use Cases and Requirements to IESG as
Informational RFC
  Dec 2014 - Conference Recording Architecture to IESG as Informational
  Dec 2014 - Protocol and metadata for MSRP recording to IESG as Proposed
Standard RFC
  Feb 2015 - Protocol and metadata for using RTP media to record the
sharing of applications, documents and screens to the IESG as Proposed
Standard RFC