1 / 15

IETF Trade WG Meeting Summary - August 2001

The IETF Trade Working Group convened on August 10, 2001, in London to discuss the current status of various documents related to the Internet Open Trading Protocol (IOTP) and the Electronic Commerce Modeling Language (ECML). Key agenda items included implementation experiences, specification requirements, and future action plans. Several draft documents were reviewed, including updates on IOTP Version 2, Generic Voucher Language, and security improvements. The meeting concluded with scheduling future meetings and tasks for authors/editors of upcoming specifications.

jada
Télécharger la présentation

IETF Trade WG Meeting Summary - August 2001

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF TRADE WG 10 August 2001 London Donald.Eastlake@motorola.com <ietf-trade-request@lists.elistx.com> <http://lists.elistx.com/archives/ietf-trade>

  2. Agenda • 09:00 Agenda Bashing • 09:10 Documents Status • 09:25 IOTP/ECML/Voucher Implementation Experience • 09:40 ECML V2 Specification • 09:55 XML Voucher: Generic Voucher Language & API • 10:30 SCCD using ECML • 10:40 IOTP V2 Requirements • 10:50 Schedule Future Actions/Meetings • 11:00 End

  3. Document Status • RFCs out • 2801: Internet Open Trading Protocol - IOTP Version 1.0 • 2802: Digital Signatures for the 1.0 Internet Open Trading Protocol (IOTP) • 2803: Digest Values for DOM (DOMHASH) • 2935: Internet Open Trading Protocol (IOTP) HTTP Supplement • 2936: HTTP MIME Type Handler Detection

  4. Document Status (cont.) • Documents With Area Director / IESG • SET Supplement for the v1.0 Internet Open Trading Protocol (IOTP) • draft-ietf-trade-iotp-v1.0-set-02.txt • Payment API for v1.0 Internet Open Trading Protocol • draft-ietf-trade-iotp-v1.0-papi-05.txt • Requirements for Generic Voucher Trading • draft-ietf-trade-drt-requirements-02.txt • Electronic Commerce Modeling Language (ECML): Version 2 Requirements • draft-ietf-trade-ecml2-req-04.txt

  5. Document Status (cont.) • Documents in Working Group • Internet Open Trading Protocol (IOTP) Version 1 Errata • draft-ietf-trade-iotp-v1-errata-00.txt • Internet Open Trading Protocol Version 2 Requirements • draft-ietf-trade-iotp2-req-00.txt • Electronic Commerce Modeling Language (ECML): Version 2 Specification • draft-ietf-trade-ecml2-spec-01.txt • XML Voucher: Generic Voucher Language • draft-ietf-trade-voucher-lang-01.txt • Voucher Trading System Application Programming Interface (VTS-API) • draft-ietf-trade-voucher-vtsapi-00.txt

  6. IOTP/ECML/Voucher Implementation Experience • InterPay • Hitachi

  7. ECML V2 Specification • draft-ietf-trade-ecml2-spec-01.txt - Jon Parsons • An XML schema (with mapping to HTML forms) • ISO 8583 fields being added • Java Commerce Messages fields suggested by Dave Shepherd • How to indicate query versus data and optionality?

  8. XML Voucher:Generic Voucher Language & API • Ko Fujimura, NTT. • draft-ietf-trade-drt-requirements-02.txt - Done. • draft-ietf-trade-voucher-lang-01.txt - in WG. • draft-ietf-trade-voucher-vtsapi-00.txt - in WG.

  9. SCCD using ECML • Secure Channel Credit Debit • Intended to be security equivalent to purchase via filling out a web form • Should be simple…

  10. IOTP V2 Requirements • List three categories of requirements • will be included • may be included • will not be included

  11. IOTP V2 Req. (cont.) • According to current draft, will include: • Be a superset of IOTP Version 1. • Dynamic Definition of Trading Sequences. • Offer Request Block. • Improved Problem Resolution (extend to cover presentation of signed receipt to customer support party, etc.) • Handle payment protocols not tunneled through IOTP

  12. IOTP V2 Req. (cont.) • According to current draft, may inclue: • Support for wallet servers. • Support repeated/ongoing payments. • Enhanced Server to Server messages. • Include the ability to add both fields and attributes to trading blocks

  13. IOTP V2 Req. (cont.) • According to current draft, will not include: • Legal or regulatory issues surrounding the implementation of the protocol or information systems using it. • Design of an XML Messaging Layer. • Design of XML Digitial Signatures.

  14. Schedule Future Actions/Meetings • Needed: • Author/Editors for • IOTP v2 Specification • SCCD using ECML Specification • Next IETF Meeting: • Salt Lake City, Utah, 10-14 December 2001 • see info as it appears on the IETF web pagehttp://www.ietf.org

  15. END

More Related