datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

SIP Recording
charter-ietf-siprec-01-00

Snapshots: 01 01-00
Proposed Charter for "SIP Recording" (siprec) WG
WG State: Active
Charter State:
Internal review - (Rechartering)
(Needs a YES.)
Responsible AD: none

Send notices to: none
Last updated: 2014-04-24

Other versions: plain text

Charter charter-ietf-siprec-01-00

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.
  
  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
  requirements.
  
  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
  

Proposed Milestones

Done
Use Cases and Requirements to IESG as Informational RFC
Jan 2013
Submit Architecture to IESG as Informational RFC
Apr 2013
Submit protocol draft to IESG as Proposed Standard RFC
Aug 2013
Submit Metadata model and format to IESG as Proposed Standard RFC
Aug 2013
Submit SIPREC Call Flows draft to IESG as an informational RFC.