From swmp-bounces@ietf.org Fri Jun 01 00:36:08 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Htyrw-0004nC-Km; Fri, 01 Jun 2007 00:36:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Htyru-0004n5-Ra
	for swmp@ietf.org; Fri, 01 Jun 2007 00:36:06 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Htyrs-0004vm-3p
	for swmp@ietf.org; Fri, 01 Jun 2007 00:36:06 -0400
Received: from [192.168.2.119] (h-66-166-236-26.snvacaid.covad.net
	[66.166.236.26]) by william.mediamachines.com (Postfix) with ESMTP
	id AF39246440D; Thu, 31 May 2007 23:34:12 -0500 (CDT)
Message-ID: <465FA222.5050709@mediamachines.com>
Date: Thu, 31 May 2007 21:35:46 -0700
From: "Jay C. Weber" <jweber@mediamachines.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: chris <dragonmagi@gmail.com>
Subject: Re: [SWMP] Media Machines' initial design and code
References: <465ED84F.2090509@mediamachines.com>
	<d9cef8ba0705312010g1b9b084bmb1fba948e170c844@mail.gmail.com>
In-Reply-To: <d9cef8ba0705312010g1b9b084bmb1fba948e170c844@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Errors-To: swmp-bounces@ietf.org

chris wrote:
>  That is, at leasts two: high bandwidth, secure protocol over tcp/ip, 
> short payload, low latency protocol over udp.
As described in that paper I linked, the SWAMP design already can use 
TCPand/or UDP depending on the delivery requirements of a particular 
kind of message.  That is, some messages (like object instantiation) 
need guaranteed delivery, and are usually infrequent, suggesting TCP.  
Other messages (like position-changes) are streamed and need low 
latency, suggesting udp.  It's also valuable to use tcp as a fallback 
when udp ports are blocked by firewalls.

The initial implementation only roughs-in the UDP parts, though, that's 
not working yet.  But you'll see that some parts of the design (e.g., 
enveloping) are there to support UDP datagrams.
> And we may even be looking at different protocols for server-server, 
> client-server and client-client for ultimate scalable system.
Perhaps, but it certainly would be preferable if these architectural 
connections could use a unified protocol.
> On the practical front, I have managed to compile hydras for both 
> windows and linux and the local test works on my winxp client. Still 
> trying to get it to work accessing the remote linux server, but that 
> should be working soon - it might just be a matter of the port being 
> blocked.
Excellent.

jay


_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp



From swmp-bounces@ietf.org Fri Jun 01 08:54:28 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu6eC-0001Kk-Ef; Fri, 01 Jun 2007 08:54:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hu6eB-0001Kd-Ck
	for swmp@ietf.org; Fri, 01 Jun 2007 08:54:27 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hu6eA-0005qQ-5j
	for swmp@ietf.org; Fri, 01 Jun 2007 08:54:27 -0400
Received: from [192.168.2.119] (h-66-166-236-26.snvacaid.covad.net
	[66.166.236.26])
	by william.mediamachines.com (Postfix) with ESMTP id 732BA464402
	for <swmp@ietf.org>; Fri,  1 Jun 2007 07:52:36 -0500 (CDT)
Message-ID: <466016F1.5020803@mediamachines.com>
Date: Fri, 01 Jun 2007 05:54:09 -0700
From: "Jay C. Weber" <jweber@mediamachines.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: swmp@ietf.org
References: <465ED84F.2090509@mediamachines.com>	<d9cef8ba0705312010g1b9b084bmb1fba948e170c844@mail.gmail.com>
	<465FA222.5050709@mediamachines.com>
In-Reply-To: <465FA222.5050709@mediamachines.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: [SWMP] tcp and udp transports in one application protocol
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Errors-To: swmp-bounces@ietf.org

Here's the gist of how we can support tcp (stream) and udp (datagram) 
transports in one application protocol.

A base-message consists of an op-code and parameters.  A conversation 
over tcp is a stream of base messages, where the first messages 
establish the context for the rest of the messages, including 
authentication information.  I.e., the first message each side sends is 
"hello" with a "ticket" parameter containing authentication data.

Since udp datagrams don't have a connection context, each datagram needs 
to securely establish its own context.  So a datagram-message wraps a 
base-message with ticket data (as well as a sequence-number, since like 
many real-time protocols, message order is relevant).  In SWAMP, two 
agents first establish a tcp connection and thereby establish ids for 
each other, to be used in the datagram ticket data.  That is, there is a 
baseline tcp connection between the two, which may then choose to use 
udp datagrams for low-latency message exchange.

Who decides to use one transport or another?  This could just be under 
application logic control, but I think there is a very useful heuristic 
available.  SWAMP contains two messages for communicating entity-state 
information: "set" and "setf".  A set message contains string references 
to the entity and property names, and as these names tend to not be very 
compact, is suitable for messages that are sent relatively 
infrequently.  However it also has a fieldId parameter that assigns a 
compact numeric id to that entity-name and property-name pair.  Agents 
cache the fieldId information in a working set of state variables, to 
support subsequent setf messages, which are relatively compact and more 
suitable for frequent transmission.  Thus the heuristic is to sent 
set-messages over the tcp stream, and setf-messages over udp.

This means that the initial value of an entity-state variable is set 
using tcp (reliable delivery) and then frequent updates to the variable 
are sent using udp (low-latency).  This seems to me to be the ideal 
combination of the transports.

jay


_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp



From swmp-bounces@ietf.org Wed Jun 13 19:05:19 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hybtu-0008Tm-SL; Wed, 13 Jun 2007 19:05:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HybEV-00072P-Kf
	for swmp@ietf.org; Wed, 13 Jun 2007 18:22:31 -0400
