Re: [ogpx] VWRAP Draft Charter - 2009 09 01

Carlo Wood <carlo@alinoe.com> Sun, 04 October 2009 13:09 UTC

Return-Path: <carlo@alinoe.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 9AAE23A68B4 for <ogpx@core3.amsl.com>; Sun, 4 Oct 2009 06:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.185
X-Spam-Level:
X-Spam-Status: No, score=-1.185 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 iaVTMGTjLO0t for <ogpx@core3.amsl.com>; Sun, 4 Oct 2009 06:09:14 -0700 (PDT)
Received: from viefep12-int.chello.at (viefep12-int.chello.at [62.179.121.32]) by core3.amsl.com (Postfix) with ESMTP id 5F3B83A66B4 for <ogpx@ietf.org>; Sun, 4 Oct 2009 06:09:13 -0700 (PDT)
Received: from edge05.upc.biz ([192.168.13.212]) by viefep12-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20091004131044.HHBS4394.viefep12-int.chello.at@edge05.upc.biz>; Sun, 4 Oct 2009 15:10:44 +0200
Received: from mail9.alinoe.com ([77.250.43.12]) by edge05.upc.biz with edge id odAi1c03U0FlQed05dAjPB; Sun, 04 Oct 2009 15:10:44 +0200
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1MuQsT-0007zJ-0e; Sun, 04 Oct 2009 15:11:53 +0200
Date: Sun, 04 Oct 2009 15:11:53 +0200
From: Carlo Wood <carlo@alinoe.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Message-ID: <20091004131153.GA29765@alinoe.com>
References: <9b8a8de40909291316i19c79a96h111d88e73a64cc79@mail.gmail.com> <e0b04bba0909291751g157d2043g1c15e8d8ac417ccf@mail.gmail.com> <f72742de0909300910t23131532i1719d2c86423fa41@mail.gmail.com> <e0b04bba0910011434i13f890bfodd22cd15eef17697@mail.gmail.com> <f72742de0910011457o5e757135rd9db7fc7f4a1389@mail.gmail.com> <e0b04bba0910011613w6f25b684w1b0f2e8c7187b3de@mail.gmail.com> <f72742de0910011632n3488ff6aqbf93edbda2a51637@mail.gmail.com> <e0b04bba0910012252v540dd170k4b81e30052e6c974@mail.gmail.com> <9b8a8de40910020144v36077295u314d34d579e21f26@mail.gmail.com> <e0b04bba0910040050g3861008er33ff2c9d0eaf054@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <e0b04bba0910040050g3861008er33ff2c9d0eaf054@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP Draft Charter - 2009 09 01
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: Sun, 04 Oct 2009 13:09:14 -0000

On Sun, Oct 04, 2009 at 08:50:43AM +0100, Morgaine wrote:
> Note that I offered one solution to this problem at the end of this post --
> http://www.ietf.org/mail-archive/web/ogpx/current/msg00451.html .  It's really
> simple, and boils down to asset services being provided entirely by the RDs. 
> RD1 provides access to the asset service AS1 (typically proxy access --- after
> all, SL's regions already work as proxies to an asset service, so it's no big
> leap), while RD2 provides access to the asset service AS2.  No AD can ever
> provide an asset service, and therefore AD2 does not need to be consulted on
> TP.

Your phrase "RD1 provides access to the asset service AS1" is slightly misleading...
It should read: "RD1 provides (proxy) access to all asset services involved".

For example, three users visit RD1, they respectively use AS1, AS2 and AS3.
Then in order to see what they wear (or rezzed) all three asset servers need
to be accessed.

-- 
Carlo Wood <carlo@alinoe.com>