Re: [mmox] OGP scalability concerns

Jon Watte <jwatte@gmail.com> Thu, 02 April 2009 02:55 UTC

Return-Path: <jwatte@gmail.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 5BFBD3A6957 for <mmox@core3.amsl.com>; Wed, 1 Apr 2009 19:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level:
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 kmTZNtbS7pVp for <mmox@core3.amsl.com>; Wed, 1 Apr 2009 19:55:28 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by core3.amsl.com (Postfix) with ESMTP id 923AF3A67F2 for <mmox@ietf.org>; Wed, 1 Apr 2009 19:55:28 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id l35so178139waf.5 for <mmox@ietf.org>; Wed, 01 Apr 2009 19:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=B81VS/53rMpHeo81jQE3FIQQDVJerVG60PQ8+cbgON0=; b=Mtn8wcs2IBJg9gAMVJ8u4yu3HMTLfUGi3v6kDwJojz9CDgAWA6YPcqCczjjYc8CjkT quP3Ue2Rb59n+VI19iEPV8IIVd/Vp/jYfmeuCCC2Krx6oHAsARcAz0P/W5jupPfoT/w6 ZZfCD4iQ49ClXlqYzmL87j3nNMGiZY4Uy+QXQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=mSpURySB2pT8VNVZJ6Avp5Kxb9XcMbiFr7VDchR13/z1J/ah5dccFKDLu3TTUFGfLj AsxwEjl5x3JQCCTKGKa+B5jxJUXyJOl7cbzEhiJ7kNOhkhidCRDfCnvsooe1HBmELR62 R42NLFJkgx5zHLMtxBx+Iv07bdG235pIDSyL0=
Received: by 10.114.181.6 with SMTP id d6mr5639522waf.8.1238640989620; Wed, 01 Apr 2009 19:56:29 -0700 (PDT)
Received: from ?192.168.1.101? (svn.mindcontrol.org [69.17.45.136]) by mx.google.com with ESMTPS id m31sm625419wag.29.2009.04.01.19.56.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 01 Apr 2009 19:56:29 -0700 (PDT)
Message-ID: <49D4295C.2020502@gmail.com>
Date: Wed, 01 Apr 2009 19:56:28 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
References: <62BFE5680C037E4DA0B0A08946C0933D7B692E1B@rrsmsx506.amr.corp.intel.com> <CD02023C-3E7B-4E76-8429-11035C827E53@lindenlab.com> <f0b9e3410904011701i2ccb03d4r1b48d33cfe3988ea@mail.gmail.com> <49D40A06.7030708@gmail.com> <8D793BD8-6AA2-49C7-96EF-435A5B449AA6@lindenlab.com>
In-Reply-To: <8D793BD8-6AA2-49C7-96EF-435A5B449AA6@lindenlab.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] OGP scalability concerns
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, 02 Apr 2009 02:55:29 -0000

Meadhbh Hamrick (Infinity) wrote:
> I believe the term you're looking for, given your usage is 
> "universality." And no, OGP does not provide universality. OGP 

>>
>> It may sound pedantic, but I do think it's important to put as 
>> unambiguous labels on what we discuss as possible, so that we don't 
>> end up making different assumptions without realizing it, and ending 
>> up in confusion and discord.

I'm sorry: I think you misunderstood what I was saying and took it the 
wrong way. The word "interop" is clearly correct, and I am not arguing 
against that. My argument is against labeling anything and everything as 
"virtual world interop." As we've seen, it's a term that is so broad as 
to be almost meaningless. I'm merely arguing for specificity.

The proposal is to be more detailed about what kind of interop we're 
talking about in any particular case. For example, there might be VoIP 
interop, or avatar interop, or authentication interop, or simulation 
interop, or service brokerage interop, or online status interop, or text 
chat interop. Those are all forms of interop necessary to accomplish 
"full virtual world interop." The confusion arises when someone talks 
about "virtual worlds interop" but is actually only discussing one 
piece. In my opinion, it would be more accurate, and help everybody, to 
clearly specify the piece you're talking about.

Sincerely,

jw