IETF Logo Mail Archive

Re: [ogpx] Protocol for permitting policy decisions

"Dickson, Mike (ISS Software)" <mike.dickson@hp.com> Fri, 09 October 2009 00:01 UTC

Return-Path: <mike.dickson@hp.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A68BC3A67DB for <ogpx@core3.amsl.com>; Thu, 8 Oct 2009 17:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level:
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 SbwzZ7sL2A9G for <ogpx@core3.amsl.com>; Thu, 8 Oct 2009 17:01:26 -0700 (PDT)
Received: from g5t0007.atlanta.hp.com (g5t0007.atlanta.hp.com [15.192.0.44]) by core3.amsl.com (Postfix) with ESMTP id D3B1B3A67B2 for <ogpx@ietf.org>; Thu, 8 Oct 2009 17:01:24 -0700 (PDT)
Received: from G3W0631.americas.hpqcorp.net (g3w0631.americas.hpqcorp.net [16.233.59.15]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g5t0007.atlanta.hp.com (Postfix) with ESMTPS id 0969614786; Fri, 9 Oct 2009 00:03:07 +0000 (UTC)
Received: from G3W0058.americas.hpqcorp.net (16.232.1.3) by G3W0631.americas.hpqcorp.net (16.233.59.15) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 9 Oct 2009 00:01:41 +0000
Received: from GVW0433EXB.americas.hpqcorp.net ([16.234.32.148]) by G3W0058.americas.hpqcorp.net ([16.232.1.3]) with mapi; Fri, 9 Oct 2009 00:01:41 +0000
From: "Dickson, Mike (ISS Software)" <mike.dickson@hp.com>
To: Carlo Wood <carlo@alinoe.com>, Magnus Zeisig <magnus.zeisig@iis.se>
Date: Fri, 9 Oct 2009 00:01:33 +0000
Thread-Topic: [ogpx] Protocol for permitting policy decisions
Thread-Index: AcpIcGAIDsFKffUzTSGXdM02fF37JgAAtVcw
Message-ID: <4646639E08F58B42836FAC24C94624DD771A2113BB@GVW0433EXB.americas.hpqcorp.net>
References: <983F17705339E24699AA251B458249B50CC48CAEBF@EXCHANGE2K7.office.nic.se> <3a880e2c0910051239t3dcae895x4f6d5f4bf5d64cd@mail.gmail.com> <20091007203535.GA13882@alinoe.com> <983F17705339E24699AA251B458249B50CC48CB683@EXCHANGE2K7.office.nic.se> <20091008233918.GD13882@alinoe.com>
In-Reply-To: <20091008233918.GD13882@alinoe.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Infinity Linden <infinity@lindenlab.com>, "ogpx@ietf.org" <ogpx@ietf.org>
Subject: Re: [ogpx] Protocol for permitting policy decisions
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2009 00:01:27 -0000

+1 on this approach.  

It makes sense to me and seems flexible enough to cover most all the scenarios we've discussed. This is the most complex case. In a simpler one there's no keys to negotiate over because they've been pre-agreed between AD and RD so it's simply the first and last flow.  All the exchanges in the middle are driven by constraints that need to be negotiated between the services involved.

Mike

-----Original Message-----
From: ogpx-bounces@ietf.org [mailto:ogpx-bounces@ietf.org] On Behalf Of Carlo Wood
Sent: Thursday, October 08, 2009 6:39 PM
To: Magnus Zeisig
Cc: Infinity Linden; ogpx@ietf.org
Subject: Re: [ogpx] Protocol for permitting policy decisions

On Thu, Oct 08, 2009 at 10:48:33AM +0200, Magnus Zeisig wrote:
> AD -------------------------(name, <RDkey1?, RDkey2?>)------------------------>
> RD
> AD <--(name, <RDvalue1, RDvalue2, ADkey1?, ADkey2?, agentkey1?, agentkey2?>)---
> RD
> AD --(name, <RDvalues OK, ADvalue1, ADvalue2, agentvalue1, agentkey2 range?>)->
> RD
> AD <----------(name, <ADvalues OK, agentvalue1 OK, agentkey2 range>)-----------
> RD
> AD ----------------------------(name, agentkey2 OK)--------------------------->
> RD
> AD <-----------------------------(name, rez cap)-------------------------------
> RD

I'm ok with this extension, but also open to anyone suggesting it's too flexible,
in which case I guess we need to discuss (more) details.

Over all, I'd really like it if things go in basically this direction.

-- 
Carlo Wood <carlo@alinoe.com>
_______________________________________________
ogpx mailing list
ogpx@ietf.org
https://www.ietf.org/mailman/listinfo/ogpx

v2.8.7 | Report a Bug | By Email