draft-ietf-siprec-callflows-02.txt   draft-ietf-siprec-callflows-03.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: July 18, 2014 Nokia Solutions and Networks Expires: January 22, 2015 Nokia Networks
Paul. Kyzivat Paul. Kyzivat
Huawei Huawei
January 14, 2014 July 21, 2014
Session Initiation Protocol (SIP) Recording Call Flows Session Initiation Protocol (SIP) Recording Call Flows
draft-ietf-siprec-callflows-02 draft-ietf-siprec-callflows-03
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 42 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 July 18, 2014. This Internet-Draft will expire on January 22, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
skipping to change at page 3, line 31 skipping to change at page 3, line 31
This section describes the metadata model XML instances for different This section describes the metadata model XML instances for different
use cases of SIPREC. For the sake of simplicity the complete SIP/SDP use cases of SIPREC. For the sake of simplicity the complete SIP/SDP
snippets are NOT shown here. snippets are NOT shown here.
3.1. Sample Call flow 3.1. Sample Call flow
The following is a sample call flow that shows the SRC establishing a The following is a sample call flow that shows the SRC establishing a
recording session towards the SRS. The SRC in this example could be recording session towards the SRS. The SRC in this example could be
part of any one of the architectures described in section 3 of part of any one of the architectures described in section 3 of
[I-D.ietf-siprec-architecture]. [RFC7245].
SRC SRS SRC SRS
| | | |
|(1) INVITE (metadata snapshot) F1 | |(1) INVITE (metadata snapshot) F1 |
|---------------------------------------------------->| |---------------------------------------------------->|
| 200 OK | | 200 OK |
|<----------------------------------------------------| |<----------------------------------------------------|
|(3) ACK | |(3) ACK |
|---------------------------------------------------->| |---------------------------------------------------->|
|(4) RTP | |(4) RTP |
skipping to change at page 4, line 37 skipping to change at page 4, line 37
|(7) UPDATE/RE-INVITE (metadata update n-1) Fn-1 | |(7) UPDATE/RE-INVITE (metadata update n-1) Fn-1 |
|---------------------------------------------------->| |---------------------------------------------------->|
| 200 OK | | 200 OK |
|<----------------------------------------------------| |<----------------------------------------------------|
For the sake of simplicity, ACKs to RE-INVITES and BYEs are not For the sake of simplicity, ACKs to RE-INVITES and BYEs are not
shown. The subsequent sections describes the snapshot of metadata shown. The subsequent sections describes the snapshot of metadata
sent from SRC to SRS for each of the above transactions (F1 ... sent from SRC to SRS for each of the above transactions (F1 ...
Fn-1). There may be multiple UPDATES/RE-INVITES mid call to Fn-1). There may be multiple UPDATES/RE-INVITES mid call to
indicates snapshots of different CS changes. Depending on the indicates snapshots of different CS changes. Depending on the
architecture described in section 3 of [I-D.ietf-siprec-architecture] architecture described in section 3 of [RFC7245] an SRC may be a
an SRC may be a endpoint or B2BUA or as part of MEDIACTRL or endpoint or B2BUA or as part of MEDIACTRL or Conference Focus. The
Conference Focus. The subsequent sections in this document tries to subsequent sections in this document tries to list some example
list some example metadata snapshots for three major categories. metadata snapshots for three major categories.
o SRC recording streams unmixed to SRS. This includes cases where o SRC recording streams unmixed to SRS. This includes cases where
SRC is SIP UA or B2BUA. SRC is SIP UA or B2BUA.
o SRC recording mixed streams to SRS. This includes cases where SRC o SRC recording mixed streams to SRS. This includes cases where SRC
is part of SIP conference model explained in [RFC4353] is part of SIP conference model explained in [RFC4353]
o SRC having a persistent RS with SRS o SRC having a persistent RS with SRS
o Special flows like Turrent flows o Special flows like Turrent flows
Note that only those examples for which metadata changes are listed Note that only those examples for which metadata changes are listed
in each category. For some of the call flows the snapshots may be in each category. For some of the call flows the snapshots may be
same (like in case of endpoint or B2BUA acting as SRC) and the same same (like in case of endpoint or B2BUA acting as SRC) and the same
is mentioned in the text preceding the example. is mentioned in the text preceding the example.
3.2. Call Scenarios with SRC recording streams with out mixing 3.2. Call Scenarios with SRC recording streams with out mixing
The section covers the models mentioned in the architecture document The section covers the models mentioned in the architecture document
in section 3 of [I-D.ietf-siprec-architecture] where an SRC may be a in section 3 of [RFC7245] where an SRC may be a SIP-UA or B2BUA. The
SIP-UA or B2BUA. The SRS here could be a SIP-UA or an entity part of SRS here could be a SIP-UA or an entity part of MEDIACTRL
MEDIACTRL architecture described in [RFC6230]. architecture described in [RFC6230].
3.2.1. Example 1: Basic Call 3.2.1. Example 1: Basic Call
Basic call between two Participants Alice and Bob who are part of one Basic call between two Participants Alice and Bob who are part of one
CS. In this use case each participant sends two Media Streams. CS. In this use case each participant sends two Media Streams.
Media Streams sent by each participant are received all other Media Streams sent by each participant are received all other
participants in this use-case. Below is the initial snapshot sent by participants in this use-case. Below is the initial snapshot sent by
SRC in the INVITE to SRS that has complete metadata. For the sake of SRC in the INVITE to SRS that has complete metadata. For the sake of
simplicity only snippets of SIP/SDP are shown. The SRCs records the simplicity only snippets of SIP/SDP are shown. The SRCs records the
streams of each participant to SRS with out mixing in this example. streams of each participant to SRS with out mixing in this example.
skipping to change at page 19, line 8 skipping to change at page 19, line 8
<participantsessionassoc <participantsessionassoc
participant_id="zSfPoSvdSDCmU3A3TRDxAw==" participant_id="zSfPoSvdSDCmU3A3TRDxAw=="
session_id="hVpd7YQgRW2nD22h7q60JQ=="> session_id="hVpd7YQgRW2nD22h7q60JQ==">
<disasociate-time>2010-12-16T23:41:07Z</disassociate-time> <disasociate-time>2010-12-16T23:41:07Z</disassociate-time>
</participantsessionassoc> </participantsessionassoc>
</recording> </recording>
3.3. Call Scenarios with SRC recording streams by mixing 3.3. Call Scenarios with SRC recording streams by mixing
The section covers the models mentioned in the architecture document The section covers the models mentioned in the architecture document
in section 3 of [I-D.ietf-siprec-architecture] where an SRC may be in section 3 of [RFC7245] where an SRC may be part of Conference
part of Conference model either as Focus or a participant in model either as Focus or a participant in Conference. The SRS here
Conference. The SRS here could be a SIP UA or an entity part of could be a SIP UA or an entity part of MEDIACTRL architecture. Note
MEDIACTRL architecture. Note that the disconnect case is not shown that the disconnect case is not shown since the metadata snapshot
since the metadata snapshot will be same as for a non-mixing case. will be same as for a non-mixing case.
3.3.1. Example 1: Basic call with SRC mixing streams 3.3.1. Example 1: Basic call with SRC mixing streams
Basic call between two Participants Alice and Bob who are part of one Basic call between two Participants Alice and Bob who are part of one
CS. In this use case each participant sends one Media Streams. CS. In this use case each participant sends one Media Streams.
Media Streams sent by each participant is received by the other Media Streams sent by each participant is received by the other
participant. Below is the initial snapshot sent by SRC in the INVITE participant. Below is the initial snapshot sent by SRC in the INVITE
to SRS that has complete metadata. For the sake of simplicity only to SRS that has complete metadata. For the sake of simplicity only
snippets of SIP/SDP are shown. The SRCs records the streams of each snippets of SIP/SDP are shown. The SRCs records the streams of each
participant to SRS by mixing in this example. The SRC here could be participant to SRS by mixing in this example. The SRC here could be
part of conference Focus model described in section 3 of part of conference Focus model described in section 3 of [RFC7245].
[I-D.ietf-siprec-architecture].
F1 INVITE SRC --------------> SRS F1 INVITE SRC --------------> SRS
INVITE sip:recorder@example.com SIP/2.0 INVITE sip:recorder@example.com SIP/2.0
Via: SIP/2.0/TCP src.example.com;branch=z9hG4bKdf6b622b648d9 Via: SIP/2.0/TCP src.example.com;branch=z9hG4bKdf6b622b648d9
From: <sip:2000@example.com>;tag=35e195d2-947d-4585-946f-09839247 From: <sip:2000@example.com>;tag=35e195d2-947d-4585-946f-09839247
To: <sip:recorder@example.com> To: <sip:recorder@example.com>
Call-ID: d253c800-b0d1ea39-4a7dd-3f0e20a Call-ID: d253c800-b0d1ea39-4a7dd-3f0e20a
CSeq: 101 INVITE CSeq: 101 INVITE
Max-Forwards: 70 Max-Forwards: 70
skipping to change at page 31, 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-13 (work in progress), draft-ietf-siprec-metadata-15 (work in progress),
November 2013. February 2014.
[I-D.ietf-siprec-architecture] [RFC7245] 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", RFC 7245, May 2014.
Initiation Protocol", draft-ietf-siprec-architecture-11
(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 32, 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 Solutions and Networks Nokia Networks
Bangalore, Karnataka Bangalore, Karnataka
India India
Email: partha@parthasarathi.co.in Email: partha@parthasarathi.co.in
Paul Kyzivat Paul Kyzivat
Huawei Huawei
Hudson, MA Hudson, MA
USA USA
 End of changes. 12 change blocks. 
27 lines changed or deleted 24 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/