Re: [vwrap] Moving ahead with draft-ietf-vwrap-intro
Jon Freedman <jef@openmetaverse.org> Mon, 02 August 2010 17:50 UTC
Return-Path: <jef@openmetaverse.org>
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 918E33A6B9D for <vwrap@core3.amsl.com>;
Mon, 2 Aug 2010 10:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.304
X-Spam-Level:
X-Spam-Status: No, score=0.304 tagged_above=-999 required=5 tests=[AWL=-2.280,
BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001,
RCVD_IN_BL_SPAMCOP_NET=1.96]
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 MmV-RLlUVTT3 for
<vwrap@core3.amsl.com>; Mon, 2 Aug 2010 10:50:12 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com
[74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id 1399A3A6B45 for
<vwrap@ietf.org>; Mon, 2 Aug 2010 10:50:11 -0700 (PDT)
Received: by wwf26 with SMTP id 26so10029002wwf.1 for <vwrap@ietf.org>;
Mon, 02 Aug 2010 10:50:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.137.149 with SMTP id w21mr5233787wbt.169.1280771439045;
Mon, 02 Aug 2010 10:50:39 -0700 (PDT)
Received: by 10.216.175.76 with HTTP; Mon, 2 Aug 2010 10:50:38 -0700 (PDT)
X-Originating-IP: [4.59.176.6]
Date: Mon, 2 Aug 2010 13:50:38 -0400
Message-ID: <AANLkTinZ0Lxak2PLP=Mcyv3dYhpZY5xPS63kPSHNL4zV@mail.gmail.com>
From: Jon Freedman <jef@openmetaverse.org>
To: "vwrap@ietf.org" <vwrap@ietf.org>
Content-Type: multipart/alternative; boundary=0016e65b6142a9c8b3048cdad6d7
Subject: Re: [vwrap] Moving ahead with draft-ietf-vwrap-intro
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, 02 Aug 2010 17:50:13 -0000
Hello Everyone, I want to throw in my two pieces of abstract virtual world currency into the mix. After perusing the vwrap-intro draft in depth, I have a few comments. I realize that some of this may have been raised before in previous discussions. The overall document and standardization roadmap makes is great. The technology and specifications laid out are generic enough that they should be able to encompass many forms of virtual worlds and the applications which inevitably evolve upon stable platforms. In my humble opinion the requirement of HTTP/REST semantics and suggestion for the use of XMPP as a messaging protocol are great to see. On the surface, the draft supports multiple means of deploying a virtual world. This ranges from local development environments to large distributed/scalable grids. Everyone seems to agree that support of multiple models is important, and I feel that this document does address that need. My only concern in this area is highly related to my overall concern with the document as it currently stands. I am wondering if it acceptable for me to give the document a quick overall pass to help improve some of the language use ? I realize this is a draft so hopefully this is a good time for such endeavours. Many sections lack clarity and multiple virtual world colloquialisms are used. Assuming there are no issues, I will send a txt version of my edits to this list within a few days. Cheers, -- Jonathan Freedman President Open Metaverse Foundation +1 (514) 582-1533 -- Jonathan Freedman President Open Metaverse Foundation +1 (514) 582-1533
- [vwrap] Moving ahead with draft-ietf-vwrap-intro Barry Leiba
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Meadhbh Hamrick
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Morgaine
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Meadhbh Hamrick
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Meadhbh Hamrick
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Morgaine
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Meadhbh Hamrick
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Jon Freedman
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Meadhbh Hamrick
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Dzonatas Sol
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Meadhbh Hamrick
- Re: [vwrap] Moving ahead with draft-ietf-vwrap-in… Morgaine