Subject: Re: IETF 46 TRADE (IOTP) WG Meeting
From: "Donald E. Eastlake 3rd" <[email-masked]>
To: Ko Fujimura <[email-masked]>
Cc: [email-masked]
Date: Mon, 13 Dec 1999 07:54:30 -0500

I'll send in corrected minutes but I don't know if they can be fixed at this
point.  My apologies for the errors.

Donald

From:  Ko Fujimura <[email-masked]>
Date:  Mon, 13 Dec 1999 17:57:09 +0900
Message-ID:  <[email-masked]>
To:  [email-masked]
Cc:  [email-masked], [email-masked]
In-Reply-To:  In your message of "Fri, 10 Dec 1999 12:38:21 -0500"
	     	<[email-masked]>
References:  <[email-masked]>
User-Agent:  SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.2 (beta1) (Aeol
us) (sparc-sun-solaris2.6)
Content-Type:  text/plain; charset=US-ASCII
Sender:  [email-masked]
Precedence:  bulk
X-elistx:  ietf-trade
Source-Info:   From (or Sender) name not authenticated.
>Hi, I found the following typo in the minute. 
>
>At Fri, 10 Dec 1999 12:38:21 -0500,
>Donald E. Eastlake 3rd <[email-masked]> wrote:
>...
>> Ko Fujimora:
>>      Digital Rights Trading Infrastructure(DTRI) [ietf46-DRTI.ppt slides]
>
>DTRI --> DRTI
>
>>      The is a proposed new work item.
>
>The --> The DRTI
>
>>      Background objectives include mechanisms to create coupons and
>>         redit loyalty points.
>
>redit --> credit
>
>By the way, I also found some English errors in my presentation
>slides. If it is allowed (and in time), I would like to update it. I
>placed the revised version at the following URL.  All of changes are
>editorial.  
>
>http://info.isl.ntt.co.jp/flexticket/ietf/ietf46-DRTI.ppt
>
>Apologies for interrupting you.
>
>Ko
>----------------------------------------------------------
>Ko Fujimura, NTT Information Sharing Platform Laboratories
>1-1 Hikarinooka, Yokosuka-shi, Kanagawa 239-0847, JAPAN
>Tel: +81-(0)468-59-3814, Fax: +81-(0)468-59-8329
>Email: [email-masked]
>
>-----------------------------------------------------------------------
>Message addressed to: [email-masked]
>Archive available at: http://www.elistx.com/archives/ietf-trade/
>To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
>body to: [email-masked]
-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]

Date: Mon, 13 Dec 1999 17:57:09 +0900
From: Ko Fujimura <[email-masked]>
To: [email-masked]
Cc: [email-masked], [email-masked]
Subject: Re: IETF 46 TRADE (IOTP) WG Meeting
Sender: [email-masked]
Source-Info:  From (or Sender) name not authenticated.

Hi, I found the following typo in the minute. 

At Fri, 10 Dec 1999 12:38:21 -0500,
Donald E. Eastlake 3rd <[email-masked]> wrote:
...
> Ko Fujimora:
>      Digital Rights Trading Infrastructure(DTRI) [ietf46-DRTI.ppt slides]

DTRI --> DRTI

>      The is a proposed new work item.

The --> The DRTI

>      Background objectives include mechanisms to create coupons and
>         redit loyalty points.

redit --> credit

By the way, I also found some English errors in my presentation
slides. If it is allowed (and in time), I would like to update it. I
placed the revised version at the following URL.  All of changes are
editorial.  

http://info.isl.ntt.co.jp/flexticket/ietf/ietf46-DRTI.ppt

Apologies for interrupting you.

Ko
----------------------------------------------------------
Ko Fujimura, NTT Information Sharing Platform Laboratories
1-1 Hikarinooka, Yokosuka-shi, Kanagawa 239-0847, JAPAN
Tel: +81-(0)468-59-3814, Fax: +81-(0)468-59-8329
Email: [email-masked]

-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]

