Re: [ogpx] Tourist use case

Morgaine <morgaine.dinova@googlemail.com> Fri, 16 October 2009 12:00 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 7661628C20B for <ogpx@core3.amsl.com>; Fri, 16 Oct 2009 05:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.293
X-Spam-Level:
X-Spam-Status: No, score=-1.293 tagged_above=-999 required=5 tests=[AWL=0.683, 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 6yDqVcm5RODB for <ogpx@core3.amsl.com>; Fri, 16 Oct 2009 05:00:11 -0700 (PDT)
Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by core3.amsl.com (Postfix) with ESMTP id B016428B23E for <ogpx@ietf.org>; Fri, 16 Oct 2009 05:00:10 -0700 (PDT)
Received: by ewy4 with SMTP id 4so1494125ewy.37 for <ogpx@ietf.org>; Fri, 16 Oct 2009 05:00:12 -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:cc:content-type; bh=hYYHtph4FuF9H5+JqLn5rPyWjSjB8qhCzG9aMoiJOiA=; b=h/mM6RoS1vkxq/sjPeMM/JbGcwOv+X1FsO3z3F+J2JKOhNWOS13dFSyhK5qg/EAiMF WZHh8qa2jBxrTiIb9a4mVq2rqDu5IHfoUpsz5Fzwst2NPJqYzr1QmH19wmBAlvVNgBD1 aqKgJut1XBB+fRO6kc2I094hVtOwQUaZLShxY=
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 :cc:content-type; b=CBK/NW4w9TCZzRn5c2DLCUSjNQB3YMYaWbBp2vdG5Z/GyNlQLkmKf8HDCA1QmNy/8N htM7l1i1yfOMqqXRRnF5ekvRinoUcrbGH3Z79C3Belak8nAjLycor1LtVt2OMoWQZ//j EZgyevv7PNZDPBDl3g4eGw04X/ESUJdzO7KLE=
MIME-Version: 1.0
Received: by 10.211.155.16 with SMTP id h16mr1456464ebo.55.1255694412117; Fri, 16 Oct 2009 05:00:12 -0700 (PDT)
In-Reply-To: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com>
References: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com>
Date: Fri, 16 Oct 2009 13:00:12 +0100
Message-ID: <e0b04bba0910160500o272f2976ldeae866912deba1a@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: Vaughn Deluca <vaughn.deluca@gmail.com>
Content-Type: multipart/alternative; boundary=00504502c9e06177de04760c233e
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Tourist use case
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, 16 Oct 2009 12:00:12 -0000

Vaughn,

You've correctly represented my MMOX post, thanks!  (
http://www.ietf.org/mail-archive/web/mmox/current/msg01392.html )

I must stress, as you did yourself, that the "*Free Worlds Tourist*" use
case which I described there in MMOX is *different * to the simpler "tourist
use case" which we have been discussing here.  It's great that you're
shining some light into this corner.  Hopefully this will allow us to affix
labels to the various cases to keep our discussions simple yet clear.

Before addressing your actual point, I should first state that I consider it
unfortunate that the "*Free Worlds Tourist*" use case is not considered an
integral part of VWRAP requirements --- this is a practical conclusion on my
part.  On the basis of our discussions so far, I think it would be too much
to expect that a mode of operation offering such a high degree of freedom of
travel and of avatar appearance would achieve rough consensus in the group,
given that its considerable distance from Second Life policies would almost
certainly lead to intense opposition.  This is not a battle I wish to fight.

As a practical matter then, "*Free Worlds Tourist*" as defined above is not
a use case that I am pushing in VWRAP at this time, despite it being
entirely compatible with the SL/Opensim model and hence deserving
inclusion.  I'm simply going to express regret that it is likely to be a
bridge too far on political grounds and leave it at that.  I would wish it
were otherwise.

With that disclaimer, I'll answer your point about our more constrained
"tourist use case" (which perhaps needs a better name), this being a much
easier target but still a very useful one.  I will however answer it in the
immediately following post, because I don't want to get this confused with
the "*Free Worlds Tourist*" case that I described in MMOX.


Morgaine.





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

On Fri, Oct 16, 2009 at 8:34 AM, Vaughn Deluca <vaughn.deluca@gmail.com>wrote;wrote:

> The "tourist use case" has been brought up several times, but the concept
> is not always used in the same way, and needs to be more precisely defined.
>
> Morgaines original definition of the "Free Worlds Tourist use case" in
> http://www.ietf.org/mail-archive/web/mmox/current/msg01392.html
> mentions two characteristics:
>
> 1. Travel requires no prior arrangement.
>  2. Your avatar is defined by you, not by the target worlds, and it
> appears in those worlds with no prior arrangement.
>
> Point 1 is only dependent the policies of the users AD as well as that of
> the destination region. It is not dependent on the protocol, so in principle
> solved.
>
> The second point is actually extending the SL use case beyond what is in my
> view needed for a basic tourist model (and that is why the post was in the
> mmox list).  In my view  a basic tourist use case has two main
> characteristics:
>
> 1.  Travel requires no prior arrangement.
>         2.  Agent domains can use external asset services
>
> Point 2 requires that assets services expose an interface (in the current
> ogp description of the AD that is not the case).
>
> Note that this models does *not* assumes that all assets in a services
> should be useable by the agent in all domains, but only that an interface is
> available so an asset service in one domain can be contacted by another AD.
>
> I think exposing the asset service interface directly is essential for
> meaningful interop.  I think it would benefit the discussion if some
> diagrams were added to http://wiki.secondlife.com/wiki/Structural_Designand/or to the VWRAP wiki to document this possibility.
>
> -Vaughn
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>