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

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Wed, 14 March 2012 17:19 UTC

Return-Path: <pravindran@sonusnet.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E592121F871B for <siprec@ietfa.amsl.com>; Wed, 14 Mar 2012 10:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.412
X-Spam-Level:
X-Spam-Status: No, score=-4.412 tagged_above=-999 required=5 tests=[AWL=2.187, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kV1CNtHNzFzH for <siprec@ietfa.amsl.com>; Wed, 14 Mar 2012 10:19:22 -0700 (PDT)
Received: from na3sys010aog108.obsmtp.com (na3sys010aog108.obsmtp.com [74.125.245.84]) by ietfa.amsl.com (Postfix) with ESMTP id E757721F8722 for <siprec@ietf.org>; Wed, 14 Mar 2012 10:19:21 -0700 (PDT)
Received: from USMA-EX-HUB2.sonusnet.com ([69.147.176.212]) (using TLSv1) by na3sys010aob108.postini.com ([74.125.244.12]) with SMTP ID DSNKT2DTGaJ/vTIsZ14IRPB58ySiBXL4T1l1@postini.com; Wed, 14 Mar 2012 10:19:22 PDT
Received: from INBA-HUB02.sonusnet.com (10.70.51.87) by USMA-EX-HUB2.sonusnet.com (66.203.90.17) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 14 Mar 2012 13:19:30 -0400
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0355.002; Wed, 14 Mar 2012 22:49:15 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Leon Portman <Leon.Portman@nice.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] I-D Action: draft-ietf-siprec-architecture-04.txt
Thread-Index: AQHNAFN+7jAuVLtiI0aefxoa4INav5ZoBQaAgAHS3hCAADP94A==
Date: Wed, 14 Mar 2012 17:19:26 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C0E1FCC2C@inba-mail01.sonusnet.com>
References: <20120312132433.19581.40959.idtracker@ietfa.amsl.com> <07465C1D981ABC41A344374066AE1A2C39DAF8C0A7@TLVMBX01.nice.com> <387F9047F55E8C42850AD6B3A7A03C6C0E1FCACA@inba-mail01.sonusnet.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C0E1FCACA@inba-mail01.sonusnet.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [121.242.142.186]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] I-D Action: draft-ietf-siprec-architecture-04.txt
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 17:19:23 -0000

Leon,

Adding to the previous query, the same section mentions about join header usage

" o  Identify the session that is to be recorded - Possibly using the
      Join header [RFC3911]"

The problem with Join header is that Join header maps dialog and not CS. So, it is not generic approach for SIPREC. Please clarify in case I'm missing something here.

Thanks
Partha


>-----Original Message-----
>From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>Of Ravindran, Parthasarathi
>Sent: Wednesday, March 14, 2012 7:42 PM
>To: Leon Portman; siprec@ietf.org
>Subject: Re: [siprec] I-D Action: draft-ietf-siprec-architecture-04.txt
>
>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.tx
>>t
>>
>>_______________________________________________
>>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