IETF Logo Mail Archive

Re: [mmox] LLSD

Charles Krinke <cfk@pacbell.net> Fri, 20 February 2009 04:34 UTC

Return-Path: <cfk@pacbell.net>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF4343A69CB for <mmox@core3.amsl.com>; Thu, 19 Feb 2009 20:34:36 -0800 (PST)
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 n9NukkbuNect for <mmox@core3.amsl.com>; Thu, 19 Feb 2009 20:34:35 -0800 (PST)
Received: from web82607.mail.mud.yahoo.com (web82607.mail.mud.yahoo.com [68.142.201.124]) by core3.amsl.com (Postfix) with SMTP id 7FEF93A688C for <mmox@ietf.org>; Thu, 19 Feb 2009 20:34:35 -0800 (PST)
Received: (qmail 81207 invoked by uid 60001); 20 Feb 2009 04:34:49 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=IdXefOvSPGbcuYnwvh4Xul9m3qR/aMAWLlUZjXR5V1m1LNEZL8gB12vEx6Rng105qlT9PWWfeq18K1zdv5q5w04o0vHdXe6bbilJGX0KZEM57Xcm+XkhylMYc/5pMo4cG+VkbaOmhz669XENq2DZNh+LjDrCakW04mkm09e8Vec=;
X-YMail-OSG: My9vUl0VM1kOHZX.V7GfLfMmWTw2C70a5Wsl7OhLWmLaNLeX4SJvdZR8cohVcprrviOxv9BMz46K1BwDIKQ3.4Q6Inkd0iNRaCM8DlK.0Vmqd9AYqo6NwuQujdgBWzpzOl.J03c6KsPwogMPz7bfJwjYJquMNeGoRI.8uSqezV45yNPkAk5DfPvMXNuVMBWMPIcLBe_j20F4Po.BcpZ2KluA4Eo-
Received: from [67.120.11.69] by web82607.mail.mud.yahoo.com via HTTP; Thu, 19 Feb 2009 20:34:48 PST
X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1
References: <62BFE5680C037E4DA0B0A08946C0933D501FE18E@rrsmsx506.amr.corp.intel.com> <80E946E9-5C62-4E00-BE8C-A15513898F99@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933D50262DA8@rrsmsx506.amr.corp.intel.com> <29656.28734.qm@web82607.mail.mud.yahoo.com> <C803B307-0984-40AE-946A-00EDDA664502@lindenlab.com>
Date: Thu, 19 Feb 2009 20:34:48 -0800
From: Charles Krinke <cfk@pacbell.net>
To: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1746896104-1235104488=:78349"
Message-ID: <61320.78349.qm@web82607.mail.mud.yahoo.com>
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] LLSD
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2009 04:34:36 -0000

Ok, Meadhbh:

In looking at this draft *and* hoping I dont make my OpenSim peers too unhappy with me, let me ask a question.

"Is there any reason why trying to approve the draft LLSD spec would preclude or pertubate either OGP, HyperGrid or other similar notions from being supported?"

Charles




________________________________
From: Meadhbh Hamrick (Infinity) <infinity@lindenlab.com>
To: Charles Krinke <cfk@pacbell.net>
Cc: "mmox@ietf.org" <mmox@ietf.org>
Sent: Thursday, February 19, 2009 8:10:05 PM
Subject: Re: [mmox] LLSD

http://wiki.secondlife.com/wiki/MMOX is non-authoritative, but yes LLSD is one of the work items we have on the list.

the objective of LLSD is to provide an abstract type system with multiple serializations. it also defines the mime types.

however, to say that the LLSD draft exists only to define the serializations is akin to saying that ASN.1 exists only to provide input into DER or BER encodings. the two are linked, but each has a particular use.

LLSD as an abstract type system allows us to define and reason about the semantics of structured data used in PDUs independent of an existing implementation language. the serialization rules allow us to format structured data prior to transport and later de-serialize it after receipt. the MIME type registrations allow us to identify the serialization scheme used on transports that support the use of MIME types. LLIDL (pronounced "little") defines the set of expected parameters to and responses from a resource access.

LLSD was selected as the first draft to work on as it is used as a building block for other protocol interactions, some of which are published in draft form on the second life wiki. the further development of these protocols is also considered a task of the proposed working group.

-cheers
-meadhbh

On Feb 19, 2009, at 7:52 PM, Charles Krinke wrote:

In looking at the secondlife wiki at http://wiki.secondlife.com/wiki/MMOX it looks like one of the first proposals for this working group is the LLSD draft specification.

Am I correct in that the gist of the LLSD specification is essentially to propose three mime formats and thats about it for now?

application/llsd+xml
application/llsd+json
application/llsd+binary

Charles
_______________________________________________
mmox mailing list
mmox@ietf.org
https://www.ietf.org/mailman/listinfo/mmox

v2.23.0 | Report a Bug | By Email