From barryleiba.mailing.lists@gmail.com Thu Jun 3 13:41:50 2010 Return-Path: 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 E8F113A68DB; Thu, 3 Jun 2010 13:41:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.086 X-Spam-Level: X-Spam-Status: No, score=-3.086 tagged_above=-999 required=5 tests=[AWL=0.913, BAYES_50=0.001, GB_I_INVITATION=-2, GB_I_LETTER=-2] 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 oul4NLBTFsLz; Thu, 3 Jun 2010 13:41:49 -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 8252A3A6781; Thu, 3 Jun 2010 13:41:48 -0700 (PDT) Received: by fxm6 with SMTP id 6so410142fxm.31 for ; Thu, 03 Jun 2010 13:41:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=yU1z7ZPkm8KzIsS8Z7YmUVhXftzUi4Wp3odRrrUVr+Y=; b=iJogPigFaCulAXu2/gZjNt9gKET9QtTqBcWR89IRLJeCM5OwaOw2qmYQ9UU47pyQFr U0sOqfMZLC/da52q181OZeiZisEm2HV0RF5pbB12az+9Ul9AU4iURoMRQeNKtjip1vEE /j31yYTnX26dGSp0ePfNDc4HQ4s5KogbxTGGA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; b=cXz8W6yIRny5Y93HWxu4IA+FydgbGhgpCCKOA6E5Q+ZY5Co0GjyKJr6ntMQrtN3GwG zCdYtlEVOV7wGfZykXqARhkSY75CMeDFDPJB29gtHGDEhBTTAMch0Ij7ynjiYaxyi5u2 HpsVcPpIybKCko2O+gFl8Wapcn5p7bHvsmHyA= MIME-Version: 1.0 Received: by 10.223.24.133 with SMTP id v5mr10902935fab.46.1275597691957; Thu, 03 Jun 2010 13:41:31 -0700 (PDT) Received: by 10.223.122.141 with HTTP; Thu, 3 Jun 2010 13:41:31 -0700 (PDT) In-Reply-To: <20100603194905.138023A6A09@core3.amsl.com> References: <20100603194905.138023A6A09@core3.amsl.com> Date: Thu, 3 Jun 2010 16:41:31 -0400 Message-ID: From: Barry Leiba To: vwrap@ietf.org, marf@ietf.org, morg@ietf.org, ietf-dkim@mipassoc.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: [vwrap] Fwd: IETF 78 - Meeting and Sponsorship Information X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: barryleiba@computer.org List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2010 20:41:51 -0000 Working-group denizens: see the note below, and notice, in particular, the sponsorship opportunities available at this and other IETF meetings. If a company you're associated with might have an interest in sponsoring IETF activities, please put the appropriate parties in contact. And I hope to see many of you in Maastricht. Barry, as chair, passing on information from above ---------- Forwarded message ---------- From: IETF Secretariat Date: Thu, Jun 3, 2010 at 3:49 PM Subject: IETF 78 - Meeting and Sponsorship Information To: IETF Announcement list 78th IETF Meeting Maastricht, Netherlands July 25-30, 2010 1. Sponsorship Opportunities 2. Registration Types 3. Visas and Letters of Invitation 4. Accommodations & Breakfast Information 5. IETF 79 (Beijing) Visa Information 1) Sponsorship Opportunities There are still sponsorship opportunities and benefits for high profile company/organizational exposure at the upcoming IETF meeting in Maastricht, Netherlands from July 25-30, 2010. All sponsorship fees go directly to fund the operations of the IETF. See the options at: http://www.ietf.org/meeting/78/index.html =93Sponsorship Opportunities=94 under =93General=94. Each of the sponsorship options provide extended and repeat exposure at this weeklong meeting. Please contact Drew Dvorshak, dvorshak@isoc.org, with any questions and/or to reserve your organization=92s spot. Thanks in advance for supporting the critical work of the IETF! 2) Register online at: http://www.ietf.org/meetings/78/ 3) Letters of Invitation and Visas Letters of Invitation After you complete the meeting registration process, you will be given the option to request a letter of invitation. You can request the Letter of Invitation as soon as you finish registration, or at a later time by following the link provided in the confirmation email. Visas Please check the Netherlands Ministry of Foreign Affairs site (http://www.minbuza.nl/en/Services/Consular_Services/Visa) for list of countries with visa exemptions. We recommend you give yourself at least one month to complete the visa process. 4) Accommodations & Breakfast Information http://www.ietf.org/meeting/78/hotel.html 5) If you want to start planning for your trip to IETF 79 in Beijing, we have visa information online here: http://www.ietf.org/meeting/79/visa.html Only 52 days until IETF 78! _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From markl@lindenlab.com Mon Jun 7 16:39:03 2010 Return-Path: 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 9509D3A6816 for ; Mon, 7 Jun 2010 16:39:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] 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 MyyKhKsLY0jo for ; Mon, 7 Jun 2010 16:39:02 -0700 (PDT) Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 5E93B3A67E6 for ; Mon, 7 Jun 2010 16:38:59 -0700 (PDT) Received: by pxi19 with SMTP id 19so1581771pxi.31 for ; Mon, 07 Jun 2010 16:38:57 -0700 (PDT) Received: by 10.142.55.7 with SMTP id d7mr11139373wfa.344.1275953937725; Mon, 07 Jun 2010 16:38:57 -0700 (PDT) Received: from nil.lindenlab.com ([38.99.52.137]) by mx.google.com with ESMTPS id 21sm3397508pzk.0.2010.06.07.16.38.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 07 Jun 2010 16:38:56 -0700 (PDT) From: Mark Lentczner Content-Type: multipart/alternative; boundary=Apple-Mail-2--853491697 Date: Mon, 7 Jun 2010 16:38:55 -0700 Message-Id: <181BEC41-396C-4E2D-ADE8-705CBAD4C31C@lindenlab.com> To: vwrap Mime-Version: 1.0 (Apple Message framework v1078) X-Mailer: Apple Mail (2.1078) Subject: [vwrap] Linden Lab open source LLSD code X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2010 23:39:03 -0000 --Apple-Mail-2--853491697 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I'm happy to announce that Linden Lab has open sourced (MIT licensed) = its LLSD implementations in four languages: C++, JavaScript, Haskell, = and Python. The code can be found here: http://hg.secondlife.com/llsd Please let me know if this is useful, and if you need any help using it. - Mark & Josh =46rom the README file: Linden Lab LLSD Libraries ------------------------- v1 - 2010-06-07 - Joshua Bell & Mark Lentczner ABOUT =3D=3D=3D=3D=3D LLSD is defined in draft-hamrick-vwrap-type-system-00. It is a = structured data system used for interchange. See the draft for more details: http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00 The design and development of LLSD is being undertaken by the IETF VWRAP working group. Please direct design and development questions to its = mailing list. wiki - http://trac.tools.ietf.org/wg/vwrap/trac/wiki list - https://www.ietf.org/mailman/listinfo/ogpx =20 This distribution contains Linden Lab's open source (MIT licensed) implementations of the LLSD type system in four langauges: C++ LLSD JavaScript LLSD & LLIDL Haskell LLSD & LLIDL Python LLSD & LLIDL (*) There are four directories, one per file, and each has its own README = file with details for building and using the code. All versions have unit tests. Questions regarding these libraries can be directed to Josh or Mark: josh@lindenlab.com markl@lindenlab.com Linden Lab hopes that by releasing these open source, it will help = facilitiate the development of LLSD, as well as ease interoperatibility with = currently deployed systems that use LLSD such as Second Life and OpenSim. - Josh & Mark =20 (*) The Python version is currently distributed in a separate = repository: http://hg.secondlife.com/llbase/ The intention is to eventually migrate it here. Mark Lentczner Sr. Systems Architect Technology Integration Linden Lab markl@lindenlab.com Zero Linden zero.linden@secondlife.com= --Apple-Mail-2--853491697 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I'm = happy to announce that Linden Lab has open sourced (MIT licensed) its = LLSD implementations in four languages: C++, JavaScript, Haskell, and = Python. The code can be found here:

Please let me know if this is useful, and = if you need any help using it.

- Mark = & Josh

=46rom the README = file:

Linden = Lab LLSD = Libraries
-------------------------
   =  v1 - 2010-06-07 - Joshua Bell & Mark = Lentczner


ABOUT
=3D=3D=3D= =3D=3D

LLSD is defined in = draft-hamrick-vwrap-type-system-00. It is a structured = data
system used for interchange. See the draft for more = details:

<= br>
The design and development of LLSD is being undertaken by = the IETF VWRAP
working group. Please direct design and = development questions to its = mailing
list.

    
This = distribution contains Linden Lab's open source (MIT = licensed)
implementations of the LLSD type system in four = langauges:

    C++     =     LLSD
    JavaScript  LLSD = & LLIDL
    Haskell     LLSD = & LLIDL
    Python      LLSD = & LLIDL (*)

There are four directories, one = per file, and each has its own README file with
details for = building and using the code. All versions have unit = tests.

Questions regarding these libraries can = be directed to Josh or Mark:

=
Linden Lab hopes that by releasing these open source, it will = help facilitiate
the development of LLSD, as well as ease = interoperatibility with currently
deployed systems that use = LLSD such as Second Life and = OpenSim.

    - Josh & = Mark
    
(*) The Python version is = currently distributed in a separate repository:
The intention is to eventually migrate it = here.


Mark = Lentczner
Sr. Systems Architect
Technology = Integration
Linden Lab


Zero Linden
= --Apple-Mail-2--853491697-- From john.hurliman@intel.com Mon Jun 7 16:48:44 2010 Return-Path: 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 050CA3A6842 for ; Mon, 7 Jun 2010 16:48:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.998 X-Spam-Level: X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 COhbnTl6m51Y for ; Mon, 7 Jun 2010 16:48:38 -0700 (PDT) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by core3.amsl.com (Postfix) with ESMTP id 9418F3A67A4 for ; Mon, 7 Jun 2010 16:48:38 -0700 (PDT) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 07 Jun 2010 16:44:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.53,380,1272870000"; d="scan'208,217";a="574188394" Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by fmsmga002.fm.intel.com with ESMTP; 07 Jun 2010 16:47:22 -0700 Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx604.amr.corp.intel.com ([10.31.0.170]) with mapi; Mon, 7 Jun 2010 17:48:36 -0600 From: "Hurliman, John" To: Mark Lentczner , vwrap Date: Mon, 7 Jun 2010 17:48:36 -0600 Thread-Topic: [vwrap] Linden Lab open source LLSD code Thread-Index: AcsGmqShbRGXenbEQKK9CTIVbNTMcgAARG9w Message-ID: <62BFE5680C037E4DA0B0A08946C0933DDA3D3401@rrsmsx506.amr.corp.intel.com> References: <181BEC41-396C-4E2D-ADE8-705CBAD4C31C@lindenlab.com> In-Reply-To: <181BEC41-396C-4E2D-ADE8-705CBAD4C31C@lindenlab.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_62BFE5680C037E4DA0B0A08946C0933DDA3D3401rrsmsx506amrcor_" MIME-Version: 1.0 Subject: Re: [vwrap] Linden Lab open source LLSD code X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2010 23:48:44 -0000 --_000_62BFE5680C037E4DA0B0A08946C0933DDA3D3401rrsmsx506amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Great to hear, the number of liberally licensed implementations of LLSD is = up to five now (including the C# implementation in the libomv repository). = Is an up to date PHP implementation on Linden's roadmap, or would it make s= ense for someone else to start porting one of these implementations to PHP? John From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf Of M= ark Lentczner Sent: Monday, June 07, 2010 4:39 PM To: vwrap Subject: [vwrap] Linden Lab open source LLSD code I'm happy to announce that Linden Lab has open sourced (MIT licensed) its L= LSD implementations in four languages: C++, JavaScript, Haskell, and Python= . The code can be found here: http://hg.secondlife.com/llsd Please let me know if this is useful, and if you need any help using it. - Mark & Josh >From the README file: Linden Lab LLSD Libraries ------------------------- v1 - 2010-06-07 - Joshua Bell & Mark Lentczner ABOUT =3D=3D=3D=3D=3D LLSD is defined in draft-hamrick-vwrap-type-system-00. It is a structured d= ata system used for interchange. See the draft for more details: http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00 The design and development of LLSD is being undertaken by the IETF VWRAP working group. Please direct design and development questions to its mailin= g list. wiki - http://trac.tools.ietf.org/wg/vwrap/trac/wiki list - https://www.ietf.org/mailman/listinfo/ogpx This distribution contains Linden Lab's open source (MIT licensed) implementations of the LLSD type system in four langauges: C++ LLSD JavaScript LLSD & LLIDL Haskell LLSD & LLIDL Python LLSD & LLIDL (*) There are four directories, one per file, and each has its own README file = with details for building and using the code. All versions have unit tests. Questions regarding these libraries can be directed to Josh or Mark: josh@lindenlab.com markl@lindenlab.com Linden Lab hopes that by releasing these open source, it will help faciliti= ate the development of LLSD, as well as ease interoperatibility with currently deployed systems that use LLSD such as Second Life and OpenSim. - Josh & Mark (*) The Python version is currently distributed in a separate repository: http://hg.secondlife.com/llbase/ The intention is to eventually migrate it here. Mark Lentczner Sr. Systems Architect Technology Integration Linden Lab markl@lindenlab.com Zero Linden zero.linden@secondlife.com --_000_62BFE5680C037E4DA0B0A08946C0933DDA3D3401rrsmsx506amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Great to = hear, the number of liberally licensed implementations of LLSD is up to fiv= e now (including the C# implementation in the libomv repository). Is an up = to date PHP implementation on Linden’s roadmap, or would it make sens= e for someone else to start porting one of these implementations to PHP?

 

=

John

=  

From: v= wrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf Of M= ark Lentczner
Sent: Monday, June 07, 2010 4:39 PM
To: v= wrap
Subject: [vwrap] Linden Lab open source LLSD code=

 

I'm happy to announce that Linden Lab has open sourced (MIT li= censed) its LLSD implementations in four languages: C++, JavaScript, Haskel= l, and Python. The code can be found here:

      &n= bsp;     http= ://hg.secondlife.com/llsd

 

Please let me = know if this is useful, and if you need any help using it.

 

      &n= bsp;     - Mark & Josh

<= div>

 

From the README file:= <= /o:p>

 

=

Linden Lab LLSD Libraries

-------------------------=

    v1 - 2010-06-07 - Jo= shua Bell & Mark Lentczner

 

 

ABOUT

=3D=3D=3D=3D=3D

 

LLSD is defined in draft-= hamrick-vwrap-type-system-00. It is a structured data

<= div>

system used for interchange. See the draft for mor= e details:

 <= /p>

 

The des= ign and development of LLSD is being undertaken by the IETF VWRAP

working group. Please direct design an= d development questions to its mailing

list.

 

=

    

This distribution contains Linden Lab's open source (MIT licen= sed)

implementations of the L= LSD type system in four langauges:

 

   &nb= sp;C++         LLSD

    JavaScript  LLSD & LLIDL

    Haskell   &nbs= p; LLSD & LLIDL

 &nb= sp;  Python      LLSD & LLIDL (*)

 

There are four directories, one per file, and each has its own READM= E file with

details for build= ing and using the code. All versions have unit tests.

<= div>

 

Questions regarding these libraries can be directed to Josh or Mark:

 

Linden Lab hopes that by = releasing these open source, it will help facilitiate

<= div>

the development of LLSD, as well as ease interoper= atibility with currently

depl= oyed systems that use LLSD such as Second Life and OpenSim.

<= /div>

 

    - Josh & Mark

    

(*) The Python version is currently distributed in a separate repos= itory:

 