To: [email-masked]
cc: [email-masked]
Subject: IETF 46 TRADE (IOTP) WG Meeting
Date: Fri, 10 Dec 1999 12:38:21 -0500
From: "Donald E. Eastlake 3rd" <[email-masked]>
Sender: [email-masked]
Source-Info:  From (or Sender) name not authenticated.

Below are the minutes of the meeting.  The minutes and the slides of the
various presentations refered to are availabe at

<ftp://ftp.pothole.com/pub/ietf-trade/IETF-Washington/>

Thanks,
Donald

 Donald E. Eastlake 3rd   +1 914-276-2668     [email-masked]
 65 Shindegan Hill Road, RR#1  +1 914-784-7913(work)  [email-masked]
 Carmel, NY 10512 USA

IETF 46, TRADE Working Group Minutes
Notes taken by Maryann Hondo, edited by Donald Eastlake

Chair, Donald Eastlake

[See TRADE Working Group Agenda Slides]

planned agenda
     status of main documents
     implementation news
     digital rights
     Supporting Contracts (Eric Brunner wished to speak but was
     	unable to attend due to illness.)
     XML Messaging (Dave Burdett unable to attend.)
     charter update

A summary of the ECML BOF was given along with the slides presented
there [see minutes for the ECML BOF].  The ECML BOF concluded that
ECML was an appropriate work item for the TRADE working group

Status of documents:
     The main three are ready for publishing as RFCs and are
     	through last call.  ((They have since been approved by
     	the IESG as Informational and are in the RFC Editor's
     	queue.))

     The Hiroshi Maruyama DOMHASH document
          Very few comments have been received.  It provides
          canonicalization and hashing together.  It will be
          replaced by the XMLDSIG standard when it comes out.
     IOTP digital signature draft
          Only one minor change needed and revised version has been
          created.
     main protocol document
          Needs the same minor change as the IOTP digital signature
          draft plus one other minor change and some clarification to
          the text.
          
<<comment that the documents may not need new revision numbers....
are further along than might have been thought...the rfc editor might
be able to just fix these>>

     main protocol document
     	  [See Dave Burdett changes05to07.ppt slides]
          Minor changes between 5 & 6.  Version 6 was Last Called.
          Even smaller changes in Version 6 to 7 as follows:
             question of what IOTP XML namespace should be...
             question of id prefix letter on inquiry,
                currently to specify prefix letter q
             question on transaction equality test,
                only test transaction id and timestamp
             no change to protocol structure or flow

other document status:
     http transport document
          Not much activity, more feedback is needed.
          how can a merchant tell if a consumer has something that
          supports IOTP?  ECML may be helpful.
          Check for a mime type? There is a draft of how to do this.

     Architecture & payment API document is almost in an internet draft
          form....need  finish converting to draft and get it out.

     SET supplement (how to use with IOTP)
          Less conversion to internet-draft so far, still has line
             drawn figures

     SCCD, simple way to use credit cards with IOTP, without SET
          Somewhat broader in scope than just IOTP, which only needs
          consumer to merchant. This document also contains merchant
          acquirer aspects.

Implementation news...
     Hitachi is working on several implementations:
     domestic:
          SMILE coding is moving forward, trial in March or April.
     international:
          Taiwan, Costa Rica
          Use a slightly older version of the specification.
     Other known implementation plans include
          Royal Bank of Canada
          JOTP: posted on the web...a java library for IOTP.

Ko Fujimora:
     Digital Rights Trading Infrastructure(DTRI) [ietf46-DRTI.ppt slides]
     The is a proposed new work item.
     Background objectives include mechanisms to create coupons and
        redit loyalty points.

Donald Eastlake: I suggest we should start with a requirements document
   before moving to a draft specification on the Digital Rights language

Charter update:
     The Working Group Charter is out of date:  the main documents are
     complete, the supplemental documents need new milestones.
     There is the possible addition of xml messaging as a task (ie,
     take content independent part of IOTP and make it a separate
     document), digital rights, and ECML v2.

     All the slides presented here will be in the proceedings and on
     Donald's web site