Received: from e31.co.us.ibm.com ([32.97.110.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HybEU-00017C-AB
	for swmp@ietf.org; Wed, 13 Jun 2007 18:22:31 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com
	[9.17.195.227])
	by e31.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5DMMT6h004691
	for <swmp@ietf.org>; Wed, 13 Jun 2007 18:22:29 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5DMMO3V250270 for <swmp@ietf.org>; Wed, 13 Jun 2007 16:22:29 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5DMMOV7018966 for <swmp@ietf.org>; Wed, 13 Jun 2007 16:22:24 -0600
Received: from internet1.lotus.com (internet1.lotus.com [9.33.9.11])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5DMMNZX018915
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <swmp@ietf.org>; Wed, 13 Jun 2007 16:22:24 -0600
Received: from wtfmail02.edc.lotus.com (wtfmail02.lotus.com [9.33.9.69])
	by internet1.lotus.com (8.14.1/8.14.1) with ESMTP id l5DMMMk7003243
	for <swmp@ietf.org>; Wed, 13 Jun 2007 18:22:23 -0400 (EDT)
To: swmp@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
Message-ID: <OF0669724B.55BED5D1-ON852572F9.0079D0A2-852572F9.007AE524@lotus.com>
From: john_patterson@us.ibm.com
Date: Wed, 13 Jun 2007 18:23:07 -0400
X-MIMETrack: Serialize by Router on WTFMAIL02/WTF/M/Lotus(Release
	7.0.2FP2|April 16, 2007) at 06/13/2007 06:22:56 PM,
	Serialize complete at 06/13/2007 06:22:56 PM
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
X-Mailman-Approved-At: Wed, 13 Jun 2007 19:05:17 -0400
Subject: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0324882568=="
Errors-To: swmp-bounces@ietf.org

This is a multipart message in MIME format.
--===============0324882568==
Content-Type: multipart/alternative;
	boundary="=_alternative 007AE523852572F9_="

This is a multipart message in MIME format.
--=_alternative 007AE523852572F9_=
Content-Type: text/plain; charset="US-ASCII"

[Sorry, I have not yet read the paper.]

Presumably, SWMP needs to be a low latency state sharing mechanism with 
some form of virtual world specific pub-sub model.

Although SIP (really SIMPLE) and XMPP were designed for "buddy list" like 
awareness.  They do define a low latency state sharing mechanism with a 
"buddy list"-specific pub-sub model.  At first blush it would seem 
sensible to ask whether the transport layers for SIP and/or XMPP are 
serviceable for SWMP and, if so, focus attention on the virtual 
world-specific pub-sub model.


John F. Patterson
IBM Distinguished Engineer
Collaborative User Experience (CUE) Research Group
john_patterson@us.ibm.com
--=_alternative 007AE523852572F9_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">[Sorry, I have not yet read the paper.]</font>
<br>
<br><font size=2 face="sans-serif">Presumably, SWMP needs to be a low latency
state sharing mechanism with some form of virtual world specific pub-sub
model.</font>
<br>
<br><font size=2 face="sans-serif">Although SIP (really SIMPLE) and XMPP
were designed for &quot;buddy list&quot; like awareness. &nbsp;They do
define a low latency state sharing mechanism with a &quot;buddy list&quot;-specific
pub-sub model. &nbsp;At first blush it would seem sensible to ask whether
the transport layers for SIP and/or XMPP are serviceable for SWMP and,
if so, focus attention on the virtual world-specific pub-sub model.</font>
<br>
<br>
<br><font size=2 face="sans-serif">John F. Patterson<br>
IBM Distinguished Engineer<br>
Collaborative User Experience (CUE) Research Group<br>
john_patterson@us.ibm.com</font>
--=_alternative 007AE523852572F9_=--


--===============0324882568==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============0324882568==--




From swmp-bounces@ietf.org Wed Jun 13 23:18:02 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyfqU-0002iZ-3P; Wed, 13 Jun 2007 23:18:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyfqS-0002iJ-As
	for swmp@ietf.org; Wed, 13 Jun 2007 23:18:00 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyfqR-0001h9-3x
	for swmp@ietf.org; Wed, 13 Jun 2007 23:18:00 -0400
Received: from [192.168.2.119] (h-66-166-236-26.snvacaid.covad.net
	[66.166.236.26]) by william.mediamachines.com (Postfix) with ESMTP
	id 7D05A464151; Wed, 13 Jun 2007 22:18:15 -0500 (CDT)
Message-ID: <4670B35E.4090600@mediamachines.com>
Date: Wed, 13 Jun 2007 20:17:50 -0700
From: "Jay C. Weber" <jweber@mediamachines.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: john_patterson@us.ibm.com
Subject: Re: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?
References: <OF0669724B.55BED5D1-ON852572F9.0079D0A2-852572F9.007AE524@lotus.com>
In-Reply-To: <OF0669724B.55BED5D1-ON852572F9.0079D0A2-852572F9.007AE524@lotus.com>
X-Spam-Score: 1.7 (+)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1640382096=="
Errors-To: swmp-bounces@ietf.org

--===============1640382096==
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:john_patterson@us.ibm.com">john_patterson@us.ibm.com</a> wrote:
<blockquote
 cite="midOF0669724B.55BED5D1-ON852572F9.0079D0A2-852572F9.007AE524@lotus.com"
 type="cite"><font face="sans-serif" size="2">Although SIP (really
SIMPLE) and XMPP
were designed for "buddy list" like awareness. &nbsp;They do
define a low latency state sharing mechanism with a "buddy
list"-specific
pub-sub model. &nbsp;At first blush it would seem sensible to ask whether
the transport layers for SIP and/or XMPP are serviceable for SWMP and,
if so, focus attention on the virtual world-specific pub-sub model.</font>
</blockquote>
Hi John, a very good question.&nbsp; I argued with myself over using XMPP
for some time.&nbsp; In the end, like most multiuser-3D implementors I
believe, I decided that bandwidth efficiency is just too important
(much moreso than for chat) to not have a packed binary protocol,
especially over the fairly inefficient ascii encoding of XML as
required by XMPP.&nbsp; A similar situation to why, to my knowledge, nobody
uses XML encodings to stream audio or video.<br>
<br>
That is, I reluctantly turned away from XMPP as an encoding for
position-data streams.&nbsp; As I understand it, XMPP is an application
protocol so it doesn't specify transport layers to adopt, except in the
sense that people usually carry XMPP over TCP, and SWMP does use TCP as
transport (as well as UDP).<br>
<br>
I know SIP/SIMPLE less well, but I do understand that SIP is an
application protocol and likewise built on top of the standard
transports.&nbsp; Interesting idea though to use SIP to establish the
sessions, or similarly, for SWMP to subsume SIP messaging.&nbsp; I'll
definitely look into that.<br>
<br>
jay<br>
--<br>
Jay C. Weber<br>
CTO, Media Machines<br>
<br>
</body>
</html>


--===============1640382096==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============1640382096==--



From swmp-bounces@ietf.org Thu Jun 14 01:01:17 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyhSP-0003fv-KF; Thu, 14 Jun 2007 01:01:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyhSO-0003fp-5T
	for swmp@ietf.org; Thu, 14 Jun 2007 01:01:16 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyhSM-0000O0-PJ
	for swmp@ietf.org; Thu, 14 Jun 2007 01:01:16 -0400
Received: from NEO (adsl-67-113-133-74.dsl.sntc01.pacbell.net [67.113.133.74])
	by william.mediamachines.com (Postfix) with ESMTP
	id 53BB046438E; Thu, 14 Jun 2007 05:01:31 -0500 (CDT)
From: "Tony Parisi" <tparisi@mediamachines.com>
To: "'Jay C. Weber'" <jweber@mediamachines.com>,
	<john_patterson@us.ibm.com>
Subject: RE: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?
Date: Wed, 13 Jun 2007 22:01:08 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AceuMqmUifoHiP1BTk+FTivNadyf5gACet5g
In-Reply-To: <4670B35E.4090600@mediamachines.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070614100131.53BB046438E@william.mediamachines.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f8ee348dcc4be4a59bc395f7cd6343ad
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0557620821=="
Errors-To: swmp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0557620821==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0017_01C7AE06.59DF9450"

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C7AE06.59DF9450
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Just to be clear:

 

We are planning to enable XMPP integration for the chat and presence, just
not 3D state sharing because of the particularly demanding requirements.

 

Tony

 

 

  _____  

From: Jay C. Weber [mailto:jweber@mediamachines.com] 
Sent: Wednesday, June 13, 2007 8:18 PM
To: john_patterson@us.ibm.com
Cc: swmp@ietf.org
Subject: Re: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?

 

john_patterson@us.ibm.com wrote: 

Although SIP (really SIMPLE) and XMPP were designed for "buddy list" like
awareness.  They do define a low latency state sharing mechanism with a
"buddy list"-specific pub-sub model.  At first blush it would seem sensible
to ask whether the transport layers for SIP and/or XMPP are serviceable for
SWMP and, if so, focus attention on the virtual world-specific pub-sub
model. 

Hi John, a very good question.  I argued with myself over using XMPP for
some time.  In the end, like most multiuser-3D implementors I believe, I
decided that bandwidth efficiency is just too important (much moreso than
for chat) to not have a packed binary protocol, especially over the fairly
inefficient ascii encoding of XML as required by XMPP.  A similar situation
to why, to my knowledge, nobody uses XML encodings to stream audio or video.

That is, I reluctantly turned away from XMPP as an encoding for
position-data streams.  As I understand it, XMPP is an application protocol
so it doesn't specify transport layers to adopt, except in the sense that
people usually carry XMPP over TCP, and SWMP does use TCP as transport (as
well as UDP).

I know SIP/SIMPLE less well, but I do understand that SIP is an application
protocol and likewise built on top of the standard transports.  Interesting
idea though to use SIP to establish the sessions, or similarly, for SWMP to
subsume SIP messaging.  I'll definitely look into that.

jay
--
Jay C. Weber
CTO, Media Machines


------=_NextPart_000_0017_01C7AE06.59DF9450
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just to be =
clear:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>We are planning to enable XMPP =
integration
for the chat and presence, just not 3D state sharing because of the
particularly demanding requirements.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Tony<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight=
:bold'>From:</span></font></b><font
size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:windowtext'> Jay C. Weber [mailto:jweber@mediamachines.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, June 13, =
2007
8:18 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
john_patterson@us.ibm.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName =
w:st=3D"on">swmp@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [SWMP] What =
is the
relationship of SWMP to SIP and/or XMPP?</span></font><font =
color=3Dblack><span
style=3D'color:windowtext'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><a =
href=3D"mailto:john_patterson@us.ibm.com">john_patterson@us.ibm.com</a>
wrote: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3Dsans-serif><span
style=3D'font-size:10.0pt;font-family:sans-serif'>Although SIP (really =
SIMPLE)
and XMPP were designed for &quot;buddy list&quot; like awareness. =
&nbsp;They do
define a low latency state sharing mechanism with a &quot;buddy
list&quot;-specific pub-sub model. &nbsp;At first blush it would seem =
sensible
to ask whether the transport layers for SIP and/or XMPP are serviceable =
for
SWMP and, if so, focus attention on the virtual world-specific pub-sub =
model.</span></font>
<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Hi John, a =
very good
question.&nbsp; I argued with myself over using XMPP for some =
time.&nbsp; In
the end, like most multiuser-3D implementors I believe, I decided that
bandwidth efficiency is just too important (much moreso than for chat) =
to not
have a packed binary protocol, especially over the fairly inefficient =
ascii
encoding of XML as required by XMPP.&nbsp; A similar situation to why, =
to my
knowledge, nobody uses XML encodings to stream audio or video.<br>
<br>
That is, I reluctantly turned away from XMPP as an encoding for =
position-data
streams.&nbsp; As I understand it, XMPP is an application protocol so it
doesn't specify transport layers to adopt, except in the sense that =
people
usually carry XMPP over TCP, and SWMP does use TCP as transport (as well =
as
UDP).<br>
<br>
I know SIP/SIMPLE less well, but I do understand that SIP is an =
application
protocol and likewise built on top of the standard transports.&nbsp;
Interesting idea though to use SIP to establish the sessions, or =
similarly, for
SWMP to subsume SIP messaging.&nbsp; I'll definitely look into that.<br>
<br>
jay<br>
--<br>
Jay C. Weber<br>
CTO, Media Machines<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0017_01C7AE06.59DF9450--




--===============0557620821==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============0557620821==--






From swmp-bounces@ietf.org Thu Jun 14 01:11:12 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyhc0-00037W-EF; Thu, 14 Jun 2007 01:11:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyhbx-00037I-NQ
	for swmp@ietf.org; Thu, 14 Jun 2007 01:11:10 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyhbv-0003Sr-8t
	for swmp@ietf.org; Thu, 14 Jun 2007 01:11:09 -0400
Received: from NEO (adsl-67-113-133-74.dsl.sntc01.pacbell.net [67.113.133.74])
	by william.mediamachines.com (Postfix) with ESMTP
	id DE13B46438E; Thu, 14 Jun 2007 05:11:23 -0500 (CDT)
From: "Tony Parisi" <tparisi@mediamachines.com>
To: "'Tony Parisi'" <tparisi@mediamachines.com>,
	"'Jay C. Weber'" <jweber@mediamachines.com>, <john_patterson@us.ibm.com>
Subject: RE: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?
Date: Wed, 13 Jun 2007 22:11:01 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AceuMqmUifoHiP1BTk+FTivNadyf5gACet5gAAFnnhA=
In-Reply-To: <20070614100131.53BB046438E@william.mediamachines.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070614101123.DE13B46438E@william.mediamachines.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b058151374d77ee76edaac850f7449fb
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0528584821=="
Errors-To: swmp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0528584821==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0028_01C7AE07.BB059DA0"

This is a multi-part message in MIME format.

------=_NextPart_000_0028_01C7AE07.BB059DA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Just to be extra clear: when I say "we are planning to enable XMPP" I am
talking about within our own applications. They will use XMPP for chat and
presence and SWMP for 3D state. Sorry for any confusion.

 

Tony

 

 

  _____  

From: Tony Parisi [mailto:tparisi@mediamachines.com] 
Sent: Wednesday, June 13, 2007 10:01 PM
To: 'Jay C. Weber'; john_patterson@us.ibm.com
Cc: swmp@ietf.org
Subject: RE: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?

 

Just to be clear:

 

We are planning to enable XMPP integration for the chat and presence, just
not 3D state sharing because of the particularly demanding requirements.

 

Tony

 

 

  _____  

From: Jay C. Weber [mailto:jweber@mediamachines.com] 
Sent: Wednesday, June 13, 2007 8:18 PM
To: john_patterson@us.ibm.com
Cc: swmp@ietf.org
Subject: Re: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?

 

john_patterson@us.ibm.com wrote: 

Although SIP (really SIMPLE) and XMPP were designed for "buddy list" like
awareness.  They do define a low latency state sharing mechanism with a
"buddy list"-specific pub-sub model.  At first blush it would seem sensible
to ask whether the transport layers for SIP and/or XMPP are serviceable for
SWMP and, if so, focus attention on the virtual world-specific pub-sub
model. 

Hi John, a very good question.  I argued with myself over using XMPP for
some time.  In the end, like most multiuser-3D implementors I believe, I
decided that bandwidth efficiency is just too important (much moreso than
for chat) to not have a packed binary protocol, especially over the fairly
inefficient ascii encoding of XML as required by XMPP.  A similar situation
to why, to my knowledge, nobody uses XML encodings to stream audio or video.

That is, I reluctantly turned away from XMPP as an encoding for
position-data streams.  As I understand it, XMPP is an application protocol
so it doesn't specify transport layers to adopt, except in the sense that
people usually carry XMPP over TCP, and SWMP does use TCP as transport (as
well as UDP).

I know SIP/SIMPLE less well, but I do understand that SIP is an application
protocol and likewise built on top of the standard transports.  Interesting
idea though to use SIP to establish the sessions, or similarly, for SWMP to
subsume SIP messaging.  I'll definitely look into that.

jay
--
Jay C. Weber
CTO, Media Machines


------=_NextPart_000_0028_01C7AE07.BB059DA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just to be extra clear: when I say =
&#8220;we
are planning to enable XMPP&#8221; I am talking about within our own
applications. They will use XMPP for chat and presence and SWMP for 3D =
state. Sorry
for any confusion.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Tony<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight=
:bold'>From:</span></font></b><font
size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:windowtext'> Tony Parisi [mailto:tparisi@mediamachines.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, June 13, =
2007
10:01 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Jay C. Weber';
john_patterson@us.ibm.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName =
w:st=3D"on">swmp@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [SWMP] What =
is the
relationship of SWMP to SIP and/or XMPP?</span></font><font =
color=3Dblack><span
style=3D'color:windowtext'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just to be =
clear:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>We are planning to enable XMPP =
integration
for the chat and presence, just not 3D state sharing because of the
particularly demanding requirements.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Tony<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight=
:bold'>From:</span></font></b><font
size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:windowtext'> Jay C. Weber [mailto:jweber@mediamachines.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, June 13, =
2007
8:18 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
john_patterson@us.ibm.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName =
w:st=3D"on">swmp@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [SWMP] What =
is the
relationship of SWMP to SIP and/or XMPP?</span></font><font =
color=3Dblack><span
style=3D'color:windowtext'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><a =
href=3D"mailto:john_patterson@us.ibm.com">john_patterson@us.ibm.com</a>
wrote: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>Although SIP (really SIMPLE) and XMPP were =
designed
for &quot;buddy list&quot; like awareness. &nbsp;They do define a low =
latency
state sharing mechanism with a &quot;buddy list&quot;-specific pub-sub =
model.
&nbsp;At first blush it would seem sensible to ask whether the transport =
layers
for SIP and/or XMPP are serviceable for SWMP and, if so, focus attention =
on the
virtual world-specific pub-sub model.</span></font> <o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Hi John, a =
very good
question.&nbsp; I argued with myself over using XMPP for some =
time.&nbsp; In
the end, like most multiuser-3D implementors I believe, I decided that
bandwidth efficiency is just too important (much moreso than for chat) =
to not
have a packed binary protocol, especially over the fairly inefficient =
ascii
encoding of XML as required by XMPP.&nbsp; A similar situation to why, =
to my
knowledge, nobody uses XML encodings to stream audio or video.<br>
<br>
That is, I reluctantly turned away from XMPP as an encoding for =
position-data
streams.&nbsp; As I understand it, XMPP is an application protocol so it
doesn't specify transport layers to adopt, except in the sense that =
people
usually carry XMPP over TCP, and SWMP does use TCP as transport (as well =
as
UDP).<br>
<br>
I know SIP/SIMPLE less well, but I do understand that SIP is an =
application
protocol and likewise built on top of the standard transports.&nbsp;
Interesting idea though to use SIP to establish the sessions, or =
similarly, for
SWMP to subsume SIP messaging.&nbsp; I'll definitely look into that.<br>
<br>
jay<br>
--<br>
Jay C. Weber<br>
CTO, Media Machines<o:p></o:p></span></font></p>

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_0028_01C7AE07.BB059DA0--




--===============0528584821==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============0528584821==--






From swmp-bounces@ietf.org Thu Jun 14 05:00:25 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HylBo-00032h-SO; Thu, 14 Jun 2007 05:00:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HylBn-000321-AM
	for swmp@ietf.org; Thu, 14 Jun 2007 05:00:23 -0400
Received: from mxi.ltu.se ([130.240.42.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HylBl-0007MW-JW
	for swmp@ietf.org; Thu, 14 Jun 2007 05:00:23 -0400
Received: from EMMA.personal.adp.ltu.se (ross.personal.adp.ltu.se
	[130.240.150.6])
	by mxi.ltu.se (8.13.1/8.13.1) with ESMTP id l5E90Jui019556
	for <swmp@ietf.org>; Thu, 14 Jun 2007 11:00:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 14 Jun 2007 11:00:19 +0200
Message-ID: <668D1B8AD729C94DB91D17EC19B8BB910565C048@EMMA.personal.adp.ltu.se>
In-Reply-To: <20070614101123.DE13B46438E@william.mediamachines.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Intro and general Q.
Thread-Index: AceuMqmUifoHiP1BTk+FTivNadyf5gACet5gAAFnnhAABx7nAA==
From: "Sven-Erik Tiberg" <Sven-Erik.Tiberg@ltu.se>
To: <swmp@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 681e62a2ce9b0804b459fe780d892beb
Subject: [SWMP] Intro and general Q.
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1049804650=="
Errors-To: swmp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1049804650==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7AE62.6EE72760"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7AE62.6EE72760
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi.
=20
I'm Sven-Erik Tiberg at Lulea Univ. of Technology / Sweden and one of my
interest are Distributed Real-Time simulations like low-cost client
-server driversimulators using X3D Human Mashine Interface with haptic
and server-side simulation engines like Mathworks/simulab-models,
carsim.com, racer.nl or Aspentech.com for process simulations.=20
=20
Collected some info at http://tellus.arb.ltu.se/moodle WBSP_public.
=20
Current "challange" are communication of states between HMI-client and
simulationengine-server. Have been looking into DIS and a custom made
raw-data transfer over UDP using python.twisted on client side.=20
DIS seems to have rerached it's end of developent and are not so easy to
get info about.
UDP raw-data are a custom made ( me ) protocol that needs some work on
the client side and are non std.
=20
Learned about SWAMP from jay at mediamachines and the info about it
covers my livingroom desk and more places at home. And my mind are not
compleatly with my family all the time.
=20
Some Q. before I compleatly dissapear behind my papars and laptop:
In a driver simulator there are some looptimes for updates, the
outerloop HMI <> car model use to be <=3D 50 mSec.=20
The outerloop will be used for transport of states beween client and
server, any limitations in SWAMP on this?
=20
/ Thank for letting me join your e-discussions.
=20
Sven-Erik Tiberg=20
IT - dept.=20
Lulea Univ. of Technology=20
Sweden
=20
=20
=20

------_=_NextPart_001_01C7AE62.6EE72760
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times =
New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times =
New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times =
New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue bgColor=3Dwhite>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007>Hi.</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>I'm =
Sven-Erik Tiberg=20
at Lulea Univ. of Technology / Sweden and one of my interest are =
Distributed=20
Real-Time simulations like low-cost client -server driversimulators =
using X3D=20
Human Mashine Interface with haptic and server-side simulation engines =
like=20
Mathworks/simulab-models, carsim.com, racer.nl or Aspentech.com for =
process=20
simulations. </SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN =
class=3D182293308-14062007>Collected some info=20
at <A=20
href=3D"http://tellus.arb.ltu.se/moodle">http://tellus.arb.ltu.se/moodle<=
/A>&nbsp;WBSP_public.</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>Current =
"challange"=20
are communication of states between HMI-client and =
simulationengine-server. Have=20
been looking into DIS and a custom made&nbsp;raw-data transfer over UDP =
using=20
python.twisted on client side. </SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>DIS =
seems to have=20
rerached it's end of developent and are not so easy to get info=20
about.</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>UDP =
raw-data are a=20
custom made ( me ) protocol that needs some work on the client side and =
are non=20
std.</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>Learned=20
about&nbsp;SWAMP from jay at mediamachines and the info about it covers =
my=20
livingroom desk and more places at home. And my mind are not compleatly =
with my=20
family all the time.</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>Some Q. =
before I=20
compleatly dissapear behind my papars and=20
laptop:</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>In =
a&nbsp;driver=20
simulator there are some looptimes for updates, the outerloop HMI =
&lt;&gt; car=20
model use to be &lt;=3D 50 mSec. </SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>The =
outerloop will=20
be used for transport of states beween client and server, any =
limitations in=20
SWAMP on this?</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>/ Thank =
for letting=20
me join your e-discussions.</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN =
class=3D182293308-14062007>Sven-Erik Tiberg=20
</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>IT - =
dept.=20
</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN class=3D182293308-14062007>Lulea =
Univ. of=20
Technology </SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007>Sweden</SPAN></o:p></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
class=3D182293308-14062007></SPAN></o:p></SPAN></FONT>&nbsp;</DIV></BODY>=
</HTML>

------_=_NextPart_001_01C7AE62.6EE72760--


--===============1049804650==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============1049804650==--




From swmp-bounces@ietf.org Thu Jun 14 10:52:00 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyqfE-0001sq-K6; Thu, 14 Jun 2007 10:51:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyqfD-0001sg-1M
	for swmp@ietf.org; Thu, 14 Jun 2007 10:51:07 -0400
Received: from www.yumetech.com ([203.27.111.20] helo=yumetech.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyqfA-0003my-Fe
	for swmp@ietf.org; Thu, 14 Jun 2007 10:51:07 -0400
Received: from [192.168.1.171] (office.yumetech.com [203.27.111.129])
	(authenticated bits=0)
	by yumetech.com (8.13.8/8.13.7) with ESMTP id l5EEp0E1011343
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 07:51:01 -0700
Message-ID: <467155C4.102@yumetech.com>
Date: Thu, 14 Jun 2007 07:50:44 -0700
From: Alan Hudson <giles@yumetech.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Tony Parisi <tparisi@mediamachines.com>
Subject: Re: [SWMP] What is the relationship of SWMP to SIP and/or XMPP?
References: <20070614100131.53BB046438E@william.mediamachines.com>
In-Reply-To: <20070614100131.53BB046438E@william.mediamachines.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: swmp@ietf.org, john_patterson@us.ibm.com
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: giles@yumetech.com
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Errors-To: swmp-bounces@ietf.org

Tony Parisi wrote:
> Just to be clear:
> 
>  
> 
> We are planning to enable XMPP integration for the chat and presence, just
> not 3D state sharing because of the particularly demanding requirements.
> 
>  

I've had a fair bit of luck pushing entity locations over XMPP.  I have 
also prototyped using XML binary to deliver the data(using XMPP 
attachments).  I liked having the open source servers already available 
and the services available to them(replication, logging, security)...

That said, I suspect you can hand roll a direct binary protocol that 
will be faster.  Though I think the XML binary work will be comparable.

Not sure how much extensibility is needed in this protocol.  For me the 
ability to add new parts to the protocol over time has been a big help. 
  Parsing XML makes the client very resilient to changes in the 
format(at least additions).  I also like XML's model of allowing 
optional data without enlarging the data packet.  A study I did of DIS 
showed it used about 20% of its packet size on extensions mechanisms.

I like the work NPS did on Bamboo.  The idea was to have a multi-user 
simulation that never was down for maintenance.  You had to be able to 
extend the system in pieces.  The clients would need to know how to 
gracefully ignore new data items.  XML has a nice mechanism for this.

The other reason we use XMPP is to lower the barrier of entry to the 
system.  Lots of people know how to program for XML.  Any library we 
develop to directly talk to this protocol will be less understood and 
less widely available then XML libraries.

There's the sell for XMPP from my side.  Its been convinient to use at a 
cost of some performance.  I like some of the features it gives us.  But 
perhaps those features could just be designed into a similar system.
-- 
Alan Hudson

President Yumetech, Inc.                               www.yumetech.com
President Web3D Consortium                             www.web3d.org
206 340 8900

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp



From swmp-bounces@ietf.org Sat Jun 23 21:01:06 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2GTR-0007mU-QA; Sat, 23 Jun 2007 21:01:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I18V7-0004EF-2E
	for swmp@ietf.org; Wed, 20 Jun 2007 18:18:09 -0400
Received: from e5.ny.us.ibm.com ([32.97.182.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I18V5-0002Sk-AH
	for swmp@ietf.org; Wed, 20 Jun 2007 18:18:09 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e5.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5KMI400028153
	for <swmp@ietf.org>; Wed, 20 Jun 2007 18:18:04 -0400
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5KMI4v6431396 for <swmp@ietf.org>; Wed, 20 Jun 2007 18:18:04 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1])
	by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5KMI3SG012952 for <swmp@ietf.org>; Wed, 20 Jun 2007 18:18:03 -0400
Received: from internet1.lotus.com (internet1.lotus.com [9.33.9.11])
	by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5KMI34I012934
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 20 Jun 2007 18:18:03 -0400
Received: from wtfmail02.edc.lotus.com (wtfmail02.lotus.com [9.33.9.69])
	by internet1.lotus.com (8.14.1/8.14.1) with ESMTP id l5KMI3RJ017503;
	Wed, 20 Jun 2007 18:18:03 -0400 (EDT)
To: jweber@DOMAIN.HIDDEN, john_patterson@us.ibm.com
Subject: Re: [SWMP] Media Machines' initial design and code 
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
Message-ID: <OFEA6E617C.FAAC38A3-ON85257300.006DDB5F-85257300.007A7F58@lotus.com>
From: john_patterson@us.ibm.com
Date: Wed, 20 Jun 2007 18:18:36 -0400
X-MIMETrack: Serialize by Router on WTFMAIL02/WTF/M/Lotus(Release
	7.0.2FP2|April 16, 2007) at 06/20/2007 06:18:37 PM,
	Serialize complete at 06/20/2007 06:18:37 PM
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2d133cc328f58695161c98bb4f4dc213
X-Mailman-Approved-At: Sat, 23 Jun 2007 21:01:05 -0400
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0983091647=="
Errors-To: swmp-bounces@ietf.org

This is a multipart message in MIME format.
--===============0983091647==
Content-Type: multipart/alternative;
	boundary="=_alternative 007A7F5685257300_="

This is a multipart message in MIME format.
--=_alternative 007A7F5685257300_=
Content-Type: text/plain; charset="US-ASCII"

Jay Weber wrote:

I'd like to point the group to Media Machines' initial work towards SWMP.

We presented an overview paper at the Web3D 2007 Symposium, which you can 
find at http://www.mediamachines.com/hydra/swampweb3d2007.pdf

I have now managed to look through the paper and I am ready to ask some 
questions.

First, let me state that I am not especially familiar with X3D.  I have 
looked quickly at it, but I have not gotten to the depth that the authors 
have.  It is possible that some of my questions are best answered by 
referring me back to X3D.

Second, I understand the swamp protocol (I use the name from the paper.) 
to be a peer-to-peer state replication protocol.  By peer-to-peer, I do 
not mean that it is useless for a server-based approach, but that it only 
addresses communication between two network nodes and this communication 
is completely symmetric; there is no assumption about either node having a 
different role from the other.  By state replication, I mean that both 
nodes maintain a copy of the state (at least the relevant, e.g., 
dynamically changing, state) and the protocol is used to keep these copies 
synchronized.

Third, I assume there is a desire for swmp to embrace the full breadth of 
virtual worlds implementations.  The paper (and subsequent postings) 
clearly recognize alternative network configurations (peer-to-peer, 
server-based, and hybrid) as an issue.  The paper is less clear on its 
position regarding varying approaches to where certain virtual worlds 
semantics, e.g., physics, collision detection, etc., will occur, i.e., 
centrally or peripherally.  I do not fault the paper for that, I just want 
to point out that this is a major differentiator among existing 
implementations and, if possible, we want to support many, if not all, 
alternatives.

Fourth, I assume that swamp supports packing multiple messages onto a 
single udp packet.  Without that I am having a little trouble 
understanding the obsession with keeping messages short (as evidenced by 
the setf method.).

Fifth, I assume that the purpose of swamp is for communicating state that 
is dynamic (ie, changing due to interactions with the virtual world) and 
not for the purpose of moving the static aspects of the 3D models.  It is 
not stated, but I am assuming that terrain, avatars, and in-world objects 
are initially obtained via prior download/install, http, or some other 
query-response protocol.  SWAMP is not for retrieving this static 
information; it is for maintaining the dynamic attributes of these models 
as they change due to being instantiated in a virtual world.

So, here are my questions:

1)  Should the base model be more generic with X3D as a specific type?

Many systems starting with Linda and moving through JavaSpaces and TSpaces 
have adopted the attitude that a state sharing system can use a very 
generic notion of how the state is organized.  These systems assume the 
state is in tuples; other systems assume something more akin to 
property-value pairs.  In any case, the base model is very generic and not 
tied to any particular purpose or specialized representation.  I wonder 
whether that would be a better approach for swmp.

I am not arguing that there is no place for X3D, just that we might prefer 
to treat it as a special case of a more generic state representation 
scheme.  X3D would be less embedded in the PDUs and more a conventional 
and well-defined set of types, fields, values, etc. that can be mapped 
into the generic PDU.  The value of this is that when we find some other 
kind of state that we would like to synchronize, we would not be 
struggling to map it into an X3D-based message structure.  Instead, we 
would map it into tuples or property-value pairs, which would certainly be 
less awkward and might also be more efficient.

As it stands, the biggest impediment to this approach posed by swamp is 
the rather small number of bits allocated to type information (and 
possibly the fieldID, though I do not fully understand its purpose.)

2)  Is X3D the right model?

I am not familiar enough with X3D to have a strong position on this.  I am 
mostly reacting to the idea that (to a first approximation) it is a scene 
graph representation.  That means it is tied to the display of the virtual 
world, which means it is more view than model in the model-view-controller 
(MVC) sense.  Presumably, our primary objective is to share the model of 
the world.

This is the chain of reasoning that drives my question.  In truth, it is 
more an aesthetic reaction to focusing on sharing views than a deep 
engineering concern.  I am aware that scene graphs often have highly 
abstracted grouping nodes that function like models in the MVC sense.  I 
also know that these high-level nodes have properties that can encode the 
more abstract model state.  In all likelihood, any model can be 
represented using the scene graph and therefore X3D is adequate.  But, 
should designers/developers be compelled to represent their models that 
way.  For example, must a fire be modeled as an X3D object or could we 
treat it as something unseen that causes changes to the visible objects 
based on complex computations?

Having said all this, I do understand that we must also be able to share 
the view objects.  I also recognize that X3D is a better representation of 
the state of a virtual world than something more abstract that I have not 
yet dreamed up.  Perhaps the best resolution of this question is to treat 
it as a special case of my argument in 1) above.  Supporting X3D 
synchronization is key, but it should not be the only form of state that 
we are prepared to synchronize.

3)  Should notifications of changes be distinguished from instructions to 
make a change?