=
<= /div>= --_000_62BFE5680C037E4DA0B0A08946C0933DDA3D3401rrsmsx506amrcor_-- From xugu@xugumadison.org Mon Jun 7 18:37:23 2010 Return-Path: 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 D82313A68BE for ; Mon, 7 Jun 2010 18:37:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.623 X-Spam-Level: X-Spam-Status: No, score=0.623 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622] 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 uT3onynX13PB for ; Mon, 7 Jun 2010 18:37:22 -0700 (PDT) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by core3.amsl.com (Postfix) with ESMTP id 855D33A68E6 for ; Mon, 7 Jun 2010 18:37:09 -0700 (PDT) Received: by ey-out-2122.google.com with SMTP id 9so140505eyd.5 for ; Mon, 07 Jun 2010 18:37:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.32.197 with SMTP id e5mr11244479ebd.28.1275961027043; Mon, 07 Jun 2010 18:37:07 -0700 (PDT) Received: by 10.213.8.208 with HTTP; Mon, 7 Jun 2010 18:37:06 -0700 (PDT) In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DDA3D3401@rrsmsx506.amr.corp.intel.com> References: <181BEC41-396C-4E2D-ADE8-705CBAD4C31C@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933DDA3D3401@rrsmsx506.amr.corp.intel.com> Date: Tue, 8 Jun 2010 02:37:06 +0100 Message-ID: From: Xugu Madison To: "Hurliman, John" , vwrap Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [vwrap] Linden Lab open source LLSD code X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2010 01:37:24 -0000 For reference the Java LLSD implementation (although it is a partial implementation, and primarily intended for use with RegAPI) is BSD licensed, which makes six... http://mimuve.cs.st-andrews.ac.uk/llsd-java/src/llsd-java-0.2.1.zip On 8 June 2010 00:48, Hurliman, John wrote: > Great to hear, the number of liberally licensed implementations of LLSD i= s > up to five now (including the C# implementation in the libomv repository)= . > Is an up to date PHP implementation on Linden=92s roadmap, or would it ma= ke > sense for someone else to start porting one of these implementations to P= HP? > > > > John > > > > From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf Of > Mark Lentczner > Sent: Monday, June 07, 2010 4:39 PM > To: vwrap > Subject: [vwrap] Linden Lab open source LLSD code > > > > I'm happy to announce that Linden Lab has open sourced (MIT licensed) its > LLSD implementations in four languages: C++, JavaScript, Haskell, and > Python. The code can be found here: > > =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 http://hg.secondlife.com/llsd > > > > Please let me know if this is useful, and if you need any help using it. > > > > =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Mark & Josh > > > > From the README file: > > > > Linden Lab LLSD Libraries > > ------------------------- > > =A0=A0 =A0v1 - 2010-06-07 - Joshua Bell & Mark Lentczner > > > > > > ABOUT > > =3D=3D=3D=3D=3D > > > > LLSD is defined in draft-hamrick-vwrap-type-system-00. It is a structured > data > > system used for interchange. See the draft for more details: > > > > =A0=A0 =A0http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00 > > > > The design and development of LLSD is being undertaken by the IETF VWRAP > > working group. Please direct design and development questions to its mail= ing > > list. > > > > =A0=A0 =A0wiki - http://trac.tools.ietf.org/wg/vwrap/trac/wiki > > =A0=A0 =A0list - https://www.ietf.org/mailman/listinfo/ogpx > > > > This distribution contains Linden Lab's open source (MIT licensed) > > implementations of the LLSD type system in four langauges: > > > > =A0=A0 =A0C++ =A0 =A0 =A0 =A0 LLSD > > =A0=A0 =A0JavaScript =A0LLSD & LLIDL > > =A0=A0 =A0Haskell =A0 =A0 LLSD & LLIDL > > =A0=A0 =A0Python =A0 =A0 =A0LLSD & LLIDL (*) > > > > There are four directories, one per file, and each has its own README fil= e > with > > details for building and using the code. All versions have unit tests. > > > > Questions regarding these libraries can be directed to Josh or Mark: > > =A0=A0 =A0josh@lindenlab.com > > =A0=A0 =A0markl@lindenlab.com > > > > Linden Lab hopes that by releasing these open source, it will help > facilitiate > > the development of LLSD, as well as ease interoperatibility with currentl= y > > deployed systems that use LLSD such as Second Life and OpenSim. > > > > =A0=A0 =A0- Josh & Mark > > > > (*) The Python version is currently distributed in a separate repository: > > =A0=A0 =A0http://hg.secondlife.com/llbase/ > > The intention is to eventually migrate it here. > > > > > > Mark Lentczner > > Sr. Systems Architect > > Technology Integration > > Linden Lab > > > > markl@lindenlab.com > > > > Zero Linden > > zero.linden@secondlife.com > > _______________________________________________ > vwrap mailing list > vwrap@ietf.org > https://www.ietf.org/mailman/listinfo/vwrap > > From markl@lindenlab.com Tue Jun 8 16:49:19 2010 Return-Path: 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 D42403A6848 for ; Tue, 8 Jun 2010 16:49:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] 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 LPFqbDQGtO-m for ; Tue, 8 Jun 2010 16:49:18 -0700 (PDT) Received: from mail-pz0-f180.google.com (mail-pz0-f180.google.com [209.85.222.180]) by core3.amsl.com (Postfix) with ESMTP id 3157A3A6833 for ; Tue, 8 Jun 2010 16:49:18 -0700 (PDT) Received: by pzk10 with SMTP id 10so3687324pzk.20 for ; Tue, 08 Jun 2010 16:49:17 -0700 (PDT) Received: by 10.142.248.40 with SMTP id v40mr12596197wfh.92.1276040956244; Tue, 08 Jun 2010 16:49:16 -0700 (PDT) Received: from nil.lindenlab.com ([38.99.52.137]) by mx.google.com with ESMTPS id 20sm618354pzk.11.2010.06.08.16.49.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 08 Jun 2010 16:49:14 -0700 (PDT) From: Mark Lentczner Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: multipart/alternative; boundary=Apple-Mail-5--766474229 Date: Tue, 8 Jun 2010 16:49:12 -0700 In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DDA3D3401@rrsmsx506.amr.corp.intel.com> To: vwrap References: <181BEC41-396C-4E2D-ADE8-705CBAD4C31C@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933DDA3D3401@rrsmsx506.amr.corp.intel.com> Message-Id: X-Mailer: Apple Mail (2.1078) Subject: Re: [vwrap] Linden Lab open source LLSD code X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2010 23:49:20 -0000 --Apple-Mail-5--766474229 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Jun 7, 2010, at 4:48 PM, Hurliman, John wrote: > Is an up to date PHP implementation on Linden=92s roadmap, or would it = make sense for someone else to start porting one of these = implementations to PHP? I've just added our PHP implementation to the repo. While we use it = internally extensively, it only support XML serialization. It isn't = nearly as complete an implementation as the others. However, now it's = released open source too, so enjoy, extend! http://hg.secondlife.com/llsd - Mark Mark Lentczner Sr. Systems Architect Technology Integration Linden Lab markl@lindenlab.com Zero Linden zero.linden@secondlife.com --Apple-Mail-5--766474229 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 On Jun 7, 2010, at 4:48 PM, = Hurliman, John wrote:
Is an up to date PHP = implementation on Linden=92s roadmap, or would it make sense for someone = else to start porting one of these implementations to = PHP?

I've just added our PHP implementation to = the repo. While we use it internally extensively, it only support XML = serialization. It isn't nearly as complete an implementation as the = others. However, now it's released open source too, so enjoy, = extend!


- = Mark



Mark = Lentczner
Sr. Systems Architect
Technology = Integration
Linden Lab


Zero Linden




= --Apple-Mail-5--766474229-- From markl@glyphic.com Thu Jun 10 16:07:11 2010 Return-Path: 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 D4F583A67F3 for ; Thu, 10 Jun 2010 16:07:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 VyDJn3bsnytH for ; Thu, 10 Jun 2010 16:07:07 -0700 (PDT) Received: from mail.glyphic.com (mail.glyphic.com [216.218.209.57]) by core3.amsl.com (Postfix) with ESMTP id 899D23A67E3 for ; Thu, 10 Jun 2010 16:07:07 -0700 (PDT) Received: from [10.15.0.54] (unknown [66.92.0.228]) by mail.glyphic.com (Postfix) with ESMTPSA id 5A5D04056 for ; Thu, 10 Jun 2010 16:18:09 -0700 (PDT) From: Mark Lentczner Content-Type: text/plain; charset=us-ascii Message-Id: <562CD52F-77D9-4F06-B457-27C3C25F29B5@glyphic.com> Date: Thu, 10 Jun 2010 16:07:07 -0700 To: vwrap@ietf.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v1078) X-Mailer: Apple Mail (2.1078) Subject: [vwrap] my status X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2010 23:58:28 -0000 Friends - As you probably know, there was a layoff at Linden Lab yesterday. I was = among those let go. While I hope to be able to continue to work on the = Type System draft, I'm not entirely sure of my timing... on the one hand = I now have much more free time, on the other, I've got to start looking = for a job.(*) I'll be sorting out my plans in the next few days. - Mark Lentczner http://www.ozonehouse.com/mark/ mark+vwrap@glyphic.com (*) Yup - I'm looking... anyone hiring virtual world systems architects? = :-) From josh@lindenlab.com Fri Jun 11 13:28:24 2010 Return-Path: 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 0F85A3A684F for ; Fri, 11 Jun 2010 13:28:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.117 X-Spam-Level: X-Spam-Status: No, score=-0.117 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 f3hl4Pda6oD3 for ; Fri, 11 Jun 2010 13:28:21 -0700 (PDT) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 687CA3A672E for ; Fri, 11 Jun 2010 13:28:17 -0700 (PDT) Received: by pwi8 with SMTP id 8so952679pwi.31 for ; Fri, 11 Jun 2010 13:28:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.115.80.7 with SMTP id h7mr1863474wal.159.1276288097671; Fri, 11 Jun 2010 13:28:17 -0700 (PDT) Received: by 10.114.148.16 with HTTP; Fri, 11 Jun 2010 13:28:17 -0700 (PDT) Date: Fri, 11 Jun 2010 13:28:17 -0700 Message-ID: From: Joshua Bell To: vwrap@ietf.org Content-Type: multipart/alternative; boundary=0016e64dc930b158b60488c6fae3 Subject: [vwrap] Meeting in Maastricht/IETF78 ? X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2010 20:28:24 -0000 --0016e64dc930b158b60488c6fae3 Content-Type: text/plain; charset=UTF-8 Quick poll: Are any VWRAP participants planning to attend IETF78 in Maastricht and, if so, are there VWRAP issues you would like to have on the agenda for a face-to-face meeting? The chairs are trying to gauge whether or not we should request a session slot. You can reply to the list, or privately to me. --0016e64dc930b158b60488c6fae3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Quick poll:=C2=A0

Are any VWRAP participants = planning to attend IETF78 in Maastricht and, if so, are there VWRAP issues = you would like to have on the agenda for a face-to-face meeting?
=
The chairs are trying to gauge whether or not we should request = a session slot.=C2=A0You can reply to the list, or privately to me.

--0016e64dc930b158b60488c6fae3-- From dwl@us.ibm.com Fri Jun 11 15:42:32 2010 Return-Path: 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 175DE28C13E; Fri, 11 Jun 2010 15:42:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.998 X-Spam-Level: X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 5ZNZ+9YoQIGn; Fri, 11 Jun 2010 15:42:20 -0700 (PDT) Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.144]) by core3.amsl.com (Postfix) with ESMTP id 287C028C103; Fri, 11 Jun 2010 15:42:16 -0700 (PDT) Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by e4.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id o5BMSxNR011113; Fri, 11 Jun 2010 18:28:59 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o5BMgBs8131422; Fri, 11 Jun 2010 18:42:11 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id o5BMgB3t023432; Fri, 11 Jun 2010 18:42:11 -0400 Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id o5BMgBS9023429; Fri, 11 Jun 2010 18:42:11 -0400 In-Reply-To: References: To: Joshua Bell MIME-Version: 1.0 X-KeepSent: 8733CC05:71C4FF9A-8525773F:007C59E7; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009 Message-ID: From: David W Levine Date: Fri, 11 Jun 2010 18:42:10 -0400 X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Release 8.5.1HF41 | October 22, 2009) at 06/11/2010 18:42:11, Serialize complete at 06/11/2010 18:42:11 Content-Type: multipart/alternative; boundary="=_alternative 007CB5DD8525773F_=" Cc: vwrap@ietf.org, vwrap-bounces@ietf.org Subject: Re: [vwrap] Meeting in Maastricht/IETF78 ? X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2010 22:42:32 -0000 This is a multipart message in MIME format. --=_alternative 007CB5DD8525773F_= Content-Type: text/plain; charset="US-ASCII" I am currently available to do the meeting, if there would be serious work to be done. I'd love to see some real progress on bashing together a storyline which merged in the Deployment pattern stuff, along with the pattern's Joshua proposed for exposing services into the primary drafts. But.. We'd have to have a serious set of players f2f to justify the travel, and some serious consensus building discussion prior to the meeting. I'd be looking for some clarity on various participants availability to drive the work going forward as well. - David ~ Zha vwrap-bounces@ietf.org wrote on 06/11/2010 04:28:17 PM: > [image removed] > > [vwrap] Meeting in Maastricht/IETF78 ? > > Joshua Bell > > to: > > vwrap > > 06/11/2010 04:28 PM > > Sent by: > > vwrap-bounces@ietf.org > > Quick poll: > > Are any VWRAP participants planning to attend IETF78 in Maastricht > and, if so, are there VWRAP issues you would like to have on the > agenda for a face-to-face meeting? > > The chairs are trying to gauge whether or not we should request a > session slot. You can reply to the list, or privately to me. > _______________________________________________ > vwrap mailing list > vwrap@ietf.org > https://www.ietf.org/mailman/listinfo/vwrap --=_alternative 007CB5DD8525773F_= Content-Type: text/html; charset="US-ASCII"
I am currently available to do the meeting, if there would be serious work to be done. I'd love to see some real progress on bashing together a storyline
which merged in the Deployment pattern stuff, along with the pattern's Joshua proposed for exposing services into the primary drafts. But.. We'd have
to have a serious set of players f2f to justify the travel, and some serious consensus building discussion prior to the meeting.  I'd be looking for some
clarity on various participants availability to drive the work going forward as well.


- David
~ Zha


vwrap-bounces@ietf.org wrote on 06/11/2010 04:28:17 PM:

