Current Meeting Report
Slides


2.1.5 Internet Open Trading Protocol (trade)

NOTE: This charter is a snapshot of the 52nd IETF Meeting in Salt Lake City, Utah USA. It may now be out-of-date. Last Modified: 02-Oct-01
Chair(s):
Donald Eastlake 3rd <dee3@torque.pothole.com>
Applications Area Director(s):
Ned Freed <ned.freed@mrochek.com>
Patrik Faltstrom <paf@cisco.com>
Applications Area Advisor:
Patrik Faltstrom <paf@cisco.com>
Mailing Lists:
General Discussion:ietf-trade@lists.eListX.com
To Subscribe: ietf-trade-request@lists.eListX.com
In Body: (un)subscribe
Archive: http://lists.eListX.com/archives/ietf-trade
Description of Working Group:
The Internet Open Trading Protocol 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 encapsulate and support 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 (which has been published as an Informational RFC) and develop the requirements and specifications for IOTP version 2. Version 2 will make use of an independent Messaging Layer and utilize standard XML Digital Signatures. Selection of other items for inclusion in version requirements 2 is to be from the following:

- Dynamic Definition of Trading Sequences

- Offer Request Block

- Improved Problem Resolution (extend to cover presentation of signed receipt to customer support party, etc.)

- Ability to indicate and handle a payment protocol not tunneled through IOTP

- Support for wallet servers

- Repeated/ongoing payments - Server to Server messages

- The ability to add both fields and attributes to trading blocks

- Collaboration with other protocols such as ECML.

The following is out of scope for IOTP version 2:

- legal or regulatory issues surrounding the implementation of the protocol or information systems using it.

- design of an XML Messaging Layer

The working group will specify a Secure Channel Credit Debit syntax that can be used for financial card payments in connection with IOTP.

The working group will specify requirements and specifications for Generic Rights Trading.

The working group will specify requirements for and then a syntax and processing model of ECML (Electronic Commerce Modeling Language) V2.

Goals and Milestones:
Jan 01   Submit SET Supplement to IESG for publication as Informational
Jan 01   Submit Architecture and Payment API to IESG for Informational
Jan 01   Submit Generic Rights Trading Requirements for Informational
Jan 01   Submit I-D on Secure Channel Credit/Debit ECML V2.0 Specification
Feb 01   Submit I-D on IOTP V2.0 Requirements
Feb 01   Submit I-D on Generic Right Trading Specification
Feb 01   Submit ECML V2.0 Requirements to IESG (Informational)
Mar 01   Submit IOTP V2.0 Requirements (Informational)
Mar 01   Submit Secure Channel Credit/Debit ECML V2.0 Specification (Proposed Standard).
Apr 01   Submit I-D on IOTP V2.0 Specification
May 01   Submit Generic Right Trading Specification (Proposed Standard)
Aug 01   Submit IOTP V2.0 Specification (Proposed Standard)
Internet-Drafts:
Request For Comments:
RFCStatusTitle
RFC2803 Digest Values for DOM (DOMHASH)
RFC2801 Internet Open Trading Protocol - IOTP Version 1.0
RFC2802 Digital Signatures for the 1.0 Internet Open Trading Protocol (IOTP)
RFC2935PSInternet Open Trading Protocol (IOTP) HTTP Supplement
RFC2936 HTTP MIME Type Handler Detection

Current Meeting Report

None received.

Slides

Agenda
XML Voucher and VTS-API