Current Meeting Report
Jabber Logs

2.1.8 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
NOTE: This charter is a snapshot of the 55th IETF Meeting in Altanta, Georgia USA. It may now be out-of-date.

Last Modifield: 07/29/2002

Donald Eastlake 3rd <>
Applications Area Director(s):
Ned Freed <>
Patrik Faltstrom <>
Applications Area Advisor:
Patrik Faltstrom <>
Mailing Lists:
General Discussion:
To Subscribe:
In Body: (un)subscribe
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:
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
MAY 02  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-drt-requirements-04.txt
  • - draft-ietf-trade-iotp-v1.0-papi-05.txt
  • - draft-ietf-trade-iotp-v1.0-set-02.txt
  • - draft-ietf-trade-ecml2-req-05.txt
  • - draft-ietf-trade-voucher-lang-03.txt
  • - draft-ietf-trade-ecml2-spec-04.txt
  • - draft-ietf-trade-iotp-v1-errata-01.txt
  • - draft-ietf-trade-voucher-vtsapi-02.txt
  • Request For Comments:
    RFC2803 I Digest Values for DOM (DOMHASH)
    RFC2802 I Digital Signatures for the 1.0 Internet Open Trading Protocol (IOTP)
    RFC2801 I Internet Open Trading Protocol - IOTP Version 1.0
    RFC2935 PS Internet Open Trading Protocol (IOTP) HTTP Supplement
    RFC2936 I HTTP MIME Type Handler Detection
    RFC3354 I Internet Open Trading Protocol Version 2 Requirements

    Current Meeting Report

    IETF TRADE Draft Minutes
    18 November 2002, Atlanta, Georgia
    Donald E. Eastlake 3rd, Chair
    -Agenda Bashing
    No change from agenda distributed in advance.
    -Document Status
    The status of the RFCs produced, 5 IESG approved drafts, and 4 draft 
    currently in the working group was reviewed. The IESG approved drafts were 
    all approved quite recently.
    -ECML V2 Specification
    ECML v1 and v1.1 were produced before the working group took change 
    control for ECML and have been published as Informational RFCs. The ECML V2 
    requirements have been approved by the IESG and will be published as an 
    Informational RFC. The V2 specification is almost ready for working group 
    last call. The minor changes made in the last three draft versions (-03, 
    -04, and -05) were reviewed. One field that should have been added 
    (Ecom_Loyalty_Card_Type) and will be added to produce a -06 draft that will 
    be working group last called.
    -IOTP Use of DNS SRV RR
    The motivation for 
    draft-ietf-trade-srv-higher-services-00.txt was described. It permits 
    declaration within the DNS of where to go for higher level services the way 
    that SRV (RFC 2782) and MX do for lower level services. While it 
    reserves the token "IOTP" for the use of IOTP, an additional small IOTP 
    document is required to specify how to use and extend this token for the 
    iotp-merchant, iotp-payment, iotp-delivery, and iotp-care roles.
    -XML Voucher Update
    The voucher requirements document has been approved by the IESG for 
    publication as an Informational RFC. The Voucher Language and Voucher 
    Transfer System API documents, by Ko Fujimura, who was unable to make it to 
    this IETF meeting, are being refined by the Working Group. There is some 
    indication of adoption of voucher in the Infrared Data Association. NTT has 
    developed a C version of the API but the working group members present did 
    not seem to think it was important for it to be published.
    -SCCD and IOTP V2
    Two work items are overdue. They are Secure Channel Credit Debit and IOTP 
    version 2. We do not have a draft for either and need authors. Anyone 
    willing to work on this should contact the WG chair. SCCD, if done based on 
    ECML, should be a medium-small size task. IOTP V2 is a large task but 
    could be broken up into pieces. If no one is willing to do the 
    documents, they won't happen.
    It is expected that the next WG meeting will be at the IETF meeting in San 
    Francisco, March 2003.