Re: [BLISS] Comments on draft-procter-bliss-call-park-extension-04 (Privacy Interactions)

"Dale Worley" <dworley@nortel.com> Thu, 30 April 2009 21:29 UTC

Return-Path: <dworley@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 4509E3A6C58 for <bliss@core3.amsl.com>; Thu, 30 Apr 2009 14:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.644
X-Spam-Level:
X-Spam-Status: No, score=-6.644 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, 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 4SlKDljA-IDW for <bliss@core3.amsl.com>; Thu, 30 Apr 2009 14:29:08 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 4EDAC3A6AD0 for <bliss@ietf.org>; Thu, 30 Apr 2009 14:29:07 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n3ULUOV25644; Thu, 30 Apr 2009 21:30:24 GMT
Received: from [47.141.31.160] ([47.141.31.160]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 30 Apr 2009 17:30:04 -0400
From: Dale Worley <dworley@nortel.com>
To: Scott Orton <orton@nortel.com>
In-Reply-To: <F592E36A5C943E4E91F25880D05AD1140937CB7A@zrc2hxm0.corp.nortel.com>
References: <F592E36A5C943E4E91F25880D05AD1140937CB7A@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Thu, 30 Apr 2009 17:30:03 -0400
Message-Id: <1241127003.19498.104.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Apr 2009 21:30:04.0329 (UTC) FILETIME=[D362C990:01C9C9DA]
Cc: bliss@ietf.org
Subject: Re: [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: Thu, 30 Apr 2009 21:29:09 -0000

On Tue, 2009-04-28 at 17:22 -0400, Orton, Scott (RICH1:B620) wrote:
> 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. 

If you want to use anything approaching "endpoint call control", that
is, anything more complex than an in-dialog REFER, then the anonymized
Contact has to route to Alice, or rather, the privacy service fronting
for Alice.  So it would have to be similar to a "temporary GRUU" (see
draft-ietf-sip-gruu-15), a URI which is secretly mapped to a unique
target but for only a limited time.

But assuming that the privacy service can provide such Contacts, I think
the proposed parking method (out-of-dialog REFER sent to the Park Server
so that it sends INVITE-with-Replace to the caller) should work.

Dale