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

Paul Kyzivat <pkyzivat@cisco.com> Thu, 21 April 2005 20:18 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOi7k-0007fR-0N; Thu, 21 Apr 2005 16:18:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOi7h-0007dU-R3 for sip@megatron.ietf.org; Thu, 21 Apr 2005 16:18:06 -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 QAA11531 for <sip@ietf.org>; Thu, 21 Apr 2005 16:18:04 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOiJA-0003yY-FE for sip@ietf.org; Thu, 21 Apr 2005 16:29:58 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 21 Apr 2005 16:29:11 -0400
X-IronPort-AV: i="3.92,121,1112587200"; d="scan'208"; a="45632746:sNHT27099056"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3LKHFeR019495; Thu, 21 Apr 2005 16:17:52 -0400 (EDT)
Received: from xfe-rtp-211.amer.cisco.com ([64.102.31.113]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 16:17:50 -0400
Received: from cisco.com ([161.44.79.173]) by xfe-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 16:17:49 -0400
Message-ID: <42680A6D.4020907@cisco.com>
Date: Thu, 21 Apr 2005 16:17:49 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Subject: Re: sipping-retarget (was RE: [Sip] RE: Question to Identity draft)
References: <24EAE5D4448B9D4592C6D234CBEBD59701502E53@stntexch03.cis.neustar.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Apr 2005 20:17:49.0512 (UTC) FILETIME=[3065B480:01C546AF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
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


Peterson, Jon wrote:

> If Bob is actually a group list, I would note that for certain kinds of 
> call center applications and so on, it actually -does- make sense for 
> the group to share a cert. No question, though, that for a large group 
> like that where a common cert cannot be used, it would be very difficult 
> for a location service to anticipate precisely who is going to answer.

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