1 / 16

IETF Trade WG

IETF Trade WG. Adelaide, South Australia 29 March 2000 Donald E. Eastlake, 3rd Donald.Eastlake@motorola.com. Agenda. Agenda Bashing Status of Documents Implementation News Digital Rights Trading Charter Update Future Meetings. Status of Existing Documents.

orea
Download Presentation

IETF Trade WG

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 Adelaide, South Australia 29 March 2000 Donald E. Eastlake, 3rd Donald.Eastlake@motorola.com

  2. Agenda • Agenda Bashing • Status of Documents • Implementation News • Digital Rights Trading • Charter Update • Future Meetings

  3. Status of Existing Documents • Main IOTP V1.0 internet drafts in RFC editor queue since last November: • draft-ietf-trade-iotp-v1.0-protocol-07 • draft-ietf -trade-iotp-v1.0-dsig-05 • draft-ietf -trade-hiroshi-dom-hash-03 • IOTP HTTP Supplement and MIME Handler Detector internet drafts to be WG Last Called: • draft-ietf-trade-iotp-http-04 • draft-ietf-trade-mime-detector-02 • IOTP SET Supplement and IOTP Architecture and Payment API recently posted as internet drafts thanks to Yoshiaki Kawatsura: • draft-ietf-trade-iotp-v1.0-set-00 • draft-ietf-trade-iotp-v1.0-papi-00

  4. Status of Documents (Cont.) • Secure Channel Credit/Debit (SCCD): • not yet posted • Digital-Rights Trading (new work, see presentation by Ko Fujimura): • draft-ietf-trade-drt-requirements-00 • XML Messaging (new work, see charter discussion): • draft-ietf-trade-xmlmsg-requirements-00 • Future Documents called for by new charter: • IOTP V2.0 requirements • ECML V2.0 requirements • IOTP V2.0 specification • ECML V2.0 specification

  5. APPLICATION/IOTP • HTTP Supplement specifies the APPLICATION/IOTP MIME Type (and APPLICATION/X-IOTP for backward compatibility) • Discussion on the IETF-Types list indicates that optional charset parameter should be added • Extensive discussion on IETF-Types list as to whether it should be APPLICATION/IOTP-XML, no change required

  6. Implementation News • Hitachi, et al, SMILE • Royal Bank of Canada • SIZ • CyberSource • Differential • Xenosys Corporation • PayByCheck.com • Brokat

  7. Digital-Rights Trading • Presentation by Ko Fujimura, NTT

  8. Charter Update • Submitted to Area Director After Last IETF Meeting, not yet approved • reflect completion of IOTP v1.0, adjusted milestones, split IOTP v2.0 into XML Messaging layer and trading specific portions, add ECML 2.0 and Digital Trading requirements • Multiple Venues for XML Messaging • TRADE WG, EDIINT WG, ebXML, BLOCKS BoF, B2BXML BoF • Revise new charter, dropping XML Messaging

  9. Charter Intro • Chair(s): Donald Eastlake 3rd <Donald.Eastlake@motorola.com> • Applications Area Advisor: Patrik Faltstrom <paf@swip.net> • Editor(s): David Burdett <David.Burdett@commerceone.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

  10. TRADE Charter • 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.

  11. TRADE Charter (Cont.) • The working group will document interoperability experience with IOTP version 1 (which has been approved as Informational) and develop the requirements for IOTP transport and IOTP version 2. • Selection of items for inclusion in version requirements 2 is to be from the following: • Separation of a content independent Messaging Layer • Dynamic Definition of Trading Sequences • Offer Request Block • Improved Problem Resolution (extend to cover presentation of signed receipt to customer support party, etc.) • Server to Server messages • The following are out of scope for IOTP version 2: • legal or regulatory issues surrounding the implementation of the protocol or information systems using it.

  12. TRADE Charter (Cont.) • The working group will develop requirements for Digital-Rights Trading. • The working group will develop requirements for and then a specification of ECML (Electronic Commerce Modeling Language) V2.

  13. TRADE Charter (Cont.) • Milestones • 00 Apr. Working Group Last Call • HTTP Supplement • MIME Handler Detector • 00 Apr. Internet Draft publication of Secure Channel Credit/Debit • 00 May Submit to IESG • HTTP Supplement (Proposed Standard) • MIME Handler Detector (Informational) • 00 May Working Group Last Call • SET Supplement • Architecture and Payment API • 00 May Internet Draft publication of ECML V2.0 Requirements • 00 June Internet Draft publication of IOTP V2.0 Requirements

  14. TRADE Charter (Cont.) • Milestones (Continued) • 00 June Submit to IESG • SET Supplement (Informational?) • Architecture and Payment API (Informational) • 00 July Submit to IESG • Secure Channel Credit/Debit (Proposed?) • 00 Aug. Submit to IESG • Digital Rights Trading Requirements (Informational) • ECML V2.0 Requirements (Informational) • 00 Sep Internet Draft publication of • IOTP V2.0 Specification • ECML V2.0 Specification • 00 Sep Submit to IESG • IOTP V2.0 Requirements (Informational)

  15. TRADE Charter (Cont.) • Milestones (Continued) • 00 Dec Submit to IESG • ECML V2.0 Specification (Proposed Standard) • 01 Feb Submit to IESG • IOTP V2.0 Specification (Proposed Standard)

  16. Future Meetings • Next IETF meeting • Pittsburgh, Pennsylvania, USA. • July 31 - August 4

More Related