Re: [siprec] User notification/privacy questions

Brian Rosen <br@brianrosen.net> Thu, 24 June 2010 12:44 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CB353A68C2 for <siprec@core3.amsl.com>; Thu, 24 Jun 2010 05:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.496
X-Spam-Level:
X-Spam-Status: No, score=-1.496 tagged_above=-999 required=5 tests=[AWL=1.102, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WNg7HTgpUdqs for <siprec@core3.amsl.com>; Thu, 24 Jun 2010 05:44:44 -0700 (PDT)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [70.87.156.98]) by core3.amsl.com (Postfix) with ESMTP id 3491D3A69B6 for <siprec@ietf.org>; Thu, 24 Jun 2010 05:44:44 -0700 (PDT)
Received: from [209.173.57.233] (helo=[192.168.130.22]) by ebru.winwebhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <br@brianrosen.net>) id 1ORlnN-00024m-BK; Thu, 24 Jun 2010 07:44:48 -0500
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary="Apple-Mail-10-576052110"
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C3803A26F7B@TLVMBX01.nice.com>
Date: Thu, 24 Jun 2010 08:44:39 -0400
Message-Id: <4A47C526-625B-42AA-A640-AB33415D81C1@brianrosen.net>
References: <F2D661C2-378A-43EE-8A42-F9415DDA5709@cdt.org> <07465C1D981ABC41A344374066AE1A2C3803A26F7B@TLVMBX01.nice.com>
To: Leon Portman <Leon.Portman@nice.com>
X-Mailer: Apple Mail (2.1081)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] User notification/privacy questions
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 24 Jun 2010 12:44:45 -0000

With respect to tones, the normal sip mechanism is that the "recording in progress" is signaled in the SIP transaction, and the UA does the UI, whatever it is.  That means whatever the alert mechanism is, it's generated locally, and likely has local significance.  That could include displays, tones, vibration or other mechanisms, and may have some user configurability.

Brian

On Jun 24, 2010, at 8:00 AM, Leon Portman wrote:

> Please see below
>  
> Leon
>  
>  
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of Alissa Cooper
> Sent: Thursday, June 24, 2010 2:24 PM
> To: siprec@ietf.org
> Subject: [siprec] User notification/privacy questions
>  
> I have a couple of questions about requirements 23 and 24 in draft-
> ietf-siprec-req-00 and related text in draft-hutton-siprec-session-
> recording-arch-01.
> > o REQ-023 The mechanism MUST support a means for a SIP UA to request
> >    that a session is not recorded.
>  
> Is it envisioned that the negotiation of this kind of request would 
> happen before recording starts (section 4.5 of -session-recording-arch 
> seems to intimate this)? Or is it left open-ended, so that recording 
> may start and sometime later the UA can request not to have it 
> recorded (or to stop the recording)? If it's the former, I wonder if 
> "prior to recording" should be added to the end of the sentence.
>  [LeonP] It is a good comment. The indication for not to be recorded is
> supposed to be part of the original CS, meaning prior of the recording.
> In addition, I don’t think that we want to define a mechanism where
> SRC will start asking UAs if they allowed to be recorded upon receiving recording request
>  
>  
> > o REQ-024 The mechanism MUST provide a means of indicating to the end
> >    users of a Communication Session that the session in which they are
> >    participating is being recorded.
>  
> > Examples include: inject tones into the Communication Session from
> >    the SRC, play a message at the beginning of a session, a visual
> >    indicator on a display, etc.
>  
> On timing again, would it make sense to say that the indication needs 
> to be possible upon establishment of the session? Maybe this is 
> overkill, but an indication that comes right before everyone hangs up 
> is pretty useless.
>  
> [LeonP] There was some discussion on the list if indication supposed
> to be only during the actual recording session or also even it can be recorded potentially - during the complete CS.
>  
> I'm also wondering about where the notion of injecting tones comes 
> from. Obviously without some out-of-band understanding about what a 
> tone means, hearing a tone during a session isn't going to tell end 
> users much of anything. Unless there are particular use cases where 
> particular tones are already well understood (e.g., all financial 
> traders know that a particular tone means they're being recorded), it 
> seems like a tone isn't really sufficient notification.
>  
> Alissa
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
> _______________________________________________
> 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