Re: [mmox] Permissions

Gareth Nelson <gareth@litesim.com> Mon, 23 February 2009 12:43 UTC

Return-Path: <gareth@litesim.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 273A33A6842 for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 04:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.752
X-Spam-Level:
X-Spam-Status: No, score=-1.752 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ElHjf56bD-Q for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 04:43:46 -0800 (PST)
Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.157]) by core3.amsl.com (Postfix) with ESMTP id 6D55D3A67F5 for <mmox@ietf.org>; Mon, 23 Feb 2009 04:43:46 -0800 (PST)
Received: by po-out-1718.google.com with SMTP id b23so6561221poe.4 for <mmox@ietf.org>; Mon, 23 Feb 2009 04:44:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.141.53.4 with SMTP id f4mr2032349rvk.35.1235393043135; Mon, 23 Feb 2009 04:44:03 -0800 (PST)
In-Reply-To: <53cd6c2e0902230227p7d52e84br82b29f16c04c9f70@mail.gmail.com>
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>
Date: Mon, 23 Feb 2009 12:44:03 +0000
Message-ID: <61dbdd7d0902230444k359a3576r42f3343ecf5d5d6d@mail.gmail.com>
From: Gareth Nelson <gareth@litesim.com>
To: Jesrad <jesrad@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
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 12:43:47 -0000

Well, talking to a few others it seems the general consensus is "make
a field on assets for all this stuff and make the scheme extensible".

On Mon, Feb 23, 2009 at 10:27 AM, Jesrad <jesrad@gmail.com> wrote:
> Hmm, "it's not gonna enforce IP technically" was not the point I
> wanted to make. The actual point is: attempting to define a mechanism
> for signalling what categories of actions are permitted or not under a
> specific copyright law (which may or may not be applicable depending
> on national/sovereign context) is a non-starter because of infinite
> recursion.
>
> This is one of the main reasons I suggest curtaining the issue
> entirely by adopting a multiple-host approach, where content (but not
> necessarily the MMOX-layer object reference itself) remains hosted on
> the originating grid and is not replicated between different grids
> through the cross-grid protocol. The other reason for following such
> an approach, is that it's the only one compatible with existing P2P
> VWs like Solipsis.
>
> On Mon, Feb 23, 2009 at 11:21 AM, Gareth Nelson <gareth@litesim.com> wrote:
>> On Mon, Feb 23, 2009 at 10:10 AM, Jesrad <jesrad@gmail.com> wrote:
>>>> Some people are going to insist on the DRM or not allow their content
>>>> to be transferred at all
>>>
>>> And some people like me will insist that there is a way to do it that
>>> cannot be prevented by third-party permissions system like this.
>>
>> But that's besides the point, since doing so isn't going to convince
>> people to allow the content to move AND this system does not in fact
>> prevent anything, it's a machine-readable version of the license - the
>> only force comes from compliant systems and users or the courts.
>>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>