<<   question on whether version 2 which is the goal of the original
     charter, will be delayed because of these new requirements >>

     Donald asserted that version 2 is only delayed because people need
     more experience with deployment and interoperability on version 1.

<<   does XML messaging include discovery of DTDs? >>
     no

<<   does IOTP have its own DTD? >>
     probably

     XML and cookie analogy....
<<   wedge green....there are two ASN1 deployments, cartography database
     and the library system, that have been converted to XML. >>

Tony Lewis,  VISA: WG bandwidth question....does this working group
     have the bandwidth to pickup ECML?

WG consensus that it does have the bandwidth.

Working Group support voiced for at least doing the digital rights requirement here
and then  decide where detailed design lives.

<<   questions on what is it meant to be integrated with privacy?
     >>
     Things like the W3C P3P protocol.

<<   would support of ECML dilute the IOTP, since it is weaker than IOTP?
     >>

     ECML looks like it will be widely deployed sooner, could be a bridge or
     lead in to IOTP.....The MS passport Wallet uses ECML....
-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]

To: [email-masked]
Subject: WG Last Call Re: Revised New Draft WG Charter 
Date: Wed, 08 Dec 1999 11:07:58 -0500
From: "Donald E. Eastlake 3rd" <[email-masked]>
Sender: [email-masked]
Source-Info:  From (or Sender) name not authenticated.

OK, I've fixed the typos that were pointed out and I'm staring a one
week working group last call.  I'll forward the revised charter to our
Area Director in a week, depending on what comments there are.

Thanks,
Donald

>Chair(s):
>Donald Eastlake 3rd <[email-masked]>
>
>Applications Area Advisor:
>Patrik Faltstrom <[email-masked]>
>
>Editor(s):
>David Burdett <[email-masked]>
>
>Mailing Lists:
>General Discussion:[email-masked]
>To Subscribe: [email-masked]
>In Body: (un)subscribe
>Archive: http://www.eListX.com/archives/ietf-trade
>
>The TRADE Working Group will further develop the Internet Open Trading
>Protocol (IOTP) and the Electronic Commerce Modeling Language (EMCL)
>specifications and investigate digital rights trading requirements.
>
>There will be four main threads to the activity:
>1. IOTP version 2.0
>2. XML Messaging
>3. ECML, and
>4. Digital Rights Trading Requirements.
>
>Each of these is discussed in more detail below.
>
>IOTP is an interoperable framework for Internet commerce. It is
>optimized for the case where the buyer and the merchant do not have
>a prior acquaintance and is payment system independent. It can
>encapsulates and supports payment systems such as SET, Mondex,
>secure channel card payment, GeldKarte, etc. IOTP is able to
>handle cases where such merchant roles as the shopping site,
>the payment handler, the deliverer of goods or services, and
>the provider of customer support are performed by different
>Internet sites.
>
>The  working group will document interoperability experience with
>IOTP version 1 and develop the requirements for IOTP transport and
>IOTP version 2.
>
>Selection of items for inclusion in version requirements 2 is to
>be from the following:
>- Separation of a content independent Messaging Layer
>- Dynamic Definition of Trading Sequences
>- Offer Request Block
>- Improved Problem Resolution (extend to cover presentation of
>signed receipt to customer support party, etc.)
>- Server to Server messages
>
>Legal or regulatory issues surrounding the implementation of the
>protocol or information systems using it are out of scope for IOTP
>v2.
>
>XML Messaging is based on the messaging ideas contained inside IOTP
>version 1.0, and will aim to develop a specification for the the
>reliable, resilient, secure, exchange of XML over insecure
>transport mechanisms.
>
>The goal of the working group is to develop first a set of
>requirements and then the full specification that meets these XML
>Messaging objectives.
>
>ECML version 1 provides a standard set of hierarchical field names
>and content specifications plus a few procedural guidelines for
>the transmission of basic address and payment information from a
>customer to a merchant.
>
>The goal of the working group is to develop ECML version 2 which
>may include corrections to version 1 and may include additions in
>the following areas:
>- Merchant to Consumer communications fields including purchase
>amount, receipt information, package tracking information,
>- Additional Consumer to Merchant fields including Corporate
>procurement cards, Other payment systems, Travel and entertainment,
>Affinity, frequent flyer, and other customer loyalty programs,
>Business-to-business commerce
>- Improved internationalization
>- Coordination with privacy standards
>- Specifications for exchange of ECML data using XML
>
>In real world purchases and other trading transactions, it is often
>a requirement to credit loyalty points, collect digital coupons,
>check customer membership in a certain group, and so on.  The
>working group will investigate how these activities can be
>generalized using the concept of a "digital-right", which is a
>digital representation of the right to claim goods or services,
>and will specify the requirements in the following areas:
>- The digital rights trading model
>- The language to describe diverse types of digital rights
>
>Milestones:
>99 Dec - First Internet Draft publication of
>     Secure Channel Credit Debit Supplement
>     Architecture and Payment API Supplement
>00 Jan - First Internet Draft publication of
>     Requirements for XML Messaging Layer
>     Requirements for Digital Rights Trading
>     SET Supplement
>00 Feb - Initiate Last Call on
>     SCCD, Architecture, SET, and HTTP Supplements
>00 Feb - First Internet Draft publication of
>     ECML v2 Requirements
>(00 Mar, IETF Meeting Adelaide)
>00 Apr - To IESG for Publication
>     SCCD, Architecture, SET, and HTTP Supplements
>     ECML v2 Requirements
>00 Apr - First Internet Draft publication of
>     IOTP Version 2.0 Requirements
>     ECML v2 Specification
>     XML Messaging Specification
>00 Apr - To Last Call
>     Requirements for XML Messaging
>     Requirements for Digital Rights Trading
>00 May - First Internet Draft publication of
>     IOTP Version 2.0 Specification
>00 May - To Last Call
>     IOTP Version 2.0 Requirements
>00 Jul - To Last Call
>     ECML v2 Specification
>(00 Jul/Aug, IETF Meeting Pittsburgh)
>00 Aug - Last Call
>     XML Messaging Specification
>00 Sep - Last Call
>     IOTP Vesion 2 Specification
-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]

Date: Wed, 08 Dec 1999 17:19:10 +0900
From: Ko Fujimura <[email-masked]>
To: [email-masked]
Cc: [email-masked]
Subject: Re: Revised New Draft WG Charter
Sender: [email-masked]
Source-Info:  From (or Sender) name not authenticated.

Apologies for making typos in my previous comment. 
Corrections are marked ##. 

Thanks,

Ko
-----------------------------------------------------------
At Wed, 08 Dec 1999 00:36:09 -0500,
Donald E. Eastlake 3rd <[email-masked]> wrote:

Chair(s):
Donald Eastlake 3rd <[email-masked]>

Applications Area Advisor:
Patrik Faltstrom <[email-masked]>

Editor(s):
David Burdett <[email-masked]>

Mailing Lists:
General Discussion:[email-masked]
To Subscribe: [email-masked]
In Body: (un)subscribe
Archive: http://www.eListX.com/archives/ietf-trade

The TRADE Working Group will further develop the Internet Open Trading
Protocol (IOTP) and the Electronic Commerce Modeling Language (EMCL)
specifications and investigate digital rights trading equirements.

## equirements --> requirements

There will be four main threads to the activity:
1. IOTP version 2.0
2. XML Messaging
3. ECML, and
4. Digital Rights Trading Requirements.

Each of these is discussed in more detail below.

IOTP is an interoperable framework for Internet commerce. It is
optimized for the case where the buyer and the merchant do not have
a prior acquaintance and is payment system independent. It can
encapsulates and supports payment systems such as SET, Mondex,
secure channel card payment, GeldKarte, etc. IOTP is able to
handle cases where such merchant roles as the shopping site,
the payment handler, the deliverer of goods or services, and
the provider of customer support are performed by different
Internet sites.

