Re: FW: Draft minutes of trade IETF San Diego

Ko Fujimura <fujimura@isl.ntt.co.jp> Wed, 20 December 2000 11:45 UTC

Return-Path: <ietf-trade-errors@lists.elistx.com>
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G5V00C017BFZ8@eListX.com>; Wed, 20 Dec 2000 06:45:15 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G5V00C017BEZ6@eListX.com>; Wed, 20 Dec 2000 06:45:15 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G5V00C047BEZ3@eListX.com> (original mail from fujimura@isl.ntt.co.jp) ; Wed, 20 Dec 2000 06:45:14 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G5V00C017BDZ1@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Wed, 20 Dec 2000 06:45:13 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G5V00C017BDZ0@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Wed, 20 Dec 2000 06:45:13 -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 <0G5V00BA17BBJE@eListX.com> for ietf-trade@lists.elistx.com; Wed, 20 Dec 2000 06:45:13 -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 UAA15119 for <ietf-trade@lists.elistx.com>; Wed, 20 Dec 2000 20:44:32 +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 UAA27336 for <ietf-trade@lists.elistx.com>; Wed, 20 Dec 2000 20:44:31 +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 UAA04225; Wed, 20 Dec 2000 20:44:30 +0900 (JST)
Date: Wed, 20 Dec 2000 20:48:37 +0900
From: Ko Fujimura <fujimura@isl.ntt.co.jp>
Subject: Re: FW: Draft minutes of trade IETF San Diego
To: ietf-trade@lists.elistx.com
Cc: fujimura@isl.ntt.co.jp
Message-id: <3A409C95.F1746D9B@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: <51228FAD179FD4118A8600D0B76FE2621881A2@ma07exm01.corp.isg.mot.com>
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>

Hi Walter and Donald,

Thank you very much for the minutes. I have a few comments:

Eastlake III Donald-LDE008 wrote:
> 
> Minutes of the Internet Open Trading Protocol Working Group (trade)
> 
> Wednesday, December 13 at 1300-1500
> =====================================
> 
> CHAIR: Donald Eastlake 3rd dee3@torque.pothole.com
> Minutes: Walter Houser houser.walt@forum.va.gov
...
> 7. Digital Rights Requirements - also known as Requirement for Generic
> Payments Rights - presentation by Ko Fujimura.

The title was "Requirements for Generic Rights Trading"
 
> RTS is an infrastructure to circulate diverse types of digitally
> represented rights. RTS is enables digital versions of coupons and
> tickets. We need to prevent copying.  RTS should allow sharing between
> several issuers. There are five requirements:
> 
> -       Prevent alternation
> -       Provide non-repudiation,
> -       Provide idempotency (one and only one)
> -       Prevent reproduction
> -       Prevent duplicate redemption.
> 
> Fujimura presented a Chart for Positioning of RTS in trading area shows
> the relationship of RTS with respect to IOTP. Hole observes that one needs
> to trust the coupon. Fujimura replied that trust of the coupon is the
> result of the issuer, which can be handed around by untrusted bodies. 

Yes, but more correctly, I replied that:

"trust of the coupon is the result of the issuer and the RTS. The issuer is
responsible for the contents of the right and the RTS is responsible
for preventing copy. In other words, if there is trust in the issuer and 
the RTS, trust of the holder who transfers or redeems the coupon is not 
required."

> The RTS object is an XML object, which would be defined by the WG.

I think it means that:

"The objects transported by the RTS is an XML Components which would be defined 
by the WG."
 
> Hole observed that the definition of the data representation is distinct from
> the transport issues. The latter may be appropriate for the WG, but they
> are nontrivial.
>
> The working group suggested several terms to use in lieu of digital rights
> or electronic rights, such as trading right, entitlement, coupon, and
> certificate. There was concern about confusion of the term rights with
> access control rights. Entitlement was thought cumbersome. Coupon
> communicates too much of a limitation. Certificate has a specific meaning
> with respect to network security.
...

Please add:

"It was agreed to decide the term using the mailing list."

Thanks.

Ko