Re: [ogpx] Seed capability behavior

"Infinity Linden (Meadhbh Hamrick)" <infinity@lindenlab.com> Thu, 21 January 2010 01:17 UTC

Return-Path: <infinity@lindenlab.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 4A02128C10C; Wed, 20 Jan 2010 17:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.357
X-Spam-Level:
X-Spam-Status: No, score=-1.357 tagged_above=-999 required=5 tests=[AWL=0.620, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 RnxOyXbppBQ2; Wed, 20 Jan 2010 17:17:23 -0800 (PST)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id 3A39F3A683D; Wed, 20 Jan 2010 17:17:23 -0800 (PST)
Received: by fxm10 with SMTP id 10so2621818fxm.14 for <multiple recipients>; Wed, 20 Jan 2010 17:17:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.239.159.19 with SMTP id w19mr84788hbc.138.1264036635327; Wed, 20 Jan 2010 17:17:15 -0800 (PST)
In-Reply-To: <29724.46300.qm@web112804.mail.gq1.yahoo.com>
References: <62BFE5680C037E4DA0B0A08946C0933DC4B2DCF9@rrsmsx506.amr.corp.intel.com> <606825.66007.qm@web112815.mail.gq1.yahoo.com> <5cca23bc1001201657u1f59c7aco8369580e125cad87@mail.gmail.com> <567455.42162.qm@web112804.mail.gq1.yahoo.com> <5cca23bc1001201658w43771114t8448d4514f4b4500@mail.gmail.com> <897336.43092.qm@web112804.mail.gq1.yahoo.com> <5cca23bc1001201700n19c5e795w881f7d178f2bc6fd@mail.gmail.com> <371867.46881.qm@web112814.mail.gq1.yahoo.com> <5cca23bc1001201701u71485f63w482d362c0103f28f@mail.gmail.com> <29724.46300.qm@web112804.mail.gq1.yahoo.com>
From: "Infinity Linden (Meadhbh Hamrick)" <infinity@lindenlab.com>
Date: Wed, 20 Jan 2010 17:16:55 -0800
Message-ID: <3a880e2c1001201716x4fd2ef85wee79d02a66fd2c0a@mail.gmail.com>
To: Hogmanay Milestone <hogmanay.milestone@yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ogpx-bounces@ietf.org, "ogpx@ietf.org" <ogpx@ietf.org>
Subject: Re: [ogpx] Seed capability behavior
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: Thu, 21 Jan 2010 01:17:24 -0000

On Wed, Jan 20, 2010 at 17:03, Hogmanay Milestone
<hogmanay.milestone@yahoo.com> wrote:
>>
>>but why would you need a proxy anyway?
>
>
> because the services requested by the proxy may be on the inside of a firewall while the client is on the outside. if the proxy was in the DMZ, you could use traditional network security tools to ensure that service requests only come from a proxy that you trust.
>

so if i understand you correctly, you want the client out there on the
internet to authenticate to an agent domain, get a seed capability
from the agent domain and then pass that seed capability to a proxy in
the DMZ of some organization (say, like the client's employer.)

the proxy would then use that seed cap to request service caps from...
someone? the agent domain? or a server in the client's employer's
intranet (that the proxy can access because it's in the DMZ?)

it's unclear where you're requesting the service caps from.

but i think i understand why you want the seed cap to be a one-shot.
if it wasn't a one-shot, the proxy _could_ retain the ability to
request service caps on the client's behalf.