Re: [ogpx] Proposal: Change OGPX to...

Infinity Linden <infinity@lindenlab.com> Fri, 21 August 2009 18:23 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 B035F3A6E1B for <ogpx@core3.amsl.com>; Fri, 21 Aug 2009 11:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Level:
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[AWL=0.100, 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 ok2IwcJtVcgB for <ogpx@core3.amsl.com>; Fri, 21 Aug 2009 11:23:49 -0700 (PDT)
Received: from mail-pz0-f174.google.com (mail-pz0-f174.google.com [209.85.222.174]) by core3.amsl.com (Postfix) with ESMTP id 9A7FD3A6E09 for <ogpx@ietf.org>; Fri, 21 Aug 2009 11:23:49 -0700 (PDT)
Received: by pzk4 with SMTP id 4so119260pzk.29 for <ogpx@ietf.org>; Fri, 21 Aug 2009 11:23:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.4.38 with SMTP id 38mr102336wfd.119.1250879032063; Fri, 21 Aug 2009 11:23:52 -0700 (PDT)
In-Reply-To: <4646639E08F58B42836FAC24C94624DD6FE715D7D0@GVW0433EXB.americas.hpqcorp.net>
References: <f72742de0908211026h5027c3c5y184d596b4837c165@mail.gmail.com> <4646639E08F58B42836FAC24C94624DD6FE715D7A9@GVW0433EXB.americas.hpqcorp.net> <3a880e2c0908211109o3fa668e6h27a803a97353074c@mail.gmail.com> <4646639E08F58B42836FAC24C94624DD6FE715D7D0@GVW0433EXB.americas.hpqcorp.net>
Date: Fri, 21 Aug 2009 11:23:52 -0700
Message-ID: <3a880e2c0908211123j52ba49aar547f4d224190eeef@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: "Dickson, Mike (ISS Software)" <mike.dickson@hp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ogpx@ietf.org" <ogpx@ietf.org>
Subject: Re: [ogpx] Proposal: Change OGPX to...
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, 21 Aug 2009 18:23:50 -0000

well.. fwiw... we're not baking the "grid" concept into this protocol.
it's appropriate for worlds that are grids, toroids, spheres,
cylinders or defined by a tensor field. the only requirement is that
the worlds use a 3 dimensional vector to denote locations in the world
and that the world is piecewise smooth.

but yes. in non-grid cases, both the client and the server would have
to agree a priori what the shape of the world is, and all the current
participants are only defining grid-based worlds. so your point is
definitely valid.

at this point i don't know that i care what the name is as long as we
can reach consensus and the name isn't confusing.

On Fri, Aug 21, 2009 at 11:12 AM, Dickson, Mike (ISS
Software)<mike.dickson@hp.com> wrote:
> Well, that's why I qualified it with the VW first.   :-)
>
> So I actually think the grid part *is* appropriate since SL and the worlds being modeled are laid out in one. As opposed say to Activeworlds or Croquet which are more portal based.
>
> So I understand wanting to avoid the confusion with the general grid term but in this case I actually think Grid is important.  OGP is confusing since its not descriptive enough.  I was hoping with the VWGP thingy you're essentially describing exactly what it is. A virtual world protocol for worlds laid out in a grid.
>
> Mike
>
> -----Original Message-----
> From: Infinity Linden [mailto:infinity@lindenlab.com]
> Sent: Friday, August 21, 2009 1:09 PM
> To: Dickson, Mike (ISS Software)
> Cc: Joshua Bell; ogpx@ietf.org
> Subject: Re: [ogpx] Proposal: Change OGPX to...
>
> 'cause we're trying to avoid the word "grid."
>
> before the F2F in stockholm, i was one of the most vocal proponents
> for keeping OGP. we had a fair amount of history with the name, and i
> thought it made sense to keep the name to avoid the confusion a new
> name would bring.
>
> right before the BoF, i remember Dave Crocker (and maybe others)
> saying something like "you know... some people are going to think this
> is not a virtual worlds protocol, but one for provisioning services
> and managing a grid or cloud."
>
> my response was (and i'm paraphrasing here,) "nonsense! everyone reads
> every word of every working group charter and knows what every other
> group is working on!"
>
> immediately after the BoF, someone came up and said.. "yeah. that was
> an interesting BoF, but i thought it would be a discussion of managing
> grids, you know, regular grids."
>
> so. yes. i have eaten a bit of crow and am now a convert to the idea
> that the term "grid" in the group or protocol name is confusing since
> the protocol we're defining could work on a grid, a cloud, a cluster
> or even a single host (for a small virtual world.)
>
> -cheers
> -meadhbh
>
> On Fri, Aug 21, 2009 at 10:56 AM, Dickson, Mike (ISS
> Software)<mike.dickson@hp.com> wrote:
>> How about VWGP.  "Virtual World Grid Protocol".
>>
>> Mike
>>
>> -----Original Message-----
>> From: ogpx-bounces@ietf.org [mailto:ogpx-bounces@ietf.org] On Behalf Of Joshua Bell
>> Sent: Friday, August 21, 2009 12:27 PM
>> To: ogpx@ietf.org
>> Subject: [ogpx] Proposal: Change OGPX to...
>>
>> Hey gang,
>>
>> One of the charter issues we identified coming out of Stockholm was
>> the name (for both the group and protocol suite). Open Grid Protocol
>> (OGP)" is historical, used to describe interop trials from 2008, and
>> the name was carried forward to the BoF/mailing list (with an "X" for
>> good measure). Linden Lab employees, OpenSim developers and Second
>> Life residents frequently use the term "grid" to describe the
>> collection of systems responsible for providing virtual world
>> services, even if that set of systems would more accurately be
>> described by the terms "cluster" or "cloud" (or term-of-the-week...),
>> playing off the grid-like organization of regions on a map.
>>
>> We received repeated feedback that "grid" was confusing, both on the
>> list and at Stockholm, in the broader context of the IETF. This was
>> underscored by at least one person who attended the OGPX BoF in
>> Stockholm saying they anticipated hearing a discussion about grid and
>> cloud computing services.
>>
>> A few alternatives to OGP have been offered, such as "Region Access
>> Protocol (RAP)" and "Agent / Region Interaction Protocol (ARIP)". The
>> former discounts the importance of the agent oriented aspects of the
>> protocol, the latter discounts the "access" aspect of the protocol
>> which underscores the RESTful nature of the conceptual objects on
>> either end of a protocol transaction.
>>
>> From off-list discussions, here are some new suggestions:
>>
>> * "Agent Based Open Virtual Environments (ABOVE)" - (as a group name?)
>> * "Open Virtual Entity and Region (OVER)" - (as a protocol name?)
>>
>> These have the advantage of being concise, fairly accurate,
>> pronounceable, keeping "Virtual" in the name, slightly "cute" but not
>> overly so. They are not humorous or ironic and don't reference
>> pop-culture. They don't overload "IP" (yay) and avoid "P" in the name
>> (the dreaded "ATM machine" syndrome.)
>>
>> Taking these as serious suggestions, could we get rough consensus on
>> either/both of these? Last call for objections/alternatives?
>>
>> (To maintain continuity of discussion, we should keep the OGPX mailing
>> list and other trappings until an actual working group is chartered.)
>> _______________________________________________
>> 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
>>
>