Re: [mmox] The Story So Far...

"Hurliman, John" <john.hurliman@intel.com> Thu, 19 February 2009 02:34 UTC

Return-Path: <john.hurliman@intel.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2774028C1A2 for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 18:34:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.856
X-Spam-Level:
X-Spam-Status: No, score=-5.856 tagged_above=-999 required=5 tests=[AWL=-0.257, BAYES_00=-2.599, J_BACKHAIR_44=1, RCVD_IN_DNSWL_MED=-4]
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 nUHNGnnUCdLQ for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 18:34:09 -0800 (PST)
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by core3.amsl.com (Postfix) with ESMTP id 495A428C194 for <mmox@ietf.org>; Wed, 18 Feb 2009 18:34:09 -0800 (PST)
Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 18 Feb 2009 18:32:39 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.38,231,1233561600"; d="scan'208";a="432158811"
Received: from rrsmsx603.amr.corp.intel.com ([10.31.0.57]) by fmsmga002.fm.intel.com with ESMTP; 18 Feb 2009 18:30:21 -0800
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx603.amr.corp.intel.com ([10.31.0.57]) with mapi; Wed, 18 Feb 2009 19:34:22 -0700
From: "Hurliman, John" <john.hurliman@intel.com>
To: "mmox@ietf.org" <mmox@ietf.org>
Date: Wed, 18 Feb 2009 19:34:19 -0700
Thread-Topic: [mmox] The Story So Far...
Thread-Index: AcmSE8dpU9L/wpzPSUSRXAIwk5F8xgAJhJrw
Message-ID: <62BFE5680C037E4DA0B0A08946C0933D501FE4C3@rrsmsx506.amr.corp.intel.com>
References: <1E40CE05-15D1-4970-9B0F-CD4AD11A074A@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933D501FDC38@rrsmsx506.amr.corp.intel.com> <499C5415.7060400@cox.net> <62BFE5680C037E4DA0B0A08946C0933D501FE124@rrsmsx506.amr.corp.intel.com> <2bd5b7f10902181356l64dd8366n2b5e57ef4242ae0f@mail.gmail.com>
In-Reply-To: <2bd5b7f10902181356l64dd8366n2b5e57ef4242ae0f@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mmox] The Story So Far...
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2009 02:34:10 -0000

>-----Original Message-----
>From: suzyque@gmail.com [mailto:suzyque@gmail.com] On Behalf Of Suzy
>Deffeyes
>Sent: Wednesday, February 18, 2009 1:56 PM
>To: Hurliman, John
>Cc: mmox@ietf.org
>Subject: Re: [mmox] The Story So Far...
>
>
>
>On Wed, Feb 18, 2009 at 1:41 PM, Hurliman, John
><john.hurliman@intel.com> wrote:
>
>
>       The HyperGrid implementation in OpenSim today establishes a full
>trust link between two separate service stacks (grids). It's a very
>clever way of combining grids, but doesn't address how untrusted
>administrative domains interact with each other at all. I don't
>understand why you keep comparing Agent Domain and HyperGrid.
>
>       My understanding of the Agent Domain model is that it maps every
>trust relationship between grids to a policy decision. This is important
>for the business case of company X and company Y creating a partnership
>that is explicitly configured, but glazes over the 99.999% use case of
>moving from untrusted grid A to untrusted grid B. I haven't seen any
>work from AWG addressing the possibility of eliminating all grid<->grid
>communication (google.com doesn't communicate with the links I click,
>the browser is perfectly capable of managing its own state).
>
>
>For the google 2d browsing analogy, I don't need to see a representation
>of other people that also happen to be visiting that same link, and I
>also don't have a name and 3D representation of myself that I want to
>remain consistent on my screen as I go from link to link.
>
>In our MMOX space, it can be desirable to have a consistent
>representation of self that also appears the same to others in the same
>region. Not always, but for a fair number of use cases that involve
>teleportation it does. I'm not sure how that can happen if we eliminate
>all grid to grid communication.
>

"same region" and grid<->grid are separate concepts. The idea of sharing a scene graph across administrative domains is interesting, but the current agent domain work does not include anything like that. Instead, a teleport is done from grid A to grid B where identity and appearance are the only things that need to persist. I don't see why grid<->grid communication is fundamentally necessary to transfer identity and appearance.

>Maybe Agent Domain type implementations 'squirt' too much state along
>with an agent that is being transferred into a region. Maybe we need to
>tease that apart.  I think the actual OGP implementation right now just
>squirts your name, UUID, a few bits, and desired location into the
>region.
>
>Suzy Deffeyes
>IBM
>

>