Most of the time when I have constructed protocols of this sort, I have 
distinguished between messages that indicate a desire to change the state 
and messages that indicate that the state has been changed.  SWAMP does 
not seem to make this distinction.  I assume a set message is used both to 
reflect that a change should be made and that a change has been made.  My 
bias for differentiating these messages derives from working on 
client-server implementations, but I think it is useful even in a 
peer-to-peer situation.  Usually, one node has final say on whether a 
change of state will be permitted.  For the other node, a set, add, or 
remove message is a request.  It cannot count on the request being 
honored.  For the controlling node, a setNotify, addNotify, or 
removeNotify message is definitive.  This is not a request of the 
receiving node; it is informative.

I find this differentiation of requests for changes vs. notifications of 
changes easier to follow and I would strongly recommend that swmp follow 
this approach.

4)  How does swamp support latecomers?

Presumably one of the values of having a server keep track of the state of 
the virtual world is so that late arriving clients can retrieve the 
current values and get caught up.  This is generally referred to as the 
latecomer problem.  I do not see how a latecomer requests the current 
state of the virtual world using swmp.  I expected to find a get or read 
message that would be followed by a barrage of add messages (or better yet 
addNotify messages.)

Am I missing something?  Were you planning to use http to retrieve this 
state?  If so, what were you planning to do about race conditions between 
the http request and notifications of changes to the not yet received 
state?

