Re: [mmox] Permissions

Jesrad <jesrad@gmail.com> Mon, 23 February 2009 10:26 UTC

Return-Path: <jesrad@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 CB48628C117 for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 02:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.428
X-Spam-Level:
X-Spam-Status: No, score=-2.428 tagged_above=-999 required=5 tests=[AWL=0.171, 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 hdFr0Pk+ALpy for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 02:26:56 -0800 (PST)
Received: from mail-fx0-f167.google.com (mail-fx0-f167.google.com [209.85.220.167]) by core3.amsl.com (Postfix) with ESMTP id 896263A6874 for <mmox@ietf.org>; Mon, 23 Feb 2009 02:26:55 -0800 (PST)
Received: by fxm11 with SMTP id 11so1567397fxm.13 for <mmox@ietf.org>; Mon, 23 Feb 2009 02:27:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ayvpKFggIlIAbAEHy84e+ld3nBpoRHkUq8VFPrnvI50=; b=s/syYrV/1aYE2g/+I0umWt4k3uvchyXgf8oYdmYhAQV67Ra3txuzeMoNT2pr7fUxVV ZIi4TYy3PtGwXDktXEPVy45T2KNqw5lkXtPZP8vXX2MBjaL8p5WAxT/c3uHrSJcX3O4A /alrqcwgFCfdg5hkcj8AkiDLjzHe66fC2wXNo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=jYd+cT6Q4Aag6xeezBesoxOxl1aQeZm400Ox7FBioWmT3rB6onc2RTKhNu5FeXGf+6 nftrg/mqbBxqKqQAMXn5NX6xV7ZnKP3zD+tl6Zp7GV8g4WVxNbZnDSoizjjNmEQ62ZGv VgMhTU5pYWhoW0Nh4EBWiPL2wDW5NKkf8mRjo=
MIME-Version: 1.0
Received: by 10.181.202.8 with SMTP id e8mr1479054bkq.25.1235384831602; Mon, 23 Feb 2009 02:27:11 -0800 (PST)
In-Reply-To: <61dbdd7d0902230221h66a5deb2w64f551f08c062878@mail.gmail.com>
References: <61dbdd7d0902230059u69e87ed3n3a85b905593c11@mail.gmail.com> <53cd6c2e0902230118v12f271a5u2657a358821f4d09@mail.gmail.com> <61dbdd7d0902230131v7d870dc4qb17b14d2b9c8875c@mail.gmail.com> <53cd6c2e0902230210u5de8a5e7o1f589b17d2d3bf97@mail.gmail.com> <61dbdd7d0902230221h66a5deb2w64f551f08c062878@mail.gmail.com>
Date: Mon, 23 Feb 2009 11:27:11 +0100
Message-ID: <53cd6c2e0902230227p7d52e84br82b29f16c04c9f70@mail.gmail.com>
From: Jesrad <jesrad@gmail.com>
To: "mmox@ietf.org" <mmox@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 10:26:56 -0000

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.
>