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

Meadhbh Siobhan <meadhbh.siobhan@gmail.com> Fri, 21 August 2009 00:16 UTC

Return-Path: <meadhbh.siobhan@gmail.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 187893A6F31 for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 17:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Wh7VyuY7LZzZ for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 17:16:09 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by core3.amsl.com (Postfix) with ESMTP id D02F23A6F24 for <ogpx@ietf.org>; Thu, 20 Aug 2009 17:16:06 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 5so226995qwi.31 for <ogpx@ietf.org>; Thu, 20 Aug 2009 17:16:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/l35BlAUo8jNmpNaVHWqY8YEUoaHpfg6w1eX2bheRm0=; b=KpnuKCYecrqamQz69F6khObm7CZjsBaYecm6pOF02sjNpIjNFpzQ7c1qmKWWHV32qH CTEcTR2ZS71AHc0AfZUEGNpEF1XaKHZPuKaennpVYfjbTmOjm2b/4X6yOI/UTpaHdtHb 3w3QJ4+vWn9GzH8MMrb3JZ+jNnaELY4mIRBf4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=E+kQaALjyC2fz0wMsChXN9M8hwuoGCAOldqPmq/6FIhBBBYidRQBC0SsAVxP9odBaZ 4iBCiUUjePCeseBE10roNgb732XgkdRrT5vZTHuyq5bVjoSW/ryBQ6KmwPMudVSNJljs Fzc8ekiLxeIYtkKzOucUvzKqtknlkMglNJX74=
MIME-Version: 1.0
Received: by 10.229.111.195 with SMTP id t3mr80934qcp.44.1250813769987; Thu, 20 Aug 2009 17:16:09 -0700 (PDT)
In-Reply-To: <20090820235051.GA21280@alinoe.com>
References: <f72742de0908191206m2a5b3e2fm4efcf0eaf471a758@mail.gmail.com> <3a880e2c0908191925p506de284w5ebb5cab7d893256@mail.gmail.com> <e0b04bba0908192003p34a367f2q4b99be3cf916cd72@mail.gmail.com> <20090820141835.GB28751@alinoe.com> <b8ef0a220908201101g3b448d8ck7b406fc481c56f8d@mail.gmail.com> <e0b04bba0908201342hd17ce91qac0136124cd3a444@mail.gmail.com> <f72742de0908201426m6b8feac9v57e9ef1cd73e5c06@mail.gmail.com> <f72742de0908201600y46311454la8db52c4be1b18dc@mail.gmail.com> <b8ef0a220908201609m1c77be2n3d499b7da20fec5a@mail.gmail.com> <20090820235051.GA21280@alinoe.com>
Date: Thu, 20 Aug 2009 17:16:09 -0700
Message-ID: <b8ef0a220908201716o67740c2emde12dbc29c73608c@mail.gmail.com>
From: Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
To: Carlo Wood <carlo@alinoe.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: Fri, 21 Aug 2009 00:16:10 -0000

carlo. i think we're on the same page here with respect to the
definition of the term "world." part of the confusion may stem from
the fact that radically similar discussions came up in the MMOX
effort.

one of the objectives of the OGP protocol is to allow a virtual world
to be constructed from regions, agent hosts and asset servers from
different administrative domains. in order to do that, one of the
things we think we need to do is to have a scheme by which regions are
unambiguously identified with a URL. we don't currently list
"unambiguous landmarks" in the charter because we don't talk about
landmarks at all in the charter. it's also unclear whether a landmark
format will be defined as part of this effort.

that being said, if you have an unambiguous URL that addresses a
region, you could use that as the basis for a landmark quite easily.
remember that we're only specifying the protocol in this effort, not
the application that uses it. protocol messages that carry landmarks
aren't in-scope because we're not defining a service that will produce
or consume them.

however... i think you bring up a good point, we could be more
explicit about including the "unambiguous URL defines a region" thing
in the charter. This would put it in-scope and would allow app
developers to define their own landmark format that leverages it.

