NOTE: This charter is a snapshot of the 47th IETF Meeting in Adelaide, Australia. It may now be out-of-date. Last Modified: 03-Feb-00
Chair(s):
Donald Eastlake 3rd <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>
Editor(s):
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. |
Internet-Drafts:
· Internet Open Trading Protocol - IOTP Version 1.0
· Internet Open Trading Protocol (IOTP) HTTP Supplement
· Digest Values for DOM (DOMHASH)
· Digital Signatures for the Internet Open Trading Protocol
· HTTP MIME Type Handler Detection
· Requirements for XML Messaging Version 1.0 Release 00
· Requirements for Digital-Right Trading
· Architecture and Payment API for Internet Open Trading Protocol (IOTP)
· SET Supplement for the v1.0 Internet Open Trading Protocol (IOTP)
No Request For Comments
None received.
None received.