IETF Logo Mail Archive

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

Meadhbh Hamrick <ohmeadhbh@gmail.com> Tue, 29 March 2011 00:23 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 9FF8D3A6A85 for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 17:23:49 -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 tJyfwZARCsog for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 17:23:48 -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 6171C3A696D for <vwrap@ietf.org>; Mon, 28 Mar 2011 17:23:48 -0700 (PDT)
Received: by iwn39 with SMTP id 39so4207175iwn.31 for <vwrap@ietf.org>; Mon, 28 Mar 2011 17:25:26 -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; bh=sO88ftfURdKXbrVV0z715K91eHTAU63tFH8oR+wUrUg=; b=G6t/toKRf2+y8H9nQyEsJ5JPOEWlwGBSazNUIvat3XgzOoIzv+iIA6T4AJshhyo8U4 10gTN7D6YxJMZQUchFpF0ZYeUIZIp2gRet+t/Q+3jIgL2glG5wzXUvKsDREg/wYJlFzo ZVfbZUgzBhWTaZwicduI1SKqWU8A6GRt9/NFA=
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; b=S5gIHKRpjwGnW2uSD1RaQZdNFYkyTrLIY+xPu5ux1cGSJMmVE44ZkYbcfrzARdGt81 wjNh/zaZhX5wiakTavAdWaOyuX+H6LXRNDgx2lOidwVJv/l6SUbP53CkewlLIe6Q76Mz 4PURd7jiq/SndKhGPseKPneaQuG6HbuBN1RIY=
Received: by 10.42.175.68 with SMTP id az4mr7952896icb.205.1301358325092; Mon, 28 Mar 2011 17:25:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.129 with HTTP; Mon, 28 Mar 2011 17:25:04 -0700 (PDT)
In-Reply-To: <4D9116A4.8010602@boroon.dasgupta.ch>
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> <AANLkTi=aghMKoOusjwbC7wyh=kzZwEY7a3_VCiw93ZYB@mail.gmail.com> <4D9116A4.8010602@boroon.dasgupta.ch>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Mon, 28 Mar 2011 17:25:04 -0700
Message-ID: <AANLkTim_wpu3_a7doRDPafQEahgAZV6X+z5H-=7_GQAU@mail.gmail.com>
To: Boroondas Gupte <sllists@boroon.dasgupta.ch>
Content-Type: text/plain; charset="ISO-8859-1"
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: Tue, 29 Mar 2011 00:23:50 -0000

i think that's the same thing as "service level interop" with the
added requirement that participants implement all services.

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



On Mon, Mar 28, 2011 at 4:15 PM, Boroondas Gupte
<sllists@boroon.dasgupta.ch> wrote:
> On 03/29/2011 12:58 AM, Meadhbh Hamrick wrote:
>> 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?
> How about:
>
> d. interoperability between (instances of) any two virtual world systems
> conforming to the (to be defined) VWRAP standard.
>
> Whether implementers of an existing virtual world system want to change
> that system so that it becomes conformant to the new standard and thus
> potentially interoperable with other conforming ones should be their own
> choice, of course.
>
> Cheers,
> Boroondas
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

v2.23.0 | Report a Bug | By Email