Re: [vwrap] Call for a vote on interop BETWEEN independent virtual worlds or not

Joshua Bell <josh@lindenlab.com> Mon, 20 September 2010 17:06 UTC

Return-Path: <josh@lindenlab.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A93DE3A6A61 for <vwrap@core3.amsl.com>; Mon, 20 Sep 2010 10:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.574
X-Spam-Level:
X-Spam-Status: No, score=-101.574 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 0zbuP2gztygu for <vwrap@core3.amsl.com>; Mon, 20 Sep 2010 10:06:57 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 141F33A6AAC for <vwrap@ietf.org>; Mon, 20 Sep 2010 10:06:55 -0700 (PDT)
Received: by wyi11 with SMTP id 11so5428355wyi.31 for <vwrap@ietf.org>; Mon, 20 Sep 2010 10:07:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.152.206 with SMTP id h14mr2130609wbw.145.1285002439293; Mon, 20 Sep 2010 10:07:19 -0700 (PDT)
Received: by 10.227.148.89 with HTTP; Mon, 20 Sep 2010 10:07:19 -0700 (PDT)
In-Reply-To: <AANLkTik0j66h4=HDSOD3Two03E5jRKmKCyjJP+gqip_q@mail.gmail.com>
References: <AANLkTi=C3sWti421=jjRiMfGAV4O8=p3har89cMNExPF@mail.gmail.com> <4C9766E4.9000208@hp.com> <AANLkTinphZSMNGGq00M+BKTbF1ZFVp_3WiWyf8VMFob4@mail.gmail.com> <AANLkTikZ-xQB36oy6mxDmpwn1vv8F2rEXrPNaQ44+a9=@mail.gmail.com> <AANLkTik0j66h4=HDSOD3Two03E5jRKmKCyjJP+gqip_q@mail.gmail.com>
Date: Mon, 20 Sep 2010 10:07:19 -0700
Message-ID: <AANLkTina4667arLo2PqRHSh2UoSneed_sCNdK7zdgvtS@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: multipart/alternative; boundary=001636831b7eedfaf70490b3f195
Cc: vwrap@ietf.org
Subject: Re: [vwrap] Call for a vote on interop BETWEEN independent virtual worlds or not
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 17:06:58 -0000

On Mon, Sep 20, 2010 at 9:43 AM, Morgaine <morgaine.dinova@googlemail.com>wrote;wrote:

> On Mon, Sep 20, 2010 at 4:27 PM, Jonathan Freedman <jef@openmetaverse.org>wrote;wrote:
>
> From what I can tell the drafts do support interoperability between the
> same *class* of virtual world. The catch is that the language needs to be
> significantly clearer.
>
>
> That sounds reasonable to me, Jonathan.  I believe that your first sentence
> reflects everyone's understanding of our goals ever since we formed the
> working group.  Only now has this odd "no interop between virtual worlds"
> slant been placed on our goals.
>

The group's goals are formally described in the charter:

https://datatracker.ietf.org/wg/vwrap/charter/

... which, based on previous iterations of this discussion, we carefully
crafted to not try and nail down what a "virtual world" was so as not to
offend those who have an investment in any particular reading of that term.


> Judging by the responses received here, it's clear that everyone else is
> affirming in one way or another their interest in virtual worlds that
> interoperate.  I certainly am.  I hope that we can confirm it as a matter of
> record with the help of the WG Chairs.
>

I'm having deja vu... no, wait, we have had this discussion before. Here's
one of my notes from Oct 2009:

http://www.ietf.org/mail-archive/web/ogpx/current/msg00509.html
<http://www.ietf.org/mail-archive/web/ogpx/current/msg00509.html>
... which is a response to a thread on exactly the same topic.

At the end of the day, we're attempting to describe protocols that allow
operators of virtual world services to interoperate such that users can
control avatars that move through it with the same client code, assuming
appropriate permissions. That's what's in the charter, and there's never
been disagreement about that that I'm aware of.

What we've learned from this discussion in previous iterations:

* If you call that scenario "multiple operators, multiple virtual worlds",
fine. But someone will disagree with your choice of terminology, and be
unwilling to adopt your terminology.

* If you call that scenario "multiple operators, one virtual world", fine.
But someone will disagree with your choice of terminology, and be unwilling
to adopt your terminology.

If you insist on using such terminology, please learn to recognize when you
are engaged in discussion with someone who uses different terminology and
either mentally translate or fixate on the scenario and technology, not the
label.

There is clear consensus on goals (both from pre-charter discussions, the
chartering itself, and even now if you read the scenarios being discussed in
this thread and ignore the labels). While attempting to standardize on
terminology might be a valuable discussion - and is probably within the
charter for this group, as a means to further the group's goals - please
recognize that there is a distinction between changing terminology and
changing scenarios/goals.