The  working group will document interoperability experience with
IOTP version 1 and develop the requirements for IOTP transport and
IOTP version 2.

Selection of items for inclusion in version requirements 2 is to
be from the following:
- Separation of a content independent Messaging Layer
- Dynamic Definition of Trading Sequences
- Offer Request Block
- Improved Problem Resolution (extend to cover presentation of
signed receipt to customer support party, etc.)
- Server to Server messages

Legal or regulatory issues surrounding the implementation of the
protocol or information systems using it are out of scope for IOTP
v2.

XML Messaging is based on the messaging ideas contained inside IOTP
version 1.0, and will aim to develop a specification for the the
reliable, resilient, secure, exchange of XML over insecure
transport mechanisms.

The goal of the working group is to develop first a set of
requirements and then the full specification that meets these XML
Messaging objectives.

ECML version 1 provides a standard set of hierarchical field names
and content specifications plus a few procedural guidelines for
the transmission of basic address and payment information from a
customer to a merchant.

The goal of the working group is to develop ECML version 2 which
may include corrections to version 1 and may include additions in
the following areas:
- Merchant to Consumer communications fields including purchase
amount, receipt information, package tracking information,
- Additional Consumer to Merchant fields including Corporate
procurement cards, Other payment systems, Travel and entertainment,
Affinity, frequent flyer, and other customer loyalty programs,
Business-to-business commerce
- Improved internationalization
- Coordination with privacy standards
- Specifications for exchange of ECML data using XML

In real world purchases and other trading transactions, it is often
a requirement to credit loyalty points, collect digital coupons,
check customer membership in a certain group, and so on.  The
working group will investiagate hjow these activities can be

## investiagate hjow --> investigate how

generalized using the concept of a "digital-right", which is a
digital representation of the right to claim goods or services,
and will specify the requirements in the following areas:
- The digital rights trading model
- The language to describe diverse types of digital rights

Milestones:
99 Dec - First Internet Draft publication of
     Secure Channel Credit Debit Supplement
     Architecture and Payment API Supplement
00 Jan - First Internet Draft publication of
     Requirements for XML Messaging Layer
     Requirements for Digital Rights Trading
     SET Supplement
00 Feb - Initiate Last Call on
     SCCD, Architecture, SET, and HTTP Supplements
00 Feb - First Internet Draft publication of
     ECML v2 Requirements
(00 Mar, IETF Meeting Adelaide)
00 Apr - To IESG for Publication
     SCCD, Architecture, SET, and HTTP Supplements
     ECML v2 Requirements
00 Apr - First Internet Draft publication of
     IOTP Version 2.0 Requirements
     ECML v2 Specification
     XML Messaging Specification
00 Apr - To Last Call
     Requirements for XML Messaging
     Requirements for Digital Rights Trading
00 May - First Internet Draft publication of
     IOTP Version 2.0 Specification
00 May - To Last Call
     IOTP Version 2.0 Requirements
00 Jul - To Last Call
     ECML v2 Specification
(00 Jul/Aug, IETF Meeting Pittsburgh)
00 Aug - Last Call
     XML Messaging Specification
00 Sep - Last Call
     IOTP Vesion 2 Specification
-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]

To: [email-masked]
Subject: Re: Draft new TRADE WG Charter 
Date: Wed, 08 Dec 1999 00:33:26 -0500
From: "Donald E. Eastlake 3rd" <[email-masked]>
Sender: [email-masked]
Source-Info:  From (or Sender) name not authenticated.

I'll add something like that...

Donald

From:  Ko Fujimura <[email-masked]>
Date:  Thu, 25 Nov 1999 21:56:26 +0900
Message-ID:  <[email-masked]>
To:  [email-masked]
Cc:  [email-masked], [email-masked]
In-Reply-To:  In your message of "Wed, 24 Nov 1999 17:23:55 -0800"
	     	<123B7EB05559D311B0D900A0C9EA3D7604F574@NEPTUNE>
