Re: [ogpx] ogpx focus?

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 14 June 2009 08:06 UTC

Return-Path: <dromasca@avaya.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 A44F33A6AE7; Sun, 14 Jun 2009 01:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[AWL=-0.382, BAYES_00=-2.599, HTML_MESSAGE=0.001, URIBL_RHS_DOB=1.083]
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 DPXxzjYBzneB; Sun, 14 Jun 2009 01:06:17 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id E074D3A6A96; Sun, 14 Jun 2009 01:06:16 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.42,217,1243828800"; d="scan'208,217"; a="148493623"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 14 Jun 2009 04:06:23 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 14 Jun 2009 04:06:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9ECC6.FFEDD62C"
Date: Sun, 14 Jun 2009 10:06:18 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04017907F8@307622ANEX5.global.avaya.com>
In-Reply-To: <OFCEFDB2AB.605C9953-ON852575D3.0058F278-852575D3.005CF725@us.ibm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [ogpx] ogpx focus?
Thread-Index: Acnrfp+F58ELZKPOR92SYojR1cDgmgBR+o6Q
References: <3a880e2c0906111203x3b0629e0k36579da73ed60b17@mail.gmail.com> <4A323067.3020009@comlounge.net><3a880e2c0906120854u3f327f0bma9936f26a6101813@mail.gmail.com><558312.70763.qm@web82608.mail.mud.yahoo.com> <OFCEFDB2AB.605C9953-ON852575D3.0058F278-852575D3.005CF725@us.ibm.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David W Levine" <dwl@us.ibm.com>, "Charles Krinke" <cfk@pacbell.net>
Cc: ogpx-bounces@ietf.org, ogpx@ietf.org
Subject: Re: [ogpx] ogpx focus?
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, 14 Jun 2009 08:06:18 -0000

I would suggest that the future WG does not forget the operational
deployment and manageability issues. How are services identified and
observed, how can an operator have a view of what services are dunning
and what resources they are consuming, how congestion of resources and
health status of the applications and services are being presented and
reported?
 
Dan
(OPS co-AD)


________________________________

	From: ogpx-bounces@ietf.org [mailto:ogpx-bounces@ietf.org] On
Behalf Of David W Levine
	Sent: Friday, June 12, 2009 7:55 PM
	To: Charles Krinke
	Cc: ogpx-bounces@ietf.org; ogpx@ietf.org
	Subject: Re: [ogpx] ogpx focus?
	
	

	The way I'd describe it is: 
	
	OGP  if fully articulated will define 
	
	1) A low level distributed computing approach  (Caps, LLSD,
X.509, and event queue plumbing) 
	2) A bunch of virtual worlds building bocks (Prim formats,
Inventory, Assets, Region description, policy languages) 
	3) A set of rules on how to manage services which share, and
don't share trust (Domains) 
	4) A set of computational services delivered over 1 and 2 which
can be used to build out collections of services described by 3 
	5) A specific structure of 4) which represents Linden Lab's best
take on a useful way to partition the problem space. This defines
regions, which live in region domains, and agent services which live in
an agent domain. 
	
	Nothing in OGP defines how people's policies between deployments
will be set (nor should it, that's how you run your service) I expect
there will be far more regions than agent domains, and I expect we will
find 
	lots of regions that implement some combination of OGP and
Hypergrid, or similar schemes. 
	
	I would observes, that irrespective of using OGP, Hypergrid, or
some other scheme, that it would be really quite nice if we could make
sure that 1, 2,  and 3 can be shared.  This would enhance the overall
health of the ecosystem that is developing around these closely related
technologies. 
	
	- David 
	~ Zha 
	
	
	
	  
	
	
	
Charles Krinke <cfk@pacbell.net> 
Sent by: ogpx-bounces@ietf.org 

06/12/2009 12:03 PM 

To
ogpx@ietf.org 
cc
Subject
[ogpx] ogpx focus?

	




	I would like to see if we concur on a few points, if I may. And
I am not trying to stir up controversy, but rather understand some of
the feelings of where this will eventually go.
	
	As I understand where ogp *might* go, it will be a protocol that
will allow two seperate virtual worlds to eventually, as peers, both run
a sete of master servers currently called domain servers, I believe.
	
	In that case, each world will be able, as a peer, to negotiate
via packets, the interop from worldA to worldB (or from worldB to
worldA).
	
	That is, we are not contemplating that there is only one domain
server at SecondLife, but that, say, OSGrid could run its own domain
server and have reciprocity?
	
	Charles_______________________________________________
	ogpx mailing list
	ogpx@ietf.org
	https://www.ietf.org/mailman/listinfo/ogpx
<https://www.ietf.org/mailman/listinfo/ogpx>