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

"Dale Worley" <dworley@nortel.com> Wed, 13 May 2009 22:03 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 682373A6ADD for <bliss@core3.amsl.com>; Wed, 13 May 2009 15:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level:
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 ZReQMf1KLu4p for <bliss@core3.amsl.com>; Wed, 13 May 2009 15:03:11 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 68A0328C21B for <bliss@ietf.org>; Wed, 13 May 2009 15:02:02 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n4DM3SP06781; Wed, 13 May 2009 22:03:28 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 13 May 2009 18:03:26 -0400
From: Dale Worley <dworley@nortel.com>
To: Scott Orton <orton@nortel.com>
In-Reply-To: <F592E36A5C943E4E91F25880D05AD1140937CBC6@zrc2hxm0.corp.nortel.com>
References: <F592E36A5C943E4E91F25880D05AD1140937CB7A@zrc2hxm0.corp.nortel.com> <1241127003.19498.104.camel@victoria-pingtel-com.us.nortel.com> <F592E36A5C943E4E91F25880D05AD1140937CBC6@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 13 May 2009 18:03:25 -0400
Message-Id: <1242252205.26396.14.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: 13 May 2009 22:03:26.0491 (UTC) FILETIME=[A42336B0:01C9D416]
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: Wed, 13 May 2009 22:03:12 -0000

On Tue, 2009-05-05 at 09:40 -0400, Orton, Scott (RICH1:B620) wrote:
> I agree that if we use the temporary GRUU it will work. But my
> concern is that we are now adding another requirement to the draft. If a
> UA is requesting privacy either from its Proxy or by itself then they
> have to also support draft-ietf-sip-gruu. Where making a simple change
> to parking the call will work for all scenarios without causing another
> draft to be implemented.

In the sipX project, which is a non-centralized PBX system, our
experience is that having proper Contact addresses is mandatory for most
sophisticated call-control activities.  The project hasn't addressed
sophisticated privacy questions at all.  So we are already expecting
that all UAs will support "public GRUUs", and from that point of view,
we don't see it as burdensome to expect that a UA that supports proper
privacy (and the proxy that fronts for it) also supports "temporary
GRUUs".  We expect that to be the least of the tasks needed to support
proper privacy.

The benefit of the current draft's signaling flow is that it allows an
extremely clever way of having a park server that assigns park orbits to
transmit the orbit identifier to the executing UA.

Dale