Re: [mmox] what does it mean to be interoperable?

Jon Watte <jwatte@gmail.com> Thu, 26 February 2009 19:52 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 A6F1A28C2C0 for <mmox@core3.amsl.com>; Thu, 26 Feb 2009 11:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level:
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 eihcY1C7MNfF for <mmox@core3.amsl.com>; Thu, 26 Feb 2009 11:52:49 -0800 (PST)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by core3.amsl.com (Postfix) with ESMTP id 4C7E928C123 for <mmox@ietf.org>; Thu, 26 Feb 2009 11:52:47 -0800 (PST)
Received: by yx-out-2324.google.com with SMTP id 8so892997yxm.49 for <mmox@ietf.org>; Thu, 26 Feb 2009 11:53:08 -0800 (PST)
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=yMNCcYqNigfuFCH/i3uYoNggNeuuj/7HWjUe6ORYdwI=; b=xXaFYC8sVHuCuY7aTBa0V/rNTJnRVMlLbh6h+n7nnn3jAlnxFNCYDvzjnjiNvh8+c8 NZp0VgSk0JUYkky3V/CMEBrP6bzp32guiJtbg6bbbAZxo5JEumCqzuYKnRITf+Ijp4mk O++y8uRrgsDYF42zIxjnv6sSwa7DyDCj4hhCs=
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=al2/uM/XDxKR5pieSB6wQcNr3HkF1YPw2Zydp9GGTN8gZfvVy/RJqwksIE7tBltFU2 /vU4g9bUj6b591n4wnjavDsGXUaxpZVX6YidAFPoL+4dERBwVDH1eaKtjTlijCnmAzt9 luo48k3VnR8VFvipiCmC1pmOiGdwY/SftqrKU=
Received: by 10.100.153.6 with SMTP id a6mr1932269ane.76.1235677988839; Thu, 26 Feb 2009 11:53:08 -0800 (PST)
Received: from ?192.168.168.114? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id d29sm2178394and.54.2009.02.26.11.53.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 26 Feb 2009 11:53:08 -0800 (PST)
Message-ID: <49A6F322.5020305@gmail.com>
Date: Thu, 26 Feb 2009 11:53:06 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
References: <228D0A40-F63F-4564-9200-0FF543902FD4@lindenlab.com>
In-Reply-To: <228D0A40-F63F-4564-9200-0FF543902FD4@lindenlab.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] what does it mean to be interoperable?
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, 26 Feb 2009 19:52:50 -0000

Meadhbh Hamrick (Infinity) wrote:
> 4. interoperability means some virtual worlds use precisely the same 
> protocol(s) and all virtual worlds represent data in formats 
> understandable by all other virtual worlds, without a universal client.
>

I would add option 4.5:

4.5: interoperability means all virtual worlds understand a precise set 
of protocols and all virtual worlds understand data represented in a 
common set of formats, without a universal client.

That may be what you meant, but the way you wrote it, it sounds like it 
dictates implementation details, which I think we should stay away from.

>
> so... i recommend that if we (as a group) wanted to pursue option-5.. 
> we also explicitly define what goes in an "interoperability profile." 
> that way you could get the benefit of having a relatively stable 
> protocol that could be targeted by open source developers which could 
> be used by VW operators to help make client / server apps.

I think we need to pursue 4.5, for exactly the reason you're suggesting: 
we want to avoid what you call "MOSS-like" behavior: two systems that 
claim to be interoperable, can't actually interoperate.

Sincerely,

jw