jfp
--=_alternative 007A7F5685257300_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Jay Weber wrote:</font>
<br>
<br><tt><font size=3>I'd like to point the group to Media Machines' initial
work towards SWMP.</font></tt>
<br><tt><font size=3><br>
We presented an overview paper at the Web3D 2007 Symposium, which you can
find at </font></tt><a href=http://www.mediamachines.com/hydra/swampweb3d2007.pdf><tt><font size=3 color=blue><u>http://www.mediamachines.com/hydra/swampweb3d2007.pdf</u></font></tt></a>
<br>
<br><font size=2 face="sans-serif">I have now managed to look through the
paper and I am ready to ask some questions.</font>
<br>
<br><font size=2 face="sans-serif">First, let me state that I am not especially
familiar with X3D. &nbsp;I have looked quickly at it, but I have not gotten
to the depth that the authors have. &nbsp;It is possible that some of my
questions are best answered by referring me back to X3D.</font>
<br>
<br><font size=2 face="sans-serif">Second, I understand the swamp protocol
(I use the name from the paper.) to be a peer-to-peer state replication
protocol. &nbsp;By peer-to-peer, I do not mean that it is useless for a
server-based approach, but that it only addresses communication between
two network nodes and this communication is completely symmetric; there
is no assumption about either node having a different role from the other.
&nbsp;By state replication, I mean that both nodes maintain a copy of the
state (at least the relevant, e.g., dynamically changing, state) and the
protocol is used to keep these copies synchronized.</font>
<br>
<br><font size=2 face="sans-serif">Third, I assume there is a desire for
swmp to embrace the full breadth of virtual worlds implementations. &nbsp;The
paper (and subsequent postings) clearly recognize alternative network configurations
(peer-to-peer, server-based, and hybrid) as an issue. &nbsp;The paper is
less clear on its position regarding varying approaches to where certain
virtual worlds semantics, e.g., physics, collision detection, etc., will
occur, i.e., centrally or peripherally. &nbsp;I do not fault the paper
for that, I just want to point out that this is a major differentiator
among existing implementations and, if possible, we want to support many,
if not all, alternatives.</font>
<br>
<br><font size=2 face="sans-serif">Fourth, I assume that swamp supports
packing multiple messages onto a single udp packet. &nbsp;Without that
I am having a little trouble understanding the obsession with keeping messages
short (as evidenced by the setf method.).</font>
<br>
<br><font size=2 face="sans-serif">Fifth, I assume that the purpose of
swamp is for communicating state that is dynamic (ie, changing due to interactions
with the virtual world) and not for the purpose of moving the static aspects
of the 3D models. &nbsp;It is not stated, but I am assuming that terrain,
avatars, and in-world objects are initially obtained via prior download/install,
http, or some other query-response protocol. &nbsp;SWAMP is not for retrieving
this static information; it is for maintaining the dynamic attributes of
these models as they change due to being instantiated in a virtual world.</font>
<br>
<br><font size=2 face="sans-serif">So, here are my questions:</font>
<br>
<br><font size=2 face="sans-serif">1) &nbsp;Should the base model be more
generic with X3D as a specific type?</font>
<br>
<br><font size=2 face="sans-serif">Many systems starting with Linda and
moving through JavaSpaces and TSpaces have adopted the attitude that a
state sharing system can use a very generic notion of how the state is
organized. &nbsp;These systems assume the state is in tuples; other systems
assume something more akin to property-value pairs. &nbsp;In any case,
the base model is very generic and not tied to any particular purpose or
specialized representation. &nbsp;I wonder whether that would be a better
approach for swmp.</font>
<br>
<br><font size=2 face="sans-serif">I am not arguing that there is no place
for X3D, just that we might prefer to treat it as a special case of a more
generic state representation scheme. &nbsp;X3D would be less embedded in
the PDUs and more a conventional and well-defined set of types, fields,
values, etc. that can be mapped into the generic PDU. &nbsp;The value of
this is that when we find some other kind of state that we would like to
synchronize, we would not be struggling to map it into an X3D-based message
structure. &nbsp;Instead, we would map it into tuples or property-value
pairs, which would certainly be less awkward and might also be more efficient.</font>
<br>
<br><font size=2 face="sans-serif">As it stands, the biggest impediment
to this approach posed by swamp is the rather small number of bits allocated
to type information (and possibly the fieldID, though I do not fully understand
its purpose.)</font>
<br>
<br><font size=2 face="sans-serif">2) &nbsp;Is X3D the right model?</font>
<br>
<br><font size=2 face="sans-serif">I am not familiar enough with X3D to
have a strong position on this. &nbsp;I am mostly reacting to the idea
that (to a first approximation) it is a scene graph representation. &nbsp;That
means it is tied to the display of the virtual world, which means it is
more view than model in the model-view-controller (MVC) sense. &nbsp;Presumably,
our primary objective is to share the model of the world.</font>
<br>
<br><font size=2 face="sans-serif">This is the chain of reasoning that
drives my question. &nbsp;In truth, it is more an aesthetic reaction to
focusing on sharing views than a deep engineering concern. &nbsp;I am aware
that scene graphs often have highly abstracted grouping nodes that function
like models in the MVC sense. &nbsp;I also know that these high-level nodes
have properties that can encode the more abstract model state. &nbsp;In
all likelihood, any model can be represented using the scene graph and
therefore X3D is adequate. &nbsp;But, should designers/developers be compelled
to represent their models that way. &nbsp;For example, must a fire be modeled
as an X3D object or could we treat it as something unseen that causes changes
to the visible objects based on complex computations?</font>
<br>
<br><font size=2 face="sans-serif">Having said all this, I do understand
that we must also be able to share the view objects. &nbsp;I also recognize
that X3D is a better representation of the state of a virtual world than
something more abstract that I have not yet dreamed up. &nbsp;Perhaps the
best resolution of this question is to treat it as a special case of my
argument in 1) above. &nbsp;Supporting X3D synchronization is key, but
it should not be the only form of state that we are prepared to synchronize.</font>
<br>
<br><font size=2 face="sans-serif">3) &nbsp;Should notifications of changes
be distinguished from instructions to make a change?</font>
<br>
<br><font size=2 face="sans-serif">Most of the time when I have constructed
protocols of this sort, I have distinguished between messages that indicate
a desire to change the state and messages that indicate that the state
has been changed. &nbsp;SWAMP does not seem to make this distinction. &nbsp;I
assume a set message is used both to reflect that a change should be made
and that a change has been made. &nbsp;My bias for differentiating these
messages derives from working on client-server implementations, but I think
it is useful even in a peer-to-peer situation. &nbsp;Usually, one node
has final say on whether a change of state will be permitted. &nbsp;For
the other node, a set, add, or remove message is a request. &nbsp;It cannot
count on the request being honored. &nbsp;For the controlling node, a setNotify,
addNotify, or removeNotify message is definitive. &nbsp;This is not a request
of the receiving node; it is informative.</font>
<br>
<br><font size=2 face="sans-serif">I find this differentiation of requests
for changes vs. notifications of changes easier to follow and I would strongly
recommend that swmp follow this approach.</font>
<br>
<br><font size=2 face="sans-serif">4) &nbsp;How does swamp support latecomers?</font>
<br>
<br><font size=2 face="sans-serif">Presumably one of the values of having
a server keep track of the state of the virtual world is so that late arriving
clients can retrieve the current values and get caught up. &nbsp;This is
generally referred to as the latecomer problem. &nbsp;I do not see how
a latecomer requests the current state of the virtual world using swmp.
&nbsp;I expected to find a get or read message that would be followed by
a barrage of add messages (or better yet addNotify messages.)</font>
<br>
<br><font size=2 face="sans-serif">Am I missing something? &nbsp;Were you
planning to use http to retrieve this state? &nbsp;If so, what were you
planning to do about race conditions between the http request and notifications
of changes to the not yet received state?</font>
<br>
<br><font size=2 face="sans-serif">jfp</font>
--=_alternative 007A7F5685257300_=--


--===============0983091647==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============0983091647==--




From swmp-bounces@ietf.org Sun Jun 24 12:52:57 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2VKZ-0005yM-Gk; Sun, 24 Jun 2007 12:52:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2VKY-0005yG-Jk
	for swmp@ietf.org; Sun, 24 Jun 2007 12:52:54 -0400
Received: from web90501.mail.mud.yahoo.com ([216.252.100.168])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I2VKV-0006E4-8X
	for swmp@ietf.org; Sun, 24 Jun 2007 12:52:54 -0400
Received: (qmail 26637 invoked by uid 60001); 24 Jun 2007 16:52:50 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=j1rDRkvazAIHm5EhWiltwsKyDu+aP6kSGfR1iW8fsLNdiknD2bcj9PZ/8LYWDrLtJeNEoNqLmxa4IH3fmnnczY5oTcBpKasXVoPsWWcAjNX4jJc13fdeHggib/VRD1zmvpMbKGK6DBp+x4W6L9AlIYtUAyxXKUYFHZjGVd5b6Wo=;
X-YMail-OSG: 1q7s_tQVM1lSwhjkjS1b0RlPsh0th0SphnYsR7a.QVVN0.nCY5PDIbWq1v2Th7Kk_YA.a6ZnZkWn0D9jY13AdYh9h7perV45Q6UdofzwAQMRnJvncww-
Received: from [144.134.129.214] by web90501.mail.mud.yahoo.com via HTTP;
	Sun, 24 Jun 2007 09:52:50 PDT
Date: Sun, 24 Jun 2007 09:52:50 -0700 (PDT)
From: Paul Aslin <fabricatorgeneral@yahoo.com>
Subject: Re: [SWMP] Media Machines' initial design and code 
To: john_patterson@us.ibm.com
In-Reply-To: <OFEA6E617C.FAAC38A3-ON85257300.006DDB5F-85257300.007A7F58@lotus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <672580.26268.qm@web90501.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Errors-To: swmp-bounces@ietf.org


The easiest way to explain how x3d (and vrml) work is a
simple example.

DEF Object Transform {
 translation 0 0 0
 children [
 ]
}

To set translation to something you'd use javascript like
this in a Script node(*).

Object.translation=value;

This is commonly refered to as object, attribute, value. So
SWMP needs to support the same data.

