[BLISS] Comments on draft-procter-bliss-call-park-extension-04 (Privacy Interactions)
"Scott Orton" <orton@nortel.com> Tue, 28 April 2009 21:21 UTC
Return-Path: <ORTON@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FFDA3A6AF3 for <bliss@core3.amsl.com>; Tue, 28 Apr 2009 14:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level:
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 fE7AMEDPsJtk for <bliss@core3.amsl.com>; Tue, 28 Apr 2009 14:21:30 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 761FD28B56A for <bliss@ietf.org>; Tue, 28 Apr 2009 14:21:10 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n3SLMPv05176; Tue, 28 Apr 2009 21:22:26 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9C847.63BB9725"
Date: Tue, 28 Apr 2009 16:22:09 -0500
Message-ID: <F592E36A5C943E4E91F25880D05AD1140937CB7A@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Comments on draft-procter-bliss-call-park-extension-04 (Privacy Interactions)
Thread-Index: AcnIR2RJC7BC+ODLRoC9vBfISk/UWg==
From: Scott Orton <orton@nortel.com>
To: Michael Procter <michael@voip.co.uk>
Cc: bliss@ietf.org
Subject: [BLISS] Comments on draft-procter-bliss-call-park-extension-04 (Privacy Interactions)
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2009 21:21:31 -0000
Michael, I have been thinking about how call park and privacy interact. I think there is an issue with the parking and retrieval of a call when the user that is being parked has applied privacy in the initial call. Lets take for example a case where Alice calls bob. Alice is using privacy as defined in RFC 3325. In this case the from header and the contact for Alice will anonymous. The contact is likely just an IP address and the from header will be sip:anonymous@anonymous.invalid. The contact header being an IP address is enough to exchange messages in a dialog but is unlikely to be enough to route a new call to the Alice. If it was enough then you privacy is not very good as nothing is preventing the user from returning a private call. So when a Refer is generated to the Call park server the referTo in the Refer will not be routable. I really want to be able to park a call with an anonymous originator. The only way that I can see to reliably do this it to Refer Alice to the callpark server rather than send a unsolicited Refer to the call park server. This also leads to an interesting scenario. If the call park server and Alice's proxy which is applying privacy for her are the same server. Then once the call is parked the CallPark server has to be sure to apply privacy to the dialog notify that it sends back to Bob. The other issue this brings up is that we may want to specify that the Notify for the Refer needs to include the orbit parameter in the contact in the case that Alice is referred to the callpark server. So the question is do we want to have two call flows to park a call one to the park server and one to the client being parked. I think it is better to settle on one and in order to support parking a call with privacy enabled I think the flow needs to show the Refer going to the client being parked. Of course if we go with this flow there is now an issue of how to retrieve the parked call. Since the call is private there is no way to send an Invite with replaces back to Alice to retrieve the call. One solution to this would be for the callpark server to act as a Third party call control device and in the park dialog event specify itself in the dialog event. Then when the call is attempted to be retrieved the Invite would go to the call park server. It could then either send a Refer to the parked call to connect it to the retrieving party or act as a BBUA and send a reinvite to the parked party with the SDP of Bob's retrieving request. As an example of why this is necessary, lets take a real world example of a car dealership. A call comes in for the sales floor from an anonymous caller. The attendant answering the call needs to be able to park the call and let a salesman retrieve the call. I can provide call flows. But I have not had a chance to work them up. Scott
- [BLISS] Comments on draft-procter-bliss-call-park… Scott Orton
- Re: [BLISS] Comments on draft-procter-bliss-call-… Dale Worley
- Re: [BLISS] Comments on draft-procter-bliss-call-… Francois Audet
- Re: [BLISS] Comments on draft-procter-bliss-call-… Michael Procter
- Re: [BLISS] Comments on draft-procter-bliss-call-… Michael Procter
- Re: [BLISS] Comments on draft-procter-bliss-call-… Scott Orton
- Re: [BLISS] Comments ondraft-procter-bliss-call-p… Scott Orton
- Re: [BLISS] Comments ondraft-procter-bliss-call-p… Dale Worley
- Re: [BLISS] Comments on draft-procter-bliss-call-… Dale Worley
- Re: [BLISS] Comments ondraft-procter-bliss-call-p… Michael Procter
- Re: [BLISS] Comments ondraft-procter-bliss-call-p… Scott Orton
- Re: [BLISS] Comments ondraft-procter-bliss-call-p… Michael Procter