draft-ietf-siprec-req-11.txt   draft-ietf-siprec-req-12.txt 
SIPREC K. Rehor, Ed. SIPREC K. Rehor, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Informational L. Portman, Ed. Intended status: Informational L. Portman, Ed.
Expires: November 30, 2011 NICE Systems Expires: December 11, 2011 NICE Systems
A. Hutton A. Hutton
Siemens Enterprise Siemens Enterprise
Communications Communications
R. Jain R. Jain
IPC Systems IPC Systems
May 29, 2011 June 09, 2011
Use Cases and Requirements for SIP-based Media Recording (SIPREC) Use Cases and Requirements for SIP-based Media Recording (SIPREC)
draft-ietf-siprec-req-11 draft-ietf-siprec-req-12
Abstract Abstract
Session recording is a critical requirement in many business Session recording is a critical requirement in many business
communications environments such as call centers and financial communications environments such as call centers and financial
trading floors. In some of these environments, all calls must be trading floors. In some of these environments, all calls must be
recorded for regulatory and compliance reasons. In others, calls may recorded for regulatory and compliance reasons. In others, calls may
be recorded for quality control or business analytics. be recorded for quality control or business analytics.
Recording is typically performed by sending a copy of the session Recording is typically performed by sending a copy of the session
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 30, 2011. This Internet-Draft will expire on December 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 14, line 25 skipping to change at page 14, line 25
that a given Communication Session is not subject to recording. that a given Communication Session is not subject to recording.
Since humans don't typically look at or know about protocol signaling Since humans don't typically look at or know about protocol signaling
such as SIP, and indeed the SIP session might have originated through such as SIP, and indeed the SIP session might have originated through
a PSTN Gateway without any ability to pass on in-signaling a PSTN Gateway without any ability to pass on in-signaling
indications of recording, users can be notified of recording in the indications of recording, users can be notified of recording in the
media itself through voice announcements, a visual indicator on the media itself through voice announcements, a visual indicator on the
endpoint, or other means. endpoint, or other means.
With regards to security implications of the protocol(s), clearly With regards to security implications of the protocol(s), clearly
there is a need for authentication, authorization, eavesdropping, and there is a need for authentication, authorization and eavesdropping
protection for the solution. The SRC needs to know the SRS it is protection for the solution. The SRC needs to know the SRS it is
communicating with is legitimate, and vice-versa, even if they are in communicating with is legitimate, and vice-versa, even if they are in
different domains. Both the signaling and media for the Recording different domains. Both the signaling and media for the Recording
Session need the ability to be authenticated and protected from Session need the ability to be authenticated and protected from
eavesdropping. Requirements are detailed in the requirements eavesdropping. Requirements are detailed in the requirements
section. section.
Communication Sessions and Recording Sessions can require different Communication Sessions and Recording Sessions can require different
security levels both for signaling and media, depending on deployment security levels both for signaling and media, depending on deployment
configurations. For some environments, for example, SRS and SRC will configurations. For some environments, for example, SRS and SRC will
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/