Messages may not just be simple values, you can also send
entire scene graphs or nodes via SWMP. 


(*) or ROUTE from another node

I'll reply further on this soon.

--- john_patterson@us.ibm.com wrote:

> Jay Weber wrote:
> 
> I'd like to point the group to Media Machines' initial
> work towards SWMP.
> 
> We presented an overview paper at the Web3D 2007
> Symposium, which you can 
> find at
> http://www.mediamachines.com/hydra/swampweb3d2007.pdf
> 
> I have now managed to look through the paper and I am
> ready to ask some 
> questions.
> 
> First, let me state that I am not especially familiar
> with X3D.  I have 
> looked quickly at it, but I have not gotten to the depth
> that the authors 
> have.  It is possible that some of my questions are best
> answered by 
> referring me back to X3D.
> 
> Second, I understand the swamp protocol (I use the name
> from the paper.) 
> to be a peer-to-peer state replication protocol.  By
> peer-to-peer, I do 
> not mean that it is useless for a server-based approach,
> but that it only 
> addresses communication between two network nodes and
> this communication 
> is completely symmetric; there is no assumption about
> either node having a 
> different role from the other.  By state replication, I
> mean that both 
> nodes maintain a copy of the state (at least the
> relevant, e.g., 
> dynamically changing, state) and the protocol is used to
> keep these copies 
> synchronized.
> 
> Third, I assume there is a desire for swmp to embrace the
> full breadth of 
> virtual worlds implementations.  The paper (and
> subsequent postings) 
> clearly recognize alternative network configurations
> (peer-to-peer, 
> server-based, and hybrid) as an issue.  The paper is less
> clear on its 
> position regarding varying approaches to where certain
> virtual worlds 
> semantics, e.g., physics, collision detection, etc., will
> occur, i.e., 
> centrally or peripherally.  I do not fault the paper for
> that, I just want 
> to point out that this is a major differentiator among
> existing 
> implementations and, if possible, we want to support
> many, if not all, 
> alternatives.
> 
> Fourth, I assume that swamp supports packing multiple
> messages onto a 
> single udp packet.  Without that I am having a little
> trouble 
> understanding the obsession with keeping messages short
> (as evidenced by 
> the setf method.).
> 
> Fifth, I assume that the purpose of swamp is for
> communicating state that 
> is dynamic (ie, changing due to interactions with the
> virtual world) and 
> not for the purpose of moving the static aspects of the
> 3D models.  It is 
> not stated, but I am assuming that terrain, avatars, and
> in-world objects 
> are initially obtained via prior download/install, http,
> or some other 
> query-response protocol.  SWAMP is not for retrieving
> this static 
> information; it is for maintaining the dynamic attributes
> of these models 
> as they change due to being instantiated in a virtual
> world.
> 
> So, here are my questions:
> 
> 1)  Should the base model be more generic with X3D as a
> specific type?
> 
> Many systems starting with Linda and moving through
> JavaSpaces and TSpaces 
> have adopted the attitude that a state sharing system can
> use a very 
> generic notion of how the state is organized.  These
> systems assume the 
> state is in tuples; other systems assume something more
> akin to 
> property-value pairs.  In any case, the base model is
> very generic and not 
> tied to any particular purpose or specialized
> representation.  I wonder 
> whether that would be a better approach for swmp.
> 
> I am not arguing that there is no place for X3D, just
> that we might prefer 
> to treat it as a special case of a more generic state
> representation 
> scheme.  X3D would be less embedded in the PDUs and more
> a conventional 
> and well-defined set of types, fields, values, etc. that
> can be mapped 
> into the generic PDU.  The value of this is that when we
> find some other 
> kind of state that we would like to synchronize, we would
> not be 
> struggling to map it into an X3D-based message structure.
>  Instead, we 
> would map it into tuples or property-value pairs, which
> would certainly be 
> less awkward and might also be more efficient.
> 
> As it stands, the biggest impediment to this approach
> posed by swamp is 
> the rather small number of bits allocated to type
> information (and 
> possibly the fieldID, though I do not fully understand
> its purpose.)
> 
> 2)  Is X3D the right model?
> 
> I am not familiar enough with X3D to have a strong
> position on this.  I am 
> mostly reacting to the idea that (to a first
> approximation) it is a scene 
> graph representation.  That means it is tied to the
> display of the virtual 
> world, which means it is more view than model in the
> model-view-controller 
> (MVC) sense.  Presumably, our primary objective is to
> share the model of 
> the world.
> 
> This is the chain of reasoning that drives my question. 
> In truth, it is 
> more an aesthetic reaction to focusing on sharing views
> than a deep 
> engineering concern.  I am aware that scene graphs often
> have highly 
> abstracted grouping nodes that function like models in
> the MVC sense.  I 
> also know that these high-level nodes have properties
> that can encode the 
> more abstract model state.  In all likelihood, any model
> can be 
> represented using the scene graph and therefore X3D is
> adequate.  But, 
> should designers/developers be compelled to represent
> their models that 
> way.  For example, must a fire be modeled as an X3D
> object or could we 
> treat it as something unseen that causes changes to the
> visible objects 
> based on complex computations?
> 
> Having said all this, I do understand that we must also
> be able to share 
> the view objects.  I also recognize that X3D is a better
> representation of 
> the state of a virtual world than something more abstract
> that I have not 
> yet dreamed up.  Perhaps the best resolution of this
> question is to treat 
> it as a special case of my argument in 1) above. 
> Supporting X3D 
> synchronization is key, but it should not be the only
> form of state that 
> we are prepared to synchronize.
> 
> 3)  Should notifications of changes be distinguished from
> instructions to 
> make a change?
> 
> Most of the time when I have constructed protocols of
> this sort, I have 
> distinguished between messages that indicate a desire to
> change the state 
> and messages that indicate that the state has been
> changed.  SWAMP does 
> not seem to make this distinction.  I assume a set
> message is used both to 
> reflect that a change should be made and that a change
> has been made.  My 
> bias for differentiating these messages derives from
> working on 
> client-server implementations, but I think it is useful
> even in a 
> peer-to-peer situation.  Usually, one node has final say
> on whether a 
> change of state will be permitted.  For the other node, a
> set, add, or 
> remove message is a request.  It cannot count on the
> request being 
> honored.  For the controlling node, a setNotify,
> addNotify, or 
> removeNotify message is definitive.  This is not a
> request of the 
> receiving node; it is informative.
> 
> I find this differentiation of requests for changes vs.
> notifications of 
> changes easier to follow and I would strongly recommend
> that swmp follow 
> this approach.
> 
> 4)  How does swamp support latecomers?
> 
> Presumably one of the values of having a server keep
> track of the state of 
> the virtual world is so that late arriving clients can
> retrieve the 
> current values and get caught up.  This is generally
> referred to as the 
> latecomer problem.  I do not see how a latecomer requests
> the current 
> state of the virtual world using swmp.  I expected to
> find a get or read 
> message that would be followed by a barrage of add
> messages (or better yet 
> addNotify messages.)
> 
> Am I missing something?  Were you planning to use http to
> retrieve this 
> state?  If so, what were you planning to do about race
> conditions between 
> the http request and notifications of changes to the not
> yet received 
> state?
> 
> jfp> _______________________________________________
> SWMP mailing list
> SWMP@ietf.org
> https://www1.ietf.org/mailman/listinfo/swmp
> 




 
____________________________________________________________________________________
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list&sid=396546091

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp



From swmp-bounces@ietf.org Sun Jun 24 13:46:29 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2WAP-000374-Fd; Sun, 24 Jun 2007 13:46:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2WAN-00036a-Ln
	for swmp@ietf.org; Sun, 24 Jun 2007 13:46:27 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2WAM-0001dv-5w
	for swmp@ietf.org; Sun, 24 Jun 2007 13:46:27 -0400
Received: from NEO (adsl-67-113-133-74.dsl.sntc01.pacbell.net [67.113.133.74])
	by william.mediamachines.com (Postfix) with ESMTP
	id 49011464083; Sun, 24 Jun 2007 12:45:23 -0500 (CDT)
From: "Tony Parisi" <tparisi@mediamachines.com>
To: "'Paul Aslin'" <fabricatorgeneral@yahoo.com>, <john_patterson@us.ibm.com>
Subject: RE: [SWMP] Media Machines' initial design and code 
Date: Sun, 24 Jun 2007 10:46:15 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <672580.26268.qm@web90501.mail.mud.yahoo.com>
Thread-Index: Ace2f/pQDmvnu+2mSkOITSCfbp9OjgABnStw
Message-Id: <20070624174523.49011464083@william.mediamachines.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bd8a74b81c71f965ca7918b90d1c49c0
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Errors-To: swmp-bounces@ietf.org

Hi everyone,

> The easiest way to explain how x3d (and vrml) work is a
> simple example.
> 
> DEF Object Transform {
>  translation 0 0 0
>  children [
>  ]
> }
> 
> To set translation to something you'd use javascript like
> this in a Script node(*).
> 
> Object.translation=value;
> 
> This is commonly refered to as object, attribute, value. So
> SWMP needs to support the same data.
> 

Paul, that is an incredibly lucid and concise way to illustrate X3D. Nice
:-)

Yes, SWMP does need to support X3D data types in order to transmit state
changes for an X3D simulation. However, please note that there is nothing
X3D-specific about SWMP. It is X3D-friendly... for sure. The paper we
published for the Web3D Symposium was totally oriented toward X3D because
that was the general topic area of the conference. But SWMP could be used to
transmit messages for other non-X3D simulations as well. At least, that is
the intent.

> Messages may not just be simple values, you can also send
> entire scene graphs or nodes via SWMP.
>

Yes, true, but in general it's not a good idea to do that for a good-sized
chunk of scene graph. For that case it's better to use HTTP to transfer the
data.

That's how Media Machines is designing our applications: HTTP for the data
transfer and SWMP for the dynamic state changes (in both directions). Oh and
XMPP for the chat, etc. Our general philosophy is to use the best protocol
for the specific task, and use existing ones wherever we can. We created
SWMP because there wasn't an existing open protocol to handle MMO-style
scene state changes.

Tony


