Re: [mmox] mmox Digest, Vol 1, Issue 111
Jon Watte <jwatte@gmail.com> Mon, 23 February 2009 21:06 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 D8C5528C173 for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 13:06:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level:
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081, 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 BXrZOC2w4g7F for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 13:06:28 -0800 (PST)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by core3.amsl.com (Postfix) with ESMTP id E149B3A68A6 for <mmox@ietf.org>; Mon, 23 Feb 2009 13:06:27 -0800 (PST)
Received: by an-out-0708.google.com with SMTP id b2so1162196ana.4 for <mmox@ietf.org>; Mon, 23 Feb 2009 13:06:45 -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=YdDjHLFsTVEtO0/OgZ7uGbBCVtPinwVvCH/4njwsbPg=; b=OAtKS4vfyE4iiGV1RxNCvkX60aO4qP20R+oq5Ngy6PX2Lus6JdoAChjz00zvF2opOM MK+SbsYja7ygrWFaFcMSjxM28oYxFT16MgmAzu2snrb8O2uC0PvTOHjVYTtku5TfDQTo PlpYdADQJhPhwMhuk3Mbc2x0IlqG4f+glEPXY=
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=KRFVe2MmyioRnvSlrX8q1YfwKyIguERgRuOklieiuBb1RQg4YEOWekJHRceVEEGRhv DtCjCrhowx3pquB4/RKl2cm+FWE4WLm9YihJK8yWsStagyOkpwEV5kkVUej8Fgd5Rh6x PH5gypm4Y6JWUM4Tbx+c95TfW3TVd3Udwp2qQ=
Received: by 10.100.138.17 with SMTP id l17mr2559683and.2.1235423205453; Mon, 23 Feb 2009 13:06:45 -0800 (PST)
Received: from ?192.168.168.111? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id d24sm7773932and.50.2009.02.23.13.06.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Feb 2009 13:06:44 -0800 (PST)
Message-ID: <49A30FE2.1010801@gmail.com>
Date: Mon, 23 Feb 2009 13:06:42 -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: <20090223.084454.24252.0@webmail09.vgs.untd.com> <53cd6c2e0902230613y6e86f16fyaa841a08db4b86d1@mail.gmail.com>
In-Reply-To: <53cd6c2e0902230613y6e86f16fyaa841a08db4b86d1@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org, "dyerbrookme@juno.com" <dyerbrookme@juno.com>
Subject: Re: [mmox] mmox Digest, Vol 1, Issue 111
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:06:28 -0000
Jesrad wrote: > I actually wrote that mandating the implementation of DRM on top of > any permission/copyright metadata transmission mechanism would severly > reduce the number of grid systems that comply with the protocol. > Note that it would be totally possible for someone to come up with a DRM scheme, that mandates that content create /under that DRM scheme/ only be transferred to other trusted implementors of that scheme. That would mean that, if the content was created on a compliant system, and properly marked, it could not "escape" into non-DRM systems. I think that enabling this within the standard is important. A world can then compete for attention, by implementing and adhering to some popular scheme. For example, if creators feel most comfortable with "Microsoft VW Content DRM" or "MacroMedia ContentSafe(tm)," they could make sure to create their content in a world certified by one of those providers, and mark the object as not transferable outside those domains. Part of the certification would then be to make sure that such marks are actually adhered to. This neatly splits the interoperability protocol into the interoperability part, which is free, open, and allows OpenSim or LeftistWorld to be as open as they want, and the DRM/enforcement part, which allows the concerned content creators to stay as locked-up as they want within RightistWorld. Sincerely, jw
- Re: [mmox] mmox Digest, Vol 1, Issue 111 dyerbrookme@juno.com
- Re: [mmox] mmox Digest, Vol 1, Issue 111 dyerbrookme@juno.com
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Dan Olivares
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Jesrad
- Re: [mmox] mmox Digest, Vol 1, Issue 111 dyerbrookme@juno.com
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Jesrad
- Re: [mmox] mmox Digest, Vol 1, Issue 111 dyerbrookme@juno.com
- Re: [mmox] the arguments are sidelining people... Kajikawa Jeremy
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Gareth Nelson
- Re: [mmox] mmox Digest, Vol 1, Issue 111 dyerbrookme@juno.com
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Dan Olivares
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Dan Olivares
- Re: [mmox] mmox Digest, Vol 1, Issue 111 dyerbrookme@juno.com
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Dan Olivares
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Jon Watte
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Jesrad
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Kajikawa Jeremy
- Re: [mmox] mmox Digest, Vol 1, Issue 111 dyerbrookme@juno.com
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Dan Olivares
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Dan Olivares
- Re: [mmox] mmox Digest, Vol 1, Issue 111 Kajikawa Jeremy