Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revision

Dave CROCKER <dhc@dcrocker.net> Sun, 30 August 2009 14:41 UTC

Return-Path: <dhc@dcrocker.net>
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 44B823A6852 for <ogpx@core3.amsl.com>; Sun, 30 Aug 2009 07:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level:
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599]
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 adM6ItvTN-To for <ogpx@core3.amsl.com>; Sun, 30 Aug 2009 07:41:10 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7148]) by core3.amsl.com (Postfix) with ESMTP id 9F4823A67AD for <ogpx@ietf.org>; Sun, 30 Aug 2009 07:41:09 -0700 (PDT)
Received: from [127.0.0.1] (ppp-68-120-198-98.dsl.pltn13.pacbell.net [68.120.198.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n7UEf8xp020657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Aug 2009 07:41:13 -0700
Message-ID: <4A9A8F7D.6070501@dcrocker.net>
Date: Sun, 30 Aug 2009 07:41:01 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Carlo Wood <carlo@alinoe.com>
References: <3a880e2c0908281127h6965f332na493007b032e5e93@mail.gmail.com> <20090830003055.GD22756@alinoe.com>
In-Reply-To: <20090830003055.GD22756@alinoe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 30 Aug 2009 07:41:13 -0700 (PDT)
Cc: Infinity Linden <infinity@lindenlab.com>, 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
Reply-To: dcrocker@bbiw.net
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 14:41:11 -0000

Carlo Wood wrote:
>    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.

This reads well, with two exceptions:


Minor:
      Though virtual worlds may be partitioned
      ->
      Though a virtual world may  be partitioned


Substantial:

      The meaning and import of "un-sharded" is missing.  From the last time I
asked about this, I gather the term is familiar in VW circles, but it sure isn't
in the IETF or, I believe, anywhere outside /some/ database and /some/ or all VW
environs.

      Note that the language, here, is saying that it is /not/ sharded.
Jumping into a negative reference like this suggests that sharding is to be 
expected.  Is it?  Why?  Is reference to sharding essential for the charter?  Why?

      So, this reduces down to two different issues.  One is a concept and the 
other is a vocabulary term.  If the concept is essential, what's some terse text 
that makes sense for the charter?  If the term is essential, marry it to that 
terse text.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net