References:  <123B7EB05559D311B0D900A0C9EA3D7604F574@NEPTUNE>
User-Agent:  Wanderlust/2.1.5 (Unbelievable) SEMI/1.13.4 (Terai) Chao/1.13.0 (JR Fuji
nomori) MULE XEmacs/21.2 (beta1) (Aeolus) (sparc-sun-solaris2.6)

>Hi Don and David,
>
>My comment is to add the following paragraph at the end of the
>draft: 
>
>Digital Rights Requirements
>===========================
>In the purchase or other trading transactions, it is often required to
>credit loyalty points, collect digital coupons, check membership of a
>certain group, and so on. The working group invenstigates how these
>activities can be generalized using the concept of "digital-right",
>which is a digital representation of right to claim goods or services,
>and describles the requirements on the following areas: 
>  - The digital rights trading model
>  - The language to describe diverse type of digital rights
>
>Thanks,
>
>Ko
>-----------------------------------------------------------------------
-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]

Date: Wed, 08 Dec 1999 00:36:09 -0500
From: "Donald E. Eastlake 3rd" <[email-masked]>
To: [email-masked]
Subject: Revised New Draft WG Charter
Sender: [email-masked]
Source-Info:  From (or Sender) name not authenticated.

Below is a revised draft of a new charter for the working group
based on comments posted...

Thanks,
Donald

Chair(s):
Donald Eastlake 3rd <[email-masked]>

Applications Area Advisor:
Patrik Faltstrom <[email-masked]>

Editor(s):
David Burdett <[email-masked]>

Mailing Lists:
General Discussion:[email-masked]
To Subscribe: [email-masked]
In Body: (un)subscribe
Archive: http://www.eListX.com/archives/ietf-trade

The TRADE Working Group will further develop the Internet Open Trading
Protocol (IOTP) and the Electronic Commerce Modeling Language (EMCL)
specifications and investigate digital rights trading equirements.

There will be four main threads to the activity:
1. IOTP version 2.0
2. XML Messaging
3. ECML, and
4. Digital Rights Trading Requirements.

Each of these is discussed in more detail below.

IOTP is an interoperable framework for Internet commerce. It is
optimized for the case where the buyer and the merchant do not have
a prior acquaintance and is payment system independent. It can
encapsulates and supports payment systems such as SET, Mondex,
secure channel card payment, GeldKarte, etc. IOTP is able to
handle cases where such merchant roles as the shopping site,
the payment handler, the deliverer of goods or services, and
the provider of customer support are performed by different
Internet sites.

The  working group will document interoperability experience with
IOTP version 1 and develop the requirements for IOTP transport and
IOTP version 2.

Selection of items for inclusion in version requirements 2 is to
be from the following:
- Separation of a content independent Messaging Layer
- Dynamic Definition of Trading Sequences
- Offer Request Block
- Improved Problem Resolution (extend to cover presentation of
signed receipt to customer support party, etc.)
- Server to Server messages

Legal or regulatory issues surrounding the implementation of the
protocol or information systems using it are out of scope for IOTP
v2.

XML Messaging is based on the messaging ideas contained inside IOTP
version 1.0, and will aim to develop a specification for the the
reliable, resilient, secure, exchange of XML over insecure
transport mechanisms.

The goal of the working group is to develop first a set of
requirements and then the full specification that meets these XML
Messaging objectives.

ECML version 1 provides a standard set of hierarchical field names
and content specifications plus a few procedural guidelines for
the transmission of basic address and payment information from a
customer to a merchant.

The goal of the working group is to develop ECML version 2 which
may include corrections to version 1 and may include additions in
the following areas:
- Merchant to Consumer communications fields including purchase
amount, receipt information, package tracking information,
- Additional Consumer to Merchant fields including Corporate
procurement cards, Other payment systems, Travel and entertainment,
Affinity, frequent flyer, and other customer loyalty programs,
Business-to-business commerce
- Improved internationalization
- Coordination with privacy standards
- Specifications for exchange of ECML data using XML