so i guess what i'm saying is that if we listed "a format for
unambiguous landmarks" in the charter, shouldn't we also list other
Second-Life-like features like the C/M/T permissions system? the
unambiguous URL representing a region is required for proper operation
of teleport, which IS in scope, but the unambiguous landmark format is
not required as landmarks are concepts more appropriately manipulated
by client applications.

so, is it enough to add verbiage to the charter indicating that the
protocol requires regions to be addressable by unambiguous URLs, but
not explicitly constrain their use in the charter?

-cheers
-meadhbh

On Thu, Aug 20, 2009 at 4:50 PM, Carlo Wood<carlo@alinoe.com> wrote:
> I'm feeling a bit dizzy of all the terminology :p
> And, I'm still not sure if I understand it: it's still unclear.
>
> Perhaps we'll just have to use hard examples on this mailinglist
> first to make things clear, and only then we can think about
> ways to achieve the same clearness in more abstract terms.
>
> ---
>
> 1) Right now, there is 'Second Life', and there are several
>   opensim worlds that are very very like Second Life. Never I
>   am refering to or even thinking about WoW.
>
> 2) Right now, therefore, we can call those entirely separated
>   administrative domains, different "worlds", as has been
>   done in the past several years.
>
>   We might want to change that terminology, but let me use
>   "world" to refer the currently existing different worlds,
>   where "Second Life" is one of them and -say- "opengrid X" is
>   another.
>
> 3) These worlds are separated in EVERY way:
>   - You cannot teleport bewteen them.
>   - There is no notion of Landmarks that refer outside a given world.
>   - You cannot send IM's to avatars in the other world.
>   - You cannot access any asset (or inventory) of another world.
>
> 4) I thought that the OGPX effort had as goal to change this
>   *complete* separation.
>
> However, if we want to make these limitations vanish then they
> cannot be used to DEFINE what (separate) world mean... Hence,
> the term becomes undefined and unclear (in the future).
>
> But-- there are things that define the "worlds" that do NOT
> want to change:
>
> * The administration is entirely different:
>  - A TOS only applies to one world.
>  - An Abuse Report only has effect within one virtual world.
>  - A ban by such an administration only affects their own world.
>
> I think that most ideal situation would be when it is entirely
> and only the user that decides if they want to visit another world,
> completely independent of which world that is (as they can now
> by simply logging out, and logging in elsewhere).
>
> This CAN be supported; but it would mean to both region domain
> AND agent domain (in order to switch completely between administrations etc).
>
> Of course, viewers could simply support a seemless logout and login
> elsewhere, but we (the users) want support for this in the format
> of LandMarks, so that it is relatively easy to invite someone to
> that other place, in another world.
>
> Trivially, however, two major annoyances arrise with such a simple sheme:
>
> * The need to create a new account (avatar name / password)
> * Complete loss of access to inventory:
>  - loss of shape, skin, clothes and attachments during teleport
>  - loss of everything else in the inventory
>
> If I'm correct then the latter has everything to do with the
> agent domain; thus, if someone would stay in the same agent domain
> (ie, one run by Linden Lab), then one would not need to create a
> new account, would not need to logout and re-login, would not
> lose appearance or inventory.
>
> The question remains now:
>
> how will that affect the ideal solution? Because to the user those
> worlds will suddenly appear to be a single world.
>
> What if a griefer logins in with LL, teleports to opengrid X and
> halts a sim there by running 10,000 scripts in attachments.
>
> Whose TOS determines if that is allowed? I'd say opengrid X's tos.
> And if opengrid X's TOS does not allow halting a sim, then where does
> an Abuse Report go to? I'd say... still to opengrid X's administration.
> And when they decide to ban this person, will it be possible to
> ban that (LL) account from opengrid X?
>
> These questions are not trivial, but of utmost importance (yes,
> also for the protocol): any and all administrative issues should
> be a case of the administration of the *region* one is in, and
> never of the agent domain someone belongs to.
>
> As a result, an agent domain shouldn't care less where someone
> wants to go, because they are never responsible, and therefore
> it should NOT be a matter of policy where someone can or cannot
> teleport while keeping their inventory: it should simply be
> possible, because the address is given in the LandMark.
>
> --
> Carlo Wood <carlo@alinoe.com>
>