> [image removed]
>
> [vwrap] Meeting in Maastricht/IETF78 ?
>
> Joshua Bell
>
> to:
>
> vwrap
>
> 06/11/2010 04:28 PM
>
> Sent by:
>
> vwrap-bounces@ietf.org
>
> Quick poll: 
>
> Are any VWRAP participants planning to attend IETF78 in Maastricht
> and, if so, are there VWRAP issues you would like to have on the
> agenda for a face-to-face meeting?
>
> The chairs are trying to gauge whether or not we should request a
> session slot. You can reply to the list, or privately to me.
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
 --=_alternative 007CB5DD8525773F_=-- From ohmeadhbh@gmail.com Fri Jun 11 15:48:19 2010 Return-Path: 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 C91C728C14D; Fri, 11 Jun 2010 15:48:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 wRgGhu+vWMMu; Fri, 11 Jun 2010 15:48:18 -0700 (PDT) Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 83FE928C14C; Fri, 11 Jun 2010 15:48:18 -0700 (PDT) Received: by qyk8 with SMTP id 8so203733qyk.31 for ; Fri, 11 Jun 2010 15:48:18 -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=BFTdrC+P9lZWNyFHBKplk0S6df2uGBoXppLy4M9cEBY=; b=rx2KaxQNEYJV7GhufZnrovu9GK+htlHNOGz066nh9B8gM3rBH3HqsmdxDCCo6ppqRL X+DkTaf2a7szjUMkMr3Nr1oSSeNpbRghpTlsCD3gbiGCBNuJOLRocVG6J/+L9eiIqxL5 OXfoG6irEdthRf1U/1RZRWhR9lk2yXbPt1bbo= 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=Fo0WOsffeYw/u71NbxgF4p60JH0aPqg85Z2GA5Ybx3rJYA4kAALettRisZTV2JW95M +fWrJc2z/MYjqDx+72HJBfdS7MWHLWkh5t5CJcSxkx6xfFNClPEUxrvbAtAdOSLxC4/F /uRff/IvCSfgHoqcR0lDOuFfNRCZZOlZt/JGU= Received: by 10.224.86.156 with SMTP id s28mr1068928qal.73.1276296498182; Fri, 11 Jun 2010 15:48:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.235.83 with HTTP; Fri, 11 Jun 2010 15:47:58 -0700 (PDT) In-Reply-To: References: From: Meadhbh Hamrick Date: Fri, 11 Jun 2010 15:47:58 -0700 Message-ID: To: David W Levine Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: vwrap@ietf.org, vwrap-bounces@ietf.org Subject: Re: [vwrap] Meeting in Maastricht/IETF78 ? X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2010 22:48:19 -0000 i'm happy to work on these tasks, but i can't make maastricht. -- meadhbh hamrick * it's pronounced "maeve" @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com On Fri, Jun 11, 2010 at 3:42 PM, David W Levine wrote: > > I am currently available to do the meeting, if there would be serious wor= k > to be done. I'd love to see some real progress on bashing together a > storyline > which merged in the Deployment pattern stuff, along with the pattern's > Joshua proposed for exposing services into the primary drafts. But.. We'd > have > to have a serious set of players f2f to justify the travel, and some seri= ous > consensus building discussion prior to the meeting. =A0I'd be looking for= some > clarity on various participants availability to drive the work going forw= ard > as well. > > > - David > ~ Zha > > > vwrap-bounces@ietf.org wrote on 06/11/2010 04:28:17 PM: > >> [image removed] >> >> [vwrap] Meeting in Maastricht/IETF78 ? >> >> Joshua Bell >> >> to: >> >> vwrap >> >> 06/11/2010 04:28 PM >> >> Sent by: >> >> vwrap-bounces@ietf.org >> >> Quick poll: >> >> Are any VWRAP participants planning to attend IETF78 in Maastricht >> and, if so, are there VWRAP issues you would like to have on the >> agenda for a face-to-face meeting? >> >> The chairs are trying to gauge whether or not we should request a >> session slot.=A0You can reply to the list, or privately to me. >> _______________________________________________ >> 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 > > From john.hurliman@intel.com Fri Jun 11 16:35:14 2010 Return-Path: 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 49C6A3A69AA for ; Fri, 11 Jun 2010 16:35:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.185 X-Spam-Level: X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4] 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 NxfykH8hIfd2 for ; Fri, 11 Jun 2010 16:35:13 -0700 (PDT) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by core3.amsl.com (Postfix) with ESMTP id 5532B3A67AF for ; Fri, 11 Jun 2010 16:35:13 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 11 Jun 2010 16:31:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.53,405,1272870000"; d="scan'208";a="526137500" Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by orsmga002.jf.intel.com with ESMTP; 11 Jun 2010 16:34:17 -0700 Received: from rrsmsx606.amr.corp.intel.com (10.31.1.130) by rrsmsx604.amr.corp.intel.com (10.31.0.170) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 11 Jun 2010 17:35:15 -0600 Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by RRSMSX606.amr.corp.intel.com ([10.31.1.130]) with mapi; Fri, 11 Jun 2010 17:35:15 -0600 From: "Hurliman, John" To: Joshua Bell , "vwrap@ietf.org" Date: Fri, 11 Jun 2010 17:35:14 -0600 Thread-Topic: [vwrap] Meeting in Maastricht/IETF78 ? Thread-Index: AcsJpKe2fDK1B5wQRv2XMnGviBTHSgAGgCRw Message-ID: <62BFE5680C037E4DA0B0A08946C0933DDA47A9B6@rrsmsx506.amr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Subject: Re: [vwrap] Meeting in Maastricht/IETF78 ? X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2010 23:35:14 -0000 SSBjYW5ub3QgbWFrZSBpdCBvdXQgdG8gTWFhc3RyaWNodC4gSSB3b3VsZCBiZSBpbnRlcmVzdGVk IGluIGhlYXJpbmcgZnJvbSBhbnlvbmUgd2hvIGlzIHN0aWxsIHdvcmtpbmcgb24gVldSQVAgdGhv dWdoLg0KSm9obg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHZ3cmFw LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp2d3JhcC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh bGYNCj4gT2YgSm9zaHVhIEJlbGwNCj4gU2VudDogRnJpZGF5LCBKdW5lIDExLCAyMDEwIDE6Mjgg UE0NCj4gVG86IHZ3cmFwQGlldGYub3JnDQo+IFN1YmplY3Q6IFt2d3JhcF0gTWVldGluZyBpbiBN YWFzdHJpY2h0L0lFVEY3OCA/DQo+IA0KPiBRdWljayBwb2xsOg0KPiANCj4gQXJlIGFueSBWV1JB UCBwYXJ0aWNpcGFudHMgcGxhbm5pbmcgdG8gYXR0ZW5kIElFVEY3OCBpbiBNYWFzdHJpY2h0IGFu ZCwNCj4gaWYgc28sIGFyZSB0aGVyZSBWV1JBUCBpc3N1ZXMgeW91IHdvdWxkIGxpa2UgdG8gaGF2 ZSBvbiB0aGUgYWdlbmRhIGZvcg0KPiBhIGZhY2UtdG8tZmFjZSBtZWV0aW5nPw0KPiANCj4gVGhl IGNoYWlycyBhcmUgdHJ5aW5nIHRvIGdhdWdlIHdoZXRoZXIgb3Igbm90IHdlIHNob3VsZCByZXF1 ZXN0IGENCj4gc2Vzc2lvbiBzbG90LiBZb3UgY2FuIHJlcGx5IHRvIHRoZSBsaXN0LCBvciBwcml2 YXRlbHkgdG8gbWUuDQoNCg== From morgaine.dinova@googlemail.com Sat Jun 12 08:53:07 2010 Return-Path: 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 4C30B3A68BC for ; Sat, 12 Jun 2010 08:53:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.624 X-Spam-Level: X-Spam-Status: No, score=0.624 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 J3+PXLcndV6X for ; Sat, 12 Jun 2010 08:53:06 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id A846A3A6837 for ; Sat, 12 Jun 2010 08:53:05 -0700 (PDT) Received: by wyi11 with SMTP id 11so1274864wyi.31 for ; Sat, 12 Jun 2010 08:53:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=jHA+vB3ZLxD306p7cPqEXSACydfAbn20Vd0FnoWmRrs=; b=VRaUcomZbX4y/E1waSWHLxhQR1TgWN3MkzY/2q08upiH6nUX06jX9EIcG/+emgzC9n 2HFsvTlDfnpQ3iXeFkXluHw2qRdh0nszpIW2Evwt2yl++JJPe0eAxyCPklebAuy6W9p2 1qjVN2risjbJKRi5E8kgGEAkbV2JR/V9rau4A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YKrMRZYpGHK2HeDIShL5g1sXDmMLf70l0IN4zrI7QohrW6iNK3bw9zHYy/GQ1bEUEx oPBvTkFRgdPuDkZYaAvA1fvpFWXI99fwiXxAhrZ0nmDt0x+nc6tVGcMfIr/RcVATiBWJ b4r+JVfolsRlzSlq4jq4phU1V4C6M/ixJVg7w= MIME-Version: 1.0 Received: by 10.216.184.197 with SMTP id s47mr624203wem.63.1276357984324; Sat, 12 Jun 2010 08:53:04 -0700 (PDT) Received: by 10.216.26.132 with HTTP; Sat, 12 Jun 2010 08:53:04 -0700 (PDT) Date: Sat, 12 Jun 2010 16:53:04 +0100 Message-ID: From: Morgaine To: vwrap@ietf.org Content-Type: multipart/alternative; boundary=0016e6498540454a1e0488d74052 Subject: [vwrap] SimianGrid protocols and VWRAP X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jun 2010 15:53:07 -0000 --0016e6498540454a1e0488d74052 Content-Type: text/plain; charset=ISO-8859-1 John, I know that you've been doing some very interesting work on the SimianGrid project, and that some parts of it are related to the standards effort in this Working Group. Unfortunately your protocol work beyond LLSD has never been described to us here. The IETF standards process operates through the mailing lists of its Working Groups, so if you want your work to have a direct bearing on our protocol discussions, you need to describe your protocol elements here. Actual implementations are of course exceedingly important and non-optional, but the analysis, discussion and refinement of code into an IETF standards protocol happens here, not in individual project groups. You've said before that more information is forthcoming. I would very much welcome that. While your code seems to be progressing nicely, we need any new protocol information described here to help the Working Group move along on the standards process. Morgaine. ====================================== On Sat, Jun 12, 2010 at 12:35 AM, Hurliman, John wrote: > I cannot make it out to Maastricht. I would be interested in hearing from > anyone who is still working on VWRAP though. > John > > > -----Original Message----- > > From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf > > Of Joshua Bell > > Sent: Friday, June 11, 2010 1:28 PM > > To: vwrap@ietf.org > > Subject: [vwrap] Meeting in Maastricht/IETF78 ? > > > > Quick poll: > > > > Are any VWRAP participants planning to attend IETF78 in Maastricht and, > > if so, are there VWRAP issues you would like to have on the agenda for > > a face-to-face meeting? > > > > The chairs are trying to gauge whether or not we should request a > > session slot. You can reply to the list, or privately to me. > > _______________________________________________ > vwrap mailing list > vwrap@ietf.org > https://www.ietf.org/mailman/listinfo/vwrap > --0016e6498540454a1e0488d74052 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable John, I know that you've been doing some very interesting work on the S= imianGrid project, and that some parts of it are related to the standards e= ffort in this Working Group.=A0 Unfortunately your protocol work beyond LLS= D has never been described to us here.

The IETF standards process operates through the mailing lists of its Wo= rking Groups, so if you want your work to have a direct bearing on our prot= ocol discussions, you need to describe your protocol elements here.=A0 Actu= al implementations are of course exceedingly important and non-optional, bu= t the analysis, discussion and refinement of code into an IETF standards pr= otocol happens here, not in individual project groups.

You've said before that more information is forthcoming.=A0 I would= very much welcome that.=A0 While your code seems to be progressing nicely,= we need any new protocol information described here to help the Working Gr= oup move along on the standards process.


Morgaine.






=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D

On Sat, Jun 12, 2010 at 12:35 A= M, Hurliman, John <john.hurliman@intel.com> wrote:
I cannot make it = out to Maastricht. I would be interested in hearing from anyone who is stil= l working on VWRAP though.
John

> -----Original Message-----
> From: vwrap-bounces@ietf.org= [mailto:vwrap-bounces@ietf.o= rg] On Behalf
> Of Joshua Bell
> Sent: Friday, June 11, 2010 1:28 PM
> To: vwrap@ietf.org
> Subject: [vwrap] Meeting in Maastricht/IETF78 ?
>
> Quick poll:
>
> Are any VWRAP participants planning to attend IETF78 in Maastricht and= ,
> if so, are there VWRAP issues you would like to have on the agenda for=
> a face-to-face meeting?
>
> The chairs are trying to gauge whether or not we should request a
> session slot. You can reply to the list, or privately to me.

_____________________________= __________________
vwrap mailing list
vwrap@ietf.org
h= ttps://www.ietf.org/mailman/listinfo/vwrap

--0016e6498540454a1e0488d74052-- From josh@lindenlab.com Mon Jun 14 08:51:36 2010 Return-Path: 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 45BFE3A69D8 for ; Mon, 14 Jun 2010 08:51:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.117 X-Spam-Level: X-Spam-Status: No, score=-0.117 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 ubTvmezt9rfQ for ; Mon, 14 Jun 2010 08:51:35 -0700 (PDT) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id A3B003A69D4 for ; Mon, 14 Jun 2010 08:51:35 -0700 (PDT) Received: by pwi8 with SMTP id 8so3198868pwi.31 for ; Mon, 14 Jun 2010 08:51:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.248.16 with SMTP id v16mr4675228wah.26.1276530696810; Mon, 14 Jun 2010 08:51:36 -0700 (PDT) Received: by 10.114.148.16 with HTTP; Mon, 14 Jun 2010 08:51:36 -0700 (PDT) In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DDA47A9B6@rrsmsx506.amr.corp.intel.com> References: <62BFE5680C037E4DA0B0A08946C0933DDA47A9B6@rrsmsx506.amr.corp.intel.com> Date: Mon, 14 Jun 2010 08:51:36 -0700 Message-ID: From: Joshua Bell To: "vwrap@ietf.org" Content-Type: multipart/alternative; boundary=0016e64c2e24ba70ec0488ff76f0 Subject: Re: [vwrap] Meeting in Maastricht/IETF78 ? X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2010 15:51:36 -0000 --0016e64c2e24ba70ec0488ff76f0 Content-Type: text/plain; charset=UTF-8 Thanks, all. Given that we still have a backlog of issues to work through from IETF77 and no definite attendance from group members, I'm moving that we defer from requesting a time slot for IETF78. (The cut-off for such is today.) --0016e64c2e24ba70ec0488ff76f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks, all.

Given that we still have a backlog of issue= s to work through from IETF77 and no definite attendance from group members= , I'm moving that we defer from requesting a time slot for IETF78. (The= cut-off for such is today.)

