Re: [vwrap] Statements of Consensus. Flexibity First.

Mike Dickson <mike.dickson@hp.com> Wed, 30 March 2011 20:50 UTC

Return-Path: <mike.dickson@hp.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E54073A6A88 for <vwrap@core3.amsl.com>; Wed, 30 Mar 2011 13:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.369
X-Spam-Level:
X-Spam-Status: No, score=-102.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qAYZJqm4SQR5 for <vwrap@core3.amsl.com>; Wed, 30 Mar 2011 13:50:12 -0700 (PDT)
Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.123]) by core3.amsl.com (Postfix) with ESMTP id E3CA63A68F4 for <vwrap@ietf.org>; Wed, 30 Mar 2011 13:50:11 -0700 (PDT)
X-Authority-Analysis: v=1.1 cv=2pE2Kh9Ye2ywHyyFZnC5ZQ1FvuPrdOtuPO5uN4ysVDU= c=1 sm=0 a=SNAFxGGoWQUA:10 a=IkcTkHD0fZMA:10 a=E1l+YgTSNfk5lq7wdBf7xA==:17 a=LeL_1veySWJvqq29JRgA:9 a=WO51YaM9RJ7fwHycNDwo2kyaWqcA:4 a=QEXdDO2ut3YA:10 a=E1l+YgTSNfk5lq7wdBf7xA==:117
X-Cloudmark-Score: 0
X-Originating-IP: 174.100.47.252
Received: from [174.100.47.252] ([174.100.47.252:59137] helo=[192.168.0.101]) by cdptpa-oedge03.mail.rr.com (envelope-from <mike.dickson@hp.com>) (ecelerity 2.2.3.46 r()) with ESMTP id 03/F5-05159-6E7939D4; Wed, 30 Mar 2011 20:51:50 +0000
From: Mike Dickson <mike.dickson@hp.com>
To: Morgaine <morgaine.dinova@googlemail.com>
In-Reply-To: <AANLkTinEKD7478BF4o-xe22XAtD5mJJejRV8g2GBq7oY@mail.gmail.com>
References: <20110330011458.GB8908@alinoe.com> <4D931434.2030206@boroon.dasgupta.ch> <4646639E08F58B42836FAC24C94624DD92FDE22F3F@GVW0433EXB.americas.hpqcorp.net> <AANLkTimaA3qcKOUUjQzvq86R1UMvamTc4yJh4NBMp_Gq@mail.gmail.com> <1301499645.12359.10.camel@mdickson-hplinux> <AANLkTimPvnysbzkwyUuq6PVrjo5x1ngo04ifv7FSz+D+@mail.gmail.com> <4D936C33.2020602@gmail.com> <AANLkTinEKD7478BF4o-xe22XAtD5mJJejRV8g2GBq7oY@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 30 Mar 2011 16:51:42 -0400
Message-ID: <1301518302.12359.27.camel@mdickson-hplinux>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14)
Content-Transfer-Encoding: 7bit
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] Statements of Consensus. Flexibity First.
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 20:50:14 -0000

On Wed, 2011-03-30 at 18:07 +0000, Morgaine wrote:
> No Dzonatas, that's not enough to handle the requirement.
> 
> When I TP from world X to world Y (which I may never have visited
> before), my identity, avatar and clothing need to persist across the
> teleport, and the elements that I carry with me (such as clothing) may
> come from many different worlds which I have visited previously, and
> be served from their individual asset services while I'm away touring
> in world Y.

And the content you carry with you may be scripted with state that needs
to be propogated. And physical objects (if there is such a thing on teh
target, may behave differently,... etc...).   Oh yeah, and some content
providers may not permit content on certain grids.  

The problem you want to solve is, at present, intractable.  There are
solvable ones that moves us in the right direction. If we take those
steps just maybe we can solve the harder problems.  If you make the
problem impossible then we never make progress.  This is BTW the
different IMO between VW interop and service level interop.  To do the
latter I don't need to insure exactly the same behavior across
platforms. Just that I can share some service definitions and therefore
identity, content, etc.  And that to me is a good start.

Mike