Re: [vwrap] Status and future of the VWRAP working group

Meadhbh Hamrick <ohmeadhbh@gmail.com> Mon, 28 March 2011 22:57 UTC

Return-Path: <ohmeadhbh@gmail.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 7112F3A6A96 for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 15:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 klCHMdbMKlq5 for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 15:56:59 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 87A843A68DF for <vwrap@ietf.org>; Mon, 28 Mar 2011 15:56:59 -0700 (PDT)
Received: by iwn39 with SMTP id 39so4139555iwn.31 for <vwrap@ietf.org>; Mon, 28 Mar 2011 15:58:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=luvXAwCQxgmFy2wLjrXid7t4veqTUvQGR0YgNDNl7mY=; b=vZ44AOVfJ/53GIJ8uuMA3YRIqzkcMLlsZUU/y+VJV5LxB0RaTzh5f9ZrcP99u9GHCf DP3dj2bXbAMCVc1KUDmBi8WoLqGPBGJlpPsuAeTFso3VWe0AZJcmuutreACSRSpttd9Y 8N2jKpoe6qDM4krV021pl5J0BwYClIWh0tDAM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=dWJzIxheJvIbSmW/H1MFwmsRvlKPNcgTjSo9F2xpH6Jbbr/n6lZWt3wgwlc3V+ZdQK 2tx84qglG4A3jpiFrzwI5m/X+CMYWHY3pLQzbBoPSeCIC0kKQYHFVhlE8dFOyfHsSa4+ g+ufs9Ig7UQHOIoCYSJ9d+iCK4m1+ADU0RX4I=
Received: by 10.43.66.5 with SMTP id xo5mr2186661icb.71.1301353117105; Mon, 28 Mar 2011 15:58:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.129 with HTTP; Mon, 28 Mar 2011 15:58:16 -0700 (PDT)
In-Reply-To: <AANLkTimM=ERx_WctgAzHhgm_GE_cVYM0j6FXp6xMthds@mail.gmail.com>
References: <AANLkTim=tpngqs8gt=sjCeOQgtUATVRXXKe11qUaNJFw@mail.gmail.com> <BLU159-ds1192252375D420BE8C7C9EDCB90@phx.gbl> <956AEC85-F919-4C64-96BA-277B620CAB18@gmail.com> <AANLkTimLHwMb9u5Ok-44-JgHaL_EydeSHyHUQybvNpMp@mail.gmail.com> <20110326135320.GC29908@alinoe.com> <AANLkTin=9a35pzm9QkGt6v5PgWAgsqomkYCBG8eSa4Xg@mail.gmail.com> <AANLkTinp2+skkPP0L1sWtTn1-OU=Q6_YXk_W1+QdL-8Q@mail.gmail.com> <AANLkTin25vWxk9Wd1U3ne_4DedU4Cz5JhMHTzt9gDyfA@mail.gmail.com> <AANLkTimM=ERx_WctgAzHhgm_GE_cVYM0j6FXp6xMthds@mail.gmail.com>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Mon, 28 Mar 2011 15:58:16 -0700
Message-ID: <AANLkTi=aghMKoOusjwbC7wyh=kzZwEY7a3_VCiw93ZYB@mail.gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: vwrap@ietf.org
Subject: Re: [vwrap] Status and future of the VWRAP working group
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, 28 Mar 2011 22:57:01 -0000

in other words, what does "interoperation between virtual worlds" mean?

the "service level interoperability" was sufficiently defined such
that i could (and did) go out and write code to demonstrably implement
the specification. does the term "interoperation between virtual
worlds" mean:

a. interoperability between any two existing virtual world or MMO
systems? (i.e. - between second life and world of warcraft?)

b. interoperability between second life, second life / enterprise or
OpenSIm instances?

or

c. interoperability between two OpenSim instances?

if a or b, do we have any interest from any of the implementers of
those systems to adhere to an IETF standard?

-cheers
-meadhbh

--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com



On Mon, Mar 28, 2011 at 2:15 PM, Morgaine
<morgaine.dinova@googlemail.com> wrote:
> The group's expectation of direction was already manifest at the time of
> Crista's intervention a few months ago, at which time it was unanimous that
> everybody except one person was seeking interoperation between virtual
> worlds as a primary requirement and as a key motivation for the group's
> work.
>
> The dissenting opinion was clearly, if unofficially, outvoted by <count of
> group members> to 1.  If that direction is STILL not accepted by everyone in
> the WG, I shall ask Barry to formally call a count of votes and establish
> the rough consensus officially.  Without this we will be perpetually
> disrupted by a non-representative minority pulling in the opposite direction
> to the rest of the group.
>
>
> Morgaine.
>
>
>
>
> ========================
>
> On Mon, Mar 28, 2011 at 8:53 PM, Meadhbh Hamrick <ohmeadhbh@gmail.com>
> wrote:
>>
>> Um. Morgaine. You don't get to define the wg's expectation or direction.
>> As a member of this wg (and someone who's actually written code related to
>> it's problem domain) I would like to be included in the development of this
>> group's consensus.
>>
>> On Mar 28, 2011 8:29 AM, "Morgaine" <morgaine.dinova@googlemail.com>
>> wrote:
>>
>> Barry, is there IETF precedent for a WG that has undergone this particular
>> train of events, namely a major disconnect between its originators'
>> intentions and the WG's expectations of direction?
>>
>> If so, our situation may be slightly easier to handle, since the
>> originators have withdrawn from pressing their case and there appears to be
>> almost no actual dispute remaining in the group.  Procedurally though, I
>> really don't know where we stand from the IETF's perspective.  We seem to
>> have a common goal now, but if the IETF demands paperwork, we're not there
>> yet because the designs and plans have not been worked out.  I'm hoping for
>> flexibility, but acknowledge that flexibility has a limit.
>>
>> That said, reading the IETF Mission Statement leaves no doubt that VW
>> interoperability is right in the middle of the road for the IETF.  Can the
>> group be left to work out what needs to be worked out?
>>
>>
>> Morgaine.
>>
>>
>>
>>
>> =================================
>>
>> On Sat, Mar 26, 2011 at 2:40 PM, Barry Leiba <barryleiba@computer.org>
>> wrote:
>> >
>> > Hi, Carlo, Vaugh...
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>