--0016e64c2e24ba70ec0488ff76f0-- From john.hurliman@intel.com Mon Jun 14 15:08:22 2010 Return-Path: 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 2FC473A69F0 for ; Mon, 14 Jun 2010 15:08:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.998 X-Spam-Level: X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 zrGTMNLjG-cg for ; Mon, 14 Jun 2010 15:08:13 -0700 (PDT) Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by core3.amsl.com (Postfix) with ESMTP id E39E728C0E1 for ; Mon, 14 Jun 2010 15:08:12 -0700 (PDT) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 14 Jun 2010 15:08:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.53,416,1272870000"; d="scan'208,217";a="288846499" Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by azsmga001.ch.intel.com with ESMTP; 14 Jun 2010 15:08:12 -0700 Received: from rrsmsx605.amr.corp.intel.com (10.31.1.129) by rrsmsx604.amr.corp.intel.com (10.31.0.170) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 14 Jun 2010 16:08:13 -0600 Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by RRSMSX605.amr.corp.intel.com ([10.31.1.129]) with mapi; Mon, 14 Jun 2010 16:08:12 -0600 From: "Hurliman, John" To: "vwrap@ietf.org" Date: Mon, 14 Jun 2010 16:08:12 -0600 Thread-Topic: [vwrap] SimianGrid protocols and VWRAP Thread-Index: AcsKR2Rgpp5zlY/aS62A42f0mH4+4wBv+Jag Message-ID: <62BFE5680C037E4DA0B0A08946C0933DDA50BA62@rrsmsx506.amr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_62BFE5680C037E4DA0B0A08946C0933DDA50BA62rrsmsx506amrcor_" MIME-Version: 1.0 Subject: Re: [vwrap] SimianGrid protocols and VWRAP X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2010 22:08:22 -0000 --_000_62BFE5680C037E4DA0B0A08946C0933DDA50BA62rrsmsx506amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I've recently been working closely with my team at Intel on systems scalabi= lity problems in virtual worlds and have not had as much time to focus on V= WRAP implementation. I did finish up a bit of coding over the weekend thoug= h and added initial support for VWRAP launch documents[1] to SimianGrid[2].= A bit of background: SimianGrid is a set of web services that provides critical backend componen= ts for a virtual world. These are the "grid services" in Second Life or Ope= nSim terminology, or Agent Domain in VWRAP terminology. The components incl= ude content storage and distribution (assets), user accounts/identity, user= inventory, spatial mapping (region registration, map tiles), and a login s= ervice. This is enough to provide full support for the grid connector API i= n the upcoming release of OpenSim 0.7 (which will natively support SimianGr= id), and is also compatible with the lightweight simulation platform we use= for prototyping called Simian (which SimianGrid was named after). SimianGr= id is written entirely in PHP, and also includes a web frontend named Simia= nGridFrontend using the CodeIgniter framework and a WebDAV inventory fronte= nd named SimianGridWebDAV using the SabreDAV library. A major hurdle that OpenSim-based virtual worlds have to overcome is the ac= count creation, login process, and content import process for every world a= user visits (and the myriad of issues surrounding each of those topics). W= hile one of the ultimate goals of VWRAP is to solve all of those issues, VW= RAP launch documents provide a solution for the login process and a steppin= g stone toward solving the account creation process. The plan is for Simian= Grid to support two launch document methods: authenticated and unauthentica= ted. Either can optionally carry a starting location URI. Unauthenticated m= ode is as simple as telling the rich client where the login URL of the grid= is. Authenticated mode carries identity information (agent name) and the l= ogin URL is actually a capability allowing direct login from web to world. = This also functions as a successor to the GridInfo[3] protocol that OpenSim= developed to inform viewers of various grid-specific URLs. The original plan was for launch document support to go into Snowglobe, but= with Snowglobe VWRAP development on hiatus I refitted my Cable Beach Launc= her app into VWRAP Launcher that I will release in a few days. If a VWRAP t= eleport draft surfaces I can start on an implementation, but that won't get= far without viewer support for it. Meadhbh, I have a small number of refinement suggestions for the launch doc= ument spec (again) but I'll wait until we have a few experimental grids act= ually running the code before making any firm arguments. [1] http://tools.ietf.org/html/draft-hamrick-vwrap-launch [2] http://openmetaverse.googlecode.com/ [3] http://opensimulator.org/wiki/GridInfo John From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf Of M= orgaine Sent: Saturday, June 12, 2010 8:53 AM To: vwrap@ietf.org Subject: [vwrap] SimianGrid protocols and VWRAP John, I know that you've been doing some very interesting work on the Simia= nGrid project, and that some parts of it are related to the standards effor= t in this Working Group. Unfortunately your protocol work beyond LLSD has = never been described to us here. The IETF standards process operates through the mailing lists of its Workin= g Groups, so if you want your work to have a direct bearing on our protocol= discussions, you need to describe your protocol elements here. Actual imp= lementations are of course exceedingly important and non-optional, but the = analysis, discussion and refinement of code into an IETF standards protocol= happens here, not in individual project groups. You've said before that more information is forthcoming. I would very much= welcome that. While your code seems to be progressing nicely, we need any= new protocol information described here to help the Working Group move alo= ng on the standards process. Morgaine. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On Sat, Jun 12, 2010 at 12:35 AM, Hurliman, John > wrote: I cannot make it out to Maastricht. I would be interested in hearing from a= nyone who is still working on VWRAP though. John > -----Original Message----- > From: vwrap-bounces@ietf.org [mailto:vwrap= -bounces@ietf.org] On Behalf > Of Joshua Bell > Sent: Friday, June 11, 2010 1:28 PM > To: vwrap@ietf.org > Subject: [vwrap] Meeting in Maastricht/IETF78 ? > > Quick poll: > > Are any VWRAP participants planning to attend IETF78 in Maastricht and, > if so, are there VWRAP issues you would like to have on the agenda for > a face-to-face meeting? > > The chairs are trying to gauge whether or not we should request a > session slot. You can reply to the list, or privately to me. _______________________________________________ vwrap mailing list vwrap@ietf.org https://www.ietf.org/mailman/listinfo/vwrap --_000_62BFE5680C037E4DA0B0A08946C0933DDA50BA62rrsmsx506amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’v= e recently been working closely with my team at Intel on systems scalabilit= y problems in virtual worlds and have not had as much time to focus on VWRA= P implementation. I did finish up a bit of coding over the weekend though a= nd added initial support for VWRAP launch documents[1] to SimianGrid[2]. A = bit of background:

&n= bsp;

SimianGrid is a set of web= services that provides critical backend components for a virtual world. Th= ese are the “grid services” in Second Life or OpenSim terminolo= gy, or Agent Domain in VWRAP terminology. The components include content st= orage and distribution (assets), user accounts/identity, user inventory, sp= atial mapping (region registration, map tiles), and a login service. This i= s enough to provide full support for the grid connector API in the upcoming= release of OpenSim 0.7 (which will natively support SimianGrid), and is al= so compatible with the lightweight simulation platform we use for prototypi= ng called Simian (which SimianGrid was named after). SimianGrid is written = entirely in PHP, and also includes a web frontend named SimianGridFrontend = using the CodeIgniter framework and a WebDAV inventory frontend named Simia= nGridWebDAV using the SabreDAV library.

 

A ma= jor hurdle that OpenSim-based virtual worlds have to overcome is the accoun= t creation, login process, and content import process for every world a use= r visits (and the myriad of issues surrounding each of those topics). While= one of the ultimate goals of VWRAP is to solve all of those issues, VWRAP = launch documents provide a solution for the login process and a stepping st= one toward solving the account creation process. The plan is for SimianGrid= to support two launch document methods: authenticated and unauthenticated.= Either can optionally carry a starting location URI. Unauthenticated mode = is as simple as telling the rich client where the login URL of the grid is.= Authenticated mode carries identity information (agent name) and the login= URL is actually a capability allowing direct login from web to world. This= also functions as a successor to the GridInfo[3] protocol that OpenSim dev= eloped to inform viewers of various grid-specific URLs.

 

The original plan was for launch document support to go into Sno= wglobe, but with Snowglobe VWRAP development on hiatus I refitted my Cable = Beach Launcher app into VWRAP Launcher that I will release in a few days. I= f a VWRAP teleport draft surfaces I can start on an implementation, but tha= t won’t get far without viewer support for it.

<= p class=3DMsoNormal> 

Meadhbh, I have a small number of refinement suggestions for the la= unch document spec (again) but I’ll wait until we have a few experime= ntal grids actually running the code before making any firm arguments.=

 

[1] http://tools.ietf.org/html/draft-hamrick-vwrap-launch<= /a>

[2] http://openmetaverse.googlecode.com/

[3] http://opensimulator.org/wiki/GridInfo

 

John

 

 

From: vwrap-bounces@ietf.org [mailto:vwrap-b= ounces@ietf.org] On Behalf Of Morgaine
Sent: Saturday, Jun= e 12, 2010 8:53 AM
To: vwrap@ietf.org
Subject: [vwrap] = SimianGrid protocols and VWRAP

 

John= , I know that you've been doing some very interesting work on the SimianGri= d project, and that some parts of it are related to the standards effort in= this Working Group.  Unfortunately your protocol work beyond LLSD has= never been described to us here.

The IETF standards process operate= s through the mailing lists of its Working Groups, so if you want your work= to have a direct bearing on our protocol discussions, you need to describe= your protocol elements here.  Actual implementations are of course ex= ceedingly important and non-optional, but the analysis, discussion and refi= nement of code into an IETF standards protocol happens here, not in individ= ual project groups.

You've said before that more information is fort= hcoming.  I would very much welcome that.  While your code seems = to be progressing nicely, we need any new protocol information described he= re to help the Working Group move along on the standards process.

Morgaine.






=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

On Sat, Jun 12, 2010 at 12:35 A= M, Hurliman, John <john.hurli= man@intel.com> wrote:

I cannot ma= ke it out to Maastricht. I would be interested in hearing from anyone who i= s still working on VWRAP though.
John


> -----Original Message-----
> From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf
> Of Jos= hua Bell
> Sent: Friday, June 11, 2010 1:28 PM
> To: vwrap@ietf.org
> Subject: [vwrap] Meeting= in Maastricht/IETF78 ?
>
> Quick poll:
>
> Are any= VWRAP participants planning to attend IETF78 in Maastricht and,
> if= so, are there VWRAP issues you would like to have on the agenda for
>= ; a face-to-face meeting?
>
> The chairs are trying to gauge wh= ether or not we should request a
> session slot. You can reply to the= list, or privately to me.

_______________________________________________
vwrap mailing l= ist
vwrap@ietf.org
https://www.i= etf.org/mailman/listinfo/vwrap

 

= --_000_62BFE5680C037E4DA0B0A08946C0933DDA50BA62rrsmsx506amrcor_-- From john.hurliman@intel.com Wed Jun 16 21:50:35 2010 Return-Path: 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 5B8DC3A6938 for ; Wed, 16 Jun 2010 21:50:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.998 X-Spam-Level: X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4] 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 RgbAC4tigML6 for ; Wed, 16 Jun 2010 21:50:33 -0700 (PDT) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by core3.amsl.com (Postfix) with ESMTP id 7AE933A689B for ; Wed, 16 Jun 2010 21:50:30 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 16 Jun 2010 21:50:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.53,429,1272870000"; d="scan'208";a="808796461" Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by fmsmga001.fm.intel.com with ESMTP; 16 Jun 2010 21:50:35 -0700 Received: from rrsmsx601.amr.corp.intel.com (10.31.0.151) by rrsmsx604.amr.corp.intel.com (10.31.0.170) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 16 Jun 2010 22:50:35 -0600 Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx601.amr.corp.intel.com ([10.31.0.151]) with mapi; Wed, 16 Jun 2010 22:50:35 -0600 From: "Hurliman, John" To: "vwrap@ietf.org" Date: Wed, 16 Jun 2010 22:50:32 -0600 Thread-Topic: [vwrap] SimianGrid protocols and VWRAP Thread-Index: AcsKR2Rgpp5zlY/aS62A42f0mH4+4wBv+JagAHPs9IA= Message-ID: <62BFE5680C037E4DA0B0A08946C0933DDA50C612@rrsmsx506.amr.corp.intel.com> References: <62BFE5680C037E4DA0B0A08946C0933DDA50BA62@rrsmsx506.amr.corp.intel.com> In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DDA50BA62@rrsmsx506.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [vwrap] SimianGrid protocols and VWRAP X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 04:50:35 -0000 I just released the first version of the VWRAP Launcher on . Source code and a Windows installer are available (p= ackaged binaries for other platforms will come when I have time or someone = else volunteers). VWRAP launch document support in SimianGrid is still bein= g worked on and not integrated into the web interface yet, but you can test= out unauthenticated launches by visiting: http://yoursimiangrid.com/GridFrontend/index.php/launch Which should return a JSON LLSD document with an application/calm+json MIME= type containing the login URL for that grid. The launcher app supports man= y more features in launch documents: starting location URIs, pre-authentica= ted logins, and various SL viewer helper URLs that should just start workin= g when SimianGrid is updated with new launch code. I also added a Google Maps world map interface to SimianGrid; we should be = clicking from OpenSim maps straight in-world soon. John > -----Original Message----- > From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf > Of Hurliman, John > Sent: Monday, June 14, 2010 3:08 PM > To: vwrap@ietf.org > Subject: Re: [vwrap] SimianGrid protocols and VWRAP >=20 > I've recently been working closely with my team at Intel on systems > scalability problems in virtual worlds and have not had as much time to > focus on VWRAP implementation. I did finish up a bit of coding over the > weekend though and added initial support for VWRAP launch documents[1] > to SimianGrid[2]. A bit of background: >=20 >=20 >=20 > SimianGrid is a set of web services that provides critical backend > components for a virtual world. These are the "grid services" in Second > Life or OpenSim terminology, or Agent Domain in VWRAP terminology. The > components include content storage and distribution (assets), user > accounts/identity, user inventory, spatial mapping (region > registration, map tiles), and a login service. This is enough to > provide full support for the grid connector API in the upcoming release > of OpenSim 0.7 (which will natively support SimianGrid), and is also > compatible with the lightweight simulation platform we use for > prototyping called Simian (which SimianGrid was named after). > SimianGrid is written entirely in PHP, and also includes a web frontend > named SimianGridFrontend using the CodeIgniter framework and a WebDAV > inventory frontend named SimianGridWebDAV using the SabreDAV library. >=20 >=20 >=20 > A major hurdle that OpenSim-based virtual worlds have to overcome is > the account creation, login process, and content import process for > every world a user visits (and the myriad of issues surrounding each of > those topics). While one of the ultimate goals of VWRAP is to solve all > of those issues, VWRAP launch documents provide a solution for the > login process and a stepping stone toward solving the account creation > process. The plan is for SimianGrid to support two launch document > methods: authenticated and unauthenticated. Either can optionally carry > a starting location URI. Unauthenticated mode is as simple as telling > the rich client where the login URL of the grid is. Authenticated mode > carries identity information (agent name) and the login URL is actually > a capability allowing direct login from web to world. This also > functions as a successor to the GridInfo[3] protocol that OpenSim > developed to inform viewers of various grid-specific URLs. >=20 >=20 >=20 > The original plan was for launch document support to go into Snowglobe, > but with Snowglobe VWRAP development on hiatus I refitted my Cable > Beach Launcher app into VWRAP Launcher that I will release in a few > days. If a VWRAP teleport draft surfaces I can start on an > implementation, but that won't get far without viewer support for it. >=20 >=20 >=20 > Meadhbh, I have a small number of refinement suggestions for the launch > document spec (again) but I'll wait until we have a few experimental > grids actually running the code before making any firm arguments. >=20 >=20 >=20 > [1] http://tools.ietf.org/html/draft-hamrick-vwrap-launch >=20 > [2] http://openmetaverse.googlecode.com/ >=20 > [3] http://opensimulator.org/wiki/GridInfo >=20 >=20 >=20 > John >=20 >=20 >=20 >=20 >=20 > From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf > Of Morgaine > Sent: Saturday, June 12, 2010 8:53 AM > To: vwrap@ietf.org > Subject: [vwrap] SimianGrid protocols and VWRAP >=20 >=20 >=20 > John, I know that you've been doing some very interesting work on the > SimianGrid project, and that some parts of it are related to the > standards effort in this Working Group. Unfortunately your protocol > work beyond LLSD has never been described to us here. >=20 > The IETF standards process operates through the mailing lists of its > Working Groups, so if you want your work to have a direct bearing on > our protocol discussions, you need to describe your protocol elements > here. Actual implementations are of course exceedingly important and > non-optional, but the analysis, discussion and refinement of code into > an IETF standards protocol happens here, not in individual project > groups. >=20 > You've said before that more information is forthcoming. I would very > much welcome that. While your code seems to be progressing nicely, we > need any new protocol information described here to help the Working > Group move along on the standards process. >=20 >=20 > Morgaine. >=20 >=20 >=20 >=20 >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > On Sat, Jun 12, 2010 at 12:35 AM, Hurliman, John > wrote: >=20 > I cannot make it out to Maastricht. I would be interested in hearing > from anyone who is still working on VWRAP though. > John >=20 >=20 > > -----Original Message----- > > From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On > Behalf > > Of Joshua Bell > > Sent: Friday, June 11, 2010 1:28 PM > > To: vwrap@ietf.org > > Subject: [vwrap] Meeting in Maastricht/IETF78 ? > > > > Quick poll: > > > > Are any VWRAP participants planning to attend IETF78 in Maastricht > > and, if so, are there VWRAP issues you would like to have on the > > agenda for a face-to-face meeting? > > > > The chairs are trying to gauge whether or not we should request a > > session slot. You can reply to the list, or privately to me. >=20 > _______________________________________________ > vwrap mailing list > vwrap@ietf.org > https://www.ietf.org/mailman/listinfo/vwrap >=20 >=20 From josh@lindenlab.com Thu Jun 17 10:38:09 2010 Return-Path: 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 0F5C13A6B0B for ; Thu, 17 Jun 2010 10:38:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.254 X-Spam-Level: X-Spam-Status: No, score=0.254 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 jMftzi5O3Gc7 for ; Thu, 17 Jun 2010 10:38:06 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id D6B0A3A6929 for ; Thu, 17 Jun 2010 10:37:50 -0700 (PDT) Received: by vws15 with SMTP id 15so97384vws.31 for ; Thu, 17 Jun 2010 10:37:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.89.166 with SMTP id e38mr1639475vcm.247.1276796272447; Thu, 17 Jun 2010 10:37:52 -0700 (PDT) Received: by 10.220.203.201 with HTTP; Thu, 17 Jun 2010 10:37:52 -0700 (PDT) In-Reply-To: References: <181BEC41-396C-4E2D-ADE8-705CBAD4C31C@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933DDA3D3401@rrsmsx506.amr.corp.intel.com> Date: Thu, 17 Jun 2010 10:37:52 -0700 Message-ID: From: Joshua Bell To: vwrap Content-Type: multipart/alternative; boundary=0016e64766044512dd04893d4cf3 Subject: Re: [vwrap] Linden Lab open source LLSD code X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 17:38:10 -0000 --0016e64766044512dd04893d4cf3 Content-Type: text/plain; charset=UTF-8 FYI, I've added: Ruby: * A small impl that just supports XML serialization. Hopefully someone can take it farther. This is tagged as "v3". C++ * JSON serialization support, with unit tests. Note that Linden doesn't use this in production (yet) so approach the code with caution. * As proposed on the WG: asBinary() for string values now does a base64 decode and returns the binary data if successful, an empty vector otherwise; asString() for binary values now does a base64 encode and returns the string. * I limit the serialization of fractional seconds in dates to 3 places to match other languages. This change may need to be reverted. * I have not built/tested these changes on Windows or Mac OS, so this is not yet tagged. --0016e64766044512dd04893d4cf3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable FYI, I've added:

Ruby:
* A small impl that= just supports XML serialization. Hopefully someone can take it farther. Th= is is tagged as "v3".

C++
* JS= ON serialization support, with unit tests. Note that Linden doesn't use= this in production (yet) so approach the code with caution.
* As proposed on the WG: asBinary() for string values now does a base6= 4 decode and returns the binary data if successful, an empty vector otherwi= se; =C2=A0asString() for binary values now does a base64 encode and returns= the string.
* I limit the serialization of fractional seconds in dates to 3 places= to match other languages. This change may need to be reverted.
*= I have not built/tested these changes on Windows or Mac OS, so this is not= yet tagged.

--0016e64766044512dd04893d4cf3-- From josh@lindenlab.com Thu Jun 17 13:11:39 2010 Return-Path: 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 9F8823A6B14 for ; Thu, 17 Jun 2010 13:11:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.876 X-Spam-Level: X-Spam-Status: No, score=0.876 tagged_above=-999 required=5 tests=[AWL=-0.746, BAYES_60=1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 I21kAVI5Xs9t for ; Thu, 17 Jun 2010 13:11:38 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 306663A69EC for ; Thu, 17 Jun 2010 13:11:38 -0700 (PDT) Received: by vws15 with SMTP id 15so252990vws.31 for ; Thu, 17 Jun 2010 13:11:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.63.135 with SMTP id b7mr6138692vci.262.1276805500800; Thu, 17 Jun 2010 13:11:40 -0700 (PDT) Received: by 10.220.203.201 with HTTP; Thu, 17 Jun 2010 13:11:40 -0700 (PDT) Date: Thu, 17 Jun 2010 13:11:40 -0700 Message-ID: From: Joshua Bell To: vwrap@ietf.org Content-Type: multipart/alternative; boundary=e0cb4e88768b528e7a04893f72dd Subject: [vwrap] Linden Lab Involvement in Virtual World Interoperability X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 20:11:39 -0000 --e0cb4e88768b528e7a04893f72dd Content-Type: text/plain; charset=UTF-8 (Speaking as a Linden Lab employee/individual, not co-chair) Hey friends - As Linden Lab recently announced ( http://www.prnewswire.com/news-releases/linden-lab-restructures-to-generate-efficiencies-and-support-investment-in-new-platforms-95982564.html), the company has undergone some restructuring and refocusing of efforts. As part of that refocusing, Linden has reduced engineering resources tasked specifically with implementing the standards emerging through the VWRAP WG process. Linden will continue to be engaged on efforts that directly align with business goals and current development needs, and in fostering the ecosystem around Second Life - for example, publication of data formats and APIs for interfacing with Second Life. For the near term, however, Linden will not be explicitly funding production of specifications or implementations related to virtual world interoperability. Linden Lab continues to be supportive of the standardization process and we hope to be able to be more actively involved at some point in the future. I plan to volunteer my personal time to mediate discussions as co-chair of the working group, as long as there remains interest in tackling issues within the VWRAP WG charter. As individuals, many other Linden Lab employees are and continue to be involved in standardization efforts, around virtual worlds and other IETF efforts. Thanks, Joshua Bell Director of Technology Integration Linden Research, Inc. --e0cb4e88768b528e7a04893f72dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
(Speaking as a Linden Lab employee/individual, not co-chair)

Hey friends -=C2=A0

As Linden Lab = recently announced (http://www.prnewswire.com/news-releases/linden-lab= -restructures-to-generate-efficiencies-and-support-investment-in-new-platfo= rms-95982564.html), the company has undergone some restructuring and re= focusing of efforts.

As part of that refocusing, Linden has reduced engineer= ing resources tasked specifically with implementing the standards emerging = through the VWRAP WG process. Linden will continue to be engaged on efforts= that directly align with business goals and current development needs, and= in fostering the ecosystem around Second Life - for example, publication o= f data formats and APIs for interfacing with Second Life. For the near term= , however, Linden will not be explicitly funding production of specificatio= ns or implementations related to virtual world interoperability. Linden Lab= continues to be supportive of the standardization process and we hope to b= e able to be more actively involved at some point in the future.

I plan to volunteer my personal time to mediate discuss= ions as co-chair of the working group, as long as there remains interest in= tackling issues within the VWRAP WG charter. As individuals, many other Li= nden Lab employees are and continue to be involved in standardization effor= ts, around virtual worlds and other IETF efforts.

Thanks,

Joshua Bell
= Director of Technology Integration
Linden Research, Inc.

--e0cb4e88768b528e7a04893f72dd-- From morgaine.dinova@googlemail.com Thu Jun 17 14:09:58 2010 Return-Path: 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 656693A6B22 for ; Thu, 17 Jun 2010 14:09:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.457 X-Spam-Level: * X-Spam-Status: No, score=1.457 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SARE_FWDLOOK=1.666] 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 5-aVQbp96XUP for ; Thu, 17 Jun 2010 14:09:57 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id BE7E13A6B1F for ; Thu, 17 Jun 2010 14:09:56 -0700 (PDT) Received: by wya21 with SMTP id 21so324472wya.31 for ; Thu, 17 Jun 2010 14:09:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=VrJdYSnX1J3IUjdjK4R3tMz2ncFcVYwi8wogH8lPY4I=; b=a1njwp8FB/nZJOsByb2niO7RlAkQzRrH8EHeRhPwiVlzBushTHbIHUKGgyIAxqIFjf SZqNgM4SDqJ5fB96HsChD1QnbHWkYHp/dUqTiBfe4k5dvNrwJhDyloHGUQ55TAvdd+5w mKVwxTBjZ37YIhan4gUOKlX1Dn3WOZL0Hwyoc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Jb3DwBtWh+hBisdQZ8ohT9XOVM+JvDwqVDjmJWXk3kaa3pznIB/7yrEq7bUPkpvdvK fxYs1fYjlHmd4Tmla5dYCPQvPFZneE6SCBi9IF/UVJoorFDUzngXjrjZAH8gzCBCQmZX 1Utg9GARwvGgw/QxqwxDqPILiP8zFJwSihkmE= MIME-Version: 1.0 Received: by 10.216.88.144 with SMTP id a16mr69567wef.77.1276808997850; Thu, 17 Jun 2010 14:09:57 -0700 (PDT) Received: by 10.216.72.67 with HTTP; Thu, 17 Jun 2010 14:09:57 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Jun 2010 22:09:57 +0100 Message-ID: From: Morgaine To: vwrap@ietf.org Content-Type: multipart/alternative; boundary=0016e6d77e67c34eba0489404222 Subject: Re: [vwrap] Linden Lab Involvement in Virtual World Interoperability X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 21:09:58 -0000 --0016e6d77e67c34eba0489404222 Content-Type: text/plain; charset=ISO-8859-1 Sorry to hear about the reduction in resourcing at the Lab, Joshua, but I'm very glad to hear that you're remaining at VWRAP in a personal capacity. Interest in VW protocols and interop is certain to bloom in the years ahead, so there's going to be a lot to do, with or without sponsorship. I would also wish to voice my support for your independent co-chairing, which has always been even-handed and forward looking. The future of VW interop looks bright to me, and VWRAP can certainly be a useful part of that. Morgaine. ================================= On Thu, Jun 17, 2010 at 9:11 PM, Joshua Bell wrote: > (Speaking as a Linden Lab employee/individual, not co-chair) > > Hey friends - > > As Linden Lab recently announced ( > http://www.prnewswire.com/news-releases/linden-lab-restructures-to-generate-efficiencies-and-support-investment-in-new-platforms-95982564.html), > the company has undergone some restructuring and refocusing of efforts. > > As part of that refocusing, Linden has reduced engineering resources tasked > specifically with implementing the standards emerging through the VWRAP WG > process. Linden will continue to be engaged on efforts that directly align > with business goals and current development needs, and in fostering the > ecosystem around Second Life - for example, publication of data formats and > APIs for interfacing with Second Life. For the near term, however, Linden > will not be explicitly funding production of specifications or > implementations related to virtual world interoperability. Linden Lab > continues to be supportive of the standardization process and we hope to be > able to be more actively involved at some point in the future. > > I plan to volunteer my personal time to mediate discussions as co-chair of > the working group, as long as there remains interest in tackling issues > within the VWRAP WG charter. As individuals, many other Linden Lab employees > are and continue to be involved in standardization efforts, around virtual > worlds and other IETF efforts. > > Thanks, > > Joshua Bell > Director of Technology Integration > Linden Research, Inc. > > > _______________________________________________ > vwrap mailing list > vwrap@ietf.org > https://www.ietf.org/mailman/listinfo/vwrap > > --0016e6d77e67c34eba0489404222 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sorry to hear about the reduction in resourcing at the Lab, Joshua, but I&#= 39;m very glad to hear that you're remaining at VWRAP in a personal cap= acity.=A0 Interest in VW protocols and interop is certain to bloom in the y= ears ahead, so there's going to be a lot to do, with or without sponsor= ship.

I would also wish to voice my support for your independent co-chairing,= which has always been even-handed and forward looking.=A0 The future of VW= interop looks bright to me, and VWRAP can certainly be a useful part of th= at.


Morgaine.



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Thu, Jun 17, 2010 at 9:11 PM, Joshua Bell <josh@lindenlab.com> wrote:
(Speaking as= a Linden Lab employee/individual, not co-chair)

H= ey friends -=A0

As Linden Lab recently announced (http://www.prnewswire.com/news-releases/linden-lab-restructures-to-genera= te-efficiencies-and-support-investment-in-new-platforms-95982564.html),= the company has undergone some restructuring and refocusing of efforts.

As part of that refocusing, Linden has reduced engineer= ing resources tasked specifically with implementing the standards emerging = through the VWRAP WG process. Linden will continue to be engaged on efforts= that directly align with business goals and current development needs, and= in fostering the ecosystem around Second Life - for example, publication o= f data formats and APIs for interfacing with Second Life. For the near term= , however, Linden will not be explicitly funding production of specificatio= ns or implementations related to virtual world interoperability. Linden Lab= continues to be supportive of the standardization process and we hope to b= e able to be more actively involved at some point in the future.

I plan to volunteer my personal time to mediate discuss= ions as co-chair of the working group, as long as there remains interest in= tackling issues within the VWRAP WG charter. As individuals, many other Li= nden Lab employees are and continue to be involved in standardization effor= ts, around virtual worlds and other IETF efforts.

Thanks,

Joshua Bell
Director of Technology Integration
Linden= Research, Inc.


_______________________________________________
vwrap mailing list
vwrap@ietf.org
h= ttps://www.ietf.org/mailman/listinfo/vwrap


--0016e6d77e67c34eba0489404222-- From barryleiba.mailing.lists@gmail.com Thu Jun 17 16:09:58 2010 Return-Path: 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 1D24F3A6B3E for ; Thu, 17 Jun 2010 16:09:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 hHwzVy2-pwTb for ; Thu, 17 Jun 2010 16:09:57 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 28D2A3A6B3D for ; Thu, 17 Jun 2010 16:09:57 -0700 (PDT) Received: by vws15 with SMTP id 15so414781vws.31 for ; Thu, 17 Jun 2010 16:09:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=9tLLSJEu5MJV1AjRsLb1z3gZ/HDf1D95RE1m4V2ZcDs=; b=DOoKWujQYuYysrs+0klhAnp6J8ltZpF2aB28VrQA1tZKI1WDPS556eHq+H9MmkeceV PTlLp3B+wGFI5PIGDyOAcTUXXy3r/vFd0PcGRmIfz4vccbNEVjdH7qCmB8XheJKq7qz1 n7EKpCU4pfIV5PRQep9Ut6EXR71eGQVgo/yBg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; b=B3NMu52a075kW7GIJ5hUu22Kn/MMSOLw0rzj6uT0hySWHk4vnhDaxiA3YI2eeypt0Y xzAenpXuLOunrPr/44H8AU1chWnX8fAjCy3dWbLl0/qogpp3Zp8dACfSyK9NfmO0/Y+c Rqw/nP1kC0KV6ip7K7co9W15lJ7kYVSBfVtr8= MIME-Version: 1.0 Received: by 10.220.127.2 with SMTP id e2mr116727vcs.137.1276816199252; Thu, 17 Jun 2010 16:09:59 -0700 (PDT) Received: by 10.220.91.40 with HTTP; Thu, 17 Jun 2010 16:09:59 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Jun 2010 19:09:59 -0400 Message-ID: From: Barry Leiba To: vwrap@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [vwrap] Moving startup documents into the working group X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: barryleiba@computer.org List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 23:09:58 -0000 Quoting from my previous message: > It's time to think about which pre-WG documents the working group is > ready to adopt. =A0As I introduce this, I want to stress that adoption > of documents does NOT mean that the group has consensus on the current > content of those documents, that it collectively agrees with what they > say, that the documents are in any sense "ready". =A0All it means is > that the working group thinks they're headed in the right direction, > and can be used as a starting point for further refinement. =A0Indeed, > documents adopted as starting points by the working group might have a > number of significant revisions before they are declared "ready" and > are sent to the IESG. We've had very little response to this, but the response that we've had supports adopting these: > * Introduction and Goals > http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01 > * Trust Model and User Authentication > http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01 > * Abstract Type System for the Transmission of Dynamic Structured Data > http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00 I am, therefore, approving the following document names: - draft-ietf-vwrap-intro - draft-ietf-vwrap-authentication - draft-ietf-vwrap-type-system Noting that these are all under Meadhbh's editorship: Meadhbh, will you please post revisions of these documents before the IETF 79 deadline of 5 July at 17:00 PDT ? Post them with the new names as -00 versions, and they will become working-group documents. Please post whatever version you have of them by the deadline -- even if some have not changed since the last individual-draft version. Thanks. Barry, as chair From john.hurliman@intel.com Thu Jun 17 16:16:35 2010 Return-Path: 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 EBBF23A6B41 for ; Thu, 17 Jun 2010 16:16:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.369 X-Spam-Level: X-Spam-Status: No, score=-4.369 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4] 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 rcDjflcTfKl5 for ; Thu, 17 Jun 2010 16:16:35 -0700 (PDT) Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by core3.amsl.com (Postfix) with ESMTP id 017963A6B3F for ; Thu, 17 Jun 2010 16:16:34 -0700 (PDT) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 17 Jun 2010 16:16:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.53,434,1272870000"; d="scan'208";a="290212013" Received: from rrsmsx603.amr.corp.intel.com ([10.31.0.57]) by azsmga001.ch.intel.com with ESMTP; 17 Jun 2010 16:16:37 -0700 Received: from rrsmsx605.amr.corp.intel.com (10.31.1.129) by rrsmsx603.amr.corp.intel.com (10.31.0.57) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 17 Jun 2010 17:16:37 -0600 Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by RRSMSX605.amr.corp.intel.com ([10.31.1.129]) with mapi; Thu, 17 Jun 2010 17:16:37 -0600 From: "Hurliman, John" To: "barryleiba@computer.org" , "vwrap@ietf.org" Date: Thu, 17 Jun 2010 17:16:37 -0600 Thread-Topic: [vwrap] Moving startup documents into the working group Thread-Index: AcsOcjnRold2ietbTDuMT5SMQRvk8gAAME8w Message-ID: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 23:16:36 -0000 What happened to the launch document draft? Aside from the LLSD type system= , it's the only document that we have a working implementation and deployme= nt for. John -----Original Message----- From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf Of B= arry Leiba Sent: Thursday, June 17, 2010 4:10 PM To: vwrap@ietf.org Subject: Re: [vwrap] Moving startup documents into the working group Quoting from my previous message: > It's time to think about which pre-WG documents the working group is=20 > ready to adopt. =A0As I introduce this, I want to stress that adoption=20 > of documents does NOT mean that the group has consensus on the current=20 > content of those documents, that it collectively agrees with what they=20 > say, that the documents are in any sense "ready". =A0All it means is=20 > that the working group thinks they're headed in the right direction,=20 > and can be used as a starting point for further refinement. =A0Indeed,=20 > documents adopted as starting points by the working group might have a=20 > number of significant revisions before they are declared "ready" and=20 > are sent to the IESG. We've had very little response to this, but the response that we've had sup= ports adopting these: > * Introduction and Goals > http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01 > * Trust Model and User Authentication > http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01 > * Abstract Type System for the Transmission of Dynamic Structured Data > http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00 I am, therefore, approving the following document names: - draft-ietf-vwrap-intro - draft-ietf-vwrap-authentication - draft-ietf-vwrap-type-system Noting that these are all under Meadhbh's editorship: Meadhbh, will you ple= ase post revisions of these documents before the IETF 79 deadline of 5 July at 17:00 PDT ? Post them with the new names as -00 versions, and they will become working-group documents. Please post wh= atever version you have of them by the deadline -- even if some have not ch= anged since the last individual-draft version. Thanks. Barry, as chair _______________________________________________ vwrap mailing list vwrap@ietf.org https://www.ietf.org/mailman/listinfo/vwrap From barryleiba.mailing.lists@gmail.com Thu Jun 17 16:23:47 2010 Return-Path: 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 C05BC3A6B37 for ; Thu, 17 Jun 2010 16:23:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.299 X-Spam-Level: X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, 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 sO5ruhdAxx8t for ; Thu, 17 Jun 2010 16:23:47 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id D64D63A6B2E for ; Thu, 17 Jun 2010 16:23:46 -0700 (PDT) Received: by vws15 with SMTP id 15so429247vws.31 for ; Thu, 17 Jun 2010 16:23:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=13238z3ZiK0lBNK9bRxV+08tJp7xHN8vcsrc1QDZdws=; b=kg0OW9uHIFGsYDS8JPfYPTWs+01rbGNRfBkuWwzf2/bL8C9KkKQ9yClJ3S8+lkDeg9 c8pj/pL3MM1acxT4iV3ebsQouQmK93ViuReBBDUqJ1lQdNEQG97enekzkHRKYbY/IYCL eks9GRZ8oie9PMaEa3hgamarWC7/ZxbgloEX4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=XA3ahyvTOEbNlX64/mH4PgtKQsie6BJwMEC3/rkYn6E9wGu8bgsR2Uk//j5rT0JWq5 lud27nBzkHp2he5LOYxzrnS9r/SmtrU8TIpGd0uiX24X/N6Kc5G8eNG6acmdVTjSBp+r Ibm5dA8kZbkFZxYc/xdq2OH3lVLVzn7N9scJQ= MIME-Version: 1.0 Received: by 10.220.89.212 with SMTP id f20mr152606vcm.67.1276817031984; Thu, 17 Jun 2010 16:23:51 -0700 (PDT) Received: by 10.220.91.40 with HTTP; Thu, 17 Jun 2010 16:23:51 -0700 (PDT) In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> Date: Thu, 17 Jun 2010 19:23:51 -0400 Message-ID: From: Barry Leiba To: "Hurliman, John" Content-Type: text/plain; charset=ISO-8859-1 Cc: "vwrap@ietf.org" Subject: Re: [vwrap] Moving startup documents into the working group X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: barryleiba@computer.org List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 23:23:47 -0000 On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John wrote: > What happened to the launch document draft? Aside from the LLSD type > system, it's the only document that we have a working implementation and > deployment for. What happened is that we only got two votes on it, one for adopting it (you) and one against (Morgaine). That's not rough consensus, so we're not adopting it yet. See Morgaine's message: http://www.ietf.org/mail-archive/web/vwrap/current/msg00152.html ...for her comments about why she said no. Barry From john.hurliman@intel.com Thu Jun 17 16:27:24 2010 Return-Path: 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 694013A6B45 for ; Thu, 17 Jun 2010 16:27:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.392 X-Spam-Level: X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 RX6WzKYMgG7j for ; Thu, 17 Jun 2010 16:27:23 -0700 (PDT) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by core3.amsl.com (Postfix) with ESMTP id 9F4EB3A6B43 for ; Thu, 17 Jun 2010 16:27:23 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 17 Jun 2010 16:27:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.53,434,1272870000"; d="scan'208";a="527947095" Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by orsmga002.jf.intel.com with ESMTP; 17 Jun 2010 16:27:24 -0700 Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx604.amr.corp.intel.com ([10.31.0.170]) with mapi; Thu, 17 Jun 2010 17:27:26 -0600 From: "Hurliman, John" To: "barryleiba@computer.org" Date: Thu, 17 Jun 2010 17:27:26 -0600 Thread-Topic: [vwrap] Moving startup documents into the working group Thread-Index: AcsOdCedXFoTHE3TRmijjXa5n254zAAAE4jA Message-ID: <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "vwrap@ietf.org" Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 23:27:24 -0000 Ok. I was counting Meadhbh's follow-up e-mail addressing the launch documen= t (http://www.ietf.org/mail-archive/web/vwrap/current/msg00154.html) as a += 1, although I guess it wasn't explicitly stated. -----Original Message----- From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com]=20 Sent: Thursday, June 17, 2010 4:24 PM To: Hurliman, John Cc: vwrap@ietf.org Subject: Re: [vwrap] Moving startup documents into the working group On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John w= rote: > What happened to the launch document draft? Aside from the LLSD type=20 > system, it's the only document that we have a working implementation=20 > and deployment for. What happened is that we only got two votes on it, one for adopting it (you) and one against (Morgaine). That's not rough consensus, so we're not= adopting it yet. See Morgaine's message: http://www.ietf.org/mail-archive/web/vwrap/current/msg00152.html ...for her comments about why she said no. Barry From mike.dickson@hp.com Thu Jun 17 17:20:36 2010 Return-Path: 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 D8B9C3A67C3 for ; Thu, 17 Jun 2010 17:20:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] 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 lEeG8+GSVPZ9 for ; Thu, 17 Jun 2010 17:20:32 -0700 (PDT) Received: from g5t0008.atlanta.hp.com (g5t0008.atlanta.hp.com [15.192.0.45]) by core3.amsl.com (Postfix) with ESMTP id B2D9E3A6359 for ; Thu, 17 Jun 2010 17:20:32 -0700 (PDT) Received: from G3W0630.americas.hpqcorp.net (g3w0630.americas.hpqcorp.net [16.233.58.74]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g5t0008.atlanta.hp.com (Postfix) with ESMTPS id 257C2245C4; Fri, 18 Jun 2010 00:20:37 +0000 (UTC) Received: from G3W0058.americas.hpqcorp.net (16.232.1.3) by G3W0630.americas.hpqcorp.net (16.233.58.74) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 18 Jun 2010 00:18:14 +0000 Received: from GVW0433EXB.americas.hpqcorp.net ([16.234.32.147]) by G3W0058.americas.hpqcorp.net ([16.232.1.3]) with mapi; Fri, 18 Jun 2010 00:18:14 +0000 From: "Dickson, Mike (ISS Software)" To: "Hurliman, John" , "barryleiba@computer.org" Date: Fri, 18 Jun 2010 00:18:06 +0000 Thread-Topic: [vwrap] Moving startup documents into the working group Thread-Index: AcsOdCedXFoTHE3TRmijjXa5n254zAAAE4jAAAHIU1A= Message-ID: <4646639E08F58B42836FAC24C94624DD85DB8D2B09@GVW0433EXB.americas.hpqcorp.net> References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "vwrap@ietf.org" Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 00:20:36 -0000 I'll add a +1 (and should have earlier) to move this onward. I agree with = Meadbh's comments on purpose and as John indicated there's some implementat= ion experience with it as well. Mike -----Original Message----- From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf Of H= urliman, John Sent: Thursday, June 17, 2010 6:27 PM To: barryleiba@computer.org Cc: vwrap@ietf.org Subject: Re: [vwrap] Moving startup documents into the working group Ok. I was counting Meadhbh's follow-up e-mail addressing the launch documen= t (http://www.ietf.org/mail-archive/web/vwrap/current/msg00154.html) as a += 1, although I guess it wasn't explicitly stated. -----Original Message----- From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com]=20 Sent: Thursday, June 17, 2010 4:24 PM To: Hurliman, John Cc: vwrap@ietf.org Subject: Re: [vwrap] Moving startup documents into the working group On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John w= rote: > What happened to the launch document draft? Aside from the LLSD type=20 > system, it's the only document that we have a working implementation=20 > and deployment for. What happened is that we only got two votes on it, one for adopting it (you) and one against (Morgaine). That's not rough consensus, so we're not= adopting it yet. See Morgaine's message: http://www.ietf.org/mail-archive/web/vwrap/current/msg00152.html ...for her comments about why she said no. Barry _______________________________________________ vwrap mailing list vwrap@ietf.org https://www.ietf.org/mailman/listinfo/vwrap From ohmeadhbh@gmail.com Thu Jun 17 17:22:22 2010 Return-Path: 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 ECB953A6359 for ; Thu, 17 Jun 2010 17:22:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.299 X-Spam-Level: X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, 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 SCXyaDzPzM99 for ; Thu, 17 Jun 2010 17:22:20 -0700 (PDT) Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 9BF0D3A67A2 for ; Thu, 17 Jun 2010 17:22:20 -0700 (PDT) Received: by qyk8 with SMTP id 8so1615067qyk.31 for ; Thu, 17 Jun 2010 17:22:23 -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=se17NeKu71LV/wJVe0J/w07i18co6RAYJah7fYsMz7M=; b=nqERzRTC3ypfCa3VRbWdCDDo3XK+UafmAhMfDm2qgt5g+WvGudbLe0j6lhehbIDTDg vHmzA3QIV1/dRRWvmptYl2fgLKcuQ8T8UWGA/X2HC2GxX0DtGg6L7EjssjGBl0CRSJXX d92nlRLh0+pRnrMmt4EsBT6MHb5DVnens4/k4= 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=WBd5qeupOjqSf8x7Z4tVdOMNKGvYdSTNguV1ukZJq9+CD2+fUDo01oOZKWFzUmVpwI nmnUzGCmIBCB0D7I/ru+LKlr1lM1ubtI/nDZOHBzSeaeSnTAi0dV2pg/yzqbZ0j6g9Zr be5ifsH0A5ZSre3REZkvvoO/Yu00cESAaVmGY= Received: by 10.224.59.133 with SMTP id l5mr191650qah.51.1276820542174; Thu, 17 Jun 2010 17:22:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.40.17 with HTTP; Thu, 17 Jun 2010 17:22:02 -0700 (PDT) In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> From: Meadhbh Hamrick Date: Thu, 17 Jun 2010 17:22:02 -0700 Message-ID: To: "Hurliman, John" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "vwrap@ietf.org" , "barryleiba@computer.org" Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 00:22:22 -0000 yeah. peeps should imply that i +1 any draft i author. i'm sort of abstaining in an any official vote as i'm far from being a disinterested party. also... i wanted to give people a bit of time to discuss the drafts before weighing in too heavily. my response to morgaine's response was not to discuss the technical merits of the draft, but to provide additional context as to what the draft was supposed to address. -cheers -meadhbh -- meadhbh hamrick * it's pronounced "maeve" @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com On Thu, Jun 17, 2010 at 4:27 PM, Hurliman, John w= rote: > Ok. I was counting Meadhbh's follow-up e-mail addressing the launch docum= ent (http://www.ietf.org/mail-archive/web/vwrap/current/msg00154.html) as a= +1, although I guess it wasn't explicitly stated. > > -----Original Message----- > From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com] > Sent: Thursday, June 17, 2010 4:24 PM > To: Hurliman, John > Cc: vwrap@ietf.org > Subject: Re: [vwrap] Moving startup documents into the working group > > On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John = wrote: >> What happened to the launch document draft? Aside from the LLSD type >> system, it's the only document that we have a working implementation >> and deployment for. > > What happened is that we only got two votes on it, one for adopting it > (you) and one against (Morgaine). =A0That's not rough consensus, so we're= not adopting it yet. =A0See Morgaine's message: > =A0 http://www.ietf.org/mail-archive/web/vwrap/current/msg00152.html > ...for her comments about why she said no. > > Barry > _______________________________________________ > vwrap mailing list > vwrap@ietf.org > https://www.ietf.org/mailman/listinfo/vwrap > From morgaine.dinova@googlemail.com Thu Jun 17 18:45:55 2010 Return-Path: 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 E49503A6870 for ; Thu, 17 Jun 2010 18:45:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.948 X-Spam-Level: X-Spam-Status: No, score=0.948 tagged_above=-999 required=5 tests=[AWL=0.510, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 y6O-aiBC5oUB for ; Thu, 17 Jun 2010 18:45:54 -0700 (PDT) Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 163C13A6874 for ; Thu, 17 Jun 2010 18:45:53 -0700 (PDT) Received: by wwb24 with SMTP id 24so457861wwb.31 for ; Thu, 17 Jun 2010 18:45:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=ID43h+UDZTgvfiuB4MvATq0NTt10PQwDEp8VKsQxuQg=; b=bFQpjW+qw7MwFZCedzIHd2BGdZst0sjol9sJMtx8zgL3kO7cdVO6+u/nFtTx6CX5Sp STm0+RwIYyoi0HvzfGqEUcMJTvPHyfjcKr5+FJaZVKTr1SZVBfnwhFR2/D7kEP52nWyc wboxHXL36NZm3m8x5aF+sJIk6lZA2+1niDuP4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=fk9ZEI1fuWjQSp4ZH1VrJ3iUhp0RsBGUnVGruoUXFLIeXaYN2u+iA3CRBFFIG3jKI2 1eYMJlR/YjEXhf6GYY4wWf3YUQRvTli6NJ34GqxTPo2zFYo4ZXndSjT513f6vrieT3dh xkoxFEp+f4ay/qvySHEUk+RDv7OqdM7VvpAak= MIME-Version: 1.0 Received: by 10.216.172.204 with SMTP id t54mr258261wel.44.1276825555094; Thu, 17 Jun 2010 18:45:55 -0700 (PDT) Received: by 10.216.72.67 with HTTP; Thu, 17 Jun 2010 18:45:54 -0700 (PDT) In-Reply-To: References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> Date: Fri, 18 Jun 2010 02:45:54 +0100 Message-ID: From: Morgaine To: vwrap@ietf.org Content-Type: multipart/alternative; boundary=0016367fb0cfa6cce10489441d3d Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 01:45:56 -0000 --0016367fb0cfa6cce10489441d3d Content-Type: text/plain; charset=ISO-8859-1 Perhaps someone could explain using a different form of words how client launching forms a natural part of a VW interop protocol? I don't doubt at all that it's useful to launch a client application from a web page, but I gave the document a "No" simply because I don't see how it's in scope for us. Should the SMTP standard include a document on how to launch a mail client? Should the XMPP standard include a document on how to launch a Jabber client? Should the SNMP standard include a document on how to launch snmpwalk? I don't think it's actually *harmful* to have an auxiliary document only marginally related to VWs within our document set, so I could probably be persuaded for the sake of unanimity. But it does seem an oddball specification within our protocol context. Perhaps the best defense for it is that it promotes the cause of VW interop by creating a Web standard in the area. In that sense it's a useful document despite client launching having little direct relevance to our VWRAP client-server protocol. Barry, I won't argue further against adding this document to our set so go right ahead on that, given the general support. Usefulness probably trumps relevance and consistency in this case anyway. :-) Morgaine. ============================== On Fri, Jun 18, 2010 at 1:22 AM, Meadhbh Hamrick wrote: > yeah. peeps should imply that i +1 any draft i author. > > i'm sort of abstaining in an any official vote as i'm far from being a > disinterested party. also... i wanted to give people a bit of time to > discuss the drafts before weighing in too heavily. my response to > morgaine's response was not to discuss the technical merits of the > draft, but to provide additional context as to what the draft was > supposed to address. > > -cheers > -meadhbh > -- > meadhbh hamrick * it's pronounced "maeve" > @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com > > > > On Thu, Jun 17, 2010 at 4:27 PM, Hurliman, John > wrote: > > Ok. I was counting Meadhbh's follow-up e-mail addressing the launch > document (http://www.ietf.org/mail-archive/web/vwrap/current/msg00154.html) > as a +1, although I guess it wasn't explicitly stated. > > > > -----Original Message----- > > From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com] > > Sent: Thursday, June 17, 2010 4:24 PM > > To: Hurliman, John > > Cc: vwrap@ietf.org > > Subject: Re: [vwrap] Moving startup documents into the working group > > > > On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John > wrote: > >> What happened to the launch document draft? Aside from the LLSD type > >> system, it's the only document that we have a working implementation > >> and deployment for. > > > > What happened is that we only got two votes on it, one for adopting it > > (you) and one against (Morgaine). That's not rough consensus, so we're > not adopting it yet. See Morgaine's message: > > http://www.ietf.org/mail-archive/web/vwrap/current/msg00152.html > > ...for her comments about why she said no. > > > > Barry > > _______________________________________________ > > 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 > --0016367fb0cfa6cce10489441d3d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Perhaps someone could explain using a different form of words how client la= unching forms a natural part of a VW interop protocol?

I don't d= oubt at all that it's useful to launch a client application from a web = page, but I gave the document a "No" simply because I don't s= ee how it's in scope for us.

Should the SMTP standard include a document on how to launch a mail cli= ent?=A0 Should the XMPP standard include a document on how to launch a Jabb= er client?=A0 Should the SNMP standard include a document on how to launch = snmpwalk?

I don't think it's actually harmful=A0 to have an auxili= ary document only marginally related to VWs within our document set, so I c= ould probably be persuaded for the sake of unanimity.=A0 But it does seem a= n oddball specification within our protocol context.

Perhaps the best defense for it is that it promotes the cause of VW int= erop by creating a Web standard in the area.=A0 In that sense it's a us= eful document despite client launching having little direct relevance to ou= r VWRAP client-server protocol.

Barry, I won't argue further against adding this document to our se= t so go right ahead on that, given the general support.=A0 Usefulness proba= bly trumps relevance and consistency in this case anyway. :-)


Morgaine.




=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Fri, Jun 18, 2010 at 1:22 AM, Meadhbh Hamrick <= ;ohmeadhbh@gmail.com> = wrote:
yeah. peeps shoul= d imply that i +1 any draft i author.

i'm sort of abstaining in an any official vote as i'm far from bein= g a
disinterested party. also... i wanted to give people a bit of time to
discuss the drafts before weighing in too heavily. my response to
morgaine's response was not to discuss the technical merits of the
draft, but to provide additional context as to what the draft was
supposed to address.

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



On Thu, Jun 17, 2010 at 4:27 PM, Hurliman, John <john.hurliman@intel.com> wrote:
> Ok. I was counting Meadhbh's follow-up e-mail addressing the launc= h document (http://www.ietf.org/mail-archive/web/vwrap/= current/msg00154.html) as a +1, although I guess it wasn't explicit= ly stated.
>
> -----Original Message-----
> From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com]
> Sent: Thursday, June 17, 2010 4:24 PM
> To: Hurliman, John
> Cc: vwrap@ietf.org
> Subject: Re: [vwrap] Moving startup documents into the working group >
> On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John <john.hurliman@intel.com> wrote:
>> What happened to the launch document draft? Aside from the LLSD ty= pe
>> system, it's the only document that we have a working implemen= tation
>> and deployment for.
>
> What happened is that we only got two votes on it, one for adopting it=
> (you) and one against (Morgaine). =A0That's not rough consensus, s= o we're not adopting it yet. =A0See Morgaine's message:
> =A0 http://www.ietf.org/mail-archive/web/vwrap/cur= rent/msg00152.html
> ...for her comments about why she said no.
>
> Barry
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
_______________________________________________
vwrap mailing list
vwrap@ietf.org
h= ttps://www.ietf.org/mailman/listinfo/vwrap

--0016367fb0cfa6cce10489441d3d-- From djshag@hotmail.com Thu Jun 17 19:19:11 2010 Return-Path: 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 9640B3A691D for ; Thu, 17 Jun 2010 19:19:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] 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 ejjrGhAziyA2 for ; Thu, 17 Jun 2010 19:19:09 -0700 (PDT) Received: from bay0-omc2-s4.bay0.hotmail.com (bay0-omc2-s4.bay0.hotmail.com [65.54.190.79]) by core3.amsl.com (Postfix) with ESMTP id C944E3A6933 for ; Thu, 17 Jun 2010 19:19:09 -0700 (PDT) Received: from BAY136-DS1 ([65.54.190.125]) by bay0-omc2-s4.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Jun 2010 19:19:15 -0700 X-Originating-IP: [74.57.140.246] X-Originating-Email: [djshag@hotmail.com] Message-ID: From: "Patnad Babii" To: References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com><62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> In-Reply-To: Date: Thu, 17 Jun 2010 22:19:03 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_04D2_01CB0E6B.18230970" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-OriginalArrivalTime: 18 Jun 2010 02:19:15.0863 (UTC) FILETIME=[A64F8270:01CB0E8C] Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 02:19:11 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_04D2_01CB0E6B.18230970 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I give also my vote to that document, its not like it is set in stone = anyways and it can give a kick start to VW who try to implement the = protocol. If at a later stage we find it has not its place in the WG, = then it can be put aside.=20 From: Morgaine=20 Sent: Thursday, June 17, 2010 9:45 PM To: vwrap@ietf.org=20 Subject: Re: [vwrap] Moving startup documents into the working group Perhaps someone could explain using a different form of words how client = launching forms a natural part of a VW interop protocol? I don't doubt at all that it's useful to launch a client application = from a web page, but I gave the document a "No" simply because I don't = see how it's in scope for us. Should the SMTP standard include a document on how to launch a mail = client? Should the XMPP standard include a document on how to launch a = Jabber client? Should the SNMP standard include a document on how to = launch snmpwalk? I don't think it's actually harmful to have an auxiliary document only = marginally related to VWs within our document set, so I could probably = be persuaded for the sake of unanimity. But it does seem an oddball = specification within our protocol context. Perhaps the best defense for it is that it promotes the cause of VW = interop by creating a Web standard in the area. In that sense it's a = useful document despite client launching having little direct relevance = to our VWRAP client-server protocol. Barry, I won't argue further against adding this document to our set so = go right ahead on that, given the general support. Usefulness probably = trumps relevance and consistency in this case anyway. :-) Morgaine. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D On Fri, Jun 18, 2010 at 1:22 AM, Meadhbh Hamrick = wrote: yeah. peeps should imply that i +1 any draft i author. i'm sort of abstaining in an any official vote as i'm far from being a disinterested party. also... i wanted to give people a bit of time to discuss the drafts before weighing in too heavily. my response to morgaine's response was not to discuss the technical merits of the draft, but to provide additional context as to what the draft was supposed to address. -cheers -meadhbh -- meadhbh hamrick * it's pronounced "maeve" @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com On Thu, Jun 17, 2010 at 4:27 PM, Hurliman, John = wrote: > Ok. I was counting Meadhbh's follow-up e-mail addressing the launch = document = (http://www.ietf.org/mail-archive/web/vwrap/current/msg00154.html) as a = +1, although I guess it wasn't explicitly stated. > > -----Original Message----- > From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com] > Sent: Thursday, June 17, 2010 4:24 PM > To: Hurliman, John > Cc: vwrap@ietf.org > Subject: Re: [vwrap] Moving startup documents into the working group > > On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John = wrote: >> What happened to the launch document draft? Aside from the LLSD = type >> system, it's the only document that we have a working = implementation >> and deployment for. > > What happened is that we only got two votes on it, one for adopting = it > (you) and one against (Morgaine). That's not rough consensus, so = we're not adopting it yet. See Morgaine's message: > http://www.ietf.org/mail-archive/web/vwrap/current/msg00152.html > ...for her comments about why she said no. > > Barry > _______________________________________________ > 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 -------------------------------------------------------------------------= ------- _______________________________________________ vwrap mailing list vwrap@ietf.org https://www.ietf.org/mailman/listinfo/vwrap ------=_NextPart_000_04D2_01CB0E6B.18230970 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I give also my vote to that document, its not = like it is=20 set in stone anyways and it can give a kick start to VW who try to = implement the=20 protocol. If at a later stage we find it has not its place in the WG, = then it=20 can be put aside.
 
 