In real world purchases and other trading transactions, it is often
a requirement to credit loyalty points, collect digital coupons,
check customer membership in a certain group, and so on.  The
working group will investiagate hjow these activities can be
generalized using the concept of a "digital-right", which is a
digital representation of the right to claim goods or services,
and will specify the requirements in the following areas:
- The digital rights trading model
- The language to describe diverse types of digital rights

Milestones:
99 Dec - First Internet Draft publication of
     Secure Channel Credit Debit Supplement
     Architecture and Payment API Supplement
00 Jan - First Internet Draft publication of
     Requirements for XML Messaging Layer
     Requirements for Digital Rights Trading
     SET Supplement
00 Feb - Initiate Last Call on
     SCCD, Architecture, SET, and HTTP Supplements
00 Feb - First Internet Draft publication of
     ECML v2 Requirements
(00 Mar, IETF Meeting Adelaide)
00 Apr - To IESG for Publication
     SCCD, Architecture, SET, and HTTP Supplements
     ECML v2 Requirements
00 Apr - First Internet Draft publication of
     IOTP Version 2.0 Requirements
     ECML v2 Specification
     XML Messaging Specification
00 Apr - To Last Call
     Requirements for XML Messaging
     Requirements for Digital Rights Trading
00 May - First Internet Draft publication of
     IOTP Version 2.0 Specification
00 May - To Last Call
     IOTP Version 2.0 Requirements
00 Jul - To Last Call
     ECML v2 Specification
(00 Jul/Aug, IETF Meeting Pittsburgh)
00 Aug - Last Call
     XML Messaging Specification
00 Sep - Last Call
     IOTP Vesion 2 Specification
-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]

To: [email-masked]
Subject: Re: Draft new TRADE WG Charter 
Date: Wed, 08 Dec 1999 00:28:40 -0500
From: "Donald E. Eastlake 3rd" <[email-masked]>
Sender: [email-masked]
Source-Info:  From (or Sender) name not authenticated.

From:  David Burdett <[email-masked]>
Message-ID:  <123B7EB05559D311B0D900A0C9EA3D7604F574@NEPTUNE>
To:  "[email-masked]'" <[email-masked]>, [email-masked]
Date:  Wed, 24 Nov 1999 17:23:55 -0800

>Folks
>
>Apologies for the delay in responding to this but I've at last had the time
>to get to it. Anyway comments are included below marked with a ##.
>
>David
>
>-----Original Message-----
>From: [email-masked] [mailto:[email-masked]]
>Sent: Tuesday, November 16, 1999 11:43 AM
>To: [email-masked]
>Subject: Draft new TRADE WG Charter
>
>
>Our current charter is way out of date.  Appended below for discussion is
>the new TRADE WG Charter which reflects the consensus of those in
>attendance at the Wasington, DC, IETF Meeting...
>
>Thanks,
>Donald
>
>Donald E. Eastlake, 3rd
>17 Skyline Drive, Hawthorne, NY 10532 USA
>[email-masked]   tel: 1-914-784-7913, fax: 1-914-784-3833
>
>home: 65 Shindegan Hill Road, RR#1, Carmel, NY 10512 USA
>[email-masked]   tel: 1-914-276-2668
>
>
>
>Chair(s):
>Donald Eastlake 3rd <[email-masked]>
>
>Applications Area Advisor:
>Patrik Faltstrom <[email-masked]>
>
>Editor(s):
>David Burdett <[email-masked]>
>
>Mailing Lists:
>General Discussion:[email-masked]
>To Subscribe: [email-masked]
>In Body: (un)subscribe
>Archive: http://www.eListX.com/archives/ietf-trade
>
>The TRADE Working Group will further develop the Internet Open Trading
>Protocol (IOTP) and the Electronic Commerce Modeling Language (EMCL)
>specifications and investigate digital rights trading equirements.
>
>##There will be four main threads to the activity:
>1. IOTP version 2.0
>2. XML Messaging
>3. ECML, and
>4. Digital Rights Trading Requirements.

I'll try incorporating some of this, but IETF WG charters are usually
short and sweet without much internal subheadings in the main body...

