draft-ietf-siprec-callflows-01.txt   draft-ietf-siprec-callflows-02.txt 
SIPREC Ram Mohan. Ravindranath SIPREC Ram Mohan. Ravindranath
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track Parthasarathi. Ravindran Intended status: Standards Track Parthasarathi. Ravindran
Expires: January 14, 2014 Nokia Siemens Networks Expires: July 18, 2014 Nokia Solutions and Networks
Paul. Kyzivat Paul. Kyzivat
Huawei Huawei
July 13, 2013 January 14, 2014
Session Initiation Protocol (SIP) Recording Call Flows Session Initiation Protocol (SIP) Recording Call Flows
draft-ietf-siprec-callflows-01 draft-ietf-siprec-callflows-02
Abstract Abstract
Session recording is a critical requirement in many communications Session recording is a critical requirement in many communications
environments such as call centers and financial trading. In some of environments such as call centers and financial trading. In some of
these environments, all calls must be recorded for regulatory, these environments, all calls must be recorded for regulatory,
compliance, and consumer protection reasons. Recording of a session compliance, and consumer protection reasons. Recording of a session
is typically performed by sending a copy of a media stream to a is typically performed by sending a copy of a media stream to a
recording device. This document lists call flows that has snapshot recording device. This document lists call flows that has snapshot
of metadata sent from SRC to SRS, the metadata format for which is of metadata sent from SRC to SRS, the metadata format for which is
skipping to change at page 1, line 41 skipping to change at page 1, line 42
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 January 14, 2014. This Internet-Draft will expire on July 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 24 skipping to change at page 2, line 24
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Metadata XML schema Instances . . . . . . . . . . . . . . . . 3 3. Metadata XML schema Instances . . . . . . . . . . . . . . . . 3
3.1. Sample Call flow . . . . . . . . . . . . . . . . . . . . . 3 3.1. Sample Call flow . . . . . . . . . . . . . . . . . . . . . 3
3.2. Call Scenarios with SRC recording streams with out 3.2. Call Scenarios with SRC recording streams with out
mixing . . . . . . . . . . . . . . . . . . . . . . . . . . 5 mixing . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2.1. Example 1: Basic Call . . . . . . . . . . . . . . . . 5 3.2.1. Example 1: Basic Call . . . . . . . . . . . . . . . . 5
3.2.2. Example 2: Hold/resume . . . . . . . . . . . . . . . . 7 3.2.2. Example 2: Hold/resume . . . . . . . . . . . . . . . . 7
3.2.3. Example 3:Call Transfer (RE-INVITE and REFER based) . 10 3.2.3. Example 3:Call Transfer (RE-INVITE and REFER based) . 10
3.2.4. Example 4: Call disconnect . . . . . . . . . . . . . . 16 3.2.4. Example 4: Call disconnect . . . . . . . . . . . . . . 17
3.3. Call Scenarios with SRC recording streams by mixing . . . 18 3.3. Call Scenarios with SRC recording streams by mixing . . . 19
3.3.1. Example 1: Basic call with SRC mixing streams . . . . 18 3.3.1. Example 1: Basic call with SRC mixing streams . . . . 19
3.3.2. Example 2: Hold/resume with SRC recording by 3.3.2. Example 2: Hold/resume with SRC recording by
mixing streams . . . . . . . . . . . . . . . . . . . . 20 mixing streams . . . . . . . . . . . . . . . . . . . . 21
3.3.3. Example 3: Metadata snapshot of joining/dropping 3.3.3. Example 3: Metadata snapshot of joining/dropping
of a participant to a session . . . . . . . . . . . . 23 of a participant to a session . . . . . . . . . . . . 24
3.3.4. Example 4: Call disconnect . . . . . . . . . . . . . . 26 3.3.4. Example 4: Call disconnect . . . . . . . . . . . . . . 27
3.4. Call scenarios with persistent RS between SRC and SRS . . 26 3.4. Call scenarios with persistent RS between SRC and SRS . . 27
3.4.1. Example 1: Metadata snapshot during CS disconnect 3.4.1. Example 1: Metadata snapshot during CS disconnect
with persistent RS between SRC and SRS . . . . . . . . 26 with persistent RS between SRC and SRS . . . . . . . . 27
3.5. Turrent-Case: Multiple CS into single RS with mixed 3.5. Turrent-Case: Multiple CS into single RS with mixed
stream . . . . . . . . . . . . . . . . . . . . . . . . . . 27 stream . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4. Security Considerations . . . . . . . . . . . . . . . . . . . 29 4. Security Considerations . . . . . . . . . . . . . . . . . . . 30
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 30 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 31
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.1. Normative References . . . . . . . . . . . . . . . . . . . 30 7.1. Normative References . . . . . . . . . . . . . . . . . . . 31
7.2. Informative References . . . . . . . . . . . . . . . . . . 30 7.2. Informative References . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
1. Overview 1. Overview
[I-D.ietf-siprec-metadata] document focuses on the Recording metadata [I-D.ietf-siprec-metadata] document focuses on the Recording metadata
which describes the communication session. The document lists a few which describes the communication session. The document lists a few
examples and shows the snapshots of metadata sent from SRC to SRS. examples and shows the snapshots of metadata sent from SRC to SRS.
For the sake of simplicity the entire SIP [RFC3261] messages are not For the sake of simplicity the entire SIP [RFC3261] messages are not
shown at various points, instead only a snippets of the SIP/SDP shown at various points, instead only a snippets of the SIP/SDP
messages and the XML snapshot of metadata is shown. messages and the XML snapshot of metadata is shown.
skipping to change at page 30, line 23 skipping to change at page 31, line 23
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
7.2. Informative References 7.2. Informative References
[I-D.ietf-siprec-metadata] [I-D.ietf-siprec-metadata]
R, R., Ravindran, P., and P. Kyzivat, "Session Initiation R, R., Ravindran, P., and P. Kyzivat, "Session Initiation
Protocol (SIP) Recording Metadata", Protocol (SIP) Recording Metadata",
draft-ietf-siprec-metadata-12 (work in progress), draft-ietf-siprec-metadata-13 (work in progress),
May 2013. November 2013.
[I-D.ietf-siprec-architecture] [I-D.ietf-siprec-architecture]
Hutton, A., Portman, L., Jain, R., and K. Rehor, "An Hutton, A., Portman, L., Jain, R., and K. Rehor, "An
Architecture for Media Recording using the Session Architecture for Media Recording using the Session
Initiation Protocol", draft-ietf-siprec-architecture-08 Initiation Protocol", draft-ietf-siprec-architecture-11
(work in progress), May 2013. (work in progress), December 2013.
[RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session [RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
Initiation Protocol (SIP) Event Package for Conference Initiation Protocol (SIP) Event Package for Conference
State", RFC 4575, August 2006. State", RFC 4575, August 2006.
[RFC4353] Rosenberg, J., "A Framework for Conferencing with the [RFC4353] Rosenberg, J., "A Framework for Conferencing with the
Session Initiation Protocol (SIP)", RFC 4353, Session Initiation Protocol (SIP)", RFC 4353,
February 2006. February 2006.
[RFC6230] Boulton, C., Melanchuk, T., and S. McGlashan, "Media [RFC6230] Boulton, C., Melanchuk, T., and S. McGlashan, "Media
skipping to change at page 31, line 18 skipping to change at page 32, line 18
Cisco Systems, Inc. Cisco Systems, Inc.
Cessna Business Park, Cessna Business Park,
Kadabeesanahalli Village, Varthur Hobli, Kadabeesanahalli Village, Varthur Hobli,
Sarjapur-Marathahalli Outer Ring Road Sarjapur-Marathahalli Outer Ring Road
Bangalore, Karnataka 560103 Bangalore, Karnataka 560103
India India
Email: rmohanr@cisco.com Email: rmohanr@cisco.com
Parthasarathi Ravindran Parthasarathi Ravindran
Nokia Siemens Networks Nokia Solutions and Networks
Manyata Embassy business Park Bangalore, Karnataka
Bangalore, Karnataka 560045
India India
Email: partha@parthasarathi.co.in Email: partha@parthasarathi.co.in
Paul Kyzivat Paul Kyzivat
Huawei Huawei
Hudson, MA Hudson, MA
USA USA
Email: pkyzivat@alum.mit.edu Email: pkyzivat@alum.mit.edu
 End of changes. 14 change blocks. 
28 lines changed or deleted 28 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/