From: Morgaine
Sent: Thursday, June 17, 2010 9:45 PM
Subject: Re: [vwrap] Moving startup documents into the = working=20 group

Perhaps someone could explain using a different form of = words how=20 client launching forms a natural part of a VW interop protocol?

I = don't=20 doubt at all that it's useful to launch a client application from a web = page,=20 but I gave the document a "No" simply because I don't see how it's in = scope for=20 us.

Should the SMTP standard include a document on how to launch = a mail=20 client?  Should the XMPP standard include a document on how to = launch a=20 Jabber client?  Should the SNMP standard include a document on how = to=20 launch snmpwalk?

I don't think it's actually harmful  = to have=20 an auxiliary document only marginally related to VWs within our document = set, so=20 I could probably be persuaded for the sake of unanimity.  But it = does seem=20 an oddball specification within our protocol context.

Perhaps the = best=20 defense for it is that it promotes the cause of VW interop by creating a = Web=20 standard in the area.  In that sense it's a useful document despite = client=20 launching having little direct relevance to our VWRAP client-server=20 protocol.

Barry, I won't argue further against adding this = document to=20 our set so go right ahead on that, given the general support.  = Usefulness=20 probably trumps relevance and consistency in this case anyway.=20 :-)


Morgaine.




=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Fri, Jun 18, 2010 at 1:22 AM, Meadhbh = Hamrick <ohmeadhbh@gmail.com> = wrote:
yeah. peeps should imply that i +1 any draft i=20 author.

