Internet Open Trading Protocol (trade) -------------------------------------- Charter Last Modified: 2004-03-15 Current Status: Active Working Group Chair(s): Donald Eastlake 3rd Applications Area Director(s): Ted Hardie Scott Hollenbeck Applications Area Advisor: Scott Hollenbeck 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: 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) Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Feb 01 Jan 05 XML Voucher: Generic Voucher Language Feb 01 Oct 04 Electronic Commerce Modeling Language (ECML):Version 2 Specification Jul 01 Feb 04 Voucher Trading System Application Programming Interface (VTS-API) Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC2803 I May 00 Digest Values for DOM (DOMHASH) RFC2802 I May 00 Digital Signatures for the 1.0 Internet Open Trading Protocol (IOTP) RFC2801 I May 00 Internet Open Trading Protocol - IOTP Version 1.0 RFC2935 PS Sep 00 Internet Open Trading Protocol (IOTP) HTTP Supplement RFC2936 I Sep 00 HTTP MIME Type Handler Detection RFC3354 I Aug 02 Internet Open Trading Protocol Version 2 Requirements RFC3504 I Mar 03 Internet Open Trading Protocol (IOTP) Version 1, Errata RFC3505 I Mar 03 Electronic Commerce Modeling Language (ECML):Version 2 Requirements RFC3506 I Mar 03 Requirements and Design for Voucher Trading System (VTS) RFC3538 I Jun 03 Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP) RFC3867 I Nov 04 Payment API for v1.0 Internet Open Trading Protocol (IOTP)