Re: [ogpx] OGPX WG draft charter, 2009-08-19 revision

David W Levine <dwl@us.ibm.com> Fri, 21 August 2009 13:54 UTC

Return-Path: <dwl@us.ibm.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 7046D3A6926; Fri, 21 Aug 2009 06:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.549
X-Spam-Level:
X-Spam-Status: No, score=-5.549 tagged_above=-999 required=5 tests=[AWL=1.049, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 X5JbU7-XNcPc; Fri, 21 Aug 2009 06:54:58 -0700 (PDT)
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.145]) by core3.amsl.com (Postfix) with ESMTP id 7E5CB3A6E11; Fri, 21 Aug 2009 06:54:51 -0700 (PDT)
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e5.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id n7LDkp3n002906; Fri, 21 Aug 2009 09:46:51 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n7LDsu0a248198; Fri, 21 Aug 2009 09:54:56 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n7LDspQB016090; Fri, 21 Aug 2009 09:54:56 -0400
Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n7LDsoPr015992; Fri, 21 Aug 2009 09:54:51 -0400
In-Reply-To: <b8ef0a220908201725l5b9d20d6qcb2921d3547277db@mail.gmail.com>
References: <e0b04bba0908191914h4837045ct777d2c63a30ddaf0@mail.gmail.com> <20090820141835.GB28751@alinoe.com> <b8ef0a220908201101g3b448d8ck7b406fc481c56f8d@mail.gmail.com> <e0b04bba0908201342hd17ce91qac0136124cd3a444@mail.gmail.com> <f72742de0908201426m6b8feac9v57e9ef1cd73e5c06@mail.gmail.com> <f72742de0908201600y46311454la8db52c4be1b18dc@mail.gmail.com> <b8ef0a220908201609m1c77be2n3d499b7da20fec5a@mail.gmail.com> <20090820235051.GA21280@alinoe.com> <20090820235657.GB21280@alinoe.com> <f72742de0908201716i6f5adc29o18313a6e55318a7f@mail.gmail.com> <b8ef0a220908201725l5b9d20d6qcb2921d3547277db@mail.gmail.com>
To: Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
MIME-Version: 1.0
X-KeepSent: 048CEB61:3E58783F-85257619:004946AA; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009
Message-ID: <OF048CEB61.3E58783F-ON85257619.004946AA-85257619.004C6C7B@us.ibm.com>
From: David W Levine <dwl@us.ibm.com>
Date: Fri, 21 Aug 2009 09:54:45 -0400
X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Build V851_07072009|July 07, 2009) at 08/21/2009 09:54:50, Serialize complete at 08/21/2009 09:54:50
Content-Type: multipart/alternative; boundary="=_alternative 004C6C7885257619_="
Cc: ogpx-bounces@ietf.org, ogpx@ietf.org
Subject: Re: [ogpx] OGPX WG draft charter, 2009-08-19 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: Fri, 21 Aug 2009 13:54:59 -0000

I am going to suggest inserting a very  concise paragraph after the second 
paragraph. 

>>> Insert 

Regions and Services implemented according to the specifications may be 
assembled into
multiple virtual worlds. These worlds may embody multiple domains of 
trust. Deployed virtual
worlds may support different policies of use. Constrained by these 
policies, the protocols will
permit interoperation across OGPX  virtual worlds with compatible policies 
and trust models. 

>>> end insert

I poersonally think this is implicit, but making it explicit doesn't hurt. 


I think this preserves the separation of concern we desire. Mechanisms are 
defined at the
protocol level. Policy is defined separate from mechanism. It should be 
possible to deploy
everything from highly constrained walled gardens to very open grids. The 
degree of 
avatar, agent, service and digital goods flow between specific virtual 
worlds will vary according
to the policies, and trust boundaries established by deployers. Nothing in 
the specifications
dictates specific policies

This follows the existing  practices of the web and internet.The core 
protocols
and formats of the internet permit interoperation, but deployers routinely 
constrain 
the accessibility and reach of services based on policy. 


- David W. Levine
~ Zha Ewry (ISL)