Skip to main content

Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP)
draft-ietf-trade-iotp-v1.0-set-02

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3538.
Author Yoshiaki Kawatsura
Last updated 2015-10-14 (Latest revision 2000-11-27)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3538 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Patrik Fältström
Send notices to (None)
draft-ietf-trade-iotp-v1.0-set-02
A new Request for Comments is now available in online RFC libraries.

        RFC 3538

        Title:      Secure Electronic Transaction (SET) Supplement for
                    the v1.0 Internet Open Trading Protocol (IOTP)
        Author(s):  Y. Kawatsura
        Status:     Informational
        Date:       June 2003
        Mailbox:    kawatura@bisd.hitachi.co.jp
        Pages:      56
        Characters: 103475
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-trade-iotp-v1.0-set-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3538.txt

This document describes detailed Input/Output parameters for the
Internet Open Trading Protocol (IOTP) Payment Application Programming
Interface (API).  It also describes procedures in the Payment Bridge
for the use of SET (SET Secure Electronic Transaction) as the payment
protocol within Version 1.0 of the IOTP.

This document is a product of the Internet Open Trading Protocol
Working Group.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.