>Each of these is discussed in more detail below.
>
>IOTP Version 2.0
>================
>##
>IOTP is an interoperable framework for Internet commerce. It is
>optimized for the case where the buyer and the merchant do not have
>a prior acquaintance and is payment system independent. It can
>encapsulates and supports payment systems such as SET, Mondex,
>secure channel card payment, GeldKarte, etc. IOTP is able to
>handle cases where such merchant roles as the shopping site,
>the payment handler, the deliverer of goods or services, and
>the provider of customer support are performed by different
>Internet sites.
>
>The  working group will document interoperability experience with
>IOTP version 1 and develop the requirements for IOTP transport and
>IOTP version 2.
>
>Selection of items for inclusion in version requirements 2 is to
>be from the following ## to be varied based on implementation experience##:

I'm not sure how much effect "implementation" experience could have on
the desireability of some of these.  At least it does not seem reasonable
that implementation would be the sole input for deciding...

>- Separation of a content independent Messaging Layer
>- Dynamic Definition of Trading Sequences
>- Offer Request Block
>- Improved Problem Resolution (extend to cover presentation of
>signed receipt to customer support party, etc.)
>- Server to Server messages
>
>Legal or regulatory issues surrounding the implementation of the
>protocol or information systems using it are out of scope for IOTP
>v2.
>
>##XML Messaging
>=============
>XML Messaging is based on the messaging ideas contained inside IOTP version 
>1.0, and will aim to develop a specification for the the reliable, 
>resilient, secure, tamper resistant, authenticated exchange of XML or other 
>electronic documents over insecure transport mechanisms.

Once you have said "secure", I think "tamper resistant" and "authenticated"
are redundant.

>The goal of the working group is to develop first a set of requirements and 
>then the full specification that meets the above objectives.
>
>ECML
>====
>##
>ECML version 1 provides a standard set of hierarchical field names
>and content specifications plus a few procedural guidelines for
>the transmission of basic address and payment information from a
>customer to a merchant.
>
>The goal of the working group is to develop ECML version 2 which
>may include corrections to version 1 and may include additions in
>the following areas:
>- Merchant to Consumer communications fields including purchase
>amount, receipt information, package tracking information,
>- Additional Consumer to Merchant fields including Corporate
>procurement cards, Other payment systems, Travel and entertainment,
>Affinity, frequent flyer, and other customer loyalty programs,
>Business-to-business commerce
>- Improved internationalization
>- Coordination with privacy standards
>- Specifications for exchange of ECML data using XML
>
>Milestones:
>99 Dec - First Internet Draft publication of
>     Secure Channel Credit Debit Supplement
>     Architecture and Payment API Supplement
>00 Jan - First Internet Draft publication of
>     Requirements for XML Messaging Layer
>     Requirements for Digital Rights Trading
>     SET Supplement
>00 Feb - Initiate Last Call on
>     SCCD, Architecture, SET, and HTTP Supplements
>00 Feb - First Internet Draft publication of
>     ECML v2 Requirements
>(00 Mar, IETF Meeting Adelaide)
>00 Apr - To IESG for Publication
>     SCCD, Architecture, SET, and HTTP Supplements
>     ECML v2 Requirements
>00 Apr - First Internet Draft publication of
>     IOTP Version 2.0 Requirements
>     ECML v2 Specification
>     XML Messaging Specification
>00 Apr - To Last Call
>     Requirements for XML Messaging
>     Requirements for Digital Rights Trading
>00 May - First Internet Draft publication of
>     IOTP Version 2.0 Specification
>00 May - To Last Call
>     IOTP Version 2.0 Requirements
>00 Jul - To Last Call
>     ECML v2 Specification
>(00 Jul/Aug, IETF Meeting Pittsburgh)
>00 Aug - Last Call
>     XML Messaging Specification
>00 Sep - Last Call
>     IOTP Vesion 2 Specification

Thanks,
Donald
-----------------------------------------------------------------------
Message addressed to: [email-masked]
Archive available at: http://www.elistx.com/archives/ietf-trade/
To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
body to: [email-masked]