Re: [ogpx] OGPX WG draft charter, 2009-08-19 revision

Infinity Linden <infinity@lindenlab.com> Thu, 20 August 2009 20:42 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 913CE28C123 for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 13:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.815
X-Spam-Level:
X-Spam-Status: No, score=-1.815 tagged_above=-999 required=5 tests=[AWL=0.162, 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 17rKk+N9PfGZ for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 13:42:10 -0700 (PDT)
Received: from mail-px0-f171.google.com (mail-px0-f171.google.com [209.85.216.171]) by core3.amsl.com (Postfix) with ESMTP id B13203A6CF5 for <ogpx@ietf.org>; Thu, 20 Aug 2009 13:42:10 -0700 (PDT)
Received: by pxi1 with SMTP id 1so3873601pxi.31 for <ogpx@ietf.org>; Thu, 20 Aug 2009 13:42:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.138.7 with SMTP id q7mr17898wfn.314.1250800934547; Thu, 20 Aug 2009 13:42:14 -0700 (PDT)
In-Reply-To: <e0b04bba0908201319v14cfeaa6k615ef8c8485dd09a@mail.gmail.com>
References: <f72742de0908191206m2a5b3e2fm4efcf0eaf471a758@mail.gmail.com> <e0b04bba0908191914h4837045ct777d2c63a30ddaf0@mail.gmail.com> <3a880e2c0908191925p506de284w5ebb5cab7d893256@mail.gmail.com> <e0b04bba0908192003p34a367f2q4b99be3cf916cd72@mail.gmail.com> <20090820141835.GB28751@alinoe.com> <b8ef0a220908201054y4139c43cm4b7429c8346e961@mail.gmail.com> <e0b04bba0908201319v14cfeaa6k615ef8c8485dd09a@mail.gmail.com>
Date: Thu, 20 Aug 2009 13:42:14 -0700
Message-ID: <3a880e2c0908201342n50dd18e0o19a30722fc1847dd@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ogpx@ietf.org
Subject: Re: [ogpx] OGPX WG draft charter, 2009-08-19 revision
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, 20 Aug 2009 20:42:11 -0000

morgaine, let's let carlo speak for carlo. -thx

On Thu, Aug 20, 2009 at 1:19 PM, Morgaine<morgaine.dinova@googlemail.com> wrote:
> Meadhbh is once again misrepresenting people:
>
> On Thu, Aug 20, 2009 at 6:54 PM, Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
> wrote, in answer to Carlo:
>>
>> Are you seriously suggesting that Linden Lab should not participate in
>> the development of an open virtual worlds protocol? wha?
>
> No, Carlo did not suggest that.  Carlo simply asked for an answer on whether
> OGP would also cover interop between more than one virtual world.  Joshua's
> latest group charter does not list such communication in the scope of OGPX,
> and therefore Carlo's question is a good one.
>
>  I have also been misrepresented, but that is of no matter compared to
> getting the scope of OGPX clarified cleanly and openly, so that we know
> exactly what the protocol will be specified to do and what it will not
> address.
>
>
> Morgaine.
>
>
>
>
>
>
>
>
>
> On Thu, Aug 20, 2009 at 6:54 PM, Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
> wrote:
>>
>> Are you seriously suggesting that Linden Lab should not participate in
>> the development of an open virtual worlds protocol? wha?
>>
>> We originally wanted to have a working group where we could resolve
>> issues that separate different virtual worlds protocols. That group
>> was MMOX, and at the BoF we couldn't even get agreement as to what the
>> term "interoperable" meant.
>>
>> Because we could not get agreement, this effort (OGPX) was initiated.
>> Our objective is NOT to define a protocol that encompasses every
>> existent virtual world. It is to produce a protocol that may be used
>> by deployers to produce one, two or many distinct virtual worlds.
>> Deployers would then get to decide which virtual worlds they wish to
>> interact with. They may also choose to provide access to some or all
>> of their "virtual real estate" to other participants through a
>> federation scheme. This latter use case is considered the most common
>> use case, because it allows virtual worlds deployers to share part of
>> their world without requiring them to share ALL of their world.
>>
>> Morgaine has several times mentioned she does not agree with the
>> approach we are taking. I do not apologize that those of us who
>> organized the MMOX and OGPX BoFs have requirements different from
>> hers. Nor do I apologize for taking the "let's boil the ocean one
>> thimble at a time," approach. At the end of the day, there are people
>> interested in deploying open virtual worlds, that are implemented
>> using an open protocol. If people wish to participate constructively
>> in this effort with us, we will participate with them. If people wish
>> to discount the experience of over six years of deploying virtual
>> worlds, and a business model that DEPENDS on providing services to
>> others, they can participate in other standardization efforts.
>>
>> -Cheers
>> -Meadhbh / Infinity
>>
>>
>>
>>
>> On Thu, Aug 20, 2009 at 7:18 AM, Carlo Wood<carlo@alinoe.com> wrote:
>> >
>> > I think that what Morgaine is trying to say is that
>> > if Linden Lab's official (or hidden) policy is to NOT
>> > interop with other virtual worlds, then they are not
>> > the right party to trust when it comes to defining
>> > a protocol that most, if not all, other parties DO
>> > want to support interop.
>> >
>> > Since it seems, at this point, that the policy of
>> > LL will prohibit interop in the future between
>> > SL and other grids, there is a lack of trust right now;
>> > and as a result of that lack of trust, a very clear
>> > statement about the intent of the OGPX (as opposed to LL)
>> > about interop MUST be part of this draft.
>> >
>> > Personally, I will reject any protocol that doesn't
>> > make it a priority to concentrate on interoperability
>> > (such as sharing LM's and teleporting). So, instead
>> > of adding a paragraph that clearly states that the
>> > objective of OGPX is to not support interop, I'd rather
>> > see a paragraph added that clearly states that it
>> > IS to support interop.
>> >
>> > The keyword here being "clearly". That is certainly
>> > not the case at the moment.
>> >
>> > --
>> > Carlo Wood <carlo@alinoe.com>
>> > _______________________________________________
>> > ogpx mailing list
>> > ogpx@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ogpx
>> >
>
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>