i'm sort of abstaining in an any official vote as i'm = far from=20 being a
disinterested party. also... i wanted to give people a bit = of time=20 to
discuss the drafts before weighing in too heavily. my response=20 to
morgaine's response was not to discuss the technical merits of=20 the
draft, but to provide additional context as to what the draft=20 was
supposed to address.

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



On Thu, Jun 17, 2010 at 4:27 PM, Hurliman, = John=20 <john.hurliman@intel.com>=20 wrote:
> Ok. I was counting Meadhbh's follow-up e-mail = addressing the=20 launch document (http://www.ietf.org/mail-archive/web/vwrap/current/msg001= 54.html)=20 as a +1, although I guess it wasn't explicitly stated.
>
> = -----Original Message-----
> From: Barry Leiba [mailto:barryleiba.mailing.lis= ts@gmail.com]
>=20 Sent: Thursday, June 17, 2010 4:24 PM
> To: Hurliman, = John
> Cc:=20 vwrap@ietf.org
> Subject: = Re:=20 [vwrap] Moving startup documents into the working = group
>
> On=20 Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John <john.hurliman@intel.com>=20 wrote:
>> What happened to the launch document draft? Aside = from the=20 LLSD type
>> system, it's the only document that we have a = working=20 implementation
>> and deployment for.
>
> What = happened=20 is that we only got two votes on it, one for adopting it
> (you) = and one=20 against (Morgaine).  That's not rough consensus, so we're not = adopting it=20 yet.  See Morgaine's message:
>   http://www.ietf.org/mail-archive/web/vwrap/current/msg001= 52.html
>=20 ...for her comments about why she said no.
>
> = Barry
>=20 _______________________________________________
> vwrap mailing=20 list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>_______________________________________________
vwrap=20 mailing list
vwrap@ietf.org
https://www.ietf.org/mailman/listinfo/vwrap
=

