2.1.6 Internet Open Trading Protocol (trade)

NOTE: This charter is a snapshot of the 42nd IETF Meeting in Chicago, Illinois. It may now be out-of-date. Last Modified: 23-Jul-98


Don Eastlake <dee3@torque.pothole.com>

Applications Area Director(s):

Keith Moore <moore@cs.utk.edu>
Patrik Faltstrom <paf@swip.net>

Applications Area Advisor:

Patrik Faltstrom <paf@swip.net>


Surendra Reddy <skreddy@us.oracle.com>

Mailing Lists:

General Discussion:ietf-trade@lists.eListX.com
To Subscribe: ietf-trade-request@lists.eListX.com
In Body: (un)subscribe
Archive: http://www.eListX.com/archives/ietf-trade

Description of Working Group:

The Internet Open Trading Protocol provides 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 will be able to encapsulate and support payment systems such as SET, Mondex, CyberCash's CyberCoin, DigiCash's e-cash, 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 Internet Open Trading Protocol (IOTP) working group will (1) determine requirements and document scenarios for IOTP message transport and for IOTP version 2 specification, (2) document interoperability experience with IOTP version 1 (which will have been published as Informational), and (3) develop the specification for IOTP transport and IOTP version 2.

Selection of items for inclusion in version 2 is expected to be from the following and others suggested by the Working Group:

- Dynamic Definition of Trading Sequences - Multiple Protocol Options - Offer Request Block - Public Key Signatures (v1.0 uses secret key signatures) - Signatures on the Delivery Response - Improved Problem Resolution (extend to cover presentation of signed receipt to customer support party, etc.) - Selection of Additional Options - OTP Architecture (informational development of standard interfaces to software components).

The following are out of scope for version 2:

- server to server messages (except as messages needed for client to server communications may also be useful for server to server communications) - legal or regulatory issues surrounding the implementation of the protocol or information systems using it.

Goals and Milestones:

Jul 98


Submit IOTP v1.0 to the IESG to consider publication as an Informational RFC.

Oct 98


Submit Internet-Draft of Open Trading Protocol requirements and scenarios

Oct 98


Submit IOTP transport requirements Internet Draft

Dec 98


Submit Internet-Draft on IOTP v1.0 interoperability experience

Jan 99


Submit Internet-Draft on IOTP transport requirements to IESG for publication as an Informational RFC.

Jan 99


Submit Internet-Draft on IOTP v1.0 interoperability experience to IESG for publication as an Informational RFC.

Feb 99


Submit Internet-Draft of IOTP v2.0 specification

Feb 99


Submit Internet-Draft of IOTP transport specification

May 99


Submit IOTP transport specification I-D to IESG for consideration as a Proposed Standard.

Jun 99


Submit IOTP v2.0 specification I-D to IESG for consideration as a Proposed Standard.

No Current Internet-Drafts
No Request For Comments

Current Meeting Report

Minutes of the 1st IETF Trade Working Group Meeting:
Wednesday August 26th, 1998
9 am-11:30 AM

1. Donald Eastlake started the 1st IETF Trade Working Group meeting with the
following agenda:

Unfortunately a number of documents were not ready in time and so could not be
substantively discussed.

2. Group members raised many questions regarding the trade charter. Donald advised
them to discuss that on the list.

3. IOTP 1.0 will be published as informational RFC.

4. Group felt that we need to come up with requirements for 2.0 work which will be
carried out under IETF Working Group. Donald pointed Business Functional
requirements of the IOTP 1.0 spec would be a good candidates for starting of
discussions on IOTP 2.0 requirements.

5. Donald requested the group members to send their suggestions/comments on
transitioning IOTP specification development from OTP Consortium to IETF.

6. Implementation Status of IOTP Spec 0.9: RBC(Royal Bank of Canada) has
implemented OTP product based on otp .9 spec. Waiting for Chris Smith's report
on the completeness of the .9 spec and hence released 99.

7. Donald explained the difference between OBI (Open Buying on the Internet) and
IOTP as:

8. Patrik Faltstrom (Area Director) explained to the group that all IETF Trade WG
intermediate meetings between IETF meetings MUST be announced on the IETF
Announce list and minutes SHOULD be published to WG mailing list.

9. On the issue of getting access to the OTP Consortium web site private area and
mailing lists, Donald and Steve Fabes explained that all mailing lists from OTP can
be moved to IETF Trade WG archive and Steve Fabes also mentioned that all IETF
Trade WG members will be given access to the current OTP private area. All IETF
Trade discussions are archived at: http://www.elistx/com/archives/ietf-trade

10. Steve Fabes read out the list of OTP consortium members.

11. Different members expressed the immediate need for strawman documents on
Requirements and current IOTP specification. Donald assured to the group that
these documents would be published at the earlist as I-Ds.

12. Next interim IETF Trade WG meeting will be held at Cybercash in Reston, Virginia,
on September 9th through 11th and Donald mentioned that all the minutes of these
meeting would be published Trade discussion list.

As there is no further issues to be discussed, meeting adjourned.


None received.

Attendees List

go to list