Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revision
Carlo Wood <carlo@alinoe.com> Sun, 30 August 2009 00:29 UTC
Return-Path: <carlo@alinoe.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 AB80A3A68DC for <ogpx@core3.amsl.com>; Sat, 29 Aug 2009 17:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.375
X-Spam-Level:
X-Spam-Status: No, score=-1.375 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 BYdGSw2df49U for <ogpx@core3.amsl.com>; Sat, 29 Aug 2009 17:29:45 -0700 (PDT)
Received: from viefep14-int.chello.at (viefep14-int.chello.at [62.179.121.34]) by core3.amsl.com (Postfix) with ESMTP id 456B33A67E5 for <ogpx@ietf.org>; Sat, 29 Aug 2009 17:29:42 -0700 (PDT)
Received: from edge05.upc.biz ([192.168.13.212]) by viefep14-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090830002947.EJQM29725.viefep14-int.chello.at@edge05.upc.biz>; Sun, 30 Aug 2009 02:29:47 +0200
Received: from mail9.alinoe.com ([77.250.43.12]) by edge05.upc.biz with edge id aQVj1c05G0FlQed05QVlRs; Sun, 30 Aug 2009 02:29:47 +0200
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1MhYJr-00071I-G2; Sun, 30 Aug 2009 02:30:55 +0200
Date: Sun, 30 Aug 2009 02:30:55 +0200
From: Carlo Wood <carlo@alinoe.com>
To: Infinity Linden <infinity@lindenlab.com>
Message-ID: <20090830003055.GD22756@alinoe.com>
References: <3a880e2c0908281127h6965f332na493007b032e5e93@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3a880e2c0908281127h6965f332na493007b032e5e93@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP Draft Charter: 2009 08 28 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: Sun, 30 Aug 2009 00:29:46 -0000
On Fri, Aug 28, 2009 at 11:27:08AM -0700, Infinity Linden wrote: > Adjacent locations in virtual worlds accessible by this protocol may > be explicitly partitioned into "regions" to facilitate the > computational and communication load balancing required to simulate > the virtual environment. Such virtual worlds may consist of regions > administered by distinct organizations. Though these virtual worlds > may be partitioned, they remain "un-sharded;" all inhabitants and > objects in a particular location in a virtual world may initiate > interaction with all other inhabitants and objects in that location; > and, service endpoint addresses refer to at most one location. The > state of a virtual world is independent of the client applications > that access it and may persist between user sessions. Going with the definition that "virtual world" is from the perspective of the user (every place reachable), I think that using "a virtual world" is less confusing, and I'd rewrite the above paragraph as follows: Adjacent locations in a virtual world accessible by this protocol may be explicitly partitioned into "regions" to facilitate the computational and communication load balancing required to simulate the virtual environment. Such a virtual world may consist of regions administered by distinct organizations. Though virtual worlds may be partitioned, they remain "un-sharded;" all inhabitants and objects in a particular location in a virtual world may initiate interaction with all other inhabitants and objects in that location; and service endpoint addresses refer to at most one location. The state of a virtual world is independent of the client applications that access it and may persist between user sessions. (also removed the comma after 'and'). > Regions and services implemented according to the specifications may > be deployed by separate organizations with varying policies and trust > domains. The OGPX protocols will provide the mechanisms for these s/The OGPX protocols/VWRAP/ > virtual world services to interoperate, when permitted by policy and > shared trust domains. To support the exegesis of the specifications, > the group may define a non-exhaustive set of non-normative policies > protocol participants may enforce. s/protocol/that protocol/ > > The protocol should describe interaction semantics for these virtual > worlds, independent of transport, leveraging existing standards where Idem, in order to not confuse people in thinking that the collection of all reachable regions exists of multiple virtual worlds, I'd use "a virtual world" here. Thus: The protocol should describe interaction semantics for the regions of a virtual world independent of transport, leveraging existing standards where > practical. It should define interoperability expectations for server > to server interactions as well as client-server interactions. Though > the protocol is independent of transport, early interoperability > trials used HTTP(S) for non-real-time messages. The working group will > define specific features that must be replicated in other transports > and will define the use of HTTP(S) as a transport of protocol > messages. > > Foundational components of the protocol include the publication of: > > * an abstract type system, suitable for describing the application > protocol in an implementation neutral manner, > > * a security model describing trust relationships between > participating entities, > > * guidelines for the use of existing authentication and > confidentiality mechanisms, > > * an application-layer protocol for establishing the user's avatar > in a virtual world, > > * an application-layer protocol for moving a user's avatar between > adjacent and remote locations in a virtual world, > > * format descriptions for objects and avatars in a virtual world, and > > * an application-layer protocol for identifying agents, and > requesting information about them. > > The protocol defined by this group will carry information about the > virtual environment, its contents and its inhabitants. It is an > application layer protocol, independent of transport, based partially > on these previously published internet drafts: > > * http://tools.ietf.org/html/draft-hamrick-ogp-intro > * http://tools.ietf.org/html/draft-hamrick-llsd > * http://tools.ietf.org/html/draft-hamrick-ogp-auth > * http://tools.ietf.org/html/draft-hamrick-ogp-launch > * http://tools.ietf.org/html/draft-lentczner-ogp-base > * http://tools.ietf.org/html/draft-levine-ogp-clientcap > * http://tools.ietf.org/html/draft-levine-ogp-layering > > Goals and Milestones: > > * October 2009 "Introduction and Goals" to the IESG as an > Informational RFC > > * October 2009 "Abstract Type System for the Transmission of Dynamic > Structured Data" to the IESG as Proposed Standard > > * October 2010 "Foundational Concepts and Transport Expectations" to > the IESG as Proposed Standard > > * February 2010 "Guidelines for Host Authentication" to the IESG as > an Informational RFC > > * February 2010 "Service Establishment" to the IESG as Proposed > Standard > > * February 2010 "Client Application Launch Message" to the IESG as > an Informational RFC > > * February 2010 "Simulation Presence Establishment" to the IESG as > Proposed Standard > > * June 2010 "Primitive Object Format" to the IESG as Proposed > Standard > > * June 2010 "Digital Asset Access" to the IESG as Proposed Standard > > * June 2010 "Entity Identifiers" to the IESG as Proposed standard However, I remain sceptical about the lack of stressing the importance of making interop possible as much as possible between regions where little overlap in ToS exist, or only partial trust exists. Imho, the whole effort of this group is meaningless unless the end result will make it possible for many independent parties to take part in creating one big virtual world. The more (policy) restrictions are *necessary* for an acceptable interop, the less this effort will have succeeded; hence, it should be an important, of not the most important goal of this working group! -- Carlo Wood <carlo@alinoe.com>
- [ogpx] VWRAP Draft Charter: 2009 08 28 revision Infinity Linden
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Joshua Bell
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Infinity Linden
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Carlo Wood
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Kari Lippert
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Carlo Wood
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Carlo Wood
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Carlo Wood
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Kari Lippert
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Dave CROCKER
- [ogpx] one virtual world, or many? Dave CROCKER
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Dave CROCKER
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] one virtual world, or many? Kari Lippert
- Re: [ogpx] one virtual world, or many? Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Kari Lippert
- Re: [ogpx] one virtual world, or many? Meadhbh Siobhan
- Re: [ogpx] one virtual world, or many? Kari Lippert
- Re: [ogpx] one virtual world, or many? Kari Lippert
- Re: [ogpx] one virtual world, or many? Meadhbh Siobhan
- Re: [ogpx] one virtual world, or many? Meadhbh Siobhan
- Re: [ogpx] one virtual world, or many? Kari Lippert
- Re: [ogpx] one virtual world, or many? Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Carlo Wood
- Re: [ogpx] one virtual world, or many? Carlo Wood
- Re: [ogpx] one virtual world, or many? Charles Krinke
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Kari Lippert
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Carlo Wood
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Kari Lippert
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] one virtual world, or many? Dave CROCKER
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Joshua Bell
- Re: [ogpx] one virtual world, or many? Joshua Bell
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Carlo Wood
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Meadhbh Siobhan
- Re: [ogpx] one virtual world, or many? Meadhbh Siobhan
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Suzy Deffeyes
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Dan Olivares
- Re: [ogpx] one virtual world, or many? Charles Krinke
- Re: [ogpx] one virtual world, or many? Infinity Linden
- Re: [ogpx] one virtual world, or many? Infinity Linden
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine
- Re: [ogpx] one virtual world, or many? Joshua Bell
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Suzy Deffeyes
- Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revisi… Morgaine