Re: [mmox] Permissions

Jon Watte <jwatte@gmail.com> Mon, 23 February 2009 22:51 UTC

Return-Path: <jwatte@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41BDA3A69AB for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 14:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level:
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8mT7OKUbM4L for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 14:51:01 -0800 (PST)
Received: from mail-gx0-f174.google.com (mail-gx0-f174.google.com [209.85.217.174]) by core3.amsl.com (Postfix) with ESMTP id 4F60A3A63D3 for <mmox@ietf.org>; Mon, 23 Feb 2009 14:51:01 -0800 (PST)
Received: by gxk22 with SMTP id 22so5893806gxk.13 for <mmox@ietf.org>; Mon, 23 Feb 2009 14:51:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=IGDrmZcGdpkL96Bbtjab7qInOzo3oISUYVBzrp7xJRo=; b=SjZLVSzhN097wsKA5pHoiSLrAUrF0bqMQcMKqHYfNVzPVCeajRxrToRUmZbZiU+wgt YObVM1Q7TZt7aI+1oEN60oz18RNjmxGR6vE4MRzvxQWCGuLwgbAoWhz0KbCMnzAyd/p0 E/n9ptHBqkLqczHet1boeLJlpziRhVUatXCjo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=AXVIjEUyVb71cjXpYbtompWxWoGgZFM/qvYGzUwnX3l+ahcblyimSbIk19Ccd2iWyE udJY7fwtQsLHiCxoCy8hdgSmfmniypx7QAvD/UEJ1vOT9sU1Krcn1QqG3zumGT1MAZxV 7B4b8OiCodvfbFrqeyNO8f8nfjT/Xxm8B+wq0=
Received: by 10.100.112.10 with SMTP id k10mr4799269anc.114.1235429479522; Mon, 23 Feb 2009 14:51:19 -0800 (PST)
Received: from ?192.168.168.111? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id d35sm9700451and.38.2009.02.23.14.51.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Feb 2009 14:51:18 -0800 (PST)
Message-ID: <49A32864.9040605@gmail.com>
Date: Mon, 23 Feb 2009 14:51:16 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Jesrad <jesrad@gmail.com>
References: <61dbdd7d0902230059u69e87ed3n3a85b905593c11@mail.gmail.com> <53cd6c2e0902230118v12f271a5u2657a358821f4d09@mail.gmail.com> <49A30AE5.6060307@gmail.com> <53cd6c2e0902231323p641cd6d4s99d5f97a0340c4c2@mail.gmail.com> <49A31AD2.40402@gmail.com> <53cd6c2e0902231408y3fb35487v4125171b4ca5b16d@mail.gmail.com>
In-Reply-To: <53cd6c2e0902231408y3fb35487v4125171b4ca5b16d@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] Permissions
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 22:51:02 -0000

Jesrad wrote:
>> soccer ball. My argument is simply against the idea that a single client
>> connecting to two separate virutal world servers could provide a usefully
>> consistent view of a virtual world simulation.
>>     
>
> Well, that's precisely the model Solipsis is based on, and it seems to
> give a reasonably consistent view. The node with the soccer ball can
> decide to let others know about it or not, and that makes little
> difference for the rest of the world. In this model you're free to
>   

In the general case, letting arbitrary, untrusted clients introduce 
content into a virtual world is not desirable. It would actually leave 
organizational users open to various kinds of discrimination and 
harassment lawsuits.

However, if for Sollipsis you consider each "peer" as being a "server" 
in the proposal I've suggested (which, btw, was explicitly called out in 
the keynote slides for last year's IEEE MMVE), then it is the same 
model. I would expect that you could actually quite easily implement the 
proposed interoperability model into Sollipsis and interoperate with any 
other peer or server that wanted to interoperate with you.

Sincerely,

jw