RE: sipping-retarget (was RE: [Sip] RE: Question to Identity draf t)

"Francois Audet" <audet@nortel.com> Fri, 22 April 2005 02:48 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOoDY-0000i7-3N; Thu, 21 Apr 2005 22:48:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOoDU-0000hw-Ej for sip@megatron.ietf.org; Thu, 21 Apr 2005 22:48:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12413 for <sip@ietf.org>; Thu, 21 Apr 2005 22:48:25 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOoP1-00053E-5A for sip@ietf.org; Thu, 21 Apr 2005 23:00:23 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j3M2m7F03741; Thu, 21 Apr 2005 22:48:08 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <JJ898ZDZ>; Thu, 21 Apr 2005 22:48:08 -0400
Message-ID: <1ECE0EB50388174790F9694F77522CCF01F986B2@zrc2hxm0.corp.nortel.com>
From: Francois Audet <audet@nortel.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>, 'Paul Kyzivat' <pkyzivat@cisco.com>
Subject: RE: sipping-retarget (was RE: [Sip] RE: Question to Identity draf t)
Date: Thu, 21 Apr 2005 22:48:00 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: "'fluffy@cisco.com'" <fluffy@cisco.com>, 'IETF SIP List' <sip@ietf.org>, 'Fries Steffen' <steffen.fries@siemens.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1319970569=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I think we circled that one: in some cases it is appropriate, in 
other cases it is not.

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz] 
> Sent: Thursday, April 21, 2005 16:51
> To: Paul Kyzivat
> Cc: Audet, Francois [SC100:9T51:EXCH]; Fries Steffen; 
> fluffy@cisco.com; IETF SIP List
> Subject: RE: sipping-retarget (was RE: [Sip] RE: Question to 
> Identity draft)
> 
> 
> 
> That is certainly one of the primary cases I had in mind when 
> I suggested that a "group cert" would sometimes work; a case 
> where there is in fact effectively a group user agent.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > I think this is largely a red herring. In many call center 
> > applications
> > it will be a requirement not to disclose the identity of the actual 
> > agent - probably not even a synonym. There is a high 
> likelihood that the 
> > call center will act as a B2BUA between the caller and the 
> agents, for 
> > that reason and others. ("Your call may be monitored for 
> quality.") So 
> > there will be no retargetting as far as the caller is 
> concerned, and no 
> > identity problem.
> > 
> > 	Paul
> > 
> 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip