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

"Peterson, Jon" <jon.peterson@neustar.biz> Thu, 21 April 2005 23:51 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOlSQ-0008Tf-V1; Thu, 21 Apr 2005 19:51:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOlSO-0008TV-Oi for sip@megatron.ietf.org; Thu, 21 Apr 2005 19:51:41 -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 TAA02458 for <sip@ietf.org>; Thu, 21 Apr 2005 19:51:37 -0400 (EDT)
Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOldu-00019F-8Y for sip@ietf.org; Thu, 21 Apr 2005 20:03:35 -0400
Received: from stntsmtp1.cis.neustar.com (smartexch.neustar.com [10.31.13.79]) by oak.neustar.com (8.12.8/8.11.0) with ESMTP id j3LNpTKD017616; Thu, 21 Apr 2005 23:51:29 GMT
Received: from stntexch03.cis.neustar.com ([10.31.13.45]) by stntsmtp1.cis.neustar.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 19:51:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: sipping-retarget (was RE: [Sip] RE: Question to Identity draft)
Date: Thu, 21 Apr 2005 19:51:28 -0400
Message-ID: <24EAE5D4448B9D4592C6D234CBEBD59701502E56@stntexch03.cis.neustar.com>
Thread-Topic: sipping-retarget (was RE: [Sip] RE: Question to Identity draft)
Thread-Index: AcVGrzRarx0J0Ez2QGW7khfU2gPq2wAHYeLA
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: Paul Kyzivat <pkyzivat@cisco.com>
X-OriginalArrivalTime: 21 Apr 2005 23:51:28.0964 (UTC) FILETIME=[0962D840:01C546CD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
Cc: fluffy@cisco.com, IETF SIP List <sip@ietf.org>, Francois Audet <audet@nortel.com>, 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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

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