Re: [siprec] I-D Action: draft-ietf-siprec-architecture-04.txt

Partha Hi

The ways of identification of CS to be recorded for  SRS initiated flows are very dependent on actual SRC implementation.
For example, if SRC is PBX, it can be even CTI call id, participants ids, DNS name of end point etc.

For gateways it can be IP and PORT of RTP stream for example. 

This what i meant that it is very defendant on SRC and on the way how SRS knows about CSs.

Regards

Leon

On Mar 14, 2012, at 4:12 PM, "Ravindran, Parthasarathi" <pravindran@sonusnet.com> wrote:

> Leon,
> 
> Could you please explain in detail about Sec 3.2.2 update
> 
> "   o  The actual mechanism of the identification is depends on SRC
>      policy."
> 
> Thanks
> partha
> 
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>> Of Leon Portman
>> Sent: Tuesday, March 13, 2012 9:20 PM
>> To: siprec@ietf.org
>> Subject: Re: [siprec] I-D Action: draft-ietf-siprec-architecture-04.txt
>> 
>> Main changes. They are mainly consist from Gonzalo and other mailing
>> lists comments.
>> 
>> 1. Definitions: Adding recording unaware UA definition and fixing some
>> other definitions 2. Consistent abbreviation usage in the document 3.
>> Figures fixes 4. Adding policy mentions in Endpoint as SRC 5. Removing
>> WEBRTC mentions 6. Adding more descriptions in SRS initiated flows
>> 7.Adding support for RS without metadata
>> 
>> There are some small typo mistakes in v04. I have already fixed them and
>> will update in next version
>> 
>> Regards
>> 
>> Leon
>> 
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>> Of internet-drafts@ietf.org
>> Sent: Monday, March 12, 2012 3:25 PM
>> To: i-d-announce@ietf.org
>> Cc: siprec@ietf.org
>> Subject: [siprec] I-D Action: draft-ietf-siprec-architecture-04.txt
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. This draft is a work item of the SIP Recording Working
>> Group of the IETF.
>> 
>> 	Title           : An Architecture for Media Recording using the
>> Session Initiation Protocol
>> 	Author(s)       : Andrew Hutton
>>                         Leon Portman
>>                         Rajnish Jain
>>                         Ken Rehor
>> 	Filename        : draft-ietf-siprec-architecture-04.txt
>> 	Pages           : 16
>> 	Date            : 2012-03-12
>> 
>>  Session recording is a critical requirement in many communications
>>  environments such as call centers and financial trading.  In some of
>>  these environments, all calls must be recorded for regulatory,
>>  compliance, and consumer protection reasons.  Recording of a session
>>  is typically performed by sending a copy of a media stream to a
>>  recording device.  This document describes architectures for
>>  deploying session recording solutions in an environment which is
>>  based on the Session Initiation Protocol (SIP).
>> 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-siprec-architecture-
>> 04.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-siprec-architecture-04.txt
>> 
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec