2.1.10 Internet Open Trading Protocol (trade)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional Trade Page

Last Modified: 2003-08-18

Donald Eastlake 3rd <Donald.Eastlake@motorola.com>
Applications Area Director(s):
Ned Freed <ned.freed@mrochek.com>
Ted Hardie <hardie@qualcomm.com>
Applications Area Advisor:
Ned Freed <ned.freed@mrochek.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

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

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)
Goals and Milestones:
Done  Submit SET Supplement to IESG for publication as Informational
Done  Submit Architecture and Payment API to IESG forInformational
Done  Submit Generic Rights Trading Requirements for Informational
Done  Submit I-D on IOTP V2.0 Requirements
Done  Submit I-D on Generic Right Trading Specification
Done  Submit ECML V2.0 Requirements to IESG (Informational)
Done  Submit IOTP V2.0 Requirements (Informational)
Mar 02  Submit I-D on Secure Channel Credit/Debit ECML V2.0 Specification
Done  Submit Generic Right Trading Specification (Proposed Standard)
Jul 02  Submit Secure Channel Credit/Debit ECML V2.0 Specification (Proposed Standard).
Dec 02  Submit I-D on IOTP V2.0 Specification
Jul 03  Submit IOTP V2.0 Specification (Proposed Standard)
  • - draft-ietf-trade-iotp-v1.0-papi-05.txt
  • - draft-ietf-trade-voucher-lang-05.txt
  • - draft-ietf-trade-ecml2-spec-08.txt
  • - draft-ietf-trade-voucher-vtsapi-05.txt
  • - draft-ietf-trade-srv-higher-services-00.txt
  • Request For Comments:
    Digest Values for DOM (DOMHASH) (RFC 2803) (22552 bytes)
    Digital Signatures for the 1.0 Internet Open Trading Protocol (IOTP) (RFC 2802) (52756 bytes)
    Internet Open Trading Protocol - IOTP Version 1.0 (RFC 2801) (598794 bytes)
    Internet Open Trading Protocol (IOTP) HTTP Supplement (RFC 2935) (16168 bytes)
    HTTP MIME Type Handler Detection (RFC 2936) (25238 bytes)
    Internet Open Trading Protocol Version 2 Requirements (RFC 3354) (9671 bytes)
    Internet Open Trading Protocol (IOTP) Version 1, Errata (RFC 3504) (8655 bytes)
    Electronic Commerce Modeling Language (ECML):Version 2 Requirements (RFC 3505) (13915 bytes)
    Requirements and Design for Voucher Trading System (VTS) (RFC 3506) (30945 bytes)
    Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP) (RFC 3538) (103475 bytes)

    Current Meeting Report

    Minutes, TRADE WG.
    Donald Eastlake 3rd, Chair
    Ted Hardie, Scribe.
    The group met to review ongoing working and describe status.
    No agenda bashing, so this was the final agenda:
    13:00   Agenda Bashing
    13:10   Documents Status
            IOTP Update, RFC 3538
            ECML Update
            Voucher Update
    13:30   IOTP use of DNS SRV RR
                    IOTP Tokens
    13:55   SCCD and IOTP v2, the search for authors RFC 3354
    14:10   Future Actions/Meetings
    draft-ietf-trade-srv-higher-services-00.txt has applicability beyond 
    Trade; needs review beyond this group.  DNSEXT contacted, as have been the 
    authors of the SRV specifications.  Further review may be needed, and Andy 
    Newton pointed draft-daigle-napstr-02.txt for review as a possible 
    alternative approach.
    The Chair asked for authors of sccd and iotpv2, as they may not survive the 
    lack of energy.  None at this meeting.
    The chair indicated that the group may need one more working group 
    meeting, but probably no more than that.
    The group concluded with an open mic session; their being no issues 
    raised, it 


    IETF TRADE Working Group