Concluded WG Internet Open Trading Protocol (trade)
Note: The data for concluded WGs is occasionally incorrect.
WG | Name | Internet Open Trading Protocol | |
---|---|---|---|
Acronym | trade | ||
Area | Applications Area (app) | ||
State | Concluded | ||
Charter | charter-ietf-trade-01 Approved | ||
Document dependencies | |||
Additional resources | Additional Trade Page | ||
Personnel | Chair | Donald E. Eastlake 3rd | |
Mailing list | Address | ietf-trade@lists.eListX.com | |
To subscribe | ietf-trade-request@lists.eListX.com | ||
Archive | http://lists.eListX.com/archives/ietf-trade |
Final Charter for 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.
Milestones
Date | Milestone | Associated documents |
---|---|---|
Jul 2003 | Submit IOTP V2.0 Specification (Proposed Standard) | |
Dec 2002 | Submit I-D on IOTP V2.0 Specification | |
Jul 2002 | Submit Secure Channel Credit/Debit ECML V2.0 Specification (Proposed Standard). | |
Mar 2002 | Submit I-D on Secure Channel Credit/Debit ECML V2.0 Specification |
Done milestones
Date | Milestone | Associated documents |
---|---|---|
Done | Submit Generic Right Trading Specification (Proposed Standard) | |
Done | Submit IOTP V2.0 Requirements (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 Generic Rights Trading Requirements for Informational | |
Done | Submit Architecture and Payment API to IESG forInformational | |
Done | Submit SET Supplement to IESG for publication as Informational |