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

Morgaine <morgaine.dinova@googlemail.com> Fri, 21 August 2009 02:16 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 375B73A68D0 for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 19:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.876
X-Spam-Level:
X-Spam-Status: No, score=-1.876 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, 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 btiXksIDoryO for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 19:16:49 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by core3.amsl.com (Postfix) with ESMTP id 4B6223A6B4F for <ogpx@ietf.org>; Thu, 20 Aug 2009 19:16:49 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 22so121473eye.31 for <ogpx@ietf.org>; Thu, 20 Aug 2009 19:16:47 -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=wMLJspVUy8IWSY4AlgxliZr3AIgM3m+A5T8In7nAqYI=; b=FPwXpN4QSUTFwsW+0V0fKGjgH8frr/oRycLznFv/t52R3nmDhnL5I3gdPA3wdK88+N IqNoefwAPhPQS4ItW24bKFadee9wHbsDt7YzhtMFYi3I4BNxKy4dak3W7Seq5O7Ke+er AHtGW4zKsfKqCLnzSGhRoRwLNdEPFYnUF6aws=
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=QngR4yDMO7fryZqyzqR0A0aAT5fIHyTdbgVO8ouw0QHyOVJz5XYurf9dCs5OgDPfa2 as4McjPdz1lc3/v/tePjBDo9dy/mHo3eYez/PViuHmDt4WeobqRsafXZgamoKSVzLeT8 8eqm9Y572DdF4AOPnGA7dB8V0i3ubbXNT/Ri4=
MIME-Version: 1.0
Received: by 10.210.117.4 with SMTP id p4mr661065ebc.7.1250821006904; Thu, 20 Aug 2009 19:16:46 -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: Fri, 21 Aug 2009 03:16:46 +0100
Message-ID: <e0b04bba0908201916w30e40df3vde60a7e1eda14169@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0015174c336ecb4f5804719d75ef
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 02:16:51 -0000

Carlo has expressed the issue perfectly in his post.

This isn't merely about a choice of words, it's a matter of actual
functionality.  Given two SL-compatible virtual worlds each comprising
multiple regions, either OGP provides a mechanism for teleporting from a
region in the first world to a region in the second world, or it doesn't.

Many things go along with cross-world teleports of course.  Cross-world
landmarks is one issue, continuity of inventory while in compatible worlds
is another, and so on.

While the details are of course complex to work out, at the heart of it is a
very simple question about goals, and it deserves a clear answer.  Will OGP
provide interop between SL-compatible virtual worlds, or is that not
intended OGP functionality?

 We need to know what is in scope for OGPX, because that scope determines
our discussions, our implementations, our deliverables and our timelines.

Morgaine.








On Fri, Aug 21, 2009 at 12:50 AM, 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>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>