Re: Working Group Last Call and naming fordraft-ietf-trade-drt-requirements-01.txt

Ko Fujimura <fujimura@isl.ntt.co.jp> Wed, 24 January 2001 07:07 UTC

Return-Path: <ietf-trade-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G7N00A04NRSLM@eListX.com> (original mail from fujimura@isl.ntt.co.jp) ; Wed, 24 Jan 2001 02:07:04 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G7N00A01NRSLK@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Wed, 24 Jan 2001 02:07:04 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G7N00A01NRRLJ@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Wed, 24 Jan 2001 02:07:03 -0500 (EST)
Received: from tama3.tas.ntt.co.jp (tama3.tas.ntt.co.jp [192.68.248.40]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G7N008FONRPZQ@eListX.com> for ietf-trade@lists.elistx.com; Wed, 24 Jan 2001 02:07:03 -0500 (EST)
Received: from nttmail.ecl.ntt.co.jp (nttmail.tas.ntt.co.jp [192.68.248.11]) by tama3.tas.ntt.co.jp (8.9.3+3.2W/3.7W/01/21/00) with ESMTP id QAA21550; Wed, 24 Jan 2001 16:06:03 +0900 (JST envelope-from fujimura@isl.ntt.co.jp)
Received: from alsace.isl.ntt.co.jp by nttmail.ecl.ntt.co.jp (8.9.3+3.2W/3.7W/10/05/00) with ESMTP id QAA29642; Wed, 24 Jan 2001 16:05:58 +0900 (JST envelope-from fujimura@isl.ntt.co.jp)
Received: from isl.ntt.co.jp (degas.isl.ntt.co.jp [129.60.104.56]) by alsace.isl.ntt.co.jp (8.8.8/3.7W) with ESMTP id QAA21060; Wed, 24 Jan 2001 16:05:57 +0900 (JST)
Date: Wed, 24 Jan 2001 16:10:26 +0900
From: Ko Fujimura <fujimura@isl.ntt.co.jp>
Subject: Re: Working Group Last Call and naming fordraft-ietf-trade-drt-requirements-01.txt
To: Renato Iannella <renato@iprsystems.com>
Cc: ietf-trade@lists.elistx.com
Message-id: <3A6E7FE2.7370F303@isl.ntt.co.jp>
MIME-version: 1.0
X-Mailer: Mozilla 4.75 [ja] (Win98; U)
Content-type: text/plain
Content-transfer-encoding: 7bit
X-Accept-Language: ja
References: <567731.3188218747@localhost>
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <mailto:ietf-trade-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-trade>
List-Help: <http://lists.elistx.com/doc/email-manage.html>, <mailto:ietf-trade-request@lists.elistx.com?body=help>

Thank you for your suggestions and links to the DRM resources.

Renato Iannella wrote:
> 
> Use of "rights" implies intellectual/legal/social behaviours, such
> as copyright, moral rights etc. The modelling, requirements, languages
> for this type of right is significant (see [1] to [11]).
> 

I think that "rights" are often used for "access rights" as well as "IP rights". 
Example of such usage are found in RFC2086, 2820, and draft-ietf-ldapext-acl-model-06.txt

I also think that most of "tickets" are a kind of "access rights" for a physical
resources, and those concept are similar. I, therefore, think that the usage of 
"rights" in the draft is common, too.
I believes that what this draft describes is nothing more than "trading aspect of rights".

> This leads me to the point in "Section 7. Q & A"
> 
> ----
>   - Is it possible to ensure digital "property" rights?
> 
>   Yes, since digital property rights can be considered as a kind of
>   electronic-right. RTS, however, would need to be extended by adding
>   some protected rendering system that would regenerate the original
>   digital contents securely.
> -----
> 
> I would say they answer is "No". You cannot _ensure_ this.
> (see the references below)

Right. I would like to change it to:

  - Is it possible to support "digital property right?"

  Digital property right can be considered as a kind of electronic-right and
  it can be traded using RTS.  However, some protected rendering system would 
  be required to regenerate the digital contents securely in order to support 
  digital property rights. These requirements are out of scope of RTS.

Regards,

Ko