Re: [dispatch] Comments on draft-lawrence-sip-3rd-party-authorization-00

"Dale Worley" <dworley@nortel.com> Tue, 26 May 2009 19:25 UTC

Return-Path: <dworley@nortel.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37E3E3A6835 for <dispatch@core3.amsl.com>; Tue, 26 May 2009 12:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level:
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080, 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 3aR4siUy1TYe for <dispatch@core3.amsl.com>; Tue, 26 May 2009 12:25:32 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 4354A3A7162 for <dispatch@ietf.org>; Tue, 26 May 2009 12:25:28 -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 n4QJQnV21900; Tue, 26 May 2009 19:26:49 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 26 May 2009 15:26:48 -0400
From: Dale Worley <dworley@nortel.com>
To: Alan Hawrylyshen <ahawrylyshen@ditechnetworks.com>
In-Reply-To: <BB945FE3-76FD-4DCB-802F-391667C4F3CD@ditechnetworks.com>
References: <BB945FE3-76FD-4DCB-802F-391667C4F3CD@ditechnetworks.com>
Content-Type: text/plain; charset="utf-8"
Organization: Nortel Networks
Date: Tue, 26 May 2009 15:26:47 -0400
Message-Id: <1243366007.3754.25.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: quoted-printable
X-OriginalArrivalTime: 26 May 2009 19:26:48.0295 (UTC) FILETIME=[E9BF0F70:01C9DE37]
Cc: dispatch@ietf.org
Subject: Re: [dispatch] Comments on draft-lawrence-sip-3rd-party-authorization-00
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 May 2009 19:25:37 -0000

On Mon, 2009-05-18 at 11:24 -0700, Alan Hawrylyshen wrote:
> p.5 § 2.2 par 10
> 
> This hints at a much larger problem in SIP.
> Can Bob determine from Alice's subscription requests the (minimum)
> degree of disclosure required to satisfy Alice's interests? How can
> Bob know the application of the information requested. As you indicate
> later in the draft, this remains a significant challenge, although it
> is quite likely outside the scope of your draft. The JOIN vs 'line in
> use' indications being a great example of the two extremes.

I'm not sure that this is a problem in quite the way you write it.

All that is needed, I think, is for Bob to determine the information
which Alice is authorized to see.  From that information, Alice can
determine if that is enough information to satisfy her interests.

This approach avoids Alice having to be able to declare her interests,
and Bob having to interpret the declaration.

What makes the problem messy is if the question of what Alice is
authorized to know is variable or duration-sensitive.

Dale