> 
> (*) or ROUTE from another node
> 
> I'll reply further on this soon.
> 
> --- john_patterson@us.ibm.com wrote:
> 
> > Jay Weber wrote:
> >
> > I'd like to point the group to Media Machines' initial
> > work towards SWMP.
> >
> > We presented an overview paper at the Web3D 2007
> > Symposium, which you can
> > find at
> > http://www.mediamachines.com/hydra/swampweb3d2007.pdf
> >
> > I have now managed to look through the paper and I am
> > ready to ask some
> > questions.
> >
> > First, let me state that I am not especially familiar
> > with X3D.  I have
> > looked quickly at it, but I have not gotten to the depth
> > that the authors
> > have.  It is possible that some of my questions are best
> > answered by
> > referring me back to X3D.
> >
> > Second, I understand the swamp protocol (I use the name
> > from the paper.)
> > to be a peer-to-peer state replication protocol.  By
> > peer-to-peer, I do
> > not mean that it is useless for a server-based approach,
> > but that it only
> > addresses communication between two network nodes and
> > this communication
> > is completely symmetric; there is no assumption about
> > either node having a
> > different role from the other.  By state replication, I
> > mean that both
> > nodes maintain a copy of the state (at least the
> > relevant, e.g.,
> > dynamically changing, state) and the protocol is used to
> > keep these copies
> > synchronized.
> >
> > Third, I assume there is a desire for swmp to embrace the
> > full breadth of
> > virtual worlds implementations.  The paper (and
> > subsequent postings)
> > clearly recognize alternative network configurations
> > (peer-to-peer,
> > server-based, and hybrid) as an issue.  The paper is less
> > clear on its
> > position regarding varying approaches to where certain
> > virtual worlds
> > semantics, e.g., physics, collision detection, etc., will
> > occur, i.e.,
> > centrally or peripherally.  I do not fault the paper for
> > that, I just want
> > to point out that this is a major differentiator among
> > existing
> > implementations and, if possible, we want to support
> > many, if not all,
> > alternatives.
> >
> > Fourth, I assume that swamp supports packing multiple
> > messages onto a
> > single udp packet.  Without that I am having a little
> > trouble
> > understanding the obsession with keeping messages short
> > (as evidenced by
> > the setf method.).
> >
> > Fifth, I assume that the purpose of swamp is for
> > communicating state that
> > is dynamic (ie, changing due to interactions with the
> > virtual world) and
> > not for the purpose of moving the static aspects of the
> > 3D models.  It is
> > not stated, but I am assuming that terrain, avatars, and
> > in-world objects
> > are initially obtained via prior download/install, http,
> > or some other
> > query-response protocol.  SWAMP is not for retrieving
> > this static
> > information; it is for maintaining the dynamic attributes
> > of these models
> > as they change due to being instantiated in a virtual
> > world.
> >
> > So, here are my questions:
> >
> > 1)  Should the base model be more generic with X3D as a
> > specific type?
> >
> > Many systems starting with Linda and moving through
> > JavaSpaces and TSpaces
> > have adopted the attitude that a state sharing system can
> > use a very
> > generic notion of how the state is organized.  These
> > systems assume the
> > state is in tuples; other systems assume something more
> > akin to
> > property-value pairs.  In any case, the base model is
> > very generic and not
> > tied to any particular purpose or specialized
> > representation.  I wonder
> > whether that would be a better approach for swmp.
> >
> > I am not arguing that there is no place for X3D, just
> > that we might prefer
> > to treat it as a special case of a more generic state
> > representation
> > scheme.  X3D would be less embedded in the PDUs and more
> > a conventional
> > and well-defined set of types, fields, values, etc. that
> > can be mapped
> > into the generic PDU.  The value of this is that when we
> > find some other
> > kind of state that we would like to synchronize, we would
> > not be
> > struggling to map it into an X3D-based message structure.
> >  Instead, we
> > would map it into tuples or property-value pairs, which
> > would certainly be
> > less awkward and might also be more efficient.
> >
> > As it stands, the biggest impediment to this approach
> > posed by swamp is
> > the rather small number of bits allocated to type
> > information (and
> > possibly the fieldID, though I do not fully understand
> > its purpose.)
> >
> > 2)  Is X3D the right model?
> >
> > I am not familiar enough with X3D to have a strong
> > position on this.  I am
> > mostly reacting to the idea that (to a first
> > approximation) it is a scene
> > graph representation.  That means it is tied to the
> > display of the virtual
> > world, which means it is more view than model in the
> > model-view-controller
> > (MVC) sense.  Presumably, our primary objective is to
> > share the model of
> > the world.
> >
> > This is the chain of reasoning that drives my question.
> > In truth, it is
> > more an aesthetic reaction to focusing on sharing views
> > than a deep
> > engineering concern.  I am aware that scene graphs often
> > have highly
> > abstracted grouping nodes that function like models in
> > the MVC sense.  I
> > also know that these high-level nodes have properties
> > that can encode the
> > more abstract model state.  In all likelihood, any model
> > can be
> > represented using the scene graph and therefore X3D is
> > adequate.  But,
> > should designers/developers be compelled to represent
> > their models that
> > way.  For example, must a fire be modeled as an X3D
> > object or could we
> > treat it as something unseen that causes changes to the
> > visible objects
> > based on complex computations?
> >
> > Having said all this, I do understand that we must also
> > be able to share
> > the view objects.  I also recognize that X3D is a better
> > representation of
> > the state of a virtual world than something more abstract
> > that I have not
> > yet dreamed up.  Perhaps the best resolution of this
> > question is to treat
> > it as a special case of my argument in 1) above.
> > Supporting X3D
> > synchronization is key, but it should not be the only
> > form of state that
> > we are prepared to synchronize.
> >
> > 3)  Should notifications of changes be distinguished from
> > instructions to
> > make a change?
> >
> > Most of the time when I have constructed protocols of
> > this sort, I have
> > distinguished between messages that indicate a desire to
> > change the state
> > and messages that indicate that the state has been
> > changed.  SWAMP does
> > not seem to make this distinction.  I assume a set
> > message is used both to
> > reflect that a change should be made and that a change
> > has been made.  My
> > bias for differentiating these messages derives from
> > working on
> > client-server implementations, but I think it is useful
> > even in a
> > peer-to-peer situation.  Usually, one node has final say
> > on whether a
> > change of state will be permitted.  For the other node, a
> > set, add, or
> > remove message is a request.  It cannot count on the
> > request being
> > honored.  For the controlling node, a setNotify,
> > addNotify, or
> > removeNotify message is definitive.  This is not a
> > request of the
> > receiving node; it is informative.
> >
> > I find this differentiation of requests for changes vs.
> > notifications of
> > changes easier to follow and I would strongly recommend
> > that swmp follow
> > this approach.
> >
> > 4)  How does swamp support latecomers?
> >
> > Presumably one of the values of having a server keep
> > track of the state of
> > the virtual world is so that late arriving clients can
> > retrieve the
> > current values and get caught up.  This is generally
> > referred to as the
> > latecomer problem.  I do not see how a latecomer requests
> > the current
> > state of the virtual world using swmp.  I expected to
> > find a get or read
> > message that would be followed by a barrage of add
> > messages (or better yet
> > addNotify messages.)
> >
> > Am I missing something?  Were you planning to use http to
> > retrieve this
> > state?  If so, what were you planning to do about race
> > conditions between
> > the http request and notifications of changes to the not
> > yet received
> > state?
> >
> > jfp> _______________________________________________
> > SWMP mailing list
> > SWMP@ietf.org
> > https://www1.ietf.org/mailman/listinfo/swmp
> >
> 
> 
> 
> 
> 
> __________________________________________________________________________
> __________
> Need Mail bonding?
> Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
> http://answers.yahoo.com/dir/?link=list&sid=396546091
> 
> _______________________________________________
> SWMP mailing list
> SWMP@ietf.org
> https://www1.ietf.org/mailman/listinfo/swmp




_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp



From swmp-bounces@ietf.org Mon Jun 25 15:30:45 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2uGr-0000hr-5P; Mon, 25 Jun 2007 15:30:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2uGo-0000Ls-Rp
	for swmp@ietf.org; Mon, 25 Jun 2007 15:30:42 -0400
Received: from mxi.ltu.se ([130.240.42.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2uGn-0000EI-DK
	for swmp@ietf.org; Mon, 25 Jun 2007 15:30:42 -0400
Received: from EMMA.personal.adp.ltu.se (rachel.personal.adp.ltu.se
	[130.240.150.5])
	by mxi.ltu.se (8.13.1/8.13.1) with ESMTP id l5PIUiWx004288
	for <swmp@ietf.org>; Mon, 25 Jun 2007 20:30:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [SWMP] Media Machines' initial design and code
Date: Mon, 25 Jun 2007 21:28:25 +0200
Message-ID: <668D1B8AD729C94DB91D17EC19B8BB9104E84C2D@EMMA.personal.adp.ltu.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [SWMP] Media Machines' initial design and code
Thread-Index: Ace2f/pQDmvnu+2mSkOITSCfbp9OjgABnStwADYkPHg=
References: <20070624174523.49011464083@william.mediamachines.com>
From: "Sven-Erik Tiberg" <Sven-Erik.Tiberg@ltu.se>
To: <swmp@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1991826802=="
Errors-To: swmp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1991826802==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B75F.500B9D45"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B75F.500B9D45
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi.

Presently setting up a linux mashine to handle Flux server. As I'm =
targeting low-bandwith (>=3D8Mbits) distributed simulations for =
driversimulator, are there any settings to restrict the shortest time =
between package sending over SWMP?

BG

Sven-Erik Tiberg

Lulea Univ. of Technology / sweden


------_=_NextPart_001_01C7B75F.500B9D45
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: [SWMP] Media Machines' initial design =
and code</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<P>Hi.</P>=0A=
<P>Presently setting up a linux mashine to handle Flux server. As I'm =
targeting low-bandwith (&gt;=3D8Mbits)&nbsp;distributed simulations for =
driversimulator, are there any settings to restrict the shortest time =
between package sending over SWMP?</P>=0A=
<P>BG</P>=0A=
<P>Sven-Erik Tiberg</P>=0A=
<P>Lulea Univ. of Technology / sweden</P></BODY></HTML>
------_=_NextPart_001_01C7B75F.500B9D45--


--===============1991826802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============1991826802==--




From swmp-bounces@ietf.org Mon Jun 25 16:51:31 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2vX1-0003q3-B4; Mon, 25 Jun 2007 16:51:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2vX0-0003px-3E
	for swmp@ietf.org; Mon, 25 Jun 2007 16:51:30 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2vWz-0003pP-Mr
	for swmp@ietf.org; Mon, 25 Jun 2007 16:51:30 -0400
Received: from [192.168.2.119] (h-66-166-236-26.snvacaid.covad.net
	[66.166.236.26]) by william.mediamachines.com (Postfix) with ESMTP
	id BC311464003; Mon, 25 Jun 2007 15:50:26 -0500 (CDT)
Message-ID: <46802ACC.1090109@mediamachines.com>
Date: Mon, 25 Jun 2007 13:51:24 -0700
From: "Jay C. Weber" <jweber@mediamachines.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: john_patterson@us.ibm.com
Subject: Re: [SWMP] Media Machines' initial design and code
References: <OF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com>
In-Reply-To: <OF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com>
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0676660931=="
Errors-To: swmp-bounces@ietf.org

--===============0676660931==
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:john_patterson@us.ibm.com">john_patterson@us.ibm.com</a> wrote:
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2">I have now managed to
look through the
paper and I am ready to ask some questions.</font>
  <br>
</blockquote>
Hi John, sorry for the delay, I had a little holiday last week.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2">Second, I understand the
swamp protocol
(I use the name from the paper.) to be a peer-to-peer state replication
protocol. By peer-to-peer, I do not mean that it is useless for a
server-based approach, but that it only addresses communication between
two network nodes and this communication is completely symmetric; there
is no assumption about either node having a different role from the
other.
&nbsp;By state replication, I mean that both nodes maintain a copy of the
state (at least the relevant, e.g., dynamically changing, state) and
the
protocol is used to keep these copies synchronized.</font>
  <br>
</blockquote>
Yes, it is intentionally independent of the architecture, so it can be
used with peer-peer, client-server, peer-server, and other
architectural variations.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2">Third, I assume there is
a desire for
swmp to embrace the full breadth of virtual worlds implementations.
&nbsp;The
paper (and subsequent postings) clearly recognize alternative network
configurations
(peer-to-peer, server-based, and hybrid) as an issue. &nbsp;The paper is
less clear on its position regarding varying approaches to where
certain
virtual worlds semantics, e.g., physics, collision detection, etc.,
will
occur, i.e., centrally or peripherally. &nbsp;I do not fault the paper
for that, I just want to point out that this is a major differentiator
among existing implementations and, if possible, we want to support
many,
if not all, alternatives.</font>
  <br>
</blockquote>
Yes; overall our work encompasses system architectures and virtual
world semantics (and X3D provides some of this), but that paper focuses
on the sub-problem of a protocol for communicating world-state changes.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2">Fourth, I assume that
swamp supports
packing multiple messages onto a single udp packet. &nbsp;Without that
I am having a little trouble understanding the obsession with keeping
messages
short (as evidenced by the setf method.).</font></blockquote>
Absolutely, minimizing individual message size allows the system to
optimize packet sizes and/or message buffering for bandwidth
utilization.&nbsp; The message enveloping in the paper doesn't include this,
nor does the reference implementation, yet.&nbsp; I think the implementation
should do the buffering automatically, perhaps with a time-to-wait
parameter so the application can tune the buffering to trade off
bandwidth and latency.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2">Fifth, I assume that the
purpose of
swamp is for communicating state that is dynamic (ie, changing due to
interactions
with the virtual world) and not for the purpose of moving the static
aspects
of the 3D models. &nbsp;It is not stated, but I am assuming that terrain,
avatars, and in-world objects are initially obtained via prior
download/install,
http, or some other query-response protocol. &nbsp;SWAMP is not for
retrieving
this static information; it is for maintaining the dynamic attributes
of
these models as they change due to being instantiated in a virtual
world.</font>
  <br>
</blockquote>
Right.&nbsp; When we use it with X3D, the static "base scene" is retrieved
via HTTP and loaded, and then the SWMP session starts up to manage the
dynamic aspects.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2"></font><font
 face="sans-serif" size="2">1) &nbsp;Should the base model be more
generic with X3D as a specific type?</font>
  <br>
  <br>
  <font face="sans-serif" size="2">Many systems starting with Linda and
moving through JavaSpaces and TSpaces have adopted the attitude that a
state sharing system can use a very generic notion of how the state is
organized. &nbsp;These systems assume the state is in tuples; other systems
assume something more akin to property-value pairs. &nbsp;In any case,
the base model is very generic and not tied to any particular purpose
or
specialized representation. &nbsp;I wonder whether that would be a better
approach for swmp.</font>
  <br>
</blockquote>
Agreed that state descriptions should be as generic as possible.&nbsp; Our
SWMP is already an Object-Property-Value triple, except that we use the
X3D terms (which are also used elsewhere) of Node-Field-Value.<br>
<br>
But, as you noted, where this gets X3D-specific is with the types of
the values.&nbsp; Though I do not know of another open-standard enumeration
of the types one needs for communicating the values one needs for 3D
scenes, so it may be that the X3D enumeration is the best choice, given
that we need some standardized enumeration.&nbsp; Note that X3D's types are
based on other standards, like IEEE floats, and our SWMP also uses the
standard IETF Network Byte Order.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2">2) &nbsp;Is X3D the right
model?</font>
  <br>
  <br>
  <font face="sans-serif" size="2">I am not familiar enough with X3D to
have a strong position on this. &nbsp;I am mostly reacting to the idea
that (to a first approximation) it is a scene graph representation.
&nbsp;That
means it is tied to the display of the virtual world, which means it is
more view than model in the model-view-controller (MVC) sense.
&nbsp;Presumably,
our primary objective is to share the model of the world.</font><br>
</blockquote>
I think the X3D is more model than view, in the MVC sense.&nbsp; And a
scene-graph model is prevalent enough that it is a reasonable choice
for the model.<br>
<br>
Of course a key advantage that X3D has over other scene-graph models,
is that it is a mature International Standard.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><br>
  <font face="sans-serif" size="2">3) &nbsp;Should notifications of changes
