Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revision

Morgaine <morgaine.dinova@googlemail.com> Mon, 31 August 2009 04:27 UTC

Return-Path: <morgaine.dinova@googlemail.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 8AD2228C17A for <ogpx@core3.amsl.com>; Sun, 30 Aug 2009 21:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.568
X-Spam-Level:
X-Spam-Status: No, score=-0.568 tagged_above=-999 required=5 tests=[AWL=-1.006, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 TqeQEfjNxZ9z for <ogpx@core3.amsl.com>; Sun, 30 Aug 2009 21:27:02 -0700 (PDT)
Received: from mail-ew0-f225.google.com (mail-ew0-f225.google.com [209.85.219.225]) by core3.amsl.com (Postfix) with ESMTP id 98DA03A6B92 for <ogpx@ietf.org>; Sun, 30 Aug 2009 21:27:01 -0700 (PDT)
Received: by ewy25 with SMTP id 25so3788067ewy.9 for <ogpx@ietf.org>; Sun, 30 Aug 2009 21:27:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=vMLOm0bX6b3kqTAZhKSO/TjVSZIm24WJigSpirqrh+Y=; b=lhJ1PdTykXM3qKX3sJHI0NNE6sWhmBQhH4+jjx0kBWtJq1ZiN3/rNZ8zfabY+DW/19 9VCfKEk9tp8eRTg+R+QPFrvdqDFsPDIE66BWhWsnL7AKD95c1XFEwGUR8bEhe89GO5Gz 5vE5ypJ5jaBNrM+7TMEeRl8vhZs0eur84NE+Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=yEzofkawFRhN3Q7uiG48pQ6DAvcaS2keXRK4AJfYLtFwA5aRr7RIPzPvf5mfZ2HYqy Nrq2fKMu+3ZEXxYJTmmE3ZArjzw9V9NDYGKvel6HUPzqJR9WE+DHjgt5/n5CYwUEdJy0 10QRbqC/0ArYcM8A71khSvjwlP6/ZPkNUA0SI=
MIME-Version: 1.0
Received: by 10.211.132.36 with SMTP id j36mr4738666ebn.51.1251692825971; Sun, 30 Aug 2009 21:27:05 -0700 (PDT)
In-Reply-To: <20090830230832.GB25364@alinoe.com>
References: <3a880e2c0908281127h6965f332na493007b032e5e93@mail.gmail.com> <20090830003055.GD22756@alinoe.com> <4A9A8F7D.6070501@dcrocker.net> <b8ef0a220908301013t29821ac5q8d03d97002bdfdb1@mail.gmail.com> <20090830230832.GB25364@alinoe.com>
Date: Mon, 31 Aug 2009 05:27:05 +0100
Message-ID: <e0b04bba0908302127u4f36b98fp81e766c2cbc6526a@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=001636b2ad56428c120472687267
Subject: Re: [ogpx] VWRAP Draft Charter: 2009 08 28 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: Mon, 31 Aug 2009 04:27:03 -0000

I support Carlo's request that we define the terms that we use before we use
them.

As Carlo's says, undefined terms should not be used in the charter or in the
group name --- it introduces uncertainty and confusion.  I would add that *even
less* should undefined terms appear in our protocol specifications, which
are relatively precise documents of interest to implementors.  If we don't
know what a virtual world is, the term should be abandoned in favour of one
that we do understand.

Carlo offers one way of defining the topological entities in our problem
space, based on size and administration, which sounds quite viable.  A
meaning of virtual world might be agreed in this way.

As an alternative, I propose a simpler and much more flexible approach:
define virtual worlds as anything that implements the required endpoints of
the VWRAP protocol.  We do not need to know anything else about them.  This
lets the people who actually design the virtual worlds decide what
constitutes a virtual world.  The only thing that interests us is that these
"virtual worlds" implement the VWRAP endpoints.

This is highly workable in practice.  After all, Linden Lab knows that SL is
a virtual world, they don't need it defined.  Likewise, the owners of OSgrid
know that OSgrid is a virtual world too, they don't need it defined.  As a
result, a definition of "virtual world" by an IETF workgroup will have
little practical effect outside of the specifications, because the
implementors will design their worlds as it suits them.  If they are to
interoperate through VWRAP however, then both LL and OSgrid will ensure that
they implement the protocol correctly, no matter their internal differences.

Note that this is the approach taken in a large number of IETF protocols:
the implementation behind the endpoint is just an *implementation detail*,
and is of no consequence as long as it implements the protocol correctly.
Precedent suggests that this is the right approach.

I believe that this is simpler, more powerful, and much more flexible than
defining "virtual world" on the basis of topology.  All we need to know is
that VWRAP endpoints are available, and not what kind of entity actually
implements them.

Morgaine.








===================================

On Mon, Aug 31, 2009 at 12:08 AM, Carlo Wood <carlo@alinoe.com> wrote:

> I think that any effort to work on the final wording
> should be stopped until we finally agree on what "virtual world" means...
>
> I understand that you don't want to define what virtual world means,
> in which case you shouldn't use it at all in the charter and also
> not in the protocol name (VWrap).
>
> There are several levels of 'locations' in an SL-like whatever:
>
> First, the words that are already in use by the community:
>
> 1) simulator
> 2) estate
> 3) region
> 4) land
> 5) island
> 6) virtual world
>
> Then the locations that we need terms for to be able to even
> TALK about them:
>
> A) A smallest partition
> B) A collection of adjacent A's run by a single administration
> C) A collection of adjecent B's run by different administrations (which
> very likely use the same TOS etc)
> D) A collection of C's that are not adjacent but still fall under the same
> TOS etc.
> E) A collection of D's that have totally different administrations and
> possibly different TOS etc, but which interoperate.
> F) The whole of all E's that do not interoperate, but still use VWRAP.
> G) The rest that use the term "virtual world", but do not use VWRAP.
>
> MMOX and WoW is part of G. I consider that not relevant as it should be
> clear by now what is part of G and what not.
>
> Meadhbh, do you disagree with my list(s)?
> Anything you want to add, or change my rough definitions of things?
>
> Please don't reply with "we don't want to define this" :p
> We NEED to define this, or we can't TALK about this!
>
> --
> Carlo Wood <carlo@alinoe.com>
>
> PS I hope it should be clear by now: the problem we are having
>   is that you call 'E' "a virtual world", while Morgaine, Kari,
>   me and others want to call 'D' "virtual world". Moreover,
>   you do as if D or E do not exist, so that we will not
>   be able to talk about them separately later on :/
>
>   You might convince me to call 'E' "virtual world", but
>   then we need a well defined term for 'D' in order to
>   communicate about D, too.
>
>   In my previous post I proposed to use "Galaxy" for E.
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>