Re: [mmox] The Story So Far...

Jon Watte <jwatte@gmail.com> Wed, 18 February 2009 21:33 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 CAF1528C228 for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 13:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level:
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[AWL=0.267, 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 82EaMsKF4a44 for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 13:33:51 -0800 (PST)
Received: from mail-qy0-f11.google.com (mail-qy0-f11.google.com [209.85.221.11]) by core3.amsl.com (Postfix) with ESMTP id 100EA28C223 for <mmox@ietf.org>; Wed, 18 Feb 2009 13:33:49 -0800 (PST)
Received: by qyk4 with SMTP id 4so190496qyk.13 for <mmox@ietf.org>; Wed, 18 Feb 2009 13:34:01 -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=zoUYrON9J9wwdPHemEKtBUapGDMMRLX7j9Ij0cpAs8U=; b=SX7rEX0n89K/XCBIj9NRKiwVGlKZpsSjRUoZKGw57OKw64W0jumMNlPwworjy577np yIVRVfJDGvtpsvZ25pCH3UthfgORAEnTkmdSpyw2TuZ9kCyedJL6MHTqJCQBFqVeQYoi RBlBU/pxAD3QoLMfUvJlT6xY0pDn9MuKJc9Zc=
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=m8NFIUIElDrGToXZRKALzZVivreWWxC4g61gsKgg0rYkvnwsyVlliJWTAKyT0ZGy3Q FTrHr150gmp+fRhJhFgftl2pi/L8Kb9IYJYWjE9N+PtQNrNIA5LKPtDt5EPN/S1ubb8h uyMMTaLUVxWzKJ7/OzlFBUk5ji6zJ2JEjUPBw=
Received: by 10.229.100.7 with SMTP id w7mr79679qcn.5.1234992841731; Wed, 18 Feb 2009 13:34:01 -0800 (PST)
Received: from ?192.168.168.101? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id 9sm694071yws.55.2009.02.18.13.34.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 18 Feb 2009 13:34:01 -0800 (PST)
Message-ID: <499C7EC7.9070701@gmail.com>
Date: Wed, 18 Feb 2009 13:33:59 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Mark Lentczner <markl@lindenlab.com>
References: <1E40CE05-15D1-4970-9B0F-CD4AD11A074A@lindenlab.com>
In-Reply-To: <1E40CE05-15D1-4970-9B0F-CD4AD11A074A@lindenlab.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] The Story So Far...
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: Wed, 18 Feb 2009 21:33:51 -0000

Mark Lentczner wrote:
> While there is plenty to do and discuss in order to develop OGP into a 
> fully workable protocol, we think it represents an initial shared 
> vision of an interoperable protocol and hope it can evolve and grow in 
> the context of this group.

In my opinion, OGP is too Second Life specific to serve as a useful 
basis for a vendor neutral interoperability standard. If that is the 
basis for this IETF working group, then there's no need for me, or any 
other virtual world vendors, to be here.

Standardizing Second Life protocols might be useful for the Second Life 
sub-universe of virtual worlds, but I think trying to call it "generally 
interoperable" would be stretching the truth past bursting. There's too 
much content and too many players in production today using vastly 
different technologies for that to work.

See a different message for what I think is a great use case/scenario 
for what "interoperability" actually looks like (which I think we need 
to agree on before lower-level details like what kinds of protocols 
we'll need can be defined).

Sincerely,

jw