be distinguished from instructions to make a change?</font>
  <br>
  <br>
  <font face="sans-serif" size="2">Most of the time when I have
constructed
protocols of this sort, I have distinguished between messages that
indicate
a desire to change the state and messages that indicate that the state
has been changed. &nbsp;SWAMP does not seem to make this distinction. &nbsp;I
assume a set message is used both to reflect that a change should be
made
and that a change has been made. &nbsp;My bias for differentiating these
messages derives from working on client-server implementations, but I
think
it is useful even in a peer-to-peer situation. &nbsp;Usually, one node
has final say on whether a change of state will be permitted.</font><br>
</blockquote>
Very interesting issue, I left the change vs. notify semantics (and
implemented it) as the semantics of the particular architecture but I
can see some advantage to making this explicit through separate
messages.<br>
<blockquote
 cite="midOF41A27D35.842CC4AF-ON85257300.007D3706-85257302.006C8601@lotus.com"
 type="cite"><font face="sans-serif" size="2">4) &nbsp;How does swamp
support latecomers?</font>
  <br>
  <br>
  <font face="sans-serif" size="2">Presumably one of the values of
having
a server keep track of the state of the virtual world is so that late
arriving
clients can retrieve the current values and get caught up. &nbsp;This is
generally referred to as the latecomer problem. &nbsp;I do not see how
a latecomer requests the current state of the virtual world using swmp.</font></blockquote>
That (who updates latecomers) is also in the architecture, and
implemented in the current code base as the server updating latecomer
clients.<br>
<br>
<br>
jay<br>
<br>
</body>
</html>


--===============0676660931==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============0676660931==--



From swmp-bounces@ietf.org Mon Jun 25 17:21:50 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2w0M-0007uM-K1; Mon, 25 Jun 2007 17:21:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2w0L-0007u8-91
	for swmp@ietf.org; Mon, 25 Jun 2007 17:21:49 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2w0K-0000rX-2H
	for swmp@ietf.org; Mon, 25 Jun 2007 17:21:49 -0400
Received: from [192.168.2.119] (h-66-166-236-26.snvacaid.covad.net
	[66.166.236.26]) by william.mediamachines.com (Postfix) with ESMTP
	id D2F0E46400B; Mon, 25 Jun 2007 16:20:45 -0500 (CDT)
Message-ID: <468031EB.5010109@mediamachines.com>
Date: Mon, 25 Jun 2007 14:21:47 -0700
From: "Jay C. Weber" <jweber@mediamachines.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Sven-Erik Tiberg <Sven-Erik.Tiberg@ltu.se>
Subject: Re: [SWMP] Media Machines' initial design and code
References: <20070624174523.49011464083@william.mediamachines.com>
	<668D1B8AD729C94DB91D17EC19B8BB9104E84C2D@EMMA.personal.adp.ltu.se>
In-Reply-To: <668D1B8AD729C94DB91D17EC19B8BB9104E84C2D@EMMA.personal.adp.ltu.se>
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1976509417=="
Errors-To: swmp-bounces@ietf.org

--===============1976509417==
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sven-Erik Tiberg wrote:
<blockquote
 cite="mid668D1B8AD729C94DB91D17EC19B8BB9104E84C2D@EMMA.personal.adp.ltu.se"
 type="cite">
  <title>RE: [SWMP] Media Machines' initial design and code</title>
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta content="MSHTML 6.00.6000.16481" name="GENERATOR">
  <p>Presently setting up a linux mashine to handle Flux server. As I'm
targeting low-bandwith (&gt;=8Mbits)&nbsp;distributed simulations for
driversimulator, are there any settings to restrict the shortest time
between package sending over SWMP?</p>
</blockquote>
not via the SWMP API, but you can tweak the way the API calls into the
HawkNL network library.&nbsp; HawkNL has a call nlSetSocketOpt which,
unfortunately, is not well-documented (the docs at
<a class="moz-txt-link-freetext" href="http://www.hawksoft.com/hawknl/docs/index.html">http://www.hawksoft.com/hawknl/docs/index.html</a>) are a version behind)
but you can look at the code.<br>
<br>
jay<br>
<br>
</body>
</html>


--===============1976509417==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============1976509417==--



From swmp-bounces@ietf.org Tue Jun 26 13:20:33 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3EiO-0006Tp-JD; Tue, 26 Jun 2007 13:20:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3EVi-0002si-FK
	for swmp@ietf.org; Tue, 26 Jun 2007 13:07:26 -0400
Received: from e31.co.us.ibm.com ([32.97.110.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3EV9-0001J5-OZ
	for swmp@ietf.org; Tue, 26 Jun 2007 13:07:26 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com
	[9.17.195.227])
	by e31.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5QH6nS0030226
	for <swmp@ietf.org>; Tue, 26 Jun 2007 13:06:49 -0400
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5QH6jAF240888 for <swmp@ietf.org>; Tue, 26 Jun 2007 11:06:46 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5QH6iTh024921 for <swmp@ietf.org>; Tue, 26 Jun 2007 11:06:45 -0600
Received: from internet1.lotus.com (internet1.lotus.com [9.33.9.11])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5QH6hEU024781
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 26 Jun 2007 11:06:44 -0600
Received: from wtfmail02.edc.lotus.com (wtfmail02.lotus.com [9.33.9.69])
	by internet1.lotus.com (8.14.1/8.14.1) with ESMTP id l5QH6hDc015499;
	Tue, 26 Jun 2007 13:06:43 -0400 (EDT)
In-Reply-To: <46802ACC.1090109@mediamachines.com>
To: "Jay C. Weber" <jweber@mediamachines.com>
Subject: Re: [SWMP] Media Machines' initial design and code
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
Message-ID: <OF9311E6B3.E102E931-ON85257306.005BE41A-85257306.005DFDB9@lotus.com>
From: john_patterson@us.ibm.com
Date: Tue, 26 Jun 2007 13:07:17 -0400
X-MIMETrack: Serialize by Router on WTFMAIL02/WTF/M/Lotus(Release
	7.0.2FP2|April 16, 2007) at 06/26/2007 01:07:18 PM,
	Serialize complete at 06/26/2007 01:07:18 PM
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 75ac735ede4d089f7192d230671d536e
X-Mailman-Approved-At: Tue, 26 Jun 2007 13:20:30 -0400
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0684308076=="
Errors-To: swmp-bounces@ietf.org

This is a multipart message in MIME format.
--===============0684308076==
Content-Type: multipart/alternative;
	boundary="=_alternative 005DFDB685257306_="

This is a multipart message in MIME format.
--=_alternative 005DFDB685257306_=
Content-Type: text/plain; charset="US-ASCII"

Jay:

Thanks for the response.

It looks like I got the situation mostly right.  Here are some residual 
reactions resulting from your reply:

1)  I am OK with Node-Field-Value as a generic representation of state. It 
is not much different from Object-Property-Value, except I assume the node 
naming implies a hierarchical relationship.  I do think we will need a 
richer representation for type.  To be fully general, I question whether 
enumerated types is the way to go (as opposed to Mime types.)  Doesn't 
enumeration require one to know all possible types prior to defining the 
values.  We can't do that and be flexible for unanticipated uses of swmp.

One approach might be to define a notion of a type scheme and then use an 
enumeration within that scheme.  Thus, some more string-like value would 
indicate that these are X3D types and then a second field could indicate 
the enumerated types for that scheme.

2)  So long as X3D is a special case of a more generic state sharing 
technique, I am happy.  It is probably not worth the trouble to debate 
whether X3D is more model or view.  (It is in the nature of virtual worlds 
that the model is view-like.)  I'm just pretty sure that we will encounter 
situations when the state of something other than an X3D node needs to 
conveyed.

3)  I am glad that you see the value of a set vs setNotify message.  I 
didn't think of it before, but we are probably ready to talk about why 
there isn't any subscritpion message in the swamp protocol (and whether 
there should be one in swmp.)

4)  It sounds like you are saying that latecomer support is in your code 
even though it is not obvious how to do it based on the paper.  Does that 
mean there is a get request in your implemented protocol?

jfp



"Jay C. Weber" <jweber@mediamachines.com> 
06/25/2007 04:51 PM

To
john_patterson@us.ibm.com
cc
swmp@ietf.org
Subject
Re: [SWMP] Media Machines' initial design and code






john_patterson@us.ibm.com wrote: 
I have now managed to look through the paper and I am ready to ask some 
questions. 
Hi John, sorry for the delay, I had a little holiday last week.
Second, I understand the swamp protocol (I use the name from the paper.) 
to be a peer-to-peer state replication protocol. By peer-to-peer, I do not 
mean that it is useless for a server-based approach, but that it only 
addresses communication between two network nodes and this communication 
is completely symmetric; there is no assumption about either node having a 
different role from the other.  By state replication, I mean that both 
nodes maintain a copy of the state (at least the relevant, e.g., 
dynamically changing, state) and the protocol is used to keep these copies 
synchronized. 
Yes, it is intentionally independent of the architecture, so it can be 
used with peer-peer, client-server, peer-server, and other architectural 
variations.
Third, I assume there is a desire for swmp to embrace the full breadth of 
virtual worlds implementations.  The paper (and subsequent postings) 
clearly recognize alternative network configurations (peer-to-peer, 
server-based, and hybrid) as an issue.  The paper is less clear on its 
position regarding varying approaches to where certain virtual worlds 
semantics, e.g., physics, collision detection, etc., will occur, i.e., 
centrally or peripherally.  I do not fault the paper for that, I just want 
to point out that this is a major differentiator among existing 
implementations and, if possible, we want to support many, if not all, 
alternatives. 
Yes; overall our work encompasses system architectures and virtual world 
semantics (and X3D provides some of this), but that paper focuses on the 
sub-problem of a protocol for communicating world-state changes.
Fourth, I assume that swamp supports packing multiple messages onto a 
single udp packet.  Without that I am having a little trouble 
understanding the obsession with keeping messages short (as evidenced by 
the setf method.).
Absolutely, minimizing individual message size allows the system to 
optimize packet sizes and/or message buffering for bandwidth utilization. 
The message enveloping in the paper doesn't include this, nor does the 
reference implementation, yet.  I think the implementation should do the 
buffering automatically, perhaps with a time-to-wait parameter so the 
application can tune the buffering to trade off bandwidth and latency.
Fifth, I assume that the purpose of swamp is for communicating state that 
is dynamic (ie, changing due to interactions with the virtual world) and 
not for the purpose of moving the static aspects of the 3D models.  It is 
not stated, but I am assuming that terrain, avatars, and in-world objects 
are initially obtained via prior download/install, http, or some other 
query-response protocol.  SWAMP is not for retrieving this static 
information; it is for maintaining the dynamic attributes of these models 
as they change due to being instantiated in a virtual world. 
Right.  When we use it with X3D, the static "base scene" is retrieved via 
HTTP and loaded, and then the SWMP session starts up to manage the dynamic 
aspects.
1)  Should the base model be more generic with X3D as a specific type? 

Many systems starting with Linda and moving through JavaSpaces and TSpaces 
have adopted the attitude that a state sharing system can use a very 
generic notion of how the state is organized.  These systems assume the 
state is in tuples; other systems assume something more akin to 
property-value pairs.  In any case, the base model is very generic and not 
tied to any particular purpose or specialized representation.  I wonder 
whether that would be a better approach for swmp. 
Agreed that state descriptions should be as generic as possible.  Our SWMP 
is already an Object-Property-Value triple, except that we use the X3D 
terms (which are also used elsewhere) of Node-Field-Value.

But, as you noted, where this gets X3D-specific is with the types of the 
values.  Though I do not know of another open-standard enumeration of the 
types one needs for communicating the values one needs for 3D scenes, so 
it may be that the X3D enumeration is the best choice, given that we need 
some standardized enumeration.  Note that X3D's types are based on other 
standards, like IEEE floats, and our SWMP also uses the standard IETF 
Network Byte Order.
2)  Is X3D the right model? 