_______________________________________________
vwrap mailing=20 list
vwrap@ietf.org
https://www.ietf.org/mailman/listinfo/vwrap
= ------=_NextPart_000_04D2_01CB0E6B.18230970-- From morgaine.dinova@googlemail.com Thu Jun 17 19:48:00 2010 Return-Path: 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 B422A3A6874 for ; Thu, 17 Jun 2010 19:48:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.429 X-Spam-Level: X-Spam-Status: No, score=-0.429 tagged_above=-999 required=5 tests=[AWL=1.547, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 7WSCiY-yQFAt for ; Thu, 17 Jun 2010 19:47:59 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 929153A6782 for ; Thu, 17 Jun 2010 19:47:58 -0700 (PDT) Received: by wya21 with SMTP id 21so472701wya.31 for ; Thu, 17 Jun 2010 19:48:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=BY1AK7u029Oj3vcT2ycPxIhXMH+SVWR0Nd0a27z2Scc=; b=L0246YYg4zq1pc2VtMme4wrphOE6LNCbtzi/B+XoAWK6TMEcLPofIyrKMwVyulCc7U 3cc3jyyXuxG2j+KlB3K9Y+Q1dr2Qml6wA4du9cal3vwxB4+INJEGe/N+WBKofDlG0Qml QOeIGfBsmCAz7cI0pAhCnU0xzLuSo+pDB5f2E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=L8rL0tFP3D2uwgWpdXQ0k59PAiDkD1rsPhdY1VauOM1F3+ClsodyRx0RCOhbY2tegs jC/ouV6tP7HYMpZx9dfSPn/pU3g3aLBNbq03tTCgZG9ULsbvOUT3p75lmhfXUm4cp32R d/77gUIkryN8a0e/rtrxFtLbjootp/M0lmdSE= MIME-Version: 1.0 Received: by 10.216.154.69 with SMTP id g47mr268150wek.82.1276829280436; Thu, 17 Jun 2010 19:48:00 -0700 (PDT) Received: by 10.216.72.67 with HTTP; Thu, 17 Jun 2010 19:48:00 -0700 (PDT) In-Reply-To: References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> Date: Fri, 18 Jun 2010 03:48:00 +0100 Message-ID: From: Morgaine To: vwrap@ietf.org Content-Type: multipart/alternative; boundary=0016e65ae518b30148048944fb54 Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 02:48:00 -0000 --0016e65ae518b30148048944fb54 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jun 18, 2010 at 3:01 AM, Meadhbh Hamrick wrote: > > i think the idea here is that it's in scope because it establishes a > session between a client and a virtual world. so it's part of > "interop" because (in theory) you'll have different VWRAP clients > getting descriptors of where to rez avatars from different web based > systems (wikipedia, facebook, etc.) and trying to get them to talk to > different server implementations (OpenSim, Simian, Beyon, etc.) > That's an excellent reason, Meadhbh! Anything that promotes VW interop gets my vote, so you've converted me to +1 on this. :-) Morgaine. ================================== On Fri, Jun 18, 2010 at 3:01 AM, Meadhbh Hamrick wrote: > hey morgaine... > > i think the idea here is that it's in scope because it establishes a > session between a client and a virtual world. so it's part of > "interop" because (in theory) you'll have different VWRAP clients > getting descriptors of where to rez avatars from different web based > systems (wikipedia, facebook, etc.) and trying to get them to talk to > different server implementations (OpenSim, Simian, Beyon, etc.) > > also one of the reasons we wanted to write an internet draft for this > is that beyond the issue of getting everyone to use similar launch > messages, we wanted to use register a launch message mime type. one of > they ways to register a mime type is to write an RFC describing how > it's used. > > -cheers > -meadhbh > -- > meadhbh hamrick * it's pronounced "maeve" > @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com > > > > On Thu, Jun 17, 2010 at 6:45 PM, Morgaine > wrote: > > Perhaps someone could explain using a different form of words how client > > launching forms a natural part of a VW interop protocol? > > > > I don't doubt at all that it's useful to launch a client application from > a > > web page, but I gave the document a "No" simply because I don't see how > it's > > in scope for us. > > > > Should the SMTP standard include a document on how to launch a mail > client? > > Should the XMPP standard include a document on how to launch a Jabber > > client? Should the SNMP standard include a document on how to launch > > snmpwalk? > > > > I don't think it's actually harmful to have an auxiliary document only > > marginally related to VWs within our document set, so I could probably be > > persuaded for the sake of unanimity. But it does seem an oddball > > specification within our protocol context. > > > > Perhaps the best defense for it is that it promotes the cause of VW > interop > > by creating a Web standard in the area. In that sense it's a useful > > document despite client launching having little direct relevance to our > > VWRAP client-server protocol. > > > > Barry, I won't argue further against adding this document to our set so > go > > right ahead on that, given the general support. Usefulness probably > trumps > > relevance and consistency in this case anyway. :-) > > > > > > Morgaine. > > > > > > > > > > ============================== > > > > On Fri, Jun 18, 2010 at 1:22 AM, Meadhbh Hamrick > > wrote: > >> > >> yeah. peeps should imply that i +1 any draft i author. > >> > >> i'm sort of abstaining in an any official vote as i'm far from being a > >> disinterested party. also... i wanted to give people a bit of time to > >> discuss the drafts before weighing in too heavily. my response to > >> morgaine's response was not to discuss the technical merits of the > >> draft, but to provide additional context as to what the draft was > >> supposed to address. > >> > >> -cheers > >> -meadhbh > >> -- > >> meadhbh hamrick * it's pronounced "maeve" > >> @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com > >> > >> > >> > >> On Thu, Jun 17, 2010 at 4:27 PM, Hurliman, John < > john.hurliman@intel.com> > >> wrote: > >> > Ok. I was counting Meadhbh's follow-up e-mail addressing the launch > >> > document ( > http://www.ietf.org/mail-archive/web/vwrap/current/msg00154.html) > >> > as a +1, although I guess it wasn't explicitly stated. > >> > > >> > -----Original Message----- > >> > From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com] > >> > Sent: Thursday, June 17, 2010 4:24 PM > >> > To: Hurliman, John > >> > Cc: vwrap@ietf.org > >> > Subject: Re: [vwrap] Moving startup documents into the working group > >> > > >> > On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John > >> > wrote: > >> >> What happened to the launch document draft? Aside from the LLSD type > >> >> system, it's the only document that we have a working implementation > >> >> and deployment for. > >> > > >> > What happened is that we only got two votes on it, one for adopting it > >> > (you) and one against (Morgaine). That's not rough consensus, so > we're > >> > not adopting it yet. See Morgaine's message: > >> > http://www.ietf.org/mail-archive/web/vwrap/current/msg00152.html > >> > ...for her comments about why she said no. > >> > > >> > Barry > >> > _______________________________________________ > >> > 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 > > > > > > _______________________________________________ > > vwrap mailing list > > vwrap@ietf.org > > https://www.ietf.org/mailman/listinfo/vwrap > > > > > --0016e65ae518b30148048944fb54 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Jun 18, 2010 at 3:01 AM, Meadhbh Hamrick <ohmeadhbh@gmail.com> wrote= :

i think the idea here is that it's in scope because it establishes a session between a client and a virtual world. so it's part of
"interop" because (in theory) you'll have different VWRAP cli= ents
getting descriptors of where to rez avatars from different web based
systems (wikipedia, facebook, etc.) and trying to get them to talk to
different server implementations (OpenSim, Simian, Beyon, etc.)


That's an excellent reason, Meadhbh!

= Anything that promotes VW interop gets my vote, so you've converted me = to +1 on this. :-)


Morgaine.




=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D

On Fri, Jun 18, 2010 at 3:01 AM, Meadhbh Ham= rick <ohmeadhbh= @gmail.com> wrote:
hey morgaine...

i think the idea here is that it's in scope because it establishes a session between a client and a virtual world. so it's part of
"interop" because (in theory) you'll have different VWRAP cli= ents
getting descriptors of where to rez avatars from different web based
systems (wikipedia, facebook, etc.) and trying to get them to talk to
different server implementations (OpenSim, Simian, Beyon, etc.)

also one of the reasons we wanted to write an internet draft for this
is that beyond the issue of getting everyone to use similar launch
messages, we wanted to use register a launch message mime type. one of
they ways to register a mime type is to write an RFC describing how
it's used.

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



On Thu, Jun 17, 2010 at 6:45 PM, Mo= rgaine
<morgaine.dinova@googl= email.com> wrote:
> Perhaps someone could explain using a different form of words how clie= nt
> launching forms a natural part of a VW interop protocol?
>
> I don't doubt at all that it's useful to launch a client appli= cation from a
> web page, but I gave the document a "No" simply because I do= n't see how it's
> in scope for us.
>
> Should the SMTP standard include a document on how to launch a mail cl= ient?
> Should the XMPP standard include a document on how to launch a Jabber<= br> > client?=A0 Should the SNMP standard include a document on how to launc= h
> snmpwalk?
>
> I don't think it's actually harmful=A0 to have an auxiliary do= cument only
> marginally related to VWs within our document set, so I could probably= be
> persuaded for the sake of unanimity.=A0 But it does seem an oddball > specification within our protocol context.
>
> Perhaps the best defense for it is that it promotes the cause of VW in= terop
> by creating a Web standard in the area.=A0 In that sense it's a us= eful
> document despite client launching having little direct relevance to ou= r
> VWRAP client-server protocol.
>
> Barry, I won't argue further against adding this document to our s= et so go
> right ahead on that, given the general support.=A0 Usefulness probably= trumps
> relevance and consistency in this case anyway. :-)
>
>
> Morgaine.
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
>
> On Fri, Jun 18, 2010 at 1:22 AM, Meadhbh Hamrick <ohmeadhbh@gmail.com>
> wrote:
>>
>> yeah. peeps should imply that i +1 any draft i author.
>>
>> i'm sort of abstaining in an any official vote as i'm far = from being a
>> disinterested party. also... i wanted to give people a bit of time= to
>> discuss the drafts before weighing in too heavily. my response to<= br> >> morgaine's response was not to discuss the technical merits of= the
>> draft, but to provide additional context as to what the draft was<= br> >> supposed to address.
>>
>> -cheers
>> -meadhbh
>> --
>> meadhbh hamrick * it's pronounced "maeve"
>> @OhMeadhbh * htt= p://meadhbh.org/ * OhMeadhbh@gma= il.com
>>
>>
>>
>> On Thu, Jun 17, 2010 at 4:27 PM, Hurliman, John <john.hurliman@intel.com>
>> wrote:
>> > Ok. I was counting Meadhbh's follow-up e-mail addressing = the launch
>> > document (http://www.ietf.org/mail-archiv= e/web/vwrap/current/msg00154.html)
>> > as a +1, although I guess it wasn't explicitly stated. >> >
>> > -----Original Message-----
>> > From: Barry Leiba [mailto:barryleiba.mailing.lists@gmail.com]
>> > Sent: Thursday, June 17, 2010 4:24 PM
>> > To: Hurliman, John
>> > Cc: vwrap@ietf.org
>> > Subject: Re: [vwrap] Moving startup documents into the workin= g group
>> >
>> > On Thu, Jun 17, 2010 at 7:16 PM, Hurliman, John
>> > <john.hurliman@= intel.com> wrote:
>> >> What happened to the launch document draft? Aside from th= e LLSD type
>> >> system, it's the only document that we have a working= implementation
>> >> and deployment for.
>> >
>> > What happened is that we only got two votes on it, one for ad= opting it
>> > (you) and one against (Morgaine). =A0That's not rough con= sensus, so we're
>> > not adopting it yet. =A0See Morgaine's message:
>> > =A0 http://www.ietf.org/mail-archive/web/= vwrap/current/msg00152.html
>> > ...for her comments about why she said no.
>> >
>> > Barry
>> > _______________________________________________
>> > 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
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>

--0016e65ae518b30148048944fb54-- From barryleiba.mailing.lists@gmail.com Fri Jun 18 13:44:20 2010 Return-Path: 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 73D943A69D4 for ; Fri, 18 Jun 2010 13:44:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.079 X-Spam-Level: X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[AWL=0.520, 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 H970W8ObK-R6 for ; Fri, 18 Jun 2010 13:44:19 -0700 (PDT) Received: from mail-yw0-f173.google.com (mail-yw0-f173.google.com [209.85.211.173]) by core3.amsl.com (Postfix) with ESMTP id 94C883A6918 for ; Fri, 18 Jun 2010 13:44:19 -0700 (PDT) Received: by ywh3 with SMTP id 3so1631569ywh.31 for ; Fri, 18 Jun 2010 13:44:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=LIy3H1u8gYr9DUoNgtJVS81gpraPhDF1EQjeOSlb2GI=; b=N6pLxVvXll6EEv1NQ9Xeed7C1amAOJPZZjwECXeqvX64NmFVqX0ifGumks2VfNehTZ 4XFB5SFOrZQvvffNg1PUwNJP/2Xh9Q5/zEZsteMuAGmjwSMLJepozx0057wWAs0KoUsg KLLs4Hy3KRCOtuOrsK9hBShclHfTlGNk4bwPA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=BUfmW/Jno5HcrmOhcRqHDI8Agc/6EHPk9sOKqDDZXaufOFM1WNsJwEVu5hg+ZUPJa4 UEGdieIU9MNobKrzMQdOIbqbEj0Zi6AZQrJ7tWdPtstFoLimTMxQ24g6aUs6vkonRWvD yVLyS0F/hTHLnwa0yrtqrm0paKZxaLVna5/Y4= MIME-Version: 1.0 Received: by 10.220.124.38 with SMTP id s38mr703227vcr.21.1276893860818; Fri, 18 Jun 2010 13:44:20 -0700 (PDT) Received: by 10.220.91.40 with HTTP; Fri, 18 Jun 2010 13:44:20 -0700 (PDT) In-Reply-To: References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> Date: Fri, 18 Jun 2010 16:44:20 -0400 Message-ID: From: Barry Leiba To: Meadhbh Hamrick Content-Type: text/plain; charset=ISO-8859-1 Cc: vwrap@ietf.org Subject: Re: [vwrap] Moving startup documents into the working group X-BeenThere: vwrap@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: barryleiba@computer.org List-Id: Virtual World Region Agent Protocol - IETF working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 20:44:20 -0000 Morgaine says... > Anything that promotes VW interop gets my vote, so you've converted me to +1 > on this. :-) Cool. OK, so, Meadhbh, I've also approved "draft-ietf-vwrap-launch". Please add that to your list, to have an updated version by the IETF 79 deadline. T'anks. Barry, as chair From ohmeadhbh@gmail.com Fri Jun 18 15:42:03 2010 Return-Path: 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 208203A6A3B for ; Fri, 18 Jun 2010 15:42:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 sMIeJBFNF8p0 for ; Fri, 18 Jun 2010 15:42:02 -0700 (PDT) Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id EB2823A6A3A for ; Fri, 18 Jun 2010 15:42:01 -0700 (PDT) Received: by gwj16 with SMTP id 16so1151840gwj.31 for ; Fri, 18 Jun 2010 15:42:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:received :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=GZ4UDgv81VHfLz7Sec7qDmcmHuN6HJi/cS2azf7st0g=; b=Zx+1VqOx39r59PNNHqiZLXiyVlUGpCEcNHMKwbtv7w83na6IpBoMUHNzHewafhxXxS CSKNxHmjc0lgh796hIoDp4+mk21S+L+G3aBkXY2d6mfJE+IEqTT72q73WMni79if6iOP PzWUzTGkroDW2fS97nHHl0AXBxXB13gtoqWwc= 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; b=Ky65vn3OV8gtAkKZJ33CGroCLr+DpXevlT5H7WfucFjvc5XGi95MJGRHtXoaZ8W2m7 +ywCgeVhVKbtHeApbvGXpOsxlFmYFdVGsZzSYyJn+iQYEnSD7Nduou8L5EzTFOVwQdgq o1u3YD5lWqyTJuqWuFRko2+4q684wXomTyEgo= MIME-Version: 1.0 Received: by 10.224.126.194 with SMTP id d2mr1158590qas.265.1276900924326; Fri, 18 Jun 2010 15:42:04 -0700 (PDT) Received: by 10.229.40.17 with HTTP; Fri, 18 Jun 2010 15:42:03 -0700 (PDT) Received: by 10.229.40.17 with HTTP; Fri, 18 Jun 2010 15:42:03 -0700 (PDT) In-Reply-To: References: <62BFE5680C037E4DA0B0A08946C0933DDA596E0B@rrsmsx506.amr.corp.intel.com> <62BFE5680C037E4DA0B0A08946C0933DDA596E1A@rrsmsx506.amr.corp.intel.com> Date: Fri, 18 Jun 2010 15:42:03 -0700 Message-ID: From: Meadhbh Hamrick To: barryleiba@computer.org Content-Type: multipart/alternative; boundary=00148536e60e0204ba048955aa07 Cc: vwrap@ietf.org Subject: Re: [vwrap] Moving startup documents into the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 22:42:03 -0000 --00148536e60e0204ba048955aa07 Content-Type: text/plain; charset=ISO-8859-1 Ossm. Will do. Thx everybody! On Jun 18, 2010 1:44 PM, "Barry Leiba" wrote: Morgaine says... > Anything that promotes VW interop gets my vote, so you've converted me to +1 > on this. :-) Cool. OK, so, Meadhbh, I've also approved "draft-ietf-vwrap-launch". Please add that to your list, to have an updated version by the IETF 79 deadline. T'anks. Barry, as chair --00148536e60e0204ba048955aa07 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Ossm. Will do. Thx everybody!

On Jun 18, 2010 1:44 PM, "Barry Leiba&quo= t; <barryleiba.mai= ling.lists@gmail.com> wrote:

Morgaine says...

> Anything that promotes VW interop gets my v= ote, so you've converted me to +1
> on this. :-)

Co= ol.

OK, so, Meadhbh, I've also approved "draft-ietf-vwrap-launch"= . =A0Please
add that to your list, to have an updated version by the IETF 79
deadline.

T'anks.

Barry, as chair

--00148536e60e0204ba048955aa07--