Re: [vwrap] Status and future of the VWRAP working group
Izzy Alanis <izzyalanis@gmail.com> Sat, 26 March 2011 15:53 UTC
Return-Path: <izzyalanis@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 6029C3A68C0 for <vwrap@core3.amsl.com>; Sat, 26 Mar 2011 08:53:15 -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=[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 k7J+meCR6Mm1 for <vwrap@core3.amsl.com>; Sat, 26 Mar 2011 08:53:14 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id D37073A6407 for <vwrap@ietf.org>; Sat, 26 Mar 2011 08:53:13 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1951190fxm.31 for <vwrap@ietf.org>; Sat, 26 Mar 2011 08:54:49 -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:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4tbTGP1Z7oFZX2JoPY1OQ1EwcO+Wld3QB16ie838eG8=; b=XnZtwEy03eeBzfUFy+PF5xHzLngR4xtVmHZ+5jM7u5EBaRQntickENQh0AsShG6S3R s0x/K6uMCJjWpne8BhbV99YKTJzAMNpSEICHVFq56UZ25NJEGXmn14EQ3QM3//ISisOS kWHMitgwzZQ4/HyxFeroyUoHox2m2tmKo6Grg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=i4lDnAIW+DqiTS/n0N+Y4paxOdooLkmC6bsV9lfu+GCZSE2LPrWLEa5tNaMIrD8HC3 Pq3+Y9hAjrNisvzNB1rLiSxExkkpTdL7Tu8vLXIeW+7v9J1LX8R+iqnUJppg+hdhyHaY AsTvk9gCcgUAdyFfx0p4qAp/RnZli0OfQhTPg=
MIME-Version: 1.0
Received: by 10.223.24.72 with SMTP id u8mr2363131fab.10.1301154887778; Sat, 26 Mar 2011 08:54:47 -0700 (PDT)
Received: by 10.223.74.204 with HTTP; Sat, 26 Mar 2011 08:54:47 -0700 (PDT)
In-Reply-To: <BLU159-ds79F94EC1FEF99BB62708DDCB80@phx.gbl>
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> <BLU159-ds79F94EC1FEF99BB62708DDCB80@phx.gbl>
Date: Sat, 26 Mar 2011 11:54:47 -0400
Message-ID: <AANLkTin0M5pgWE=trXnUqnyaFnw+TwduGb9vAJgg_AK1@mail.gmail.com>
From: Izzy Alanis <izzyalanis@gmail.com>
To: Patnad Babii <djshag@hotmail.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: Sat, 26 Mar 2011 15:53:15 -0000
+1 to: put aside the existing stuff For the purposes of the Intro doc, I think it would be possible to table the decision between LLSD/LLIDL and something else (protobuf) for the abstract type system / interface descriptions *if* the doc was couched in terms of a VWRAP-IDL that we then specify/decide on in the following IDL/type system doc. One thing we should make a decision on, and that I think is fuzzy in the draft-hamrick-vwrap-intro-01 doc, is whether the serializations are negotiated between services, or whether VWRAP mandates LLSD as the only approved serialization. Sections 2.3.1: "Web-based applications may choose to use JSON or XML. Server-to-server interactions may use the VWRAP specific binary serialization scheme..." Seems to conflict with (2.3.3): " VWRAP uses the LLSD abstract type system and the LLIDL interface description language to describe the structure and type semantics of elements in messages sent between systems. Because LLSD makes extensive use of variable width, clearly delineated data fields, services which consume protocol messages may identify and extract only those message elements they know how to handle." I'd like to take this opportunity to point out that protobuff supports the same variable width, extensibility, default values, yada yada yada. we could couch that in terms of only the IDL, and leave serialization of messages up to content negotiation between services involved. On Sat, Mar 26, 2011 at 11:03 AM, Patnad Babii <djshag@hotmail.com> wrote: > What we should focus on, is this I believe, are we going to keep LLSD (is it > good enought). Is it really needed or shall we start from scratch, with the > aim of using some new viewer / browser. > > Opensim (open source virtual platform with alot of grids already) is using > LLSD, especially because the viewer LL made is using LLSD. > > To be honest I keep saying since the beginning of these working groups (the > various ones, ogpx, vwrap, mmox..) we should put aside the existing stuff, > work more with Opensim, since they are the key to this new journey that is > open virtual worlds, its good they have HyperGrid already which does some > amazing stuff! > > What we need is a consensus, something we all agree on and go forward with > the docs. > > -----Message d'origine----- From: Barry Leiba > Sent: Saturday, March 26, 2011 10:40 AM > To: Carlo Wood > Cc: vwrap@ietf.org > Subject: Re: [vwrap] Status and future of the VWRAP working group > > Hi, Carlo, Vaughn, Izzy, Dzonatas, and everyone else. > I'm glad to see some discussion going. Izzy is right when he says this: >> >> Of course this all may not matter unless somebody actually addresses >> the underlying issue: That the group needs to start producing documents. > > Indeed. We, the chairs, need to see real progress on the documents... > particularly the introduction document. > > This discussion is a start, and, as I say, I'm pleased to see it, but > it has to turn into real document editing very soon. > > I want to say one other thing: > >> Oops, no I said 'we'... but count me out. I still see the same people >> around here and it's still going to fail just as bad as last time (or, >> as I expected the first time around... some "standard" is going to >> be produced that sucks; and that is either going to be ignored, or >> adopted by a few large "players" who then all get major head aches >> and problems that they can't fix; and in the end it will be the users >> who suffer most from having a bad protocol of course :/. > > Carlo, Meadhbh is still around, thought she (note gender) has given up > the editorship of the documents. Your input is welcome -- encouraged > -- though, of course, if you choose not to participate for whatever > reason, that's your choice. I think choosing not to participate > because some particular person is also participating is a poor choice, > but it's your choice to make. I would like to see you reconsider > that, if you're willing to do the work. > > What I do *not* want to see, and what we won't tolerate, are personal > attacks on any participant here. Do not engage in name-calling, do > not question people's integrity, do not malign the companies they work > for, and do not accuse people of malfeasance because they disagree > with you. If you present your ideas and others agree with what you > say, those ideas will make it forward. That's how we aim to work, > here, and if this working group can continue and make progress, that's > indeed how we'll work. > > So... will we make some progress on the intro document? Can we get > some real discussion on it, and a draft that shows some level of > consensus within the nest few weeks? > > Barry, as chair > _______________________________________________ > 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 >
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- [vwrap] Status and future of the VWRAP working gr… Katherine Mancuso
- [vwrap] Status and future of the VWRAP working gr… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Cristina Videira Lopes
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Fleep Tuque
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Mark Bannon
- Re: [vwrap] Status and future of the VWRAP workin… peter host
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Peter Saint-Andre
- Re: [vwrap] Status and future of the VWRAP workin… Peter Saint-Andre
- Re: [vwrap] Status and future of the VWRAP workin… Patnad Babii
- Re: [vwrap] Status and future of the VWRAP workin… Lawson English
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Fleep Tuque
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- [vwrap] Relevant panel at the IEFT: the role of s… Cristina Videira Lopes
- Re: [vwrap] Status and future of the VWRAP workin… Peter Saint-Andre
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Nexii Malthus
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Patnad Babii
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… mysticaldemina
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Fleep Tuque
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Boroondas Gupte
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Boroondas Gupte
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Dickson, Mike (ISS Software)
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick