Re: [vwrap] Consensus? What exactly should be in the protocol

Meadhbh Hamrick <ohmeadhbh@gmail.com> Wed, 22 September 2010 20:37 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 6DEED3A6B30 for <vwrap@core3.amsl.com>; Wed, 22 Sep 2010 13:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level:
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[AWL=0.810, BAYES_00=-2.599]
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 Q-NRi4Nc64Fl for <vwrap@core3.amsl.com>; Wed, 22 Sep 2010 13:36:56 -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 3312428C120 for <vwrap@ietf.org>; Wed, 22 Sep 2010 13:35:45 -0700 (PDT)
Received: by wwb18 with SMTP id 18so624769wwb.1 for <vwrap@ietf.org>; Wed, 22 Sep 2010 13:36:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=YfJ0XEImF1I+RjyGpf6aMdqo/C2Oz6I3nBEmS7vTLnw=; b=w6tEyzfA0RGCDPsjikHIsw6ZU8P2PVxT8PfdrI7SveF80YZVeTtS4VuHgXCJ0p3IPm co/gcjUWAs73s0qZCHurY0Dv6tNTOuA/GNdNnc3gLf+mhKG5JBFr7e2uN22pXuAH9JFa KNEbV6CLEBsMU3diJqhTfnt1Vcs7AKhFsjV2Y=
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=AojdlO+uTSeqcse6AKez1qkW0LQX3VqQuwUy4PFXNwd6IQKzcnfMq5h7x0m+xQ2JV2 KeTq2c4Ju1iqVuMzLfAHpfbGGiHmWRTgje7H7AzZ82aujpTz6eRwQTDX6iP/YxVbDoAs cpxjvJSrJ8kFwpBO6gjTW9RECYtH8pjx89QVc=
Received: by 10.216.234.93 with SMTP id r71mr7487200weq.104.1285187769874; Wed, 22 Sep 2010 13:36:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.170.82 with HTTP; Wed, 22 Sep 2010 13:35:49 -0700 (PDT)
In-Reply-To: <0958E24D243B46D4BCA4D25A06A1A4A0@TWEEDY64>
References: <AANLkTinxpGRZ9PEWQx=KvaBNGBba4Z+P+SaP4N80VGV1@mail.gmail.com> <E2109887-F5B2-4742-B4F7-1C4655A2DD8B@ics.uci.edu> <62BFE5680C037E4DA0B0A08946C0933D012670D0C9@rrsmsx506.amr.corp.intel.com> <4C9A070B.3070202@hp.com> <AANLkTinVX6Uo2S+7ocdTiVfiTFa9wxM=x1Cncyi5ij86@mail.gmail.com> <4C9A17FC.9090308@ics.uci.edu> <OF98CA2B26.9D4927A8-ON852577A6.00572945-852577A6.0060FB5D@us.ibm.com> <4C9A45FC.6030709@ics.uci.edu> <AANLkTi=D53zLQxg8hMXKd-uAaxfFbr8M405+i-oYdcMV@mail.gmail.com> <4C9A5466.1070408@ics.uci.edu> <0958E24D243B46D4BCA4D25A06A1A4A0@TWEEDY64>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Wed, 22 Sep 2010 13:35:49 -0700
Message-ID: <AANLkTim2YzaNFHpLv3a56_t20x8G8Yo-BGxL9PbVLNeT@mail.gmail.com>
To: kevin.tweedy@xrgrid.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: vwrap@ietf.org
Subject: Re: [vwrap] Consensus? What exactly should be in the protocol
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: Wed, 22 Sep 2010 20:37:46 -0000

On Wed, Sep 22, 2010 at 1:30 PM,  <kevin.tweedy@xrgrid.com> wrote:

> It is really true that VWRAP will not have a specification on the avatar.
>  How can one avatar go to another space without that?  How will I know how
> to expose my avatar to another space without it?

well. we did actually list a document called 'Avatar Format' in the
group charter.

i honestly don't know where morgaine go the idea we weren't going to work on it.

however... other people are working on avatar format standards, it's
entirely within the realm of possibility that this group may decide
simply to adopt a format defined by another standards development
organization