I am not familiar enough with X3D to have a strong position on this.  I am 
mostly reacting to the idea that (to a first approximation) it is a scene 
graph representation.  That means it is tied to the display of the virtual 
world, which means it is more view than model in the model-view-controller 
(MVC) sense.  Presumably, our primary objective is to share the model of 
the world.
I think the X3D is more model than view, in the MVC sense.  And a 
scene-graph model is prevalent enough that it is a reasonable choice for 
the model.

Of course a key advantage that X3D has over other scene-graph models, is 
that it is a mature International Standard.

3)  Should notifications of changes be distinguished from instructions to 
make a change? 

Most of the time when I have constructed protocols of this sort, I have 
distinguished between messages that indicate a desire to change the state 
and messages that indicate that the state has been changed.  SWAMP does 
not seem to make this distinction.  I assume a set message is used both to 
reflect that a change should be made and that a change has been made.  My 
bias for differentiating these messages derives from working on 
client-server implementations, but I think it is useful even in a 
peer-to-peer situation.  Usually, one node has final say on whether a 
change of state will be permitted.
Very interesting issue, I left the change vs. notify semantics (and 
implemented it) as the semantics of the particular architecture but I can 
see some advantage to making this explicit through separate messages.
4)  How does swamp support latecomers? 

Presumably one of the values of having a server keep track of the state of 
the virtual world is so that late arriving clients can retrieve the 
current values and get caught up.  This is generally referred to as the 
latecomer problem.  I do not see how a latecomer requests the current 
state of the virtual world using swmp.
That (who updates latecomers) is also in the architecture, and implemented 
in the current code base as the server updating latecomer clients.


jay


--=_alternative 005DFDB685257306_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Jay:</font>
<br>
<br><font size=2 face="sans-serif">Thanks for the response.</font>
<br>
<br><font size=2 face="sans-serif">It looks like I got the situation mostly
right. &nbsp;Here are some residual reactions resulting from your reply:</font>
<br>
<br><font size=2 face="sans-serif">1) &nbsp;I am OK with Node-Field-Value
as a generic representation of state. &nbsp;It is not much different from
Object-Property-Value, except I assume the node naming implies a hierarchical
relationship. &nbsp;I do think we will need a richer representation for
type. &nbsp;To be fully general, I question whether enumerated types is
the way to go (as opposed to Mime types.) &nbsp;Doesn't enumeration require
one to know all possible types prior to defining the values. &nbsp;We can't
do that and be flexible for unanticipated uses of swmp.</font>
<br>
<br><font size=2 face="sans-serif">One approach might be to define a notion
of a type scheme and then use an enumeration within that scheme. &nbsp;Thus,
some more string-like value would indicate that these are X3D types and
then a second field could indicate the enumerated types for that scheme.</font>
<br>
<br><font size=2 face="sans-serif">2) &nbsp;So long as X3D is a special
case of a more generic state sharing technique, I am happy. &nbsp;It is
probably not worth the trouble to debate whether X3D is more model or view.
&nbsp;(It is in the nature of virtual worlds that the model is view-like.)
&nbsp;I'm just pretty sure that we will encounter situations when the state
of something other than an X3D node needs to conveyed.</font>
<br>
<br><font size=2 face="sans-serif">3) &nbsp;I am glad that you see the
value of a set vs setNotify message. &nbsp;I didn't think of it before,
but we are probably ready to talk about why there isn't any subscritpion
message in the swamp protocol (and whether there should be one in swmp.)</font>
<br>
<br><font size=2 face="sans-serif">4) &nbsp;It sounds like you are saying
that latecomer support is in your code even though it is not obvious how
to do it based on the paper. &nbsp;Does that mean there is a get request
in your implemented protocol?</font>
<br>
<br><font size=2 face="sans-serif">jfp</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Jay C. Weber&quot;
&lt;jweber@mediamachines.com&gt;</b> </font>
<p><font size=1 face="sans-serif">06/25/2007 04:51 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">john_patterson@us.ibm.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">swmp@ietf.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [SWMP] Media Machines' initial design
and code</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><a href=mailto:john_patterson@us.ibm.com><font size=3 color=blue><u>john_patterson@us.ibm.com</u></font></a><font size=3>
wrote: </font>
<br><font size=2 face="sans-serif">I have now managed to look through the
paper and I am ready to ask some questions.</font><font size=3> </font>
<br><font size=3>Hi John, sorry for the delay, I had a little holiday last
week.</font>
<br><font size=2 face="sans-serif">Second, I understand the swamp protocol
(I use the name from the paper.) to be a peer-to-peer state replication
protocol. By peer-to-peer, I do not mean that it is useless for a server-based
approach, but that it only addresses communication between two network
nodes and this communication is completely symmetric; there is no assumption
about either node having a different role from the other. &nbsp;By state
replication, I mean that both nodes maintain a copy of the state (at least
the relevant, e.g., dynamically changing, state) and the protocol is used
to keep these copies synchronized.</font><font size=3> </font>
<br><font size=3>Yes, it is intentionally independent of the architecture,
so it can be used with peer-peer, client-server, peer-server, and other
architectural variations.</font>
<br><font size=2 face="sans-serif">Third, I assume there is a desire for
swmp to embrace the full breadth of virtual worlds implementations. &nbsp;The
paper (and subsequent postings) clearly recognize alternative network configurations
(peer-to-peer, server-based, and hybrid) as an issue. &nbsp;The paper is
less clear on its position regarding varying approaches to where certain
virtual worlds semantics, e.g., physics, collision detection, etc., will
occur, i.e., centrally or peripherally. &nbsp;I do not fault the paper
for that, I just want to point out that this is a major differentiator
among existing implementations and, if possible, we want to support many,
if not all, alternatives.</font><font size=3> </font>
<br><font size=3>Yes; overall our work encompasses system architectures
and virtual world semantics (and X3D provides some of this), but that paper
focuses on the sub-problem of a protocol for communicating world-state
changes.</font>
<br><font size=2 face="sans-serif">Fourth, I assume that swamp supports
packing multiple messages onto a single udp packet. &nbsp;Without that
I am having a little trouble understanding the obsession with keeping messages
short (as evidenced by the setf method.).</font>
<br><font size=3>Absolutely, minimizing individual message size allows
the system to optimize packet sizes and/or message buffering for bandwidth
utilization. &nbsp;The message enveloping in the paper doesn't include
this, nor does the reference implementation, yet. &nbsp;I think the implementation
should do the buffering automatically, perhaps with a time-to-wait parameter
so the application can tune the buffering to trade off bandwidth and latency.</font>
<br><font size=2 face="sans-serif">Fifth, I assume that the purpose of
swamp is for communicating state that is dynamic (ie, changing due to interactions
with the virtual world) and not for the purpose of moving the static aspects
of the 3D models. &nbsp;It is not stated, but I am assuming that terrain,
avatars, and in-world objects are initially obtained via prior download/install,
http, or some other query-response protocol. &nbsp;SWAMP is not for retrieving
this static information; it is for maintaining the dynamic attributes of
these models as they change due to being instantiated in a virtual world.</font><font size=3>
</font>
<br><font size=3>Right. &nbsp;When we use it with X3D, the static &quot;base
scene&quot; is retrieved via HTTP and loaded, and then the SWMP session
starts up to manage the dynamic aspects.</font>
<br><font size=2 face="sans-serif">1) &nbsp;Should the base model be more
generic with X3D as a specific type?</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Many systems starting with Linda and moving through JavaSpaces and TSpaces
have adopted the attitude that a state sharing system can use a very generic
notion of how the state is organized. &nbsp;These systems assume the state
is in tuples; other systems assume something more akin to property-value
pairs. &nbsp;In any case, the base model is very generic and not tied to
any particular purpose or specialized representation. &nbsp;I wonder whether
that would be a better approach for swmp.</font><font size=3> </font>
<br><font size=3>Agreed that state descriptions should be as generic as
possible. &nbsp;Our SWMP is already an Object-Property-Value triple, except
that we use the X3D terms (which are also used elsewhere) of Node-Field-Value.<br>
<br>
But, as you noted, where this gets X3D-specific is with the types of the
values. &nbsp;Though I do not know of another open-standard enumeration
of the types one needs for communicating the values one needs for 3D scenes,
so it may be that the X3D enumeration is the best choice, given that we
need some standardized enumeration. &nbsp;Note that X3D's types are based
on other standards, like IEEE floats, and our SWMP also uses the standard
IETF Network Byte Order.</font>
<br><font size=2 face="sans-serif">2) &nbsp;Is X3D the right model?</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
I am not familiar enough with X3D to have a strong position on this. &nbsp;I
am mostly reacting to the idea that (to a first approximation) it is a
scene graph representation. &nbsp;That means it is tied to the display
of the virtual world, which means it is more view than model in the model-view-controller
(MVC) sense. &nbsp;Presumably, our primary objective is to share the model
of the world.</font>
<br><font size=3>I think the X3D is more model than view, in the MVC sense.
&nbsp;And a scene-graph model is prevalent enough that it is a reasonable
choice for the model.<br>
<br>
Of course a key advantage that X3D has over other scene-graph models, is
that it is a mature International Standard.</font>
<br><font size=2 face="sans-serif"><br>
3) &nbsp;Should notifications of changes be distinguished from instructions
to make a change?</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Most of the time when I have constructed protocols of this sort, I have
distinguished between messages that indicate a desire to change the state
and messages that indicate that the state has been changed. &nbsp;SWAMP
does not seem to make this distinction. &nbsp;I assume a set message is
used both to reflect that a change should be made and that a change has
been made. &nbsp;My bias for differentiating these messages derives from
working on client-server implementations, but I think it is useful even
in a peer-to-peer situation. &nbsp;Usually, one node has final say on whether
a change of state will be permitted.</font>
<br><font size=3>Very interesting issue, I left the change vs. notify semantics
(and implemented it) as the semantics of the particular architecture but
I can see some advantage to making this explicit through separate messages.</font>
<br><font size=2 face="sans-serif">4) &nbsp;How does swamp support latecomers?</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
Presumably one of the values of having a server keep track of the state
of the virtual world is so that late arriving clients can retrieve the
current values and get caught up. &nbsp;This is generally referred to as
the latecomer problem. &nbsp;I do not see how a latecomer requests the
current state of the virtual world using swmp.</font>
<br><font size=3>That (who updates latecomers) is also in the architecture,
and implemented in the current code base as the server updating latecomer
clients.<br>
<br>
<br>
jay<br>
</font>
<br>
--=_alternative 005DFDB685257306_=--


--===============0684308076==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============0684308076==--




From swmp-bounces@ietf.org Tue Jun 26 13:35:40 2007
Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Ex2-0003iR-Ti; Tue, 26 Jun 2007 13:35:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Ex1-0003iL-PD
	for swmp@ietf.org; Tue, 26 Jun 2007 13:35:39 -0400
Received: from worlds.webers.org ([64.34.168.199]
	helo=william.mediamachines.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3EwA-0005uB-DG
	for swmp@ietf.org; Tue, 26 Jun 2007 13:35:39 -0400
Received: from [192.168.2.119] (h-66-166-236-26.snvacaid.covad.net
	[66.166.236.26]) by william.mediamachines.com (Postfix) with ESMTP
	id 61B8146404E; Tue, 26 Jun 2007 12:33:42 -0500 (CDT)
Message-ID: <46814E33.5020509@mediamachines.com>
Date: Tue, 26 Jun 2007 10:34:43 -0700
From: "Jay C. Weber" <jweber@mediamachines.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: john_patterson@us.ibm.com
Subject: Re: [SWMP] Media Machines' initial design and code
References: <OF9311E6B3.E102E931-ON85257306.005BE41A-85257306.005DFDB9@lotus.com>
In-Reply-To: <OF9311E6B3.E102E931-ON85257306.005BE41A-85257306.005DFDB9@lotus.com>
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>,
	<mailto:swmp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0287298920=="
Errors-To: swmp-bounces@ietf.org

--===============0287298920==
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:john_patterson@us.ibm.com">john_patterson@us.ibm.com</a> wrote:
<blockquote
 cite="midOF9311E6B3.E102E931-ON85257306.005BE41A-85257306.005DFDB9@lotus.com"
 type="cite"><font face="sans-serif" size="2">4) &nbsp;It sounds like you
are saying
that latecomer support is in your code even though it is not obvious
how
to do it based on the paper. &nbsp;Does that mean there is a get request
in your implemented protocol?</font>
  <br>
</blockquote>
In the client/server architecture we implemented, when a client
connects to the server and sends a Hello message, the server responds
with a Hello message followed by a series of set messages containing
latecomer state data.&nbsp; So there is no explicit get request, unless you
want to consider Hello to subsume the semantics "send me latecomer
data".<br>
<br>
Generalizing this issue a little, pub-sub requests are implicit in our
system.&nbsp; Our applications and supporting architectures don't need
explicit pub-subs, but I can imagine some uses for pub-sub messages,
maybe we should add them to SWMP.<br>
<br>
jay<br>
<br>
<br>
</body>
</html>


--===============0287298920==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp

--===============0287298920==--



