Re: [mmox] Permissions

Jon Watte <jwatte@gmail.com> Mon, 23 February 2009 21:20 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 DAB493A68A6 for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 13:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level:
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 RwYEqHPRg-FH for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 13:20:30 -0800 (PST)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by core3.amsl.com (Postfix) with ESMTP id 923263A6833 for <mmox@ietf.org>; Mon, 23 Feb 2009 13:20:29 -0800 (PST)
Received: by an-out-0708.google.com with SMTP id b2so1166151ana.4 for <mmox@ietf.org>; Mon, 23 Feb 2009 13:20:47 -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=DafRPY93bU3Mi1I1e3erakgSKjNADlDIKF5fChEeTmU=; b=qwAuoI/n0e7e/briUrJLSUyJOwElz0o40j80MBMlrKXuEaIeXYO60PscJau48KL9o7 hO05Fo5Trsav9Z3FQVBJ+Kt6yj+PWsPw0vH80XXarY26y6pHBrasPcJVUpqhcn9NYAct +7JYe1gSK6WXd9kw17JeLDEHu7ry3fCyYpDZ8=
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=ZtKlpMaWA7AJQozkt/20U0AW3sMs3aZ4JKuwJ/dDcjUG3nZdsYLrLamu7ciyQCIfKW XkD5KpCdVN7wfwD4olDYBtkhUV90jWRntxYxEX/fIfjmNyR4PcTyrnaWpr/lQgq9i1pX 0KaM4j2YawuQ8h3PIVmvulPnweZSwz9tYHNnc=
Received: by 10.100.8.4 with SMTP id 4mr4376844anh.118.1235424038132; Mon, 23 Feb 2009 13:20:38 -0800 (PST)
Received: from ?192.168.168.111? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id c23sm13551378ana.52.2009.02.23.13.20.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Feb 2009 13:20:37 -0800 (PST)
Message-ID: <49A31323.8010804@gmail.com>
Date: Mon, 23 Feb 2009 13:20:35 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: lenglish5@cox.net
References: <61dbdd7d0902230059u69e87ed3n3a85b905593c11@mail.gmail.com> <53cd6c2e0902230118v12f271a5u2657a358821f4d09@mail.gmail.com> <61dbdd7d0902230131v7d870dc4qb17b14d2b9c8875c@mail.gmail.com> <53cd6c2e0902230210u5de8a5e7o1f589b17d2d3bf97@mail.gmail.com> <61dbdd7d0902230221h66a5deb2w64f551f08c062878@mail.gmail.com> <53cd6c2e0902230227p7d52e84br82b29f16c04c9f70@mail.gmail.com> <61dbdd7d0902230444k359a3576r42f3343ecf5d5d6d@mail.gmail.com> <53cd6c2e0902230532kfcd975akb13e088ae23c4304@mail.gmail.com> <61dbdd7d0902230537n20f86856i8b392a80b1740bc0@mail.gmail.com> <53cd6c2e0902230559g73aa66e3u4026f34b95ec215@mail.gmail.com> <49A2FDB8.7000303@cox.net>
In-Reply-To: <49A2FDB8.7000303@cox.net>
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 21:20:30 -0000

Lawson English wrote:
> SL, sorry to keep bringing it up, but its an important usecase, has 
> 20,000 simulators and some
> ludicrous number of "assets" to deal with. If there's no local caching 
> of assets on any other grid,
> permissions allowing, then the SL servers would be expected to be 
> asset server to the metaverse
> and they already groan under the strain of talking to the limited SL 
> world. The metaverse is

Note that the SL assets can only be used when the SL servers are 
participating in an interoperation scenario. If SL makes it a 
requirement that at least one SL customer is part of any interoperation 
scenario involving SL servers, then SL has a revenue stream for each 
such interoperation scenario. From the point of view of any one service 
provider, I think that this model will work well, and it will scale 
fine. The problem is then reduced to a per-provider problem, where each 
providers' ability to serve its customers is an implementation and 
business model detail, not an interoperation detail.

> projected to become 100-100x larger than Secondlife. the AWG's 
> original mission was to try to
> desing a SL-like meta-grid that would handle such "scary numbers." We 
> can't just handwave
> the issues away and suggest that existing systems and architectures 
> will "just do it" in some way.
>

I think we've all agreed that this group is not the AWG. Our role is not 
how to figure out how to "scale Second Life" or even "scale something 
Second Life-like." Our role is to figure out how to make multiple, 
disparate systems able to talk to each other -- hopefully in a way that 
will let the greater world able to scale in aggregate.


Sincerely,

jw