RFC 3867 on Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP)

rfc-editor@rfc-editor.org Sat, 06 November 2004 00:30 UTC

Date: Fri, 05 Nov 2004 16:27:10 -0800
From: rfc-editor@rfc-editor.org
Subject: RFC 3867 on Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP)
Sender: rfc-ed@ISI.EDU
To: ietf-announce@ietf.org
Cc: rfc-editor@rfc-editor.org, ietf-trade@lists.elistx.com
Message-id: <200411060027.iA60RAi07619@boreas.isi.edu>
MIME-version: 1.0
Content-type: Multipart/Mixed; Boundary="NextPart"

A new Request for Comments is now available in online RFC libraries.


        RFC 3867

        Title:      Payment Application Programmers Interface (API)
                    for v1.0 Internet Open Trading Protocol (IOTP)
        Author(s):  Y. Kawatsura, M. Hiroya, H. Beykirch
        Status:     Informational
        Date:       November 2004
        Mailbox:    ykawatsu@itg.hitachi.co.jp, hiroya@st.rim.or.jp,
                    hbbeykirch@web.de
        Pages:      106
        Characters: 234572
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-trade-iotp-v1.0-papi-06.txt

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


The Internet Open Trading Protocol (IOTP) provides a data exchange
format for trading purposes while integrating existing pure payment 
protocols seamlessly.  This motivates the multiple layered system
architecture which consists of at least some generic IOTP application
core and multiple specific payment modules.

This document addresses a common interface between the IOTP
application core and the payment modules, enabling the
interoperability between these kinds of modules.  Furthermore, such an
interface provides the foundations for a plug-in-mechanism in actual
implementations of IOTP application cores.

Such interfaces exist at the Consumers', the Merchants' and the
Payment Handlers' installations connecting the IOTP application core
and the payment software components/legacy systems.

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

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.

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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3867.txt"><ftp://ftp.isi.edu/in-notes/rfc3867.txt>

RFC 3867 on Payment Application Programmers Inter… rfc-editor