1 / 15

IETF TRADE Working Group

IETF TRADE Working Group. 17 July 2003, Vienna, Austria Chair: Donald E.Eastlake 3rd <Donald.Eastlake@Motorola.com> <ietf-trade-request@lists.elistx.com> <http://lists.elistx.com/archives/ietf-trade>. TRADE WG Agenda. 13:00 Agenda Bashing 13:10 WG Efforts and Documents Status

bran
Download Presentation

IETF TRADE Working Group

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 Working Group 17 July 2003, Vienna, Austria Chair: Donald E.Eastlake 3rd <Donald.Eastlake@Motorola.com> <ietf-trade-request@lists.elistx.com> <http://lists.elistx.com/archives/ietf-trade>

  2. TRADE WG Agenda • 13:00 Agenda Bashing • 13:10 WG Efforts and Documents Status • IOTP Update • ECML Update • Voucher Update • 13:30 IOTP use of DNS SRV RR • IOTP Tokens • draft-ietf-trade-srv-higher-services-00.txt • 13:40 SCCD and IOTP v2, the search for authors • 13:50 Open microphone • 14:05 Future Actions/Meetings

  3. TRADE WG Efforts • IOTP – Internet Open Trading Protocol • An XML syntax for shopping that • Assumes no prior relationship between the customer and the merchant • Is payment systems independent. (Payment messages are tunneled through IOTP.) • Allows the merchant functions of shopping, payment acceptance, fulfillment, and customer care to be distributed to different host computers if desired.

  4. TRADE WG Efforts • IOTP (cont.) • Some IOTP message formats used by InterPay and Royal Bank of Canada. Also used by Hitachi in the Japanese SMILE project. • Status: Informational Version 1 Done.Need token document for SRV RR use. Need Author/Editor/Energy for SCCD. Need Author/Editor/Energy for Version 2.

  5. TRADE WG Efforts • ECML – Electronic Commerce Modeling Language • A standard naming and hierarchical structure for identity, shipping, and payment information between customers and merchants. • Version 1 was oriented to HTML Forms completion by wallet software. The field names defined are recognized by mainstream browsers. • Version 2 is generalized and XML oriented. • Status: Version 2 Proposed Standard Specification submitted.

  6. TRADE WG Efforts • XML Voucher • An XML syntax to describe a logical entity that represents a right to claim goods or services. • A voucher can be used to transfer a wide-range of electronic-values, including coupons, tickets, loyalty points, and gift certificates, which are often necessary to process in the course of payment and/or delivery transactions.

  7. TRADE WG Efforts • XML Voucher (cont.) • Progress is occurring towards deployment. A standard for using XML Voucher with infrared is being developed in the Infrared Data Association (IrDA). Members of that association should see the working draft of “Infrared Financial Messaging: Voucher Profile” • Status: Proposed Standard Specification and Informational API submitted.

  8. Document Status, RFCs • IOTP • 2801-IN: Internet Open Trading Protocol - IOTP Version 1.0 • 2802-IN: Digital Signatures for the 1.0 IOTP • 2803-IN: Digest Values for DOM (DOMHASH) • 2935-PS: IOTP HTTP Supplement • 2936-IN: HTTP MIME Type Handler Detection • 3354-IN: IOTP Version 2 Requirements • 3504-IN: IOTP Version 1, Errata • 3538-IN: Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol • ECML • 3505-IN: ECML Version 2 Requirements • Voucher • 3506-IN: Requirements and Design for Voucher Trading System

  9. Document Status, in IESG • IOTP • Payment API for v1.0 Internet Open Trading Protocoldraft-ietf-trade-iotp-v1.0-papi-05.txt - IN • ECML • ECML Version 2 Specificationdraft-ietf-trade-ecml2-spec-08.txt - PS • XML Voucher • XML Voucher: Generic Voucher Languagedraft-ietf-trade-voucher-lang-05.txt - PS • VTS Applications Program Interfacedraft-ietf-trade-voucher-vtsapi-05.txt - IN

  10. Document Status, in WG • Active Documents in the Working Group • IOTP • DNS SRV Location of Higher Level Servicesdraft-ietf-trade-srv-higher-services-00.txt

  11. IOTP use of DNS SRV RR • The service, or SRV, DNS resource record provides a facility for indicating where to find a particular service for a particular domain name. It is like MX for finding mail servers except: • It can map to different ports. • It can give different weights to different servers. • It uses a constructed name based on the service such as _ldap._tcp.example.com • See RFC 2782.

  12. IOTP use of DNS SRV RR • To extend this for higher level services such as IOTP and the XML Key Management Service (XKMS) draft-ietf-trade-srv-higher-services-00.txt extends the syntax to allow a third level such as _iotp._http._tcp.example.net. • To provide separate search for IOTP services, we need to define tokens such as _iotp-merchant, _iotp-payment, _iotp-delivery, and _iotp-care. For example _iotp-payment._http._tcp.merch.example

  13. SCCD and IOTP v2 • SCCD – Secure Channel Credit Debit • Simple payment system to be tunneled through IOTP. • Equivalent to filling in a credit card form. • Probably uses ECML syntax. • NEED AUTHOR/EDITOR. • IOTP v2 – Internet Open Trading Protocol • New version for Proposed Standard corresponding to the IOTP v2 Requirements RFC. • Can be one document or multiple documents. • NEED AUTHOR/EDITOR.

  14. Future Actions/Meetings • Needed: • Author/Editors for • SCCD Specification • IOTP v2 Specification • Next IETF Meeting: • Minneapolis, Minnesota, November 9-14, 2003 • see info about meeting as it appears on the IETF web page http://www.